Your message dated Thu, 25 Apr 2019 09:48:17 +0000
with message-id <e1hjazj-000139...@fasolo.debian.org>
and subject line Bug#927450: fixed in debian-security-support 2019.04.25
has caused the Debian Bug report #927450,
regarding debian-security-support should know that the next stable is Debian 10
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.)


-- 
927450: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927450
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: base-files
Version: 10.2
Severity: critical
Justification: breaks unrelated software


Hi.

While the bug is likely in debian-security-support, as soon as upgrading to 10.2
(downgrading to 10.1 fixes the problem) a debian-security-support hook will
fail at basically every installed/upgrade package:


# aptitude
Performing actions...
Retrieving bug reports... Done
Parsing Found/Fixed information... Done
Reading changelogs... Done
apt-listchanges: Do you want to continue? [Y/n] 
apt-listchanges: Mailing root: apt-listchanges: changelogs for kronecker
Extracting templates from packages: 100%
Preconfiguring packages ...
(Reading database ... 150402 files and directories currently installed.)
Preparing to unpack .../base-files_10.2_amd64.deb ...
Unpacking base-files (10.2) over (10.1) ...
Setting up base-files (10.2) ...
Installing new version of config file /etc/debian_version ...
Installing new version of config file /etc/issue ...
Installing new version of config file /etc/issue.net ...
=> here it was upgrade
dpkg: error: error executing hook 'if [ -x 
/usr/share/debian-security-support/check-support-status.hook ] ; then 
/usr/share/debian-security-support/check-support-status.hook ; fi', exit code 
256
=> here the hook already fails
[ Rootkit Hunter version 1.4.6 ]
File updated: searched for 181 files, found 156
Scanning processes...                                                           
                                                                                
                              
Scanning linux images...                                                        
                                                                                
                              

Running kernel seems to be up-to-date.

Failed to check for processor microcode upgrades.

No services need to be restarted.

No containers need to be restarted.

No user sessions are running outdated binaries.
E: Sub-process /usr/bin/dpkg returned an error code (2)
Processing triggers for install-info (6.5.0.dfsg.1-5) ...
Processing triggers for man-db (2.8.5-2) ...
dpkg: error: error executing hook 'if [ -x 
/usr/share/debian-security-support/check-support-status.hook ] ; then 
/usr/share/debian-security-support/check-support-status.hook ; fi', exit code 
256
=> aptitude's second try
Press Return to continue, 'q' followed by Return to quit.
  

=> I then moved on with upgrading all (remaining) packages

Performing actions...
Retrieving bug reports... Done
Parsing Found/Fixed information... Done
Reading changelogs... Done
Extracting templates from packages: 100%
Preconfiguring packages ...
(Reading database ... 150402 files and directories currently installed.)
Preparing to unpack .../archives/bash_5.0-4_amd64.deb ...
Unpacking bash (5.0-4) over (5.0-3) ...
=> fails again after the first package
dpkg: error: error executing hook 'if [ -x 
/usr/share/debian-security-support/check-support-status.hook ] ; then 
/usr/share/debian-security-support/check-support-status.hook ; fi', exit code 
256
[ Rootkit Hunter version 1.4.6 ]
File updated: searched for 181 files, found 156
Scanning processes...                                                           
                                                                                
                              
Scanning candidates...                                                          
                                                                                
                              
Scanning linux images...                                                        
                                                                                
                              

Running kernel seems to be up-to-date.

Failed to check for processor microcode upgrades.

No services need to be restarted.

No containers need to be restarted.

User sessions running outdated binaries:
 root @ session #2526: sshd[21698]
E: Sub-process /usr/bin/dpkg returned an error code (2)
Setting up bash (5.0-4) ...
update-alternatives: using /usr/share/man/man7/bash-builtins.7.gz to provide 
/usr/share/man/man7/builtins.7.gz (builtins.7.gz) in auto mode
Processing triggers for install-info (6.5.0.dfsg.1-5) ...
Processing triggers for man-db (2.8.5-2) ...
dpkg: error: error executing hook 'if [ -x 
/usr/share/debian-security-support/check-support-status.hook ] ; then 
/usr/share/debian-security-support/check-support-status.hook ; fi', exit code 
256
Press Return to continue, 'q' followed by Return to quit.



-- System Information:
Debian Release: 10.0
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_DE.UTF-8, LC_CTYPE=en_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages base-files depends on:
ii  gawk [awk]          1:4.2.1+dfsg-1
ii  mawk [awk]          1.3.3-17+b3
ii  original-awk [awk]  2012-12-20-6

base-files recommends no packages.

base-files suggests no packages.

-- Configuration Files:
/etc/profile changed [not included]

