Debian Bug report logs - #940961
aptitude: upgrade of apt is not smooth

version graph

Package: aptitude; Maintainer for aptitude is Aptitude Development Team <[email protected]>; Source for aptitude is src:aptitude (PTS, buildd, popcon).

Reported by: Oswald Buddenhagen <[email protected]>

Date: Sun, 22 Sep 2019 16:21:02 UTC

Severity: important

Merged with 933335

Found in versions aptitude/0.8.11-7, aptitude/0.8.13-5, aptitude/0.8.12-3, aptitude/0.8.13-1, aptitude/0.8.12-1, aptitude/0.8.13-3, aptitude/0.8.13-2

Reply or subscribe to this bug.

View this report as an mbox folder, status mbox, maintainer mbox


Report forwarded to [email protected], Aptitude Development Team <[email protected]>:
Bug#940961; Package aptitude. (Sun, 22 Sep 2019 16:21:04 GMT) (full text, mbox, link).


Acknowledgement sent to Oswald Buddenhagen <[email protected]>:
New Bug report received and forwarded. Copy sent to Aptitude Development Team <[email protected]>. (Sun, 22 Sep 2019 16:21:04 GMT) (full text, mbox, link).


Message #5 received at [email protected] (full text, mbox, reply):

From: Oswald Buddenhagen <[email protected]>
To: Debian Bug Tracking System <[email protected]>
Subject: aptitude: upgrade of apt is not smooth
Date: Sun, 22 Sep 2019 14:39:10 +0200
Package: aptitude
Version: 0.8.12-1
Severity: normal

while upgrading apt from within aptitude, i got this error:

[...]
Setting up libapt-pkg5.0:amd64 (1.8.4) ...
(Reading database ... 316101 files and directories currently installed.)
Preparing to unpack .../libapt-inst2.0_1.8.4_amd64.deb ...
Unpacking libapt-inst2.0:amd64 (1.8.4) over (1.8.3) ...
Preparing to unpack .../archives/apt_1.8.4_amd64.deb ...
Unpacking apt (1.8.4) over (1.8.3) ...
dpkg: error: dpkg frontend lock is locked by another process
/etc/cron.daily/apt-compat.dpkg-new
/etc/kernel/postinst.d/apt-auto-removal.dpkg-new
/etc/apt/apt.conf.d/01autoremove.dpkg-new
/etc/logrotate.d/apt.dpkg-new
/etc/ld.so.conf.d/zz_i386-biarch-compat.conf.dpkg-new
E: Sub-process /usr/bin/dpkg returned an error code (2)
dpkg: error: dpkg frontend lock is locked by another process
Press Return to continue, 'q' followed by Return to quit.

however, immediately trying again (apparently) resolved the issue:

Preconfiguring packages ...
Setting up apt (1.8.4) ...
(Reading database ... 316101 files and directories currently installed.)
Preparing to unpack .../apt-utils_1.8.4_amd64.deb ...
[...]

-- Package-specific info:
Terminal: xterm
$DISPLAY is set.
which aptitude: /usr/bin/aptitude

aptitude version information:
aptitude 0.8.12
Compiler: g++ 9.2.1 20190821
Compiled against:
  apt version 5.0.2
  NCurses version 6.1
  libsigc++ version: 2.10.1
  Gtk+ support disabled.
  Qt support disabled.

Current library versions:
  NCurses version: ncurses 6.1.20190803
  cwidget version: 0.5.18
  Apt version: 5.0.2

aptitude linkage:
	linux-vdso.so.1 (0x00007ffd1b0d5000)
	libapt-pkg.so.5.0 => /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0 (0x00007fa6bf1bf000)
	libncursesw.so.6 => /lib/x86_64-linux-gnu/libncursesw.so.6 (0x00007fa6bf184000)
	libtinfo.so.6 => /lib/x86_64-linux-gnu/libtinfo.so.6 (0x00007fa6bf154000)
	libsigc-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libsigc-2.0.so.0 (0x00007fa6bf14b000)
	libcwidget.so.4 => /usr/lib/x86_64-linux-gnu/libcwidget.so.4 (0x00007fa6bf045000)
	libsqlite3.so.0 => /usr/lib/x86_64-linux-gnu/libsqlite3.so.0 (0x00007fa6bef21000)
	libboost_iostreams.so.1.67.0 => /usr/lib/x86_64-linux-gnu/libboost_iostreams.so.1.67.0 (0x00007fa6bef01000)
	libxapian.so.30 => /usr/lib/x86_64-linux-gnu/libxapian.so.30 (0x00007fa6bece8000)
	libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007fa6becc7000)
	libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007fa6beaee000)
	libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007fa6be9a9000)
	libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007fa6be98f000)
	libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007fa6be7cd000)
	libresolv.so.2 => /lib/x86_64-linux-gnu/libresolv.so.2 (0x00007fa6be7b5000)
	libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x00007fa6be798000)
	libbz2.so.1.0 => /lib/x86_64-linux-gnu/libbz2.so.1.0 (0x00007fa6be785000)
	liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5 (0x00007fa6be75c000)
	liblz4.so.1 => /usr/lib/x86_64-linux-gnu/liblz4.so.1 (0x00007fa6be73d000)
	libzstd.so.1 => /usr/lib/x86_64-linux-gnu/libzstd.so.1 (0x00007fa6be693000)
	libudev.so.1 => /lib/x86_64-linux-gnu/libudev.so.1 (0x00007fa6be668000)
	libsystemd.so.0 => /lib/x86_64-linux-gnu/libsystemd.so.0 (0x00007fa6be5c1000)
	/lib64/ld-linux-x86-64.so.2 (0x00007fa6bf81b000)
	libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007fa6be5bc000)
	librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007fa6be5b1000)
	libuuid.so.1 => /lib/x86_64-linux-gnu/libuuid.so.1 (0x00007fa6be5a6000)
	libgcrypt.so.20 => /lib/x86_64-linux-gnu/libgcrypt.so.20 (0x00007fa6be489000)
	libgpg-error.so.0 => /lib/x86_64-linux-gnu/libgpg-error.so.0 (0x00007fa6be466000)

