Your message dated Thu, 12 Nov 2015 11:59:15 +0000
with message-id <[email protected]>
and subject line Re: aptitude: cannot forbid more than 1 version of a package
has caused the Debian Bug report #642030,
regarding aptitude: cannot forbid more than 1 version of a package
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.)
--
642030: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=642030
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: aptitude
Version: 0.6.3-4
Severity: normal
If I have forbidden a package version in testing, and I see in
unstable a new version with the bug not fixed, I cannot forbid that
new one: if I do, the version in testing is not forbidden any more and
will likely get installed. Thus I have to wait until it gets migrated
and rely on me noticing at that time...
-- Package-specific info:
aptitude 0.6.3 compiled at Apr 2 2011 21:33:01
Compiler: g++ 4.5.2
Compiled against:
apt version 4.10.1
NCurses version 5.8
libsigc++ version: 2.2.4.2
Ept support enabled.
Gtk+ support disabled.
Current library versions:
NCurses version: ncurses 5.9.20110404
cwidget version: 0.5.16
Apt version: 4.10.1
linux-vdso.so.1 => (0x00007fff2b1f9000)
libapt-pkg.so.4.10 => /usr/lib/libapt-pkg.so.4.10 (0x00007f624619a000)
libncursesw.so.5 => /lib/libncursesw.so.5 (0x00007f6245f47000)
libsigc-2.0.so.0 => /usr/lib/libsigc-2.0.so.0 (0x00007f6245d41000)
libcwidget.so.3 => /usr/lib/libcwidget.so.3 (0x00007f6245a39000)
libept.so.1 => /usr/lib/libept.so.1 (0x00007f62457dd000)
libxapian.so.22 => /usr/lib/libxapian.so.22 (0x00007f62453e2000)
libz.so.1 => /usr/lib/libz.so.1 (0x00007f62451cb000)
libsqlite3.so.0 => /usr/lib/libsqlite3.so.0 (0x00007f6244f2b000)
libboost_iostreams.so.1.42.0 => /usr/lib/libboost_iostreams.so.1.42.0
(0x00007f6244d12000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0
(0x00007f6244af6000)
libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6
(0x00007f62447ec000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f6244569000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1
(0x00007f6244353000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f6243fcf000)
libutil.so.1 => /lib/x86_64-linux-gnu/libutil.so.1 (0x00007f6243dcb000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f6243bc7000)
libuuid.so.1 => /lib/libuuid.so.1 (0x00007f62439c2000)
libbz2.so.1.0 => /lib/x86_64-linux-gnu/libbz2.so.1.0
(0x00007f62437b2000)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007f62435aa000)
/lib64/ld-linux-x86-64.so.2 (0x00007f62464d3000)
Terminal: screen
$DISPLAY is set.
`which aptitude`: /usr/bin/aptitude
aptitude version information:
aptitude linkage:
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'oldstable'), (500, 'unstable'), (500,
'stable'), (101, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.0.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages aptitude depends on:
ii apt [libapt-pkg4.10] 0.8.15.6
ii libboost-iostreams1.42.0 1.42.0-4+b1
ii libc6 2.13-18
ii libcwidget3 0.5.16-3.1
ii libept1 1.0.5
ii libgcc1 1:4.6.1-4
ii libncursesw5 5.9-1
ii libsigc++-2.0-0c2a 2.2.9-1
ii libsqlite3-0 3.7.7-2
ii libstdc++6 4.6.1-4
ii libxapian22 1.2.7-1
ii zlib1g 1:1.2.3.4.dfsg-3
Versions of packages aptitude recommends:
ii apt-xapian-index 0.44
ii aptitude-doc-en | aptitude-doc <none>
ii libparse-debianchangelog-perl 1.2.0-1
ii sensible-utils 0.0.6
Versions of packages aptitude suggests:
ii debtags 1.7.11
ii tasksel 3.05
-- no debconf information
--- End Message ---
--- Begin Message ---
Hi Yann,
2011-09-18 19:16 Yann Dirson:
Package: aptitude
Version: 0.6.3-4
Severity: normal
If I have forbidden a package version in testing, and I see in
unstable a new version with the bug not fixed, I cannot forbid that
new one: if I do, the version in testing is not forbidden any more and
will likely get installed. Thus I have to wait until it gets migrated
and rely on me noticing at that time...
This matches the intended use of the feature and documentation:
"Forbid a package from being upgraded to a particular version. This
will prevent aptitude from automatically upgrading to this version,
but will allow automatic upgrades to future versions."
Even if this worked for multiple versions, if you are unsure in which
version the package is going to fix a problem, it is more practical to
use the Hold feature until you verify that it is fixed and safe to
install, rather than to keep adding F versions every time that a new
version pops up in the repositories (or failing to do so and be
installed to a version that you don't want).
In general, trying to extend Forbids to eat into the terrain of Holds
and create further overlapping between them is not good design, so I am
going to close this bug report.
Cheers.
--
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