-- no debconf information




I reported it against base-files as this is what people will ugprade and notice
if apt-listbugs is installed (they wouldn't notice it on 
debian-security-support).


Cheers,
Chris.

--- End Message ---
--- Begin Message ---
Source: debian-security-support
Source-Version: 2019.04.25

We believe that the bug you reported is fixed in the latest version of
debian-security-support, 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 927...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Holger Levsen <hol...@debian.org> (supplier of updated debian-security-support 
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 ftpmas...@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Thu, 25 Apr 2019 11:36:54 +0200
Source: debian-security-support
Architecture: source
Version: 2019.04.25
Distribution: unstable
Urgency: medium
Maintainer: Christoph Biedl <debian.a...@manchmal.in-ulm.de>
Changed-By: Holger Levsen <hol...@debian.org>
Closes: 927450
Changes:
 debian-security-support (2019.04.25) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Moritz Muehlenhoff ]
   * Remove mozjs17 from security-support-limited, long gone, add
     mozjs52 and mozjs60 instead.
   * Remove webkitgtk from security-support-limited, covered by security
     support now.
   * Remove xulrunner from security-support-limited, long gone.
   * Mark binutils as not covered by security support.
 .
   [ Holger Levsen ]
   * check-support-status.in: set latest supported version to Debian 10 /
     Buster. Closes: #927450.
   * Add empty security-support-ended.deb10 file.
   * Drop security-support-ended.deb6 as we don't support Squeeze anymore.
Checksums-Sha1:
 5c7933141eaecd2c7f379dbe519ab4edd93e4fe2 1872 
debian-security-support_2019.04.25.dsc
 b1607fbc49a92572a43d457a7a7306787b361d6e 28212 
debian-security-support_2019.04.25.tar.xz
 2255fe20c82004c0017a17bbca688a21460df4ba 6078 
debian-security-support_2019.04.25_source.buildinfo
Checksums-Sha256:
 fc6aa1c096ff610116266cd78aac7a54a884e2728746ea2a4462b47f6605822e 1872 
debian-security-support_2019.04.25.dsc
 1e49f7e1fb835b9eef171f77fddb47024014e74db85125471b6717aee3195984 28212 
debian-security-support_2019.04.25.tar.xz
 afdc02b66c81ff0d275ae122834d406cceac19079289dd1f4e9b656abcebc810 6078 
debian-security-support_2019.04.25_source.buildinfo
Files:
 8043acdba0715fc857ba07035c2845e7 1872 admin optional 
debian-security-support_2019.04.25.dsc
 4d3ed1cd35095b1f66d4b844b6b73d3d 28212 admin optional 
debian-security-support_2019.04.25.tar.xz
 e7f3d37f043437b89a3a3b8edb383f46 6078 admin optional 
debian-security-support_2019.04.25_source.buildinfo

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEuL9UE3sJ01zwJv6dCRq4VgaaqhwFAlzBgSgACgkQCRq4Vgaa
qhxLQA/7B5syb4WJSm67idLVjAVC1kzNllVPQfHCETikCtebXzJ1tlyQ7uAmTfLT
0Ooaf8w6Py/6PORFt66VADwVQPGs2ZcTJd+dnBGecvujTGmRZLwOFu4CMisGHaMO
e+IN+eceXg0YINR4YpcN/0ZR+nvXLKel5sEYHsHGfIfVPYZB5edTEF5ymmn5fmUu
+MzHgeSdoYIyIFu1aotdDJnnmFWGxHAnsUMI8nv+S8exBgdj/7gplag36sls7vLb
/B+81owQKyCB28a61e+GdMuyccwhRC4oeFAbyik0XZhD+C5GYb0G+7WgU5/inLbS
wQOyCEHEOtAELSNAN5c09caSsOe5N+nMS5F2yMzIRpbbzYqnhN+T6qyIsc9fR6Ww
SAU+CqoJELuwPWcDL9dJ7UY3Qp73vaNP9A3Dg2HgwnjwOMBpPvZk9aRiIAO5Pqs4
XVoROWL/p5jn+Gs0ttDtZM5BAd/geoJcbAmNt8Nmr1jNTfOtRcBwjvM7/nZCHFpF
TgJRHiJgViVhnEuG46cBPy0wgV3D8CcpOAd7ZSA30PATPoqRZg1YHJuJnDLBhUH+
WjfGZGdh/yrUQrw6cRsM0oDSokwyg8zuLvrAjfBj127XKtLxwfhd0zkNFngyWvvg
DzIUqK9voBQUj0Am01KkyvKmHXErsoFe8izXI1revbd7zrFyO5g=
=wJC6
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to