Bug#432017: Aptitude forgets about automatically installed status on upgrade.
Another thing which seems to reliably lose state: - setup apt-listchanges to show changelogs and prompt for confirmation - start an upgrade which would remove some now unused packages - answer 'n' to the apt-listchanges prompt The packages that would have been removed have now lost automatic status, and will not be removed if you restart the upgrade. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#432017: Aptitude forgets about automatically installed status on upgrade.
Hi. I can confirm this bug and provide another way to reproduce it: 1) Select some AutoInstalled packages for upgrade, 2) Press 'g' to run the package upgrade, 3) When apt-listbugs shows the list, reply 'n' so it aborts, 4) Upon return to the Package List view, the AutoInstall flag is reset for all the packages selected for upgrade. Will gladly provide more info if needed, -- Pablo 'merKur' Kohan [EMAIL PROTECTED] Ximpo Group Ltd. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#432017: Aptitude forgets about automatically installed status on upgrade.
On Mon, Jul 16, 2007 at 06:52:42PM +0200, Artur R. Czechowski [EMAIL PROTECTED] was heard to say: On Sun, Jul 08, 2007 at 08:08:26PM -0700, Daniel Burrows wrote: I would just break on all the calls to MarkAuto that don't pass true; if none of them trip, you probably found a bug in apt (since that should be the only thing that can disable auto-ness of a package). I run aptitude under gdb, manually set all upgradable packages into proper auto state, put a breakpoint on: pkgDepCache::MarkAuto(pkgCache::PkgIterator const, bool) and run update. Autoinstalled status has been unset and there was no breakpoint hit. BTW, just so everyone reading this bug is aware, it should be fixed with this changeset: changeset: 746:12d79eb74626 user:Daniel Burrows [EMAIL PROTECTED] date:Mon Jul 09 17:10:09 2007 -0700 summary: Run a mark-and-sweep to initialize garbage states on startup, so the apt code to handle the auto flag works properly. Daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#432017: Aptitude forgets about automatically installed status on upgrade.
The workaround suggested by Linas Žvirblis also works for me (though I find that there's no need to quit aptitude between steps 2 and 3) on both of i386 and amd64 platforms.
Bug#432017: Aptitude forgets about automatically installed status on upgrade.
Hi, On Sun, Jul 08, 2007 at 08:08:26PM -0700, Daniel Burrows wrote: I would just break on all the calls to MarkAuto that don't pass true; if none of them trip, you probably found a bug in apt (since that should be the only thing that can disable auto-ness of a package). I run aptitude under gdb, manually set all upgradable packages into proper auto state, put a breakpoint on: pkgDepCache::MarkAuto(pkgCache::PkgIterator const, bool) and run update. Autoinstalled status has been unset and there was no breakpoint hit. Regards Artur -- - You can take my soul but not my lack of enthusiasm. /Wally, Dilbert 2004.11.23/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#432017: Aptitude forgets about automatically installed status on upgrade.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I can also confirm this. Situation: a lot of packages available for upgrade, some of them manually, and some automatically installed. Step 1: Mark all packages for upgrade; Step 2: Quit aptitude and start it again; Result: All upgradeable packages have state iu; Now comes the interesting part. Step 3: Mark all upgradeable packages auto-installed iuA; Step 4: Put all of them on hold; Result: The states are back to what they were before step 1. Note that this happens even though I marked all of them auto-installed. This does not seem to work if you mark only some of the packages (the marked ones still loose the state), or if you mark them on by one (you have to mark the section title (or whatever it is called) for upgrade). So it seems that the states are not forgotten, but rather the information about the sates is displayed incorrectly. Also this seems to be specific to 64-bit platforms, as everyone who can confirm this and included system information, are running 64-bit systems. Package: aptitude Version: 0.4.5.4-1 - -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.22-rc7-git3.666.1 (SMP w/2 CPU cores; PREEMPT) Locale: LANG=lt_LT.UTF-8, LC_CTYPE=lt_LT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages aptitude depends on: ii apt [libapt-pkg-libc6.5 0.7.3 ii libc6 2.6-1 ii libgcc1 1:4.2-20070707-1 ii libncursesw55.6-3 ii libsigc++-2.0-0c2a 2.0.17-2 ii libstdc++6 4.2-20070707-1 Versions of packages aptitude recommends: pn aptitude-doc-en | aptitude-do none ii libparse-debianchangelog-perl 1.0-1 - -- no debconf information -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGklaNztOe9mov/y4RAl3mAJ9ac+bzUKJv6Ci5yPkJfTCihF0lEgCfdkF2 eSPvW0I60EiOxDzXzZEi6VY= =Rh3S -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#432017: Aptitude forgets about automatically installed status on upgrade.
On Fri, Jul 06, 2007 at 08:11:04PM +0200, Artur R. Czechowski [EMAIL PROTECTED] was heard to say: I noticed that all packages with newer version available have cleared automatically installed flag. Even setting this flag manually, exiting aptitude and running it again does not help. Could you provide more information? It works fine for me. Daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#432017: Aptitude forgets about automatically installed status on upgrade.
On Sun, Jul 08, 2007 at 11:00:46AM -0700, Daniel Burrows wrote:
On Fri, Jul 06, 2007 at 08:11:04PM +0200, Artur R. Czechowski [EMAIL
PROTECTED] was heard to say:
I noticed that all packages with newer version available have cleared
automatically installed flag. Even setting this flag manually, exiting
aptitude and running it again does not help.
Could you provide more information?
Sure. But I am not sure what exactly you need.
Version of aptitude and dependecies you have in initial submission.
System is current unstable amd64.
Configuration of apt:
szczaw:/etc/apt/apt.conf.d# ls
01autoremove 01local-apt-limit 20listchanges
01cron11resolvingdeps70debconf
szczaw:/etc/apt/apt.conf.d# grep . *
01autoremove:APT
01autoremove:{
01autoremove: NeverAutoRemove
01autoremove: {
01autoremove: ^linux-image.*;
01autoremove: ^linux-restricted-modules.*;
01autoremove: };
01autoremove:};
01cron:APT::Archives::MaxAge 30;
01cron:APT::Archives::MinAge 5;
01local-apt-limit://Acquire::http::Dl-Limit 45;
01local-apt-limit://Acquire::http::Dl-Limit 15;
11resolvingdeps:Aptitude::ProblemResolver::Discard-Null-Solution false;
20listchanges:DPkg::Pre-Install-Pkgs { /usr/bin/apt-listchanges --apt ||
test $? -ne 10; };
20listchanges:DPkg::Tools::Options::/usr/bin/apt-listchanges::Version 2;
70debconf:// Pre-configure all packages with debconf before they are
installed.
70debconf:// If you don't like it, comment it out.
70debconf:DPkg::Pre-Install-Pkgs {/usr/sbin/dpkg-preconfigure --apt ||
true;};
Note: removing all files from apt.conf.d except 20listchanges and 70debconf
does not help with solving the problem.
My sources.list:
deb http://http.us.debian.org/debian unstable main contrib non-free
deb-src http://http.us.debian.org/debian unstable main contrib non-free
/etc/apt/sources.list.d/ is empty.
To replicate the bug I manually downgrade libxcursor1 from 1:1.1.8-2 to
1.1.7-4.
szczaw:/var/lib/apt# dpkg -l libxcursor1
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err:
|uppercase=bad)
||/ Name VersionDescription
+++-==-==-
ii libxcursor11.1.7-4X cursor management library
szczaw:/var/lib/apt# grep -A 2 libxcursor1 extended_states
Package: libxcursor1
Auto-Installed: 1
Then I run aptitude. The libxcursor1 is marked to upgrade from 1.1.7-4
to 1:1.1.8-2, but without A status in 3rd column. Additionaly:
szczaw:/var/lib/apt# grep -A 2 libxcursor1 extended_states
Package: libxcursor1
Auto-Installed: 0
When I manually mark the package as an automatically installed and quit
aptitude, the extended_states is updated correctly:
szczaw:/var/lib/apt# grep -A 2 libxcursor1 extended_states
Package: libxcursor1
Auto-Installed: 1
but after another run of aptitude there is again Auto-Installed: 0
Entry from /var/lib/aptitude/pkgstates:
Package: libxcursor1
Unseen: no
State: 1
Dselect-State: 1
Remove-Reason: 4
Upgrade: yes
does not change during the procedure, except the Upgrade: yes addition.
After setting
Debug {
pkgAutoRemove true;
pkgDepCache::AutoInstall true;
}
and run:
aptitude
mark package as autoinstalled
quit
there are following lines about libxcursor1 in the output:
Update exisiting AutoInstall info: libxcursor1
AutoDep: libxcursor1
AutoDep: libxcursor1
Update exisiting AutoInstall info: libxcursor1
Skipping already written libxcursor1
BTW, after I mark the package as autoinstalled and continue with upgrade
(presing GG) package remains as autoinstalled. Until next upgrade of the
package...
I can trace the aptitude with gdb, but I'll be glad for any hints where
I should focus.
BTW, I've found #431737 in apt - maybe my problem is related to this bug.
Best regards
Artur
--
Documentation is like sex: When it is good, it is very, very, good.
And when it is bad, it is better than nothing.
/Dick Brandon/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#432017: Aptitude forgets about automatically installed status on upgrade.
On Sun, Jul 08, 2007 at 11:00:16PM +0200, Artur R. Czechowski [EMAIL PROTECTED] was heard to say: On Sun, Jul 08, 2007 at 11:00:46AM -0700, Daniel Burrows wrote: Then I run aptitude. The libxcursor1 is marked to upgrade from 1.1.7-4 to 1:1.1.8-2, but without A status in 3rd column. Additionaly: szczaw:/var/lib/apt# grep -A 2 libxcursor1 extended_states Package: libxcursor1 Auto-Installed: 0 When I manually mark the package as an automatically installed and quit aptitude, the extended_states is updated correctly: szczaw:/var/lib/apt# grep -A 2 libxcursor1 extended_states Package: libxcursor1 Auto-Installed: 1 but after another run of aptitude there is again Auto-Installed: 0 So you're saying that if you mark the package as auto, then run aptitude again, the auto flag gets cleared? I can trace the aptitude with gdb, but I'll be glad for any hints where I should focus. There are exactly 8 places in the code that invoke MarkAuto. Two of them always set the auto flag to true, a third is only invoked on undo, three more are invoked only when you change the state of a package, and the last is the internal interface for other code in aptitude to invoke. The internal interface is invoked 5 times, and all of them should be in response to user input. I would just break on all the calls to MarkAuto that don't pass true; if none of them trip, you probably found a bug in apt (since that should be the only thing that can disable auto-ness of a package). Daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#432017: Aptitude forgets about automatically installed status on upgrade.
Package: aptitude Version: 0.4.5.4-1 Severity: important Hello, I noticed that all packages with newer version available have cleared automatically installed flag. Even setting this flag manually, exiting aptitude and running it again does not help. Best regards Artur -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.21-1-amd64 (SMP w/1 CPU core) Locale: LANG=C, LC_CTYPE=pl_PL (charmap=ISO-8859-2) Shell: /bin/sh linked to /bin/bash Versions of packages aptitude depends on: ii apt [libapt-pkg-libc6.5 0.7.3Advanced front-end for dpkg ii libc6 2.5-11 GNU C Library: Shared libraries ii libgcc1 1:4.2-20070627-1 GCC support library ii libncursesw55.6-3Shared libraries for terminal hand ii libsigc++-2.0-0c2a 2.0.17-2 type-safe Signal Framework for C++ ii libstdc++6 4.2-20070627-1 The GNU Standard C++ Library v3 Versions of packages aptitude recommends: pn aptitude-doc-en | aptitude-do none (no description available) ii libparse-debianchangelog-perl 1.0-1 parse Debian changelogs and output -- no debconf information -- Documentation is like sex: When it is good, it is very, very, good. And when it is bad, it is better than nothing. /Dick Brandon/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
