Your message dated Tue, 29 Dec 2015 21:13:06 +0100
with message-id <[email protected]>
and subject line Re: [Aptitude-devel] Bug#252264: aptitude: explicit selection
of less-scored version is sticky
has caused the Debian Bug report #252264,
regarding aptitude: explicit selection of less-scored version is sticky
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.)
--
252264: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=252264
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: aptitude
Version: 0.2.14.1-2
Severity: normal
On my sarge box, if I explicitely select for installation a sid version of a
package that is already uptodate according to sarge, and then later (same
session, no install run in between) change my mind and reselect the sarge
version, then aptitude still considers the sid version as being the one to
install. IOW, it is the sid version appearing in the "available version"
column, if I hit '+' the sid version gets selected, and if I insist on
keeping the sarge version the package appears in the 'get' listing as an
ordinary package for which a new version is available in sarge, but for
which upgrade was not requested.
After the other packages get upgraded, and cache gets refreshed, the
behaviour is back to normal... at one detail: 2 packages suggested by an
installed one are now selected for automatic installation, although I don't
think they were here before, and I did not select them explicitely. Rather,
IIRC they were pulled by one sid-only package I had tagged for install
before changing my mind, and I'm quite sure they were untagged when I
deselected that sid package (qdvdauthor, from Christian Marillat's
repository).
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (990, 'testing'), (90, 'experimental'), (90, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.4.24-smp
Locale: LANG=C, LC_CTYPE=C
Versions of packages aptitude depends on:
ii apt [libapt-pkg-libc6.3-5-3 0.5.25 Advanced front-end for dpkg
ii libc6 2.3.2.ds1-12 GNU C Library: Shared libraries an
ii libgcc1 1:3.3.3-9 GCC support library
ii libncurses5 5.4-3 Shared libraries for terminal hand
ii libsigc++-1.2-5c102 1.2.5-1 Type-safe Signal Framework for C++
ii libstdc++5 1:3.3.3-9 The GNU Standard C++ Library v3
-- no debconf information
--
Yann Dirson <[email protected]> | Why make M$-Bill richer & richer ?
Debian-related: <[email protected]> | Support Debian GNU/Linux:
Pro: <[email protected]> | Freedom, Power, Stability, Gratuity
http://ydirson.free.fr/ | Check <http://www.debian.org/>
--- End Message ---
--- Begin Message ---
Version: 0.6.8.2-1
Hi,
Manuel A. Fernandez Montecelo wrote:
> >On my sarge box, if I explicitely select for installation a sid version of a
> >package that is already uptodate according to sarge, and then later (same
> >session, no install run in between) change my mind and reselect the sarge
> >version, then aptitude still considers the sid version as being the one to
> >install. IOW, it is the sid version appearing in the "available version"
> >column, if I hit '+' the sid version gets selected, and if I insist on
> >keeping the sarge version the package appears in the 'get' listing as an
> >ordinary package for which a new version is available in sarge, but for
> >which upgrade was not requested.
> >
> >After the other packages get upgraded, and cache gets refreshed, the
> >behaviour is back to normal...
Sounds familiar, indeed.
> I am not sure if I follow 100% the steps here, since the descriptions
> are a bit vague and somewhat difficult to parse for me...
It's probably clearer what he means if you ran into this in the past,
too. :-)
If you rebuilt the view (pressing "l" and then Enter without changing
the value) usually moved that package into the "upgradable packages"
section and stayed there.
> but I was trying to upgrade iceweasel to different versions of
> unstable and experimental several times and the behaviour was the
> expected one.
The package iceweasel is a good example to test and I can no more
reproduce that behaviour in neither Sid nor Wheezy (oldstable;
aptitude 0.6.8.2-1) which was quite well known to me (but never
considered an issue, more a little peculiarity.
I though could reproduce this behaviour in Debian Squeeze
(oldoldstable; aptitude 0.6.3), taking debsums from backports as
example:
i A debsums 336 kB 2.0.48+nmu3 2.0.51~bpo60+1
(Notice the absence of an "u" in the second column.)
It also made no difference if I triggered the "keep" action by
pressing "+" on the installed version in the package versions or if I
pressed ":" in the general package list view.
It even shows up after pressing "g" in the "Preview" tab in the list
of "Packages being automatically held in their current state":
Packages Preview
aptitude 0.6.3 DL Size: 1,009
--\ Packages being automatically held in their current state (1)
i A debsums 336 kB 2.0.48+nmu3 2.0.51~bpo60+1
--\ Packages to be upgraded (2)
iuA libpng12-0 328 kB 1.2.44-1+squeeze5 1.2.44-1+squeeze6
iuA libxml2 1,630 2.7.8.dfsg-2+squeeze15 2.7.8.dfsg-2+squeeze16
--\ Packages which are recommended by other packages (1)
p xml-core 266 kB <none> 0.13
Hence closing as fixed with the aptitude version in Debian 7 Wheezy.
Regards, Axel
--
,''`. | Axel Beckert <[email protected]>, http://people.debian.org/~abe/
: :' : | Debian Developer, ftp.ch.debian.org Admin
`. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5
`- | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
--- End Message ---
_______________________________________________
Aptitude-devel mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/aptitude-devel
