Bug#782777: [Aptitude-devel] Bug#782777: no more reproducible? (aptitude: marks certain packages as new and not auto-installed on every start of aptitude)

2015-04-18 Thread Axel Beckert
Hi, Christoph Anton Mitterer wrote: On Sat, 2015-04-18 at 01:05 +0200, Axel Beckert wrote: Christoph: Can you check if you can still reproduce the issue? I made an update, and checked again,... but the files still reappear as new and non-auto. Thanks for checking. I was about to tag that

Bug#782777: [Aptitude-devel] Bug#782777: no more reproducible? (aptitude: marks certain packages as new and not auto-installed on every start of aptitude)

2015-04-18 Thread Christoph Anton Mitterer
On Sat, 2015-04-18 at 15:08 +0200, Axel Beckert wrote: A very strange (and surely annoying) issue. Will try to further encircle it. Thanks a lot for this, I'd have done much more testing myself... if I wasn't kept busy with some btrfs issues right now :-/ If someone else is reading this: I'd

Bug#782777: [Aptitude-devel] Bug#782777: no more reproducible? (aptitude: marks certain packages as new and not auto-installed on every start of aptitude)

2015-04-17 Thread Axel Beckert
Sorry, me again. This gets stranger and stanger. Axel Beckert wrote: I can partially reproduce this with pure apt -- but with both, 1.0.9.8 and 1.0.9.7: # apt-mark showauto | fgrep libgcc-4.9-dev # apt-mark showmanual | fgrep libgcc-4.9-dev libgcc-4.9-dev # apt-mark auto libgcc-4.9-dev

Bug#782777: [Aptitude-devel] Bug#782777: no more reproducible? (aptitude: marks certain packages as new and not auto-installed on every start of aptitude)

2015-04-17 Thread Christoph Anton Mitterer
Hey. On Sat, 2015-04-18 at 01:05 +0200, Axel Beckert wrote: Christoph: Can you check if you can still reproduce the issue? I made an update, and checked again,... but the files still reappear as new and non-auto. Cheers, Chris. smime.p7s Description: S/MIME cryptographic signature