Hi, On Sat, Nov 29, 2014 at 03:08:22PM +0100, Martin Erik Werner wrote: > I had an issue where an "apt full-upgrade" (sid->sid) failed without > further notice like this: > > ### > (...) > Unpacking systemd-sysv (215-7) over (215-6) ... > E: Sub-process /usr/bin/dpkg returned an error code (1) > ### Probably #765687. You might be able to tell from /var/log/dpkg.log what was really wrong as apt has eaten the entire dpkg output… > and then when trying "apt-get install -f" failed with > > ### > (...) > dpkg: dependency problems prevent processing triggers for dbus: > dbus depends on libdbus-1-3 (>= 1.7.6); however: > Package libdbus-1-3:amd64 is not configured yet. > > dpkg: error processing package dbus (--configure): > dependency problems - leaving triggers unprocessed > dpkg: dependency problems prevent processing triggers for dbus: > dbus depends on libdbus-1-3 (>= 1.7.6); however: > Package libdbus-1-3:amd64 is not configured yet. > > (repeats...) > > dpkg: too many errors, stopping > Processing triggers for man-db (2.7.0.2-3) ... > Processing triggers for libc-bin (2.19-13) ... > Errors were encountered while processing: > dbus > dbus > dbus > (repeats...) > Processing was halted because there were too many errors. > E: Sub-process /usr/bin/dpkg returned an error code (1) > ### This looks a lot like one of the buggy dpkg versions we had in unstable. Please check which dpkg version is used here. If it is between 1.17.17 and 1.17.21 there isn't much we can do about it. You might have to look up the version in /var/log/apt/history.log as the full-upgrade has potentially involved dpkg as well. If the status wasn't in complete proper order before running apt the version requirement raises to 1.17.22 (which e.g. would be true for your --fix-broken call). If not or if you aren't sure you can look at /var/backups/dpkg.status* files. Find the one dated from before your upgrade and attach it if possible (the file contains information about all packages installed and in which version. If you don't want or can't (e.g. if it is against corporate policy) make this public, you can also mail it just to me – in case you find this acceptable as a compromise of course). Best regards David Kalnischkies
Attachment:
signature.asc
Description: Digital signature