Bug#1070027: in package dpkg marked as pending

On 2024-07-25 11:49:42 +0200, Vincent Lefevre wrote: > The reload is triggered with just > > dpkg -i /var/cache/apt/archives/dpkg_1.22.9_amd64.deb > > so aptitude and even apt aren't even involved in this bug: > > Jul 25 11:47:56 qaa systemd[1]: Reload requested f

Bug#1070027: in package dpkg marked as pending

Control: retitle -1 dpkg failure at "Setting up" due to dpkg frontend lock by apt-get via apt-daily.service On 2024-07-25 11:03:50 +0200, Vincent Lefevre wrote: > According to the journalctl output: > > Jul 25 10:30:36 qaa systemd[1]: Reload requested from client PID 32

Bug#1070027: in package dpkg marked as pending

Control: reopen -1 Control: severity -1 important On 2024-07-11 00:49:20 +0200, Guillem Jover wrote: > libdpkg: Try to print the executable name of the lock contending process > > Just printing the PID is not very useful to try to track down the > contending process as its presence might be

Bug#1070027: fdisk: dependency problems prevent configuration of fdisk

Hi, On 2024-06-03 00:38:01 +0200, Guillem Jover wrote: > Hi! > > On Mon, 2024-04-29 at 04:37:18 +0200, Vincent Lefevre wrote: > > On 2024-04-29 03:05:50 +0200, Guillem Jover wrote: > > > I don't think dpkg is at fault here, I assume something else is either > > >

Bug#1070027: fdisk: dependency problems prevent configuration of fdisk

On 2024-04-29 03:05:50 +0200, Guillem Jover wrote: > I don't think dpkg is at fault here, I assume something else is either > getting activated in the middle of the transaction while the package > manager frontend driving dpkg has released the lock (which it should > not), or the package manager

Bug#1070027: fdisk: dependency problems prevent configuration of fdisk

Here's the /var/log/apt/history.log part that corresponds to this upgrade: Start-Date: 2024-04-28 22:05:30 Upgrade: libsmartcols1:amd64 (2.40-6, 2.40-8), libvpx8:amd64 (1.13.1-2, 1.13.1-2+b1), libltdl7:amd64 (2.4.7-7, 2.4.7-7+b1), libpaper1:amd64 (1.1.29, 1.1.29+b1), libnftnl11:amd64 (1.2.6-2,

Bug#1065429: dpkg -s: spurious error "dpkg-query: error: --status needs a valid package name"

On 2024-03-07 03:34:08 +0100, Guillem Jover wrote: > > "apt-cache show libc6-dev" also lists this package. > > apt behaves differently, this has been also a known discrepancy, but > then they operate in general differently when it comes to their CLI > arguments anyway. The difference is bad for

Bug#1065429: dpkg -s: spurious error "dpkg-query: error: --status needs a valid package name"

On 2024-03-04 13:47:00 +0100, Vincent Lefevre wrote: > I get the following error: > > cventin:~> dpkg -s libc6-dev > dpkg-query: error: --status needs a valid package name but 'libc6-dev' is > not: ambiguous package name 'libc6-dev' with more than one installed instance

Bug#1065429: dpkg -s: spurious error "dpkg-query: error: --status needs a valid package name"

Package: dpkg Version: 1.22.5 Severity: important I get the following error: cventin:~> dpkg -s libc6-dev dpkg-query: error: --status needs a valid package name but 'libc6-dev' is not: ambiguous package name 'libc6-dev' with more than one installed instance while this is a valid package name:

Bug#770301: dpkg: fails to install second arch of Multi-Arch:same packages with Provides/Conflicts/Replaces:virtualpackage

