On Sun, Jun 18, 2006 at 10:40:40PM +0200, Robert Gomułka <[EMAIL PROTECTED]> was heard to say: > For various reasons I have some packages set on hold with following > command: > $ aptitude hold package1 package2 ... > My everyday maintenance is simple: aptitude update; aptitude > dist-upgrade > > One of my hold packages was nvidia-glx: > Log complete. > Aptitude 0.4.1: log report > Thu, Jun 15 2006 10:25:25 +0200 > [HOLD] gcj > [HOLD] libgcj-dev > [HOLD] libgda2-3 > [HOLD] mpeglib > [HOLD] nvidia-glx > [HOLD] python-imaging > [HOLD] tetex-doc > [HOLD] udev > > But next day I overlooked that something caused this nvidia-glx to be > upgraded. I pressed enter too quickly, what caused some problems to my > system. To my surprise I couldn't see HOLD nvidia-glx line any more in > aptitude logs:
[snip]
> And my question/bug report is about: "Why hold flag was removed from
> single package?". I am sure I haven't removed hold flag manually in the
> meantime.
Hmm. It looks like the problem here is that dist-upgrade uses the core
apt code to automatically install dependencies of a package that's being
upgraded or installed. The reason this turns out to be a problem is that
aptitude's private hold flag isn't known to apt. I believe it may be
possible to set the apt hold flag internally so this doesn't happen.
(there may also be undesirable interactions between hold and the problem
resolver)
Daniel
signature.asc
Description: Digital signature
