Bug#782777: [Aptitude-devel] Bug#782777: no more reproducible? (aptitude: marks certain packages as new and not auto-installed on every start of aptitude)
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 confirmed and unpreproducible at the same time. But it's back again since today on the machine I yesterday investigated the effect of downgrading apt to 1.0.9.7. I currently assume that downgrading/upgrading to apt 1.0.9.7/1.0.9.8 doesn't immediately trigger it, but calling some commands (maybe apt-get update via cron or playing around with apt-mark) is also needed to change the state files accordingly which then trigger it. A very strange (and surely annoying) issue. Will try to further encircle it. If someone else is reading this: I'd like to here if other people are affected to see how widespread the issue is. I assume that only systems where also experimental is present in the sources.list can be affected, i.e. that this will not affect Jessie when released as Stable (unless backports trigger it, too). Regarding my own systems: From those three who are currently online and also have experimental, only two show that symptom, interestingly with different packages. My Sid-Thinkpad has the issue with the same packages as Chris. My Testing-Server-VM (with experimental and sid in the sources.list, too, but prefering testing) shows the issue with exactly one package which is not mentioned so far: --\ New Packages (1) --\ libs - Collections of software routines (1) --\ Debian (1) --\ experimental (1) --\ main - The main Debian archive (1) --\ Priority standard (1) p libgnutls26 0 1.418 kB none 2.12.23-18 But neither my Sid-VM for development nor my Sid-EeePC show that symptom, even not after apt-get update. Nor do two pure Jessie systems I've checked. So apt 1.0.9.8 plus running apt-get update is not a sufficient condition for this issue I.e. I've not yet found out, which conditions all must be met to trigger the issue, but I suspect that the following conditions are at least necessary: * experimental in sources.list * apt 1.0.9.8 installed and at least once used Will continue to have an eye on that issue. Any further observations which may lead to a further encircling of that issue are very welcome. Regards, Axel -- ,''`. | Axel Beckert a...@debian.org, 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 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#782777: [Aptitude-devel] Bug#782777: no more reproducible? (aptitude: marks certain packages as new and not auto-installed on every start of aptitude)
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 like to here if other people are affected to see how widespread the issue is. I assume that only systems where also experimental is present in the sources.list can be affected, i.e. that this will not affect Jessie when released as Stable (unless backports trigger it, too). It should be noted, that, while I have experimental packages installed (kernel + iceweasel) I do not have experimental enabled right now in my sources.list. Cheers, Chris. smime.p7s Description: S/MIME cryptographic signature
Bug#782777: [Aptitude-devel] Bug#782777: no more reproducible? (aptitude: marks certain packages as new and not auto-installed on every start of aptitude)
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 libgcc-4.9-dev set to automatically installed. # apt-mark showauto | fgrep libgcc-4.9-dev # apt-mark showmanual | fgrep libgcc-4.9-dev libgcc-4.9-dev # Since I tried that with apt 1.0.9.7 as shown above and ran aptitude update for the late evening mirror push, I can no more reproduce the issue -- neither the 13 new packages show up in aptitude anymore nor does libgcc-4.9-dev always get reset to being marked as manually installed. Maybe some weird dak hiccup? IIRC there were several mirror pushes missing about a day ago. Christoph: Can you check if you can still reproduce the issue? Regards, Axel -- ,''`. | Axel Beckert a...@debian.org, 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 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#782777: [Aptitude-devel] Bug#782777: no more reproducible? (aptitude: marks certain packages as new and not auto-installed on every start of aptitude)
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