Hi, On 2014-11-21 04:56:02 +0100, Guillem Jover wrote: > Oh, so it does. :( I've started looking into fixing this, but I'll > have to ponder about it to maybe change the behavior the other way > around :/, because as it stands, and as pointed out by Johannes > off-BTS there are at least 114

Bug#923423: dpkg: Hangs for 19 mins installing texlive-fonts-extra

Control: reopen -1 On 2022-10-14 02:26:20 +0200, Guillem Jover wrote: > All these fsync()s you see in rapid succession are used as a > synchronization points, way after the data has been requested to be > synced to disk asynchronously via sync_file_range(). I don't know why, but what strace

Bug#1009913: dpkg: when the user reverts to the package maintainer's version of a conffile, the execute bit is not propagated

Hi Guillem, On 2022-04-23 19:22:37 +0200, Guillem Jover wrote: > On Wed, 2022-04-20 at 17:17:16 +0200, Vincent Lefevre wrote: > > In an upgrade, the user may get a prompt like that and answer yes > > to install the package maintainer's version of a conffile, thus > > revertin

Bug#1009913: dpkg: when the user reverts to the package maintainer's version of a conffile, the execute bit is not propagated

Package: dpkg Version: 1.21.7 Severity: normal In an upgrade, the user may get a prompt like that and answer yes to install the package maintainer's version of a conffile, thus reverting all changes done he had done: Configuration file '/etc/resolvconf/update.d/unbound' ==> Modified (by you or

Bug#1003452: dpkg: missing alternatives for x-terminal-emulator

Control: found -1 1.21.0 Control: notfound -1 1.21.1 since the issue really occurred in dpkg 1.21.0. On 2022-01-13 13:17:42 +0100, Guillem Jover wrote: [...] Thanks for the explanations. > On Wed, 2022-01-12 at 14:17:17 +0100, Vincent Lefevre wrote: > > If this is the case, > >

Bug#1003452: dpkg: missing alternatives for x-terminal-emulator

Hi, On 2022-01-12 13:13:23 +0100, Guillem Jover wrote: > On Mon, 2022-01-10 at 13:13:11 +0100, Vincent Lefevre wrote: [...] > > update-alternatives 2021-08-16 16:27:55: run with --install > > /usr/bin/x-terminal-emulator x-terminal-emulator /usr/bin/mlterm 20 --slave > >

Bug#1003452: dpkg: missing alternatives for x-terminal-emulator

Package: dpkg Version: 1.21.1 Severity: important I notice that /usr/bin/mlterm is missing from the alternatives for x-terminal-emulator: cventin:~> update-alternatives --display x-terminal-emulator x-terminal-emulator - manual mode link best version is /usr/bin/gnome-terminal.wrapper link

Bug#65925: Add new field to track package rename/split/merge

Control: retitle -1 dpkg: Add new field to track package rename/split/merge On 2020-04-22 12:31:23 +0200, Vincent Lefevre wrote: > Control: retitle -1 dpkg: should have a "Suggests-Remove" and > "Recommends-Remove" headers in packages > Control: found -1 1.19.7

Bug#65925: Add new field to track package rename/split/merge

Control: retitle -1 dpkg: should have a "Suggests-Remove" and "Recommends-Remove" headers in packages Control: found -1 1.19.7 fixing a typo in the bug 65925 title and updating the dpkg version. Also suggested from https://lists.debian.org/debian-user/2020/04/msg01073.html -- Vincent

Bug#933335: dpkg: error: dpkg frontend lock is locked by another process

Package: dpkg Version: 1.19.7 Severity: serious I wanted to upgrade with aptitude, but it failed with the error "dpkg: error: dpkg frontend lock is locked by another process". In the terminal: Performing actions... Retrieving bug reports... Done Parsing Found/Fixed information... Done

Bug#923423: dpkg: Hangs for 19 mins installing texlive-fonts-extra

Control: retitle -1 dpkg: package install can be very slow with some disks due to too frequent fsync Hi, On 2019-04-09 00:33:27 +0200, Guillem Jover wrote: > On Tue, 2019-03-05 at 15:43:05 +0100, Vincent Lefevre wrote: > > zira:~>

Bug#926472: dpkg(1) man page: should document that putting a package on hold will require to process triggers manually

Package: dpkg Version: 1.19.6 Severity: wishlist When a package is on hold, its triggers are not processed automatically, and this is regarded as a feature[*]. It should be documented that triggers need to be processed manually. [*] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901040 --

Bug#923423: dpkg: Hangs for 19 mins installing texlive-fonts-extra

I've done a test with "iozone -a -e", and with this -e option (to include fsync), the operations are much slower than on the other machine. zira:~> iozone -a -e [...] randomrandom bkwdrecordstride

Bug#923423: dpkg: Hangs for 19 mins installing texlive-fonts-extra

On 2019-03-05 15:43:05 +0100, Vincent Lefevre wrote: > I've done a test with "iozone -a -e", and with this -e option > (to include fsync), the operations are much slower than on the > other machine. >

Bug#923423: dpkg: Hangs for 19 mins installing texlive-fonts-extra

On 2019-03-05 13:52:27 +0100, Guillem Jover wrote: > Hi! > > On Sun, 2019-03-03 at 02:38:10 +0100, Vincent Lefevre wrote: > > On 2019-03-03 00:15:13 +0100, Guillem Jover wrote: > > > Did this start happening due to the new kernel version? > > > > In March 2

Bug#923423: texlive-fonts-extra installation hangs

In short: [...] 2019-02-28 00:51:01 status half-installed texlive-fonts-extra:all 2018.20190207-1 2019-02-28 01:10:50 status unpacked texlive-fonts-extra:all 2018.20190227-1 [...] And ditto in the past: [...] 2019-02-02 16:21:55 status half-installed texlive-fonts-extra:all 2018.20190126-1

Bug#850417: dpkg: error: dpkg status database is locked by another process

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). -- Vincent Lefèvre - Web: 100% accessible validated (X)HTML - Blog:

