Bug#721426: aptitude: packages are sometimes selected for upgrade by default just after aptitude is started

Control: tags -1 - moreinfo + pending Hi, 2016-03-09 15:31 Vincent Lefevre: But I notice the same issue on a different machine, where last in /var/log/aptitude, I get: Aptitude 0.7.8: log report Mon, Mar 7 2016 14:22:40 +0100 but: -rw-r--r-- 1 root root 9490347 2016-03-07 14:04:58

Bug#721426: aptitude: packages are sometimes selected for upgrade by default just after aptitude is started

On 2016-03-09 16:31:39 +0100, Vincent Lefevre wrote: > But I notice the same issue on a different machine, where last in > /var/log/aptitude, I get: > > Aptitude 0.7.8: log report > Mon, Mar 7 2016 14:22:40 +0100 > > but: > > -rw-r--r-- 1 root root 9490347 2016-03-07 14:04:58 pkgstates >

Bug#721426: aptitude: packages are sometimes selected for upgrade by default just after aptitude is started

On 2016-03-09 14:14:03 +, Manuel A. Fernandez Montecelo wrote: [...] > What's the difference between them? "Upgrade: yes" is the same in > pkgstates.old and pkgstates, respectively. > > (If you mean the "remove reason" might be correct or a small > incorrection but probably without any

Bug#721426: aptitude: packages are sometimes selected for upgrade by default just after aptitude is started

Control: tags -1 + moreinfo (Tagging it +moreinfo not necessarily because needing more info from submitter, but to separate it from the hundreds of other open reports and to mark it as "needs further consideration", "work-in-progress" or similar). Hi, 2016-03-09 11:46 Vincent Lefevre:

Bug#721426: aptitude: packages are sometimes selected for upgrade by default just after aptitude is started

Control: retitle -1 aptitude: packages from the previous upgrade are still selected for upgrade by default if there is again a new version I think this title corresponds more precisely to what I could observe. -- Vincent Lefèvre - Web: 100%

Bug#721426: aptitude: packages are sometimes selected for upgrade by default just after aptitude is started

On 2016-03-09 12:46:04 +0100, Vincent Lefevre wrote: > I have: > > -rw-r--r-- 1 9536507 2016-03-09 11:15:43 /var/lib/aptitude/pkgstates > -rw-r--r-- 1 9526471 2016-03-08 09:38:42 /var/lib/aptitude/pkgstates.old > > Note that /var/lib/aptitude/pkgstates dates from before the upgrade. > Is that

Bug#721426: aptitude: packages are sometimes selected for upgrade by default just after aptitude is started

Control: reopen -1 Control: found -1 0.7.8-1 On 2016-03-01 18:32:44 +, Manuel A. Fernandez Montecelo wrote: > 2016-03-01 17:43 Vincent Lefevre: > > On 2016-03-01 15:02:59 +, Manuel A. Fernandez Montecelo wrote: > > > 2013-08-31 12:41 Vincent Lefevre: > > > > When I start "aptitude" (no

Bug#721426: aptitude: packages are sometimes selected for upgrade by default just after aptitude is started

Control: tags -1 - moreinfo On 2016-03-01 15:02:59 +, Manuel A. Fernandez Montecelo wrote: > 2013-08-31 12:41 Vincent Lefevre: > > When I start "aptitude" (no arguments, curses interface), packages are > > sometimes selected for upgrade by default, for no apparent reason. > > Since this

Bug#721426: aptitude: packages are sometimes selected for upgrade by default just after aptitude is started

Control: tags -1 + moreinfo Hi, 2013-08-31 12:41 Vincent Lefevre: Package: aptitude Version: 0.6.8.2-1.2 Severity: normal When I start "aptitude" (no arguments, curses interface), packages are sometimes selected for upgrade by default, for no apparent reason. Since this behavior is not

Bug#721426: aptitude: packages are sometimes selected for upgrade by default just after aptitude is started

Package: aptitude Version: 0.6.8.2-1.2 Severity: normal When I start aptitude (no arguments, curses interface), packages are sometimes selected for upgrade by default, for no apparent reason. Since this behavior is not documented in the man page, I assume that this is a bug. Such packages are