Your message dated Sun, 18 Sep 2016 12:53:01 +0000 with message-id <E1blbaf-0003Bi-0G@franck.debian.org> and subject line Bug#837331: fixed in vlock 2.2.2-7 has caused the Debian Bug report #837331, regarding vlock: fails to install, remove, and install again 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 owner@bugs.debian.org immediately.) -- 837331: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837331 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: vlock: fails to install, remove, and install again
- From: Andreas Beckmann <anbe@debian.org>
- Date: Sat, 10 Sep 2016 18:06:55 +0200
- Message-id: <[🔎] 20160910160655.30999.51149.reportbug@zam581.zam.kfa-juelich.de>
Package: vlock Version: 2.2.2-6 Severity: serious User: debian-qa@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install, remove (but not purge), and install again. Before the second installation the package is in config-files-remaining state. The configuration is remaining from the last version that was successfully configured - which is the same version that is going to be installed again. Like a plain failure on initial install this makes the package too buggy for a release, thus the severity. >From the attached log (scroll to the bottom...): 0m27.8s DEBUG: Starting command: ['chroot', '/tmp/piupartss/tmpvoT99A', 'apt-get', '-y', 'install', 'vlock=2.2.2-6'] 0m29.0s DUMP: Reading package lists... Building dependency tree... Reading state information... The following NEW packages will be installed: vlock debconf: delaying package configuration, since apt-utils is not installed 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/36.7 kB of archives. After this operation, 120 kB of additional disk space will be used. dpkg: unrecoverable fatal error, aborting: unknown group 'vlock' in statoverride file E: Sub-process /usr/bin/dpkg returned an error code (2) 0m29.0s ERROR: Command failed (status=100): ['chroot', '/tmp/piupartss/tmpvoT99A', 'apt-get', '-y', 'install', 'vlock=2.2.2-6'] cheers, AndreasAttachment: vlock_2.2.2-6.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
- To: 837331-close@bugs.debian.org
- Subject: Bug#837331: fixed in vlock 2.2.2-7
- From: Helmut Grohne <helmut@subdivi.de>
- Date: Sun, 18 Sep 2016 12:53:01 +0000
- Message-id: <E1blbaf-0003Bi-0G@franck.debian.org>
Source: vlock Source-Version: 2.2.2-7 We believe that the bug you reported is fixed in the latest version of vlock, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 837331@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Helmut Grohne <helmut@subdivi.de> (supplier of updated vlock package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmaster@ftp-master.debian.org) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Format: 1.8 Date: Sun, 18 Sep 2016 14:24:05 +0200 Source: vlock Binary: vlock Architecture: source Version: 2.2.2-7 Distribution: unstable Urgency: medium Maintainer: Debian QA Group <packages@qa.debian.org> Changed-By: Helmut Grohne <helmut@subdivi.de> Description: vlock - Virtual Console locking program Closes: 793901 837331 Changes: vlock (2.2.2-7) unstable; urgency=medium . * QA upload. * Do not remove the vlock group: (Closes: #837331) Removing the group during package removal is plain broken. And removing it at all risks privilege escalations by leaving unowned files that are dynamically assigned to a different purpose. * Pass CC to configure. (Closes: #793901) Checksums-Sha1: a25f3e21d7fc7d31e95c2786392445f7d1c719a4 1639 vlock_2.2.2-7.dsc 338b29f5d57c0bad3f02c39b206baf077b8b73f5 9300 vlock_2.2.2-7.debian.tar.xz Checksums-Sha256: f73cd153ec8584990e21892acaad2ac6fb66da0230ac247296bd62676653c0ad 1639 vlock_2.2.2-7.dsc c4b407622437f52cd5c450a434da35e6459432554f84334ff84a32e0b37a281f 9300 vlock_2.2.2-7.debian.tar.xz Files: 3a0971b1ae12346094190abf9ee813e7 1639 utils optional vlock_2.2.2-7.dsc 03e7d5ed5a320853f939d3a4edfb7600 9300 utils optional vlock_2.2.2-7.debian.tar.xz -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBCgAGBQJX3olRAAoJEC0aqs8kRERCUNUP/0PTazOFN1LZW/2DWr6CuIpO lU+mXm/yIEZituiMvBJEX6+Z2vgo5Z8YrIvkcA/IYhNWThm2viemxtOT47xrrehe ZdLVwv4vchgb+DDyJ7x8UuirY/RjNSTGFKmNduzQ3FiRw/Qjl1LX5Q9uJu8xUiS0 KFrhMAeT55kcocNh6XxvWQsp4rRcCyI5jiRobWLpU6mIGS3nF+FprGwlZTxo8RDw ycyzl7LqWEc8grgDfemSLXUnwFoov8JirYjSg96LeKpYX5ZGWgEP4Z67B7Y4z5m7 vDFMFVL0MEbiLHRsft7pcuFugbMkQuvJfWKiZc5Mx/3AL7M35/9wVaLy3V1JqdXT hTVMoZwZfZs5XAO1mLgIhuG2fce1i9qkIz8t934BgdYg4Ar5lxuQUo6JDsmP2E/r zoMjJb4l1/UROiSpIdAsc/fF7SESYZvTEmcNJ9R3V9ljaJrjZ3tIhzzuiXnv+KRG lygvEfVkGfBr2d1PDzdTEF2M7nUqepZmF8whh2HC7z/y8ZhKJtNt6amRGF3qusGw 8JAZgBEtFNvg6/gyfIZBE4pppwnvIMzCfJ0eniW0+4G5muYOMpsQxiI74oPK0Nl4 jh7aKhEGIgRQwySMkrndGP7AS5F6tNRwcIyQRMKYuqUuki6jFCxb5DstZW4iGa4v NVPIax0Me3VsJ3szXJAp =4CbJ -----END PGP SIGNATURE-----
--- End Message ---