Bug#850417: dpkg: error: dpkg status database is locked by another process

Hi! On 2017-01-11 03:14:13 +0100, Guillem Jover wrote: > On Fri, 2017-01-06 at 13:46:14 +0100, Vincent Lefevre wrote: > > On 2017-01-06 13:15:18 +0100, Guillem Jover wrote: > > > That the system probably has some unnattended async calls to a > > > command t

Bug#850417: dpkg: error: dpkg status database is locked by another process

Control: severity -1 normal On 2017-01-06 13:15:18 +0100, Guillem Jover wrote: > Hi! > > On Fri, 2017-01-06 at 11:33:08 +0100, Vincent Lefevre wrote: > > Package: dpkg > > Version: 1.18.18 > > Severity: grave > > Justification: renders package unusable > &g

Bug#850417: dpkg: error: dpkg status database is locked by another process

On 2017-01-06 12:05:19 +0100, Vincent Lefevre wrote: [...] > 2017-01-06 11:24:38 status installed libapt-pkg5.0:amd64 1.4~beta3 > 2017-01-06 11:24:40 startup packages configure > 2017-01-06 11:24:40 trigproc libc-bin:amd64 2.24-8 > 2017-01-06 11:24:40 status half-configured libc-bin:

Bug#850417: dpkg: error: dpkg status database is locked by another process

Some additional information... In the /var/log/dpkg.log file: 2017-01-06 11:24:37 startup archives unpack 2017-01-06 11:24:38 upgrade libapt-pkg5.0:amd64 1.4~beta2 1.4~beta3 2017-01-06 11:24:38 status triggers-pending libc-bin:amd64 2.24-8 2017-01-06 11:24:38 status half-configured

Bug#850417: dpkg: error: dpkg status database is locked by another process

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

Bug#844300: nvidia-driver-libs:amd64: upgrade failure due to dependency issue

Control: retitle -1 dpkg: Please remove packages selected for deinstall on Multi-Arch version skew (fixing a typo in the retitle) On 2016-12-04 04:13:47 +0100, Guillem Jover wrote: > Control: severity -1 wishlist > Control: retitle -1 dpkg: Please remove packages seclected for deinstall on >

Bug#766758: ekiga is half-installed

I've just upgraded another machine, and: $ COLUMNS=70 dpkg -l | grep -v '^ii' Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version

Bug#766758: ekiga is half-installed

at 02:14:32 +0100, Vincent Lefevre wrote: I've just upgraded another machine, and: [...] So, this is similar to the other one. Ok, I know you set the version affecting the other system to 1.17.21, but is this one too that version? was it upgraded to that on the same upgrade run? 1.17.21

Bug#763831: dpkg: start-stop-daemon broken when /proc/$PID/exe points to a deleted file

Package: dpkg Version: 1.17.13 Severity: normal After rsyslog upgrade, rsyslogd cannot be restarted because start-stop-daemon thinks that it is already stopped: $ ll /var/run/rsyslogd.pid -rw-r--r-- 1 root root 5 2014-09-29 12:23:00 /var/run/rsyslogd.pid $ cat /var/run/rsyslogd.pid 1990 In ps

Bug#763831: dpkg: start-stop-daemon broken when /proc/$PID/exe points to a deleted file

