Your message dated Tue, 29 Jan 2019 11:23:34 +0100
with message-id <[email protected]>
and subject line Re: Bug#850417: dpkg: error: dpkg status database is locked by
another process
has caused the Debian Bug report #850417,
regarding dpkg: error: dpkg status database is locked by another process
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
850417: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850417
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: dpkg
Version: 1.18.18
Severity: grave
Justification: renders package unusable
When I tried to upgrade from aptitude:
Performing actions...
Retrieving bug reports... Done
Parsing Found/Fixed information... Done
Retrieving bug reports... Done
Parsing Found/Fixed information... Done
Reading changelogs... Done
apt-listchanges: Do you want to continue? [Y/n]
(Reading database ... 509222 files and directories currently installed.)
Preparing to unpack .../libapt-pkg5.0_1.4~beta3_amd64.deb ...
Unpacking libapt-pkg5.0:amd64 (1.4~beta3) over (1.4~beta2) ...
Setting up libapt-pkg5.0:amd64 (1.4~beta3) ...
dpkg: error: dpkg status database is locked by another process
====== How can you help? (doc: https://wiki.debian.org/how-can-i-help ) ======
----- Show old opportunities as well as new ones: how-can-i-help --old -----
E: Sub-process /usr/bin/dpkg returned an error code (2)
Processing triggers for libc-bin (2.24-8) ...
Press Return to continue, 'q' followed by Return to quit.
The only other process matching apt and dpkg is aptitude itself.
-- System Information:
Debian Release: stretch/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500,
'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.8.0-2-amd64 (SMP w/12 CPU cores)
Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages dpkg depends on:
ii libbz2-1.0 1.0.6-8
ii libc6 2.24-8
ii liblzma5 5.2.2-1.2
ii libselinux1 2.6-3
ii tar 1.29b-1.1
ii zlib1g 1:1.2.8.dfsg-4
dpkg recommends no packages.
Versions of packages dpkg suggests:
ii apt 1.4~beta2
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 1.19.1
Hi!
On Thu, 2017-07-27 at 01:17:33 +0100, Vincent Lefevre wrote:
> To make things clear in this bug, this bug has been confirmed:
>
> https://lists.debian.org/debian-dpkg/2017/01/msg00044.html
>
> (as referenced in bug 869546).
And this got merged in 1.19.1 with the following changelog entry, but
missing the bug closures (which I've ammended now locally):
,---
* Add support for frontend locking. This makes it possible for frontends
using this new protocol, to safely lock the dpkg database w/o risk of
race conditions with other dpkg instances or frontends supporting the
same protocol. Thanks to Julian Andres Klode <[email protected]>.
`---
Thus closing now.
Thanks,
Guillem
--- End Message ---
