Hi! On Sun, 2014-12-07 at 14:01:51 +0100, Niels Thykier wrote: > On 2014-12-05 05:20, Guillem Jover wrote: > > Given this, the only options seem to be to possibly change the > > --force-configure-any default to enabled (I'll try to test if this > > helps in the dbus situation) which I'd rather not do (but oh well), > > or disable the triggers dependency checks for jessie (and possibly > > later releases, if apt does not get fixed for jessie) and go back > > to the previous (broken, but known) behavior. :(
> As I mentioned to David/the APT maintainers, I could be interested in > having the patch for #769609 in APT. @Guillem, do you think that will > deal with the issue? That would fix the issue with dangling trigger-pending packages, but I don't think it would fix the dbus issue. I've not tried to check a dpkg workaround for that yet, sorry. I've got a fix for the nvidia kernel module one, and asked for access to the ppc system with the pam module 100% cpu usage bug, to try to confirm that's been fixed in .22, which I think it does, but would like to make sure. In any case I think .22 would be an improvement over what's currently in testing. Thanks, Guillem -- To UNSUBSCRIBE, email to debian-dpkg-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141209055900.ga32...@gaara.hadrons.org
