Your message dated Tue, 7 Feb 2017 14:47:18 +0100
with message-id <20170207134718.lqsyxrbahf3rc...@gaara.hadrons.org>
and subject line Re: Bug#814244: dpkg: provide a flag to determine the dpkg
'status'
has caused the Debian Bug report #814244,
regarding dpkg: provide a flag to determine the dpkg 'status'
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 ow...@bugs.debian.org
immediately.)
--
814244: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814244
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dpkg
Version: 1.18.3
Severity: wishlist
Hello,
when a pkg installation fails, and then you run another apt-get command, it will
check the content of /var/lib/dpkg/updates and if there is any file, requests
you to run sudo dpkkg --configure -a
The directory content check seems rather fragile, so it would be great if dpkg
could provide a cli switch to inspect its internal status. This could be used by
apt, but also by alerting tools (such as nagios/icinga) or config mgmt tools
(like pupper/cfengine) to assess the system status.
thanks for considering,
Sandro
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.2.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (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.19-22
ii liblzma5 5.1.1alpha+20120614-2.1
ii libselinux1 2.4-3
ii tar 1.28-2.1
ii zlib1g 1:1.2.8.dfsg-2+b1
dpkg recommends no packages.
Versions of packages dpkg suggests:
ii apt 1.1.5
-- no debconf information
--- End Message ---
--- Begin Message ---
Hi!
On Thu, 2016-02-11 at 19:27:39 +0100, Guillem Jover wrote:
> On Tue, 2016-02-09 at 13:36:14 +0000, Sandro Tosi wrote:
> > Package: dpkg
> > Version: 1.18.3
> > Severity: wishlist
>
> > when a pkg installation fails, and then you run another apt-get command, it
> > will
> > check the content of /var/lib/dpkg/updates and if there is any file,
> > requests
> > you to run sudo dpkkg --configure -a
> >
> > The directory content check seems rather fragile, so it would be great if
> > dpkg
> > could provide a cli switch to inspect its internal status. This could be
> > used by
> > apt, but also by alerting tools (such as nagios/icinga) or config mgmt tools
> > (like pupper/cfengine) to assess the system status.
>
> Hmm, I'm a bit conflicted by this request because the
> /var/lib/dpkg/updates directory is used as a package metadata journal
> or an update log. dpkg works perfectly fine with it as it parses the
> status file and all journal entries and constructs the current state
> in memory. It will also integrate those into the main status file once
> any write operation is performed, such as removal or install for example.
>
> apt is doing that check because it wants to be safe I guess, and
> because files in the journal imply an abrupt termination of dpkg. But
> the way to attest that the system is fine is by checking the status
> contents through a dpkg interface, such as that all packages are in a
> good known state through dpkg-query, or better via dpkg --audit.
Given there's been no further feedback, I'm closing this report.
Please reopen if you can provide more information, rationale, etc.
Thanks,
Guillem
--- End Message ---
