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
