[Aptitude-devel] Bug#729761: Does not respect holds

[Manuel A. Fernandez Montecelo]

2015-09-16 23:12 josh at joshtriplett.org:
>On Wed, Sep 16, 2015 at 11:01:16PM +0100, Manuel A. Fernandez Montecelo wrote:
>> Hi,
>>
>> 2013-11-21 00:05 Matthias Klumpp:
>> >forcemerge 137771 729761
>> >thanks
>> >
>> >Hi!
>> >This is a bug which has been known for a long time, and is the #1
>> >reason why I recommend using apt-get over aptitude ;-)
>> >Hopefully this will be fixed soon, but after so much time has passed,
>> >I doubt that. (I am also not sure what the problem is currently)
>> >Cheers,
>> >   Matthias
>> >
>> >
>> >2013/11/21 Josh Triplett <josh at joshtriplett.org>:
>> >>reassign 729761 aptitude
>> >>retitle 729761 aptitude: Does not set holds in apt
>> >>thanks
>> >>
>> >>On Tue, Nov 19, 2013 at 01:14:55AM +0100, Matthias Klumpp wrote:
>> >>>2013/11/17 Josh Triplett <josh at joshtriplett.org>:
>> >>>> Package: gnome-packagekit
>> >>>> Version: 3.8.2-4
>> >>>> Severity: normal
>> >>>>
>> >>>> I have several packages on hold.  Despite that, gnome-packagekit
>> >>>> repeatedly pops up a notification about software updates, asking me to
>> >>>> update those packages.
>> >>>>
>> >>>> I don't know if this bug lies in gnome-packagekit or in packagekit
>> >>>> itself.
>> >>>PackageKit/Aptcc does respect holds in Apt. You should use apt-mark to
>> >>>properly set a package on hold, like "apt-mark hold <pkgname>".
>> >>>If that works, everything is fine :-)
>> >>>Aptcc does not parse the custom files set by Aptitude, it only
>> >>>respects Apt settings in that regard.
>> >>
>> >>Interesting.  Sounds like a bug in aptitude for not using apt's holds.
>> >>Thanks for the clarification.
>> >>
>> >>- Josh Triplett
>>
>> I wanted to give you a heads-up about this bug report, because since
>> it's so long after the it was submitted and if you see a bug-closed
>> message for the merged bug #137771, maybe you don't notice it.
>>
>> So the news is that I commited a change that I believe that it will fix
>> the issue.  If you are still interested in the outcome of this bug
>> report and to see if it was really fixed, it would be great if you could
>> check if the problems that you were observing are gone once it's
>> released.
>
>Do you have a link to the commit?  I don't see a bug-closed message for
>137771.

https://anonscm.debian.org/cgit/aptitude/aptitude.git/commit/?id=25527ec5e551d4470f66280f76985d0049969f5e

This needed also implementing talking to dpkg direcly, since libapt does
not (yet) implement that (apt-mark uses a similar approach) -- although
it might do in the near future.

https://anonscm.debian.org/cgit/aptitude/aptitude.git/commit/?id=4b51933b69a4dfb00247e75c9890b4b5f589394c


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