On 2014-10-03 02:21:18 +0200, Vincent Lefevre wrote: The cause of the problem is: # ls -l /proc/1990/exe lrwxrwxrwx 1 root root 0 2014-09-29 12:23:00 /proc/1990/exe - /usr/sbin/rsyslogd.dpkg-new (deleted) Concerning rsyslogd, I had reported: https://bugs.debian.org/cgi-bin/bugreport.cgi

Bug#734114: dpkg: dpkg -l can have too wide columns when output is redirected

Hi, On 2014-01-04 00:12:57 +0100, Guillem Jover wrote: The issue I was already aware of related to --list, is that the code counting the needed columns does not perform the same filters as the actual listing code, so this can happen in several scenarios. In your case, given that you are

Bug#686346: dpkg is wrong about the install state of docbook-mathml, making the system in inconsistent state

Package: dpkg Version: 1.16.8 Severity: serious I did the following: ay:~ sudo apt-get install --purge debian-archive-keyring debian-faq debian-goodies debianutils deborphan desktop-file-utils dialog dict dict-foldoc dict-wn dictd dictionaries-common dictzip doc-base docbook-defguide-

Bug#620958: your mail

found 620958 1.16.0.3 thanks On 2011-04-16 09:09:43 -0700, D. Kelly wrote: You can include me in the number of users who is now being spammed by all the warnings. I managed to get rid of quite a few of them with dpkg --clear-avail but I still get all the status ones. For example: Me too

Bug#594908: dpkg should regard local versions of binary packages as newer than non-local ones

Package: dpkg Version: 1.15.8.4 Severity: normal I've patched a package and rebuilt it as documented on http://www.debian.org/doc/FAQ/ch-pkg_basics.en.html#s-sourcebuild i.e. with dch -l local ... before the build itself. But dpkg regards the local package as older than the official package:

Bug#139569: Status of this bug?

Hi, What's the status of this bug? On http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=139569, it is said: Blocking fix for 411722: coreutils: info printf just gets the man page, 483554: coreutils: info chcon gives the man page instead of the full documentation but these two bugs were

Bug#139569: Status of this bug?

On 2009-09-03 11:34:30 +0200, Raphael Hertzog wrote: What about reading the last message in the history? dpkg's install-info is going away in 1.15.4 and all install-info bugs will be closed/reassigned to the new install-info package that is provided by GNU texinfo. But since the problem is

Bug#451872: emacs22-gtk: replacing emacs-snapshot by emacs22 leads to broken alternatives

On 2007-11-19 08:21:24 +0100, Sven Joachim wrote: This is a bug in update-alternatives, not in the emacs22 packages, see the discussion I had with jidanni in #433567. Run update-alternatives --auto emacs to fix the symlinks. Discussion in #433567 is confusing. The bug report says:

Bug#445270: dpkg: update-alternatives logging

Package: dpkg Version: 1.14.6 Severity: wishlist The update-alternatives command should have a logging feature, just like dpkg, as it sometimes goes wrong, leading to dangling symlinks. -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (500,

Bug#175370: Use UTF-8 internally, convert to locale's encoding for output

Any news? -- Vincent Lefèvre [EMAIL PROTECTED] - Web: http://www.vinc17.org/ 100% accessible validated (X)HTML - Blog: http://www.vinc17.org/blog/ Work: CR INRIA - computer arithmetic / Arenaire project (LIP, ENS-Lyon)

Bug#380332: dpkg: [CONFFILE] diff command should be configurable

Package: dpkg Version: 1.13.22 Severity: wishlist The diff command used to show conffile diffs should be configurable, at least in dpkg.cfg. For instance, one should be able to choose colordiff to get colorized diffs. -- System Information: Debian Release: testing/unstable APT prefers unstable

Bug#380332: dpkg: [CONFFILE] diff command should be configurable

On 2006-07-29 19:14:34 +0100, Adam D. Barratt wrote: This appears to be another request as per #268154 and the seven others currently merged with it. Adding this report to the group... :) I'm not sure it should be in the same group as #268154. The other wishlist bugs are about 3-way diff and

Bug#349442: dpkg: Assertion `dependtry = 4' failed (abort).

Package: dpkg Version: 1.13.11 Severity: grave Justification: renders package unusable I get the following error: ay:/home/lefevre# dpkg --configure -a dpkg: ../../src/packages.c:191: process_queue: Assertion `dependtry = 4' failed. Aborted (core dumped) As a consequence, I can no longer