Dear systemd maintainers, On Sun, Mar 05, 2017 at 01:27:22PM +0100, Holger Levsen wrote: > Package: piuparts.debian.org > > the subject says it: jessie2bpo has >400 packages in dependency-failed-testing > status, which is far too many for the stable release. We should track down the > cause for this and fix it. > > see https://piuparts.debian.org/jessie2bpo/
as https://piuparts.debian.org/jessie2bpo/state-failed-testing.html shows, this is mostly due to libsystemd0 and udev (look at the numbers in brackets after the package names on that last URL, those are the number of packages affected…) which both fail as shown in https://piuparts.debian.org/jessie2bpo/fail/libsystemd0_230-7~bpo8+2.log and https://piuparts.debian.org/jessie2bpo/fail/udev_230-7~bpo8+2.log Both these logs contain this: Preparing to unpack .../udev_215-17+deb8u6_amd64.deb ... Unpacking udev (215-17+deb8u6) over (230-7~bpo8+2) ... Processing triggers for systemd (230-7~bpo8+2) ... dpkg: dependency problems prevent configuration of udev: systemd (230-7~bpo8+2) breaks udev (<< 228-5) and is installed. Version of udev to be configured is 215-17+deb8u6. dpkg: error processing package udev (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: udev E: Sub-process /usr/bin/dpkg returned an error code (1) As I see it this is because we only tell apt-get to install udev from backports but dont tell it to also upgrade systemd to that version, so this is probably rather a bug in apt (or maybe piuparts) but not in src:systemd. Do you agree? -- cheers, Holger
signature.asc
Description: Digital signature