-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-6-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages aptitude depends on:
ii  aptitude-common           0.8.12-1
ii  libapt-pkg5.0             1.8.4
ii  libboost-iostreams1.67.0  1.67.0-13
ii  libc6                     2.29-2
ii  libcwidget4               0.5.18-5
ii  libgcc1                   1:9.2.1-8
ii  libncursesw6              6.1+20190803-1
ii  libsigc++-2.0-0v5         2.10.1-2
ii  libsqlite3-0              3.29.0-2
ii  libstdc++6                9.2.1-8
ii  libtinfo6                 6.1+20190803-1
ii  libxapian30               1.4.12-1

Versions of packages aptitude recommends:
ii  libparse-debianchangelog-perl  1.2.0-13
ii  sensible-utils                 0.0.12

Versions of packages aptitude suggests:
ii  apt-xapian-index                0.50
pn  aptitude-doc-en | aptitude-doc  <none>
pn  debtags                         <none>
pn  tasksel                         <none>

-- no debconf information



Information forwarded to [email protected], Aptitude Development Team <[email protected]>:
Bug#940961; Package aptitude. (Wed, 02 Oct 2019 17:42:02 GMT) (full text, mbox, link).


Acknowledgement sent to Sven Joachim <[email protected]>:
Extra info received and forwarded to list. Copy sent to Aptitude Development Team <[email protected]>. (Wed, 02 Oct 2019 17:42:02 GMT) (full text, mbox, link).


Message #10 received at [email protected] (full text, mbox, reply):

From: Sven Joachim <[email protected]>
To: Oswald Buddenhagen <[email protected]>
Cc: [email protected]
Subject: Re: Bug#940961: aptitude: upgrade of apt is not smooth
Date: Wed, 02 Oct 2019 19:39:04 +0200
Control: forcemerge 933335 -1

Am 22.09.2019 um 14:39 schrieb Oswald Buddenhagen:

> Package: aptitude
> Version: 0.8.12-1
> Severity: normal
>
> while upgrading apt from within aptitude, i got this error:
>
> [...]
> Setting up libapt-pkg5.0:amd64 (1.8.4) ...
> (Reading database ... 316101 files and directories currently installed.)
> Preparing to unpack .../libapt-inst2.0_1.8.4_amd64.deb ...
> Unpacking libapt-inst2.0:amd64 (1.8.4) over (1.8.3) ...
> Preparing to unpack .../archives/apt_1.8.4_amd64.deb ...
> Unpacking apt (1.8.4) over (1.8.3) ...
> dpkg: error: dpkg frontend lock is locked by another process

This appears to be the same problem as #933335.  Quoting dpkg maintainer
Guillem Jover:

> This is a problem with aptitude, which I'm told has not been modified
> to make use of the new frontend locks, so it suffers from the
> historical race conditions when more than one frontend are running
> concurrently.

Cheers,
       Sven



Severity set to 'important' from 'normal' Request was from Sven Joachim <[email protected]> to [email protected]. (Wed, 02 Oct 2019 17:42:03 GMT) (full text, mbox, link).


Marked as found in versions aptitude/0.8.11-7. Request was from Sven Joachim <[email protected]> to [email protected]. (Wed, 02 Oct 2019 17:42:03 GMT) (full text, mbox, link).


Merged 933335 940961 Request was from Sven Joachim <[email protected]> to [email protected]. (Wed, 02 Oct 2019 17:42:04 GMT) (full text, mbox, link).


Marked as found in versions aptitude/0.8.12-3. Request was from Vincent Lefevre <[email protected]> to [email protected]. (Sat, 16 May 2020 22:27:04 GMT) (full text, mbox, link).


Marked as found in versions aptitude/0.8.13-1. Request was from Vincent Lefevre <[email protected]> to [email protected]. (Wed, 29 Jul 2020 08:54:06 GMT) (full text, mbox, link).


Marked as found in versions aptitude/0.8.13-2. Request was from Vincent Lefevre <[email protected]> to [email protected]. (Thu, 26 Nov 2020 21:27:03 GMT) (full text, mbox, link).


Marked as found in versions aptitude/0.8.13-3. Request was from Vincent Lefevre <[email protected]> to [email protected]. (Thu, 13 Jan 2022 01:03:03 GMT) (full text, mbox, link).


Marked as found in versions aptitude/0.8.13-5. Request was from Vincent Lefevre <[email protected]> to [email protected]. (Fri, 26 May 2023 01:27:03 GMT) (full text, mbox, link).


Send a report that this bug log contains spam.


Debian bug tracking system administrator <[email protected]>. Last modified: Tue May 13 15:52:02 2025; Machine Name: bembo

Debian Bug tracking system

Debbugs is free software and licensed under the terms of the GNU General Public License version 2. The current version can be obtained from https://bugs.debian.org/debbugs-source/.

Copyright © 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson, 2005-2017 Don Armstrong, and many other contributors.