[Aptitude-devel] Bug#638049: aptitude forgets which packages were installed automatically
Control: tags -1 - confirmed moreinfo Control: close -1 Hi, 2016-02-25 13:17 To Harald Dunkel: I'm not sure if it's worth to create a new bug, because the bug might be different specially from the merged ones, but let's see... will hopefully be fixing or triaging it soon, when looking at another set of auto-install related problems. In the end I created another bug to track the latest of the issues: #816229 I am closing this bug, specially because the merged ones are quite whacky and without much useful information, some of the reports were actually caused by other tools (aptdaemon) or claimed to be in the search and then dismissed. Since some of the problems have been addressed in the last few releases, and new ones created (like the latest example in this bug report resubmitted as #816229), the old information contained in these reports is of not much use, and there are still many open bugs about the auto-flags with procedures that are actually reproducible, so it's better to focus on those. Cheers. -- Manuel A. Fernandez Montecelo___ Aptitude-devel mailing list Aptitude-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/aptitude-devel
[Aptitude-devel] Bug#638049: aptitude forgets which packages were installed automatically
2016-02-25 10:20 Harald Dunkel: I tried it, too: On first sight the problem seems to be gone. But after removing owncloud (press "g" in the preview and wait for it to finish) php5 and its dependencies are still marked for removal Apparently the "+" on php5 in the preview window has been lost. Can you reproduce? Yup. Oh, aptiude, never-ending source of joys, the magic gift that keeps on giving... bugs :) I'm not sure if it's worth to create a new bug, because the bug might be different specially from the merged ones, but let's see... will hopefully be fixing or triaging it soon, when looking at another set of auto-install related problems. Cheers. -- Manuel A. Fernandez Montecelo___ Aptitude-devel mailing list Aptitude-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/aptitude-devel
[Aptitude-devel] Bug#638049: aptitude forgets which packages were installed automatically
I tried it, too: On first sight the problem seems to be gone. But after removing owncloud (press "g" in the preview and wait for it to finish) php5 and its dependencies are still marked for removal Apparently the "+" on php5 in the preview window has been lost. Can you reproduce? Regards Harri ___ Aptitude-devel mailing list Aptitude-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/aptitude-devel
[Aptitude-devel] Bug#638049: aptitude forgets which packages were installed automatically
2016-02-04 11:42 Harald Dunkel: I think I know how to reproduce: - install minimal Debian unstable (a container or chroot should do) - boot it or chroot to it - configure networking - enter aptitude and install a package with a huge list of dependencies (e.g. owncloud) - leave aptitude - enter aptitude - mark "owncloud" to be removed (using "_") - hit "g" once to get the list of packages to be removed - mark "php5" to be kept (using "+") - press q Now the dependencies of php5 should have lost their "automatically installed" flag. There have been some changes in the last few versions, specially the last one, related with how packages marked to install/keep are handled that might have affected this. With 0.7.6, after following the steps above and pressing '+', this is the state: --\ Packages to be removed (1) ip owncloud-28.2 MB 7.0.12~dfsg-2 7.0.12~dfsg-2 --\ Packages being removed because they are no longer used (52) idA fonts-font-awesome -1,119 kB 4.5.0~dfsg-1 4.5.0~dfsg-1 idA fonts-lohit-deva-138 kB 2.5.3-12.5.3-1 idA fonts-sil-gentium-basic -2,186 kB 1.1-7 1.1-7 idA libjs-chosen-333 kB 0.9.11-2 0.9.11-2 idA libjs-dojo-core -4,064 kB 1.10.4+dfsg-2 1.10.4+dfsg-2 idA libjs-dojo-dijit-5,478 kB 1.10.4+dfsg-2 1.10.4+dfsg-2 idA libjs-dojo-dojox-17.7 MB 1.10.4+dfsg-2 1.10.4+dfsg-2 idA libjs-jcrop -397 kB 0.9.13+dfsg-1 0.9.13+dfsg-1 idA libjs-jquery-minicolors -100 kB 1.2.1-11.2.1-1 idA libjs-jquery-mousewheel -53.2 kB 10-2 10-2 idA libjs-jquery-timepicker -134 kB 1.2-1 1.2-1 idA libjs-mediaelement -581 kB 2.15.1+dfsg-1 2.15.1+dfsg-1 idA libjs-pdf -2,329 kB 1.1.366+dfsg-1 1.1.366+dfsg-1 i A libonig2 5.9.6-15.9.6-1 idA libphp-phpmailer-648 kB 5.2.14+dfsg-1 5.2.14+dfsg-1 i A libqdbm14 1.8.78-6+b21.8.78-6+b2 idA owncloud-doc-11.6 MB 0~20151214-1 0~20151214-1 idA pdf.js-common -2,554 kB 1.1.366+dfsg-1 1.1.366+dfsg-1 idA php-assetic -368 kB 1.3.2-11.3.2-1 idA php-doctrine-annotations-143 kB 1.2.7-11.2.7-1 idA php-doctrine-cache -129 kB 1.6.0-11.6.0-1 idA php-doctrine-collections-103 kB 1.3.0-21.3.0-2 idA php-doctrine-common -323 kB 2.4.3-12.4.3-1 idA php-doctrine-dbal -1,199 kB 2.4.5-12.4.5-1 idA php-doctrine-inflector -32.8 kB 1.1.0-11.1.0-1 idA php-doctrine-lexer -52.2 kB 1.0.1-31.0.1-3 idA php-getid3 -2,174 kB 1.9.11+dfsg-1 1.9.11+dfsg-1 idA php-guzzle -1,010 kB 3.9.3+dfsg-4 3.9.3+dfsg-4 idA php-json-patch -58.4 kB 0.1.0-20.1.0-2 idA php-opencloud -1,411 kB 1.16.0+dfsg-1 1.16.0+dfsg-1 idA php-patchwork-utf8 -3,623 kB 1.3.0-11.3.0-1 idA php-pear-2,224 kB 5.6.17+dfsg-3 5.6.17+dfsg-3 idA php-pimple -39.9 kB 1.1.1-11.1.1-1 idA php-psr-log -60.4 kB 1.0.0-31.0.0-3 idA php-sabre-dav -1,038 kB 1.8.12-1 1.8.12-1 idA php-sabre-vobject -233 kB 2.1.7-12.1.7-1 idA php-seclib -1,252 kB 1.0.1-11.0.1-1 idA php-symfony-class-loader-133 kB 2.7.9+dfsg-1 2.7.9+dfsg-1 idA php-symfony-console -483 kB 2.7.9+dfsg-1 2.7.9+dfsg-1 idA php-symfony-event-dispatcher-121 kB 2.7.9+dfsg-1 2.7.9+dfsg-1 idA php-symfony-process -165 kB 2.7.9+dfsg-1 2.7.9+dfsg-1 idA php-symfony-routing -297 kB 2.7.9+dfsg-1 2.7.9+dfsg-1 iphp5 5.6.17+dfsg-3 5.6.17+dfsg-3 i A php5-cli 5.6.17+dfsg-3 5.6.17+dfsg-3 i A php5-common 5.6.17+dfsg-3 5.6.17+dfsg-3 idA php5-curl -112 kB 5.6.17+dfsg-3 5.6.17+dfsg-3 i A php5-fpm 5.6.17+dfsg-3 5.6.17+dfsg-3 idA php5-gd -136 kB 5.6.17+dfsg-3 5.6.17+dfsg-3 i A php5-json 1.3.7-11.3.7-1 idA php5-mysql -274 kB 5.6.17+dfsg-3 5.6.17+dfsg-3 idA webfs -182 kB 1.21+ds1-10+b1 1.21+ds1-10+b1 idA zendframework -44.0 MB 1.12.17+dfsg-1 1.12.17+dfsg-1 The only one
[Aptitude-devel] Bug#638049: aptitude forgets which packages were installed automatically
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi Manuel, if you want to close this bug report, then go ahead and o it. Its OK with me. I understand that this particular problem seems to be closed. Thanx for your help Harri -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQEcBAEBCAAGBQJWty9oAAoJEAqeKp5m04HLqksH/3OVlu3o1KwRaRrco/rfpVvv /MnUauUV5uUVLVBg54EzIRANVxWsbcuRzvC9IXdQ+sVGI6usLjiutg7G1gz5yLKD LqPNlcPSslKO++2f0RYUY1zOOJtC+k5gE7Upjl82xJSKThfC1FHN7GU2ftBQ+FlE JmNUN0RYMMNvYND+9KVzuvaK6i56WcXc/WJxGIitriVhwpxzMClfRvyo446GWVrB gmSWElWkPAOK7zYsr/6mV5Gev+Jv3h3eYZM5aMI+L8QcfCJliwe+5Ocsh3Mj/dNF rFEMV7xV/sKEjeb/pHdFpw2KFYG3dooE9FBaK+1iD3pDxLOlgeBLmHJG2ACungo= =Pajs -END PGP SIGNATURE- ___ Aptitude-devel mailing list Aptitude-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/aptitude-devel
[Aptitude-devel] Bug#638049: aptitude forgets which packages were installed automatically
I think I know how to reproduce: - install minimal Debian unstable (a container or chroot should do) - boot it or chroot to it - configure networking - enter aptitude and install a package with a huge list of dependencies (e.g. owncloud) - leave aptitude - enter aptitude - mark "owncloud" to be removed (using "_") - hit "g" once to get the list of packages to be removed - mark "php5" to be kept (using "+") - press q Now the dependencies of php5 should have lost their "automatically installed" flag. Maybe you already knew, but I never saw it happening live before. Regards Harri ___ Aptitude-devel mailing list Aptitude-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/aptitude-devel
[Aptitude-devel] Bug#638049: aptitude forgets which packages were installed automatically
2016-01-24 16:14 Harald Dunkel: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi Manuel, On 01/23/16 01:11, Manuel A. Fernandez Montecelo wrote: Control: tags -1 + moreinfo Hi Harald, 2011-08-16 21:07 Harald Dunkel: (I'd love to have some option in aptitude to mark all installed packages as automatically installed, except for those that do not appear on the Depends or Recommends list of any installed package. This would make the use of some high level meta packages much more interesting.) This can be done with patterns. More info would be welcome. aptitude search '?installed(?not(?or(~RDepends:~i,~RRecommends:~i))) Maybe you want to throw in ?RSuggests as well. There can be oddities with virtual packages or other corner cases or bugs, though, so tread with care if you use this in automated ways. If you use the curses interface probably you're doing the following already, but just in case... it's relatively quick to mark all Installed packages as auto-installed ('M') at once, and then mark the ones that you don't want deleted as manually installed ('m'). Or at least will be useful with packages in some sections, like "libs" or "perl" or "python", you probably want most of them auto-installed without further checking, because the packages to be marked "manual" are very few, if any. Did you keep an eye on this and saw this happening recently? I just have to look at the list of installed packages. There are some very weird packages that I *surely* did not install on purpose. They were installed via some dependency and lost the "automatically installed" flag later. Samples: libpkcs11-helper1 libwildmidi-config claws-mail-i18n seabios shared-desktop-ontologies geoip-database tons of weird perl package even more weird python packages I am afraid the problem is still in. There are cases where packages are marked as manually installed (removing the auto-installed bit) where they shouldn't be, such as marking them as "keep" (':') or selecting "Keep the following packages at their current version" in conflicts. Or using "Cancel pending actions" in the menu. I am fixing some of those for the next release. Some of these bugs can be the cause of these packages being installed in your system and not marked with the auto-flag after a while. However, this does not mean that the problem described in the original report and specially some subsequent messages is still valid with the current version of aptitude (it was at the time, and thanks for providing such a clear case!). Or, even if it's "valid" because the problem persists somewhere, if it's useful to keep around without providing information that can lead to the underlying problems being reproduced and fixed (specially after several years and many changes/fixes in underlying libraries and aptitude itself). So I don't want to close bugs gratuitously, but the problem that you proved reproducible in some of the messages doesn't seem present, or it's not happening with similar test cases now, and the merged bugs do not provide any information either, so keeping them open for a few more years is unlikely to get the problems fixed. I was asking if this still happens in command line mode or some specific command like full or safe-upgrade because I personally don't use that mode very much, except when trying to reproduce people's bugs, and not for my regular package management operations. We have some heavy users of the command line mode which are bug submitters, and that would have probably reported something about this if it's a problem that affects them, but... Cheers. -- Manuel A. Fernandez Montecelo___ Aptitude-devel mailing list Aptitude-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/aptitude-devel
[Aptitude-devel] Bug#638049: aptitude forgets which packages were installed automatically
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi Manuel, On 01/23/16 01:11, Manuel A. Fernandez Montecelo wrote: > Control: tags -1 + moreinfo > > > Hi Harald, > > 2011-08-16 21:07 Harald Dunkel: >> >> (I'd love to have some option in aptitude to mark all installed packages as >> automatically installed, except for those that do not appear on the Depends >> or Recommends list of any installed package. This would make the use of some >> high level meta packages much more interesting.) > > This can be done with patterns. > More info would be welcome. > > Did you keep an eye on this and saw this happening recently? > I just have to look at the list of installed packages. There are some very weird packages that I *surely* did not install on purpose. They were installed via some dependency and lost the "automatically installed" flag later. Samples: libpkcs11-helper1 libwildmidi-config claws-mail-i18n seabios shared-desktop-ontologies geoip-database tons of weird perl package even more weird python packages I am afraid the problem is still in. Regards Harri -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQEcBAEBCAAGBQJWpPhWAAoJEAqeKp5m04HLOtIH/A9nlbYCnToY65aVBCvNjEIO 0yE501QCNMe4GgBPHzdPKWis4MbDr8E+ZFsZLBHVT5COdJ4eTuFWAU+b5Y7z+onm deFQGXn1TaMHxpbAzGTCJiW0noYFto8g1pAsBzjSZIJEbvtwKBmJ4iL7Zvt2bSfL HZ7bX3dKAgb9G+JhWOfOCIRHxMnxiFZ+gc3+VAQaE0FOBgf2TPvCFKWtamPCrV1l GIujNRYJAzxr0vKcZ21C04aL7s/d/jieB+hnshYXRbkvLf3CNtY5nKW9St5beJk1 X3CxbBN1Y+HBfg9KOdaBvXrL7qjaDUECri+9cna0PDAH3AmYyFLS7v4oatEN4Kw= =s+II -END PGP SIGNATURE- ___ Aptitude-devel mailing list Aptitude-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/aptitude-devel
[Aptitude-devel] Bug#638049: aptitude forgets which packages were installed automatically
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 What exactly do you mean by typescript? Harri -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlFEIBcACgkQUTlbRTxpHjeCWwCfaJgiJLowHrQuguY8x79fKnbN M8UAn0sTNuncLAhUvVfI3UUx38zexVyC =JfZa -END PGP SIGNATURE- ___ Aptitude-devel mailing list Aptitude-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/aptitude-devel
[Aptitude-devel] Bug#638049: aptitude forgets which packages were installed automatically
On 16 March 2013 15:32, Harald Dunkel ha...@afaics.de wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 What exactly do you mean by typescript? A terminal session log, such as that produced by the ‘script’ command. For bug reporting, this should be complete enough to demonstrate and reproduce all relevent aspects of the issue. ___ Aptitude-devel mailing list Aptitude-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/aptitude-devel
[Aptitude-devel] Bug#638049: aptitude forgets which packages were installed automatically
On 17 March 2013 02:24, Harald Dunkel ha...@afaics.de wrote: Hi Daniel, I found a procedure to reproduce the problem by installing and removing postgresql. Here is the script: After running it I've got 2 new libraries that should have been removed automatically: Aptitude doesn't show the automatic flag for these libs. Sure, this demonstrates loss or a lack of auto-installed flag. As the two packages are missing this flag, this does not constitute a demonstration of the other issue where an unused, auto-installed package is not removed when it should be. Attached you can find the typescript and the output of dpkg -l, but the snapshots generated by aptitude-create-state-bundle are way too large for EMail and probably for the BTS, too. What would you suggest to transfer these snapshots? State bundles are not informative in this case, and we already have enough diagnostic material concerning this auto-installed issue. Regards ___ Aptitude-devel mailing list Aptitude-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/aptitude-devel
[Aptitude-devel] Bug#638049: aptitude forgets which packages were installed automatically
On Sun, 27 May 2012 22:10:36 +0200 Francesco Poli wrote: [...] I also noticed that sometimes, aptitude says it will purge some packages, but actually leaves them installed (even though scheduled for purging), as in: $ aptitude search ~i | grep ^.p | cut -c 1-35 ip autotools-dev ip hwdata ip libavahi-gobject0 ip libexiv2-9 ip libgnome-desktop-2-17 I am sure I have never manually installed these packages. I will have to manually purge them, to have them actually purged! [...] This is very weird! Please take a look at what happened on one of boxes I administer: # aptitude search ~i | grep ^id | cut -c 1-35 idA gir1.2-clutter-1.0 idA gir1.2-cogl-1.0 idA gir1.2-coglpango-1.0 idA libclutter-1.0-0 idA libcogl-common idA libcogl-pango0 idA libcogl9 # aptitude search ~i | grep ^ip | cut -c 1-35 ip autotools-dev ip gir1.2-gtk-3.0 ip hwdata ip libavahi-gobject0 ip libgnome-desktop-2-17 ip libseed-gtk3-0 # aptitude --purge-unused markauto autotools-dev gir1.2-gtk-3.0 hwdata \ libavahi-gobject0 libgnome-desktop-2-17 libseed-gtk3-0 The following packages will be REMOVED: autotools-dev{ap} hwdata{ap} libavahi-gobject0{ap} libgnome-desktop-2-17{ap} libseed-gtk3-0{ap} 0 packages upgraded, 0 newly installed, 5 to remove and 3 not upgraded. Need to get 0 B of archives. After unpacking 3,041 kB will be freed. Do you want to continue? [Y/n/?] Y ... # aptitude search ~i | grep ^ip | cut -c 1-35 ip gir1.2-clutter-1.0 ip gir1.2-cogl-1.0 ip gir1.2-coglpango-1.0 ip gir1.2-gtk-3.0 ip libclutter-1.0-0 ip libcogl-common ip libcogl-pango0 ip libcogl9 # aptitude --purge-unused markauto gir1.2-clutter-1.0 gir1.2-cogl-1.0 \ gir1.2-coglpango-1.0 gir1.2-gtk-3.0 libclutter-1.0-0 libcogl-common \ libcogl-pango0 libcogl9 The following packages will be REMOVED: gir1.2-clutter-1.0{ap} gir1.2-cogl-1.0{ap} gir1.2-coglpango-1.0{ap} gir1.2-gtk-3.0{ap} libclutter-1.0-0{ap} libcogl-common{ap} libcogl-pango0{ap} libcogl9{ap} 0 packages upgraded, 0 newly installed, 8 to remove and 3 not upgraded. Need to get 0 B of archives. After unpacking 4,981 kB will be freed. Do you want to continue? [Y/n/?] Y ... # aptitude search ~i | grep ^ip | cut -c 1-35 # aptitude search ~i | grep ^id | cut -c 1-35 The weird thing is that the first set of packages (the ones which were initially shown as idA) lost their auto-flag, after the second set of packages (initially shown as ip ) were marked with the auto-flag (and immediately purged). I had to re-set the auto-flag for the first set of packages, in order to see them automatically purged! -- http://www.inventati.org/frx/frx-gpg-key-transition-2010.txt New GnuPG key, see the transition document! . Francesco Poli . GnuPG key fpr == CA01 1147 9CD2 EFDF FB82 3925 3E1C 27E1 1F69 BFFE pgpQM6LylvqEx.pgp Description: PGP signature ___ Aptitude-devel mailing list Aptitude-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/aptitude-devel
[Aptitude-devel] Bug#638049: aptitude forgets which packages were installed automatically
Hi On 28 May 2012 04:10, Francesco Poli invernom...@paranoici.org wrote: I also noticed that sometimes, aptitude says it will purge some packages, but actually leaves them installed (even though scheduled for purging), as in: $ aptitude search ~i | grep ^.p | cut -c 1-35 This is a separate issue and should be reported with a full typescript of the session. Those packages should be removed if you run: # aptitude install After searching on the BTS, it seems to me that there are a good number of bug reports about issues with the auto flag: … I don't know why these reports are not merged together. Maybe they do not describe the same exact bug (even though, after reading all the bug histories, they still look the same issue to me...). More accurately: they exhibit similar /symptoms/. Those reports cover several different activities which cause the auto flag to be altered unexpectedly, it is not clear they all relate to the same underlying issue. While some some overlap is likely, there certainly is multiple issues causing these. A quick look suggests that some are even inconsistent, not bugs, or simply don't contain enough information. But I won't merge or close them without a more thorough investigation. Dear Aptitude Development Team, what can be done to fix this annoying bug (which I would consider more of severity important, than normal)? Direct your efforts to the code and submit a patch. Providing minimal test cases that demonstrate both failures and non-failures to respect the auto flag is also useful. At the very least, if you can reliably reproduce any of these scenarios you should run aptitude-create-state-bundle when your system is in the state *before* the auto-flag has been lost, then provide a typescript moving from that state to demonstrate how the flag is lost. The resulting state bundle and typescript should be made available via http or ftp and a message sent to aptitude-devel@lists.alioth.debian.org ___ Aptitude-devel mailing list Aptitude-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/aptitude-devel