[Aptitude-devel] Bug#252264: aptitude: explicit selection of less-scored version is sticky
Manuel A. Fernandez Montecelo
manuel.montezelo at gmail.com
Tue Dec 29 15:03:08 UTC 2015
Control: tags -1 + moreinfo unreproducible
Hi Yann,
2004-06-02 13:47 Yann Dirson:
>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...
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... but I was
trying to upgrade iceweasel to different versions of unstable and
experimental several times and the behaviour was the expected one. The
version selected for installation was the one that I indicated in every
step, and the candidate version was correctly shown.
Can you still see this happening, and if so please provide a concrete
example?
Cheers.
--
Manuel A. Fernandez Montecelo <manuel.montezelo at gmail.com>
More information about the Aptitude-devel
mailing list