[Aptitude-devel] Bug#748449: aptitude: inconsistency around "become root" when openning the packages database read-only as root

Manuel A. Fernandez Montecelo manuel.montezelo at gmail.com
Wed Feb 17 12:05:59 GMT 2016


2014-05-17 12:32 Yann Dirson:
>Package: aptitude
>Version: 0.6.10-1
>Severity: normal
>
>Launching aptitude (as root) while a dpkg is running results in a
>message saying the packages db is openned RO (that's expected), and
>says that no changes will be saved until I select "become root" (that
>is slightly awkward, but still understandable from my point of view).

To help to find the region of code in the future, in curses the messages
are:

   | E: Could not get lock /var/lib/dpkg/lock - open (11: Resource
   |    temporarily unavailable)
   |
   | E: Unable to lock the administration directory (/var/lib/dpkg/), is
   |    another process using it?
   |
   | W: Could not lock the cache file; this usually means that dpkg or
   |     another apt tool is already installing packages.  Opening in
   |     read-only mode; any changes you make to the states of packages
   |     will NOT be preserved!

-- 
Manuel A. Fernandez Montecelo <manuel.montezelo at gmail.com>



More information about the Aptitude-devel mailing list