Your message dated Fri, 11 Sep 2015 16:14:34 +0100
with message-id
<capq4b8mgkaq4wmuny+gzynh2vqtq0qd4ijhvslupokgrv6g...@mail.gmail.com>
and subject line Re: [Aptitude-devel] Bug#769222: Bug#769222: Bug#769222:
aptitude: Frequent pending actions left
has caused the Debian Bug report #769222,
regarding aptitude: Can't configure packages from trigger/wait states 'T' and
'W' (frequent pending actions left; says, it would configure packages but
doesn't)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
769222: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769222
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: aptitude
Version: 0.6.11-1
Severity: minor
I ran this twice, but had to resort to dpkg --configure -a to get the
job actually done.
# aptitude purge
The following partially installed packages will be configured:
man-db sgml-base sgml-data
No packages will be installed, upgraded, or removed.
0 packages upgraded, 0 newly installed, 0 to remove and 6 not upgraded.
Need to get 0 B of archives. After unpacking 0 B will be used.
Do you want to continue? [Y/n/?]
# aptitude purge
The following partially installed packages will be configured:
man-db sgml-base sgml-data
No packages will be installed, upgraded, or removed.
0 packages upgraded, 0 newly installed, 0 to remove and 6 not upgraded.
Need to get 0 B of archives. After unpacking 0 B will be used.
Do you want to continue? [Y/n/?]
# dpkg --configure -a
Processing triggers for sgml-base (1.26+nmu4) ...
Processing triggers for man-db (2.7.0.2-2) ...
# aptitude purge
No packages will be installed, upgraded, or removed.
0 packages upgraded, 0 newly installed, 0 to remove and 6 not upgraded.
Need to get 0 B of archives. After unpacking 0 B will be used.
Do you want to continue? [Y/n/?]
--- End Message ---
--- Begin Message ---
2015-09-11 10:25 GMT+01:00 David Kalnischkies <[email protected]>:
> On Fri, Sep 11, 2015 at 01:06:24AM +0100, Manuel A. Fernandez Montecelo wrote:
>> >I haven't really decided (mostly thanks to time issues) yet how to tackle
>> >this giant ball of pain and on top of that how to sell it to the Release
>> >Team if I would find a fix from the apt side. As said in the mentioned
>> >bugreport, that wouldn't help in any way with wheezy-upgrades though.
>
> [The bugreport was 769609 and the fix which landed in jessie with
> Release team approval was a2a75ff4516f7609f4c55b42270abb8d08943c60.]
>
>
>> In the dpkg commit fixing #766758, it says:
>>
>> This is a mostly conformant workaround for frontends like apt that do
>> not correctly call «dpkg --configure -a» or «dpkg --triggers-only -a»
>> after their normal runs, and leave packages in triggers-pending and
>> triggers-awaited states.
>
> apt/jessie does call "dpkg --configure -a" by default after performing
> its other dpkg callings. The workaround was needed as apt/wheezy is used
> in the wheezy→jessie upgrade, while at some point in this upgrade
> dpkg/jessie will be used; so dpkg has to behave as apt/wheezy expects it
> to work.
>
> [The "bleed through" of internal details like triggers is why we would
> prefer that dpkg would deal with ordering all by itself as talked about
> in the DebConf meeting]
I see, I didn't realise at the time when you were discussing that.
>> I am not sure if the front-ends are suppossed to be modified to call
>> dpkg correctly because this "conformant workaround" will be removed, or
>> what's the situation. Can you please clarify, if you know the reply
>> right away? If you have to dig no problem, I will do it.
>
> I am pretty sure the workaround will be removed at some point, so if
> aptitude calls dpkg itself in any way, it should call --configure -a at
> the end of these actions – "--configure pkg" might be the most likely
> situation to activate a trigger but any file placement or maintainer
> script can call one.
>
> I don't know if aptitude actually calls dpkg on its own, but some
> reports I had read suggested as much even through I wouldn't expect it…
> So I left this bug here for someone to check aptitude – feel free to
> close if there is no such issue.
I've been reviewing the calls and, unless I am missing somethig, there
are no calls of that kind, there are only other calls to dpkg for
different purposes.
So I think that it is safe to close the bug now. Thanks a lot for the input!
--
Manuel A. Fernandez Montecelo <[email protected]>
--- End Message ---
_______________________________________________
Aptitude-devel mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/aptitude-devel
