Package: aptitude
Version: 0.6.1.5-3
Severity: normal
When issuing the following commands:
aptitude update; echo; aptitude -dyq --purge-unused safe-upgrade
I get:
many Get lines
Fetched 302kB in 1min 25s (3532B/s)
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
Reading extended state information...
Initializing package states...
mount: /usr is busy
No packages will be installed, upgraded, or removed.
0 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 0B of archives. After unpacking 0B will be used.
E: Problem executing scripts DPkg::Post-Invoke 'mount -o remount,ro /usr'
E: Sub-process returned an error code
A package failed to install. Trying to recover:
dpkg: status database area is locked by another process
Reading package lists...
Building dependency tree...
Reading state information...
Reading extended state information...
Initializing package states...
There is a problem to remount /usr ro that is not related to aptitude.
Still, the dpkg process that is running is probably a child process of aptitude.
Aren't they suppose to communicate better, and avoid trying to remove a lock
that was placed by the other process? I am using these commands for years.
Only lately dpkg has started to warn about the lock that was placed by the other
process.
_________________________________________________________________
Hotmail: Powerful Free email with security by Microsoft.
https://signup.live.com/signup.aspx?id=60969
