Re: upgrade to debian 1.3
On Apr 29, Danny ter Haar wrote
> During the upgrade i saw the following message:
>
> Update-menus: Dpkg is locking dpkg status area: forking to background
> and wait for /var/lib/dpkg/lock to become unlocked.
> Setting up lynx (2.7-2) ...
>
> Configuration file `/etc/lynx.cfg'
[...]
> The default action is to keep your current version.
> *** lynx.cfg (Y/I/N/O/Z) [default=N] ? unable to lock dpkg status
> database(/var/lib/dpkg/lock)
> This means your system is messed up badly. Aborting.
> Somebody can shed some light on this ?
Just a guess (Joost, please comment): update-menus is expensive to run, so
it was modified not to run for each individual package install, but for each
dpkg install session. This was done by some form of waiting until dpkg's
lock was removed, and then locking it for update-menus. Your example shows
that this does (unfortunately) not indicate that the dpkg run is complete,
and that this interferes with normal dpkg operation.
Maybe this is a solution: let update-menus use a lock file of its own to
prevent concurrent runs, and have the single active run wait until dpkg's
lock file is gone before doing the expensive operations?
Greetings,
Ray
--
ART A friend of mine in Tulsa, Okla., when I was about eleven years old.
I'd be interested to hear from him. There are so many pseudos around taking
his name in vain.
- The Hipcrime Vocab by Chad C. Mulligan
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-user-request@lists.debian.org .
Trouble? e-mail to templin@bucknell.edu .
Reply to: