On 2015-02-03 16:34, Rafal Pietrak wrote: > > W dniu 03.02.2015 o 15:17, David Kalnischkies pisze: >> Control: tag -1 - newcomer >> >> Hi Rafal, >> >> [...] > > It might, but I don't think so. > > 1. in my case there was no such thing a long trail of lines with "dbus" > word in them. >
Sadly, dbus was not the only trigger issue remaining. We have had to remove the "trigger cycle" check in dpkg for Jessie because we keep seeing this issue. > 2. I do _vaguely_ remember last line above the shell prompt (after > upgrade stopped) saying: "too many errors" (after quite long running > upgrade). > I suspect that line is from dpkg. There are example of: """ dpkg: too many errors, stopping """ Maybe you were looking for "dpkg <...> --abort-after=999999"? At least that is what a quick googling suggests. > 3. to my surprise, "apt-get -f install; apt-get dist-upgrade" did help > ... to some extend: the upgrade finished without next stop, but the > system is "not actually usable" (I've filed two more bugreports > regarding that). > Trigger issues (among other?) tends be "solved" by simply re-trying, so the above certainly does not rule out a trigger issue (but it does not confirm it either). > [...] > > 5. I'm filing this bugreport, because this time there was no > "reboot-in-the middle", so I'd expect, the "apt-max-errors" (if it > really exists - I cannot find it now) is truely too low for "an average > system" .... I'd imagine, that upgrade from one major release to another > should set it temporarly to infinity ;7, but may be not. > Rather, there should be no errors during an upgrade - ever. That is one of the goals for upgrades. Somehow, setting such a (fictive?) option to infinite seems to be working around a problem that should not exist in the first place. > >> >> If not we need at the very least the actual error message(s). The >> current system state (/var/lib/dpkg/status) as well as the state before >> the upgrade (the /var/backups/dpkg.status* file dated before the update) >> could also be helpful. > > The pervious dpkg.status is gone, sorry. > > But current "dpkg.status" is c.a. 4.5MB. Is it all right to upload it > anyway? > > [...] > -R > I believe the BTS will accept it (you may want to gzip it though), but lists.d.o will silently discard it. So follow up with a separate mail afterwards to ensure we notice once you have done it. Thanks, ~Niels -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
