registry team mailing list archive

[jeroendv <75332@xxxxxxxxxxxxxxxxxx>]

TRIAGED:
as mentioned earlier, if you use the the "dpkg --set-selections" method (see 7.12 at http://www.debian.org/doc/FAQ/ch-pkg_basics.en.html) to put a package on hold, instead of the "aptitude hold <packageName>" command.
Then the update-manager will successfully ignore future upgrades for that package,
the update-notifier will also no longer warn about available upgrades for those packages that have been put on hold.

extra information:
it seems though that the concept of putting a package on hold in the dpkg-way is different from the aptitude way.
for example, after putting a package on hold using "dpgk --set-selections", I can then proceed to run "aptitude unhold"
after which aptitude will again try to upgrade the package when running "aptitude safe-upgrade".
however running "dpkg --get-selections" shows that the package is still marked as hold, and both "apt-get upgrade" and the update-manager are still ignoring it.

thus it seems that aptitude is at fault here for not playing nicely with
the update-manager/dpkg/apt-get, which is kind of weird since aptitude
is recommended as the preferred way to administer your system.

long story short, the bug as was posted is triaged, 
but maybe a new bugreport should be posted regarding this anomalous behaviour of aptitude :-s

-- 
Held back packages not ignored by update-manager
https://bugs.launchpad.net/bugs/75332
You received this bug notification because you are a member of Registry
Administrators, which is the registrant for Debian.