Package: aptitude
Version: 0.4.1-1.1
Severity: normal

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:
Aptitude 0.4.1: log report
Fri, Jun 16 2006 17:12:33 +0200

IMPORTANT: this log only lists intended actions; actions which fail due to
dpkg problems may not be completed.

Will install 31 packages, and remove 0 packages.
52.4MB of disk space will be used
===============================================================================
[INSTALL, DEPENDENCIES] busybox
[INSTALL, DEPENDENCIES] initramfs-tools
[INSTALL, DEPENDENCIES] klibc-utils
[INSTALL, DEPENDENCIES] libklibc
[INSTALL, DEPENDENCIES] linux-image-2.6.16-2-486
[INSTALL, DEPENDENCIES] nvidia-kernel-2.6.16-2-486
[HOLD] gcj
[HOLD] libgcj-dev
[HOLD] libgda2-3
[HOLD] mpeglib
[HOLD] python-imaging
[HOLD] tetex-doc
[HOLD] udev
[UPGRADE] dhcp3-client 3.0.4-2 -> 3.0.4-5
[UPGRADE] dhcp3-common 3.0.4-2 -> 3.0.4-5
[UPGRADE] libcamel1.2-8 1.6.1-3 -> 1.6.2-2
[UPGRADE] libebook1.2-5 1.6.1-3 -> 1.6.2-2
[UPGRADE] libedataserver1.2-7 1.6.1-3 -> 1.6.2-2
[UPGRADE] libnspr4-0d 1.8.0.1-11 -> 1.8.0.4-1
[UPGRADE] libnss3-0d 1.8.0.1-11 -> 1.8.0.4-1
[UPGRADE] libpisock++0c2 0.11.8-23 -> 0.11.8-24
[UPGRADE] libpisock-dev 0.11.8-23 -> 0.11.8-24
[UPGRADE] libpisock8 0.11.8-23 -> 0.11.8-24
[UPGRADE] libpisync0 0.11.8-23 -> 0.11.8-24
[UPGRADE] libsvn0 1.3.2-2 -> 1.3.2-3
[UPGRADE] nvidia-glx 1.0.8756-4 -> 1.0.8762-2
[UPGRADE] planner 0.14-1 -> 0.14-2
[UPGRADE] python-central 0.4.15 -> 0.4.16
[UPGRADE] python-subversion 1.3.2-2 -> 1.3.2-3
[UPGRADE] python2.4 2.4.3-5 -> 2.4.3-7
[UPGRADE] python2.4-dev 2.4.3-5 -> 2.4.3-7
[UPGRADE] python2.4-minimal 2.4.3-5 -> 2.4.3-7
[UPGRADE] subversion 1.3.2-2 -> 1.3.2-3
[UPGRADE] subversion-tools 1.3.2-2 -> 1.3.2-3
[UPGRADE] vim 1:7.0-017+6 -> 1:7.0-017+7
[UPGRADE] vim-common 1:7.0-017+6 -> 1:7.0-017+7
[cut]

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.

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.14rg
Locale: LANG=pl_PL, LC_CTYPE=pl_PL (charmap=ISO-8859-2)

Versions of packages aptitude depends on:
ii  apt [libapt-pkg-libc6.3-6-3.1 0.6.44.2   Advanced front-end for dpkg
ii  libc6                         2.3.6-15   GNU C Library: Shared libraries
ii  libgcc1                       1:4.1.1-5  GCC support library
ii  libncursesw5                  5.5-2      Shared libraries for terminal hand
ii  libsigc++-2.0-0c2a            2.0.16-3   type-safe Signal Framework for C++
ii  libstdc++6                    4.1.1-5    The GNU Standard C++ Library v3

Versions of packages aptitude recommends:
pn  aptitude-doc-en | aptitude-do <none>     (no description available)

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to