Bug#313417: aptitude: Does not remember package selection after install failure
On 2005-06-13 at 14:57 -0400, Daniel Burrows wrote: ... and when you start it, a big red dialog box appears with the message: W: Warning: could not lock the cache file. Opening in read-only mode Perhaps it should be doing that, but it certainly doesn't here. Maybe there's a configuration option that toggles that behaviour? I can't find one though. Is there anything I can do to trace why that might not be happening? However, that's not really the main thrust of the bug report: that was just example to recreate the bug. The point is that if aptitude cannot install packages for whatever reason (out of disk space, DB not lockable, a conflict, etc.), then it should retain the selections one has made: it's irritating to have them lost because of a problem with (potentially) just one package. Since this is a usability bug, though, I've no objections if you want to lower it to minor rather than normal. Thanks, Andrew. -- Andrew Ferrier mobile: +44 (0) 7968 147953 web: http://www.new-destiny.co.uk/andrew/ email: [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#313417: aptitude: Does not remember package selection after install failure
retitle 313417 Print a more explicit message when the state file is locked severity 313417 minor thanks On Tuesday 14 June 2005 06:32 am, Andrew Ferrier wrote: The point is that if aptitude cannot install packages for whatever reason (out of disk space, DB not lockable, a conflict, etc.), then it should retain the selections one has made: it's irritating to have them lost because of a problem with (potentially) just one package. It should always do that *unless* it happens to be operating in read-only mode due to another process having a lock on its state file [0]. Being in read-only mode (or whatever you want to call it) means exactly that changes to package states won't be preserved. Daniel [0] technically there is one other case: if it fails to write the new package selections due to something like a full disk, then of course you won't have them available, but obviously I can't magically create more disk space to save data :) -- /--- Daniel Burrows [EMAIL PROTECTED] --\ | After the game, the king and| | the pawn go in the same box.| | -- Italian proverb| \ The Turtle Moves! -- http://www.lspace.org ---/ pgpaEoc1hjKji.pgp Description: PGP signature
Bug#313417: aptitude: Does not remember package selection after install failure
Package: aptitude Version: 0.2.15.9-2 Severity: normal To recreate: 1. Lock the dpkg database e.g. open a terminal, do apt-get install apackagename, and leave it sitting at the [Y/n] prompt. 2. Open another terminal, run aptitude. Select a single package to install and hit 'g'. The package is downloaded but then fails to install with the message 'dpkg: status database area is locked by another process'. This is OK. 3. Hit return. On the return to aptitude, the selected package is no longer selected. This is a big pain when selecting a whole bunch of packages for install/upgrade/purging or some combination of those, as when it doesn't work (which I think could be for any reason, not just the recreate example above), all your selections are lost. I consider this to be a usability bug; I was surprised that it wasn't already reported, but I couldn't find it in the open list of bugs. Thanks for your work on aptitude, it's a good tool! Regards, Andrew. -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (900, 'testing'), (800, 'unstable'), (50, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.10 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages aptitude depends on: ii apt [libapt-pkg-libc6.3-5-3 0.5.28.6 Advanced front-end for dpkg ii libc6 2.3.2.ds1-22 GNU C Library: Shared libraries an ii libgcc1 1:3.4.3-13 GCC support library ii libncurses5 5.4-4Shared libraries for terminal hand ii libsigc++-1.2-5c102 1.2.5-4 type-safe Signal Framework for C++ ii libstdc++5 1:3.3.5-13 The GNU Standard C++ Library v3 -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#313417: aptitude: Does not remember package selection after install failure
On Monday 13 June 2005 11:21 am, Andrew Ferrier wrote: Package: aptitude Version: 0.2.15.9-2 Severity: normal To recreate: 1. Lock the dpkg database e.g. open a terminal, do apt-get install apackagename, and leave it sitting at the [Y/n] prompt. 2. Open another terminal, run aptitude. ... and when you start it, a big red dialog box appears with the message: W: Warning: could not lock the cache file. Opening in read-only mode I guess the implications of this might not be obvious, so I'll make the message more explicit: W: Could not lock the cache file. Opening in read-only mode; any changes you make to the states of packages will NOT be preserved! Daniel -- /--- Daniel Burrows [EMAIL PROTECTED] --\ |Note that fires are not restricted to dormitories.| | Indeed, fire can occur in off-campus residences as well. | | -- Brown University Fire Safety Guide| \ The Turtle Moves! -- http://www.lspace.org ---/ pgpMbJIVq5B4D.pgp Description: PGP signature
