Bug#814244: dpkg: provide a flag to determine the dpkg 'status'
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 libc62.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
Bug#608930: Bug#548415: reportbug: Package upgrade information in bug reports
On Fri, Feb 25, 2011 at 12:32, Mike Hommey m...@glandium.org wrote: On Tue, Jan 11, 2011 at 01:11:16AM +0100, Sandro Tosi wrote: On Thu, Jan 6, 2011 at 08:03, Mike Hommey m...@glandium.org wrote: I, for one, don't care very much about the dependency, but more about the fact that not having it installed could mean not being able to pull the information, even by installing afterwards. A dpkg.log parser would always work, except when the logs are rotated and old enough to have been removed. I tend to agree with Mike here: a log parser would be very nice, like something dpkg-log last_ops package N op_N, like purge install remove etc package version N-1 op_N-1 package version (prev_version if needed) N-2 op_N-2 package version N-3 op_N-3 package version N-4 op_N-4 package version or a series of other interesting commands. Default logrotate configuration keeps a year of log, so we have quite a bit of room even for the very lazy bug reporters :) What I'd like to avoid (with the reportbug maint hat on) is to let reportbug parse a log file (either dpkg or xapian) to extract the info it needs. Looks like things are happening http://justimho.blogspot.com/2011/02/let-me-introduce-dpkglog-and-dpkg.html Sorry to chime in so late; I've reported some bugs against libdpkg-log-perl, let's see how it goes. If I missed some, please integrated :) Regards, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-dpkg-bugs-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#608930: Bug#548415: reportbug: Package upgrade information in bug reports
On Thu, Jan 6, 2011 at 08:03, Mike Hommey m...@glandium.org wrote: I, for one, don't care very much about the dependency, but more about the fact that not having it installed could mean not being able to pull the information, even by installing afterwards. A dpkg.log parser would always work, except when the logs are rotated and old enough to have been removed. I tend to agree with Mike here: a log parser would be very nice, like something dpkg-log last_ops package N op_N, like purge install remove etc package version N-1 op_N-1 package version (prev_version if needed) N-2 op_N-2 package version N-3 op_N-3 package version N-4 op_N-4 package version or a series of other interesting commands. Default logrotate configuration keeps a year of log, so we have quite a bit of room even for the very lazy bug reporters :) What I'd like to avoid (with the reportbug maint hat on) is to let reportbug parse a log file (either dpkg or xapian) to extract the info it needs. Cheers, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-dpkg-bugs-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#608884: dpkg-vendor: please document format of /etc/dpkg/origins/ files
Package: dpkg Version: 1.15.8.6 Severity: wishlist Hello, in order to properly resolve #607850 we'd like to know the full specification of /etc/dpkg/origins/ files (we couldn't find the documentation). Thanks in advance, Sandro -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.31-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages dpkg depends on: ii coreutils 8.5-1 GNU core utilities ii libbz2-1.01.0.5-6high-quality block-sorting file co ii libc6 2.11.2-1 Embedded GNU C Library: Shared lib ii libselinux1 2.0.89-2 SELinux runtime shared libraries ii xz-utils 4.999.9beta+20100713-1 XZ-format compression utilities ii zlib1g1:1.2.3.4.dfsg-3 compression library - runtime dpkg recommends no packages. Versions of packages dpkg suggests: ii apt 0.8.10 Advanced front-end for dpkg -- no debconf information -- To UNSUBSCRIBE, email to debian-dpkg-bugs-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Bug#502860: reportbug: Gets wrong maintainer for no longer installed packages
retitle 502860 use python-apt instead of dpkg for pkgs info thanks On Mon, Oct 20, 2008 at 16:52, Raphael Hertzog [EMAIL PROTECTED] wrote: On Mon, 20 Oct 2008, Sandro Tosi wrote: Hello Ansgar, On Mon, Oct 20, 2008 at 13:23, Ansgar Burchardt [EMAIL PROTECTED] wrote: Reportbug sometimes looks up the wrong maintainer for packages that have been removed from the system. The output from dpkg --print-avail can be wrong if the package is no longer installed. Reportbug should not use this information for these packages. For example on my system I get this: But isn't it a bug in dpkg then? I can feel like --print-avail should print only available package, and nntp was no longer available on your system. I can't think an easy way to fix this if not switching to apt-cache or some other tool. Don't use dpkg --print-avail it reports only outdated information in most cases as the available file is only a left-over from dselect and as such it's almost guaranteed to not be up-to-date. There's a warning in the man page in the git repository documenting this limitation already. Use apt-cache is my suggestion. Thanks Raphael for highlight this to me; maybe the best solution is to replace all the code that exec dpkg + parse output to python-apt (even if this interface really needs a better documentation than now) Cheers, Sandro -- Sandro Tosi (aka morph, Morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#502860: reportbug: Gets wrong maintainer for no longer installed packages
Hello Ansgar, On Mon, Oct 20, 2008 at 13:23, Ansgar Burchardt [EMAIL PROTECTED] wrote: Reportbug sometimes looks up the wrong maintainer for packages that have been removed from the system. The output from dpkg --print-avail can be wrong if the package is no longer installed. Reportbug should not use this information for these packages. For example on my system I get this: But isn't it a bug in dpkg then? I can feel like --print-avail should print only available package, and nntp was no longer available on your system. I can't think an easy way to fix this if not switching to apt-cache or some other tool. I'm open to suggestions, in particular from dpkg guys. Cheers, Sandro -- Sandro Tosi (aka morph, Morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
