[Aptitude-devel] Bug#814240: systemd triggers break upgrades within unstable

[Manuel A. Fernandez Montecelo]

Hi again,

2016-02-29 13:17 Zack Weinberg:
>On Tue, Feb 23, 2016 at 8:44 AM, Manuel A. Fernandez Montecelo
><manuel.montezelo at gmail.com> wrote:
>>
>> Thanks for the report.  Do you have the logs around for those
>> installations attempts, of aptitude (the relevant section in
>> /var/log/aptitude*), apt (same for /var/log/apt/*) and dpkg
>> (/var/log/dpkg.log)?
>
>Attached.  I was having trouble finding the right bit of the logs, but
>conveniently the problem happened again this morning.  The logs start
>immediately after upgrading aptitude to 0.7.6-1, which I did
>separately from everything else.
>
>> Also, please attach the result of:
>>
>> apt-config dump
>
>Ok.

Thanks for providing the information.


>DPkg::NoTriggers "true";
>DPkg::ConfigurePending "true";
>DPkg::TriggersPending "true";

After talking about this bug a few days ago with APT Deities (David
Kalnischkies, in this case), he told me that apt doesn't use "dpkg
--triggers-only" by default.

He believes that apt /could/ issue that command when
"DPkg::TriggersPending" or "DPkg::ConfigurePending" are enabled, and
possibly other similar ones (he didn't mention the specifics).

Such options as marked as experimental and dangerous (man apt.conf) so
maybe they are better left disabled unless there's a specific need to
use them.

If you disable and things keep working normally, please report back to
this bug.


Other than that, I am running this reply through deity@ so APT folks can
take a look, give further insight/recommendations, reassign/clone the
bug to src:apt if they want to follow-up, etc.

In principle, there is nothing that aptitude can do about this (other
than disabling the options behind the user's back), so if there's no
input after some time I will close the bug.


Cheers.
-- 
Manuel A. Fernandez Montecelo <manuel.montezelo at gmail.com>