Control: tags -1 + moreinfo unreproducible
Hi,
2015-12-05 10:52 積丹尼 Dan Jacobson:
Package: aptitude
Version: 0.7.4-2
Severity: wishlist
No big deal, but here aptitude knows to not ask us
"Do you want to continue? [Y/n/?]",
# aptitude full-upgrade
...
Accept this solution? [Y/n/q/?] n
The following actions will resolve these dependencies:
Keep the following packages at their current version:
1) libperl5.22 [Not Installed]
2) perl [5.20.2-6 (now, unstable)]
3) perl-base [5.20.2-6 (now, unstable)]
4) perl-doc [5.20.2-6 (now, unstable)]
5) perl-modules-5.22 [Not Installed]
6) xserver-xorg-core [2:1.17.3-2 (now, unstable)]
Accept this solution? [Y/n/q/?]
No packages will be installed, upgraded, or removed.
0 packages upgraded, 0 newly installed, 0 to remove and 4 not upgraded.
Need to get 0 B of archives. After unpacking 0 B will be used.
Current status: 0 (+0) broken, 4 (+0) upgradable, 49736 (+0) new.
#
Where here, with the same
0 packages upgraded, 0 newly installed, 0 to remove and 4 not upgraded.
we are asked:
# aptitude purge ~c
No packages will be installed, upgraded, or removed.
0 packages upgraded, 0 newly installed, 0 to remove and 4 not upgraded.
Need to get 0 B of archives. After unpacking 0 B will be used.
Do you want to continue? [Y/n/?]
Current status: 0 (+0) broken, 4 (+0) upgradable, 49736 (+0) new.
#
So maybe it shouldn't ask in the latter case too.
I cannot reproduce it. Do you see this all of the time, or often, or
only happened once?
Maybe in your case there was something that needed to be written to the
package states on disk, or happened after some files from apt or debtags
had changed on disk and thought that its own states needed some changes,
etc.
Cheers.
--
Manuel A. Fernandez Montecelo <manuel.montez...@gmail.com>
