Bug#869546: apt fails updating itself
Control: severity -1 normal
Control: found -1 0.7.16
Control: block -1 by 850417
On Mon, Jul 24, 2017 at 08:32:16AM +0200, Michael Kauffmann wrote:
> Package: apt
> Version: 1.4.7
> Severity: grave
> Justification: renders package unusable
*Way* too much.
>
> Dear Maintainer,
>
> when doing apt-get upgrade to 9.1:
>
> >Unpacking apt (1.4.7) over (1.4.6) ...
> >Setting up apt (1.4.7) ...
> >dpkg: error: dpkg status database is locked by another process
> >E: Sub-process /usr/bin/dpkg returned an error code (2)
There is a race condition in the code, something else was locking
dpkg while apt tried to run it. Like the daily upgrade service or
something.
This exists since the dawn of time (which for the bts seems
to be 0.7.16).
See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850417
and https://lists.debian.org/debian-dpkg/2017/01/msg00044.html
for more details.
>
> Next call :
>
> >The following packages have unmet dependencies:
> > apt-utils : Depends: apt (= 1.4.6) but 1.4.7 is installed
> > E: Unmet dependencies. Try 'apt --fix-broken install' with no packages
> > root@bw:~# apt --fix-broken install
> > Correcting dependencies... Done
> > The following additional packages will be installed:
> > apt-utils
> > The following packages will be upgraded:
> > apt-utils
> > 1 upgraded, 0 newly installed, 0 to remove and 31 not upgraded.
> > 4 not fully installed or removed.
>
> Workarounded by settig apt on hold.
You don't need to hold anything. This is not a bug.
--
Debian Developer - deb.li/jak | jak-linux.org - free software dev
| Ubuntu Core Developer |
When replying, only quote what is necessary, and write each reply
directly below the part(s) it pertains to ('inline'). Thank you.
Reply to: