Your message dated Tue, 25 Feb 2020 19:21:59 +0000 with message-id <[email protected]> and subject line Bug#945837: fixed in unattended-upgrades 1.18 has caused the Debian Bug report #945837, regarding unattended-upgrades: packages kept back not listed in unattended-upgrades.log 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 [email protected] immediately.) -- 945837: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945837 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: unattended-upgrades Version: 1.15 Severity: normal Dear Maintainer, My motd currently reports: 7 updates could not be installed automatically. For more details, see /var/log/unattended-upgrades/unattended-upgrades.log (this is the output of /usr/share/unattended-upgrades/update-motd-unattended-upgrades ) However, there is no useful information in that log file. Here is the result of two manual invocations of "sudo unattended-upgrade" with no flags. Note well, there is nothing reported in "Packages that are kept back" 2019-11-29 09:09:45,219 INFO Initial blacklist: 2019-11-29 09:09:45,222 INFO Initial whitelist: 2019-11-29 09:09:45,222 INFO Starting unattended upgrades script 2019-11-29 09:09:45,223 INFO Allowed origins are: o=Debian,a=testing 2019-11-29 09:09:55,518 INFO Removing unused kernel packages: linux-image-5.2.0-2-amd64 2019-11-29 09:10:42,322 INFO Packages that were successfully auto-removed: linux-image-5.2.0-2-amd64 2019-11-29 09:10:42,323 INFO Packages that are kept back: 2019-11-29 09:10:42,902 INFO Packages that will be upgraded: gir1.2-ibus-1.0 libibus-1.0-5 libio-async-perl libv4l-0 libv4lconvert0 sensible-utils 2019-11-29 09:10:42,903 INFO Writing dpkg log to /var/log/unattended-upgrades/unattended-upgrades-dpkg.log 2019-11-29 09:11:41,873 INFO All upgrades installed 2019-11-29 09:14:19,581 INFO Initial blacklist: 2019-11-29 09:14:19,584 INFO Initial whitelist: 2019-11-29 09:14:19,585 INFO Starting unattended upgrades script 2019-11-29 09:14:19,585 INFO Allowed origins are: o=Debian,a=testing 2019-11-29 09:14:24,099 INFO Packages that will be upgraded: However, there are packages that are failing to install. Here is "apt full-upgrade -s" NOTE: This is only a simulation! apt needs root privileges for real execution. Keep also in mind that locking is deactivated, so don't depend on the relevance to the real current situation! Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages will be REMOVED: fuse The following NEW packages will be installed: fuse3 The following packages will be upgraded: gvfs gvfs-backends gvfs-common gvfs-daemons gvfs-fuse gvfs-libs sshfs 7 upgraded, 1 newly installed, 1 to remove and 0 not upgraded. Only after manually running "sudo unattended-upgrade -d" do I get useful information in the log file. Here are some excerpts: 2019-11-29 09:14:52,719 DEBUG Checking: gvfs ([<Origin component:'main' archive:'testing' origin:'Debian' label:'Debian' site:'deb.debian.org' isTrusted:True>]) 2019-11-29 09:14:52,957 DEBUG sanity check failed for: {'gvfs-daemons=1.42.1-3', 'gvfs-fuse=1.42.1-3', 'gnome=1:3.30+2', 'gvfs-backends=1.42.1-3', 'gnome-core=1:3.30+2', 'gvfs-libs=1.42.1-3', 'gvfs=1.42.1-3', 'task-gnome-desktop=3.55', 'gvfs-common=1.42.1-3'} : pkg gvfs-fuse is marked to be deleted ... 2019-11-29 09:14:54,563 DEBUG Checking: gvfs-fuse ([<Origin component:'main' archive:'testing' origin:'Debian' label:'Debian' site:'deb.debian.org' isTrusted:True>]) 2019-11-29 09:14:54,780 DEBUG sanity check failed for: {'fuse=2.9.9-2', 'gvfs-daemons=1.42.1-3', 'gvfs-fuse=1.42.1-3', 'gvfs-backends=1.42.1-3', 'fuse3=3.7.0-1', 'gvfs-libs=1.42.1-3', 'gvfs=1.42.1-3', 'gvfs-common=1.42.1-3'} : pkg fuse is marked to be deleted * What outcome did you expect instead? If packages are not being installed because other packages must be deleted, that's fine. But the log file should explicitly state so, including listing the affected packages. It seems it would be a fairly simple matter to simply print out into the log file the contents of /var/lib/unattended-upgrades/kept-back . I also suspect that if the only reason packages are being held back is because a failing sanity check, then there is a bug in earlier in the unattended-upgrade script. *** End of the template - remove these template lines *** -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.3.0-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages unattended-upgrades depends on: ii debconf [debconf-2.0] 1.5.73 ii lsb-base 11.1.0 ii lsb-release 11.1.0 ii python3 3.7.5-1 ii python3-apt 1.8.4+b1 ii python3-dbus 1.2.14-1 ii python3-distro-info 0.22 ii ucf 3.0038+nmu1 ii xz-utils 5.2.4-1+b1 Versions of packages unattended-upgrades recommends: ii anacron 2.3-29 ii cron [cron-daemon] 3.0pl1-135 ii systemd-sysv 243-8 Versions of packages unattended-upgrades suggests: pn bsd-mailx <none> pn default-mta | mail-transport-agent <none> pn needrestart <none> ii powermgmt-base 1.36 ii python3-gi 3.34.0-3 -- Configuration Files: /etc/logrotate.d/unattended-upgrades changed: /var/log/unattended-upgrades/unattended-upgrades.log /var/log/unattended-upgrades/unattended-upgrades-dpkg.log /var/log/unattended-upgrades/unattended-upgrades-shutdown.log { rotate 999 monthly missingok notifempty } -- debconf information: unattended-upgrades/enable_auto_updates: true
--- End Message ---
--- Begin Message ---Source: unattended-upgrades Source-Version: 1.18 Done: Balint Reczey <[email protected]> We believe that the bug you reported is fixed in the latest version of unattended-upgrades, 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 [email protected], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Balint Reczey <[email protected]> (supplier of updated unattended-upgrades 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 [email protected]) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Format: 1.8 Date: Tue, 25 Feb 2020 19:28:13 +0100 Source: unattended-upgrades Architecture: source Version: 1.18 Distribution: experimental Urgency: medium Maintainer: Michael Vogt <[email protected]> Changed-By: Balint Reczey <[email protected]> Closes: 768087 903875 905877 919046 945837 946491 Launchpad-Bugs-Fixed: 1251228 1434115 1850964 Changes: unattended-upgrades (1.18) experimental; urgency=medium . [ louib ] * Update blacklist translations * Fix syntax in template conf files . [ Balint Reczey ] * Keep mypy 0.761 happy * test: Create empty dirs to save kept packages list to them * Log explanation about kept back packages (LP: #1850964) (Closes: #945837, #903875) * Use GitHub Actions for CI instead of Travis. Run tests in Ubuntu Focal release because older releases don't have the needed python-apt version. * debian/tests/common-functions: Use backported python-apt from a PPA on Eoan * debian/tests: Skip upgrade-between-snapshots test. Python-apt's version is sid is too low for unattended-upgrades to work. * Use apt_pkg.Hashes instead of deprecated apt_pkg.md5sum() * autopkgtest: Skip upgrate-all-security in sid because buster can't be tested * Make allowed_origins, blacklist and whitelist attributes of UnattendedUpgradesCache * Make strict_whitelist attribute of UnattendedUpgradesCache * Apply pinning to disable not allowed origins and honor blacklist/whitelist. This makes candidate adjustments obsolete, since apt's resolver would pick candidates only from allowed origins by itself unless local pinning configuration overrides that. * Rely fully on pinning to disable allowed origins and stop adjusting candidates. * Drop Unattended-Upgrade::Allow-downgrade since now pinning is honored and downgrades are allowed for package versions with priority >= 1000. (Closes: #905877, #919046, #768087, #946491) (LP: #1251228, #1434115) * Don't ignore allowed origin when the package's priority is < 100. This used to be the way of honoring the priority, but now this special case prevents the package from showing up as a package kept back. * Assume frontend locking to be supported. Python3-apt (>= 1.9.6~) is required which supports the frontend locking API Checksums-Sha1: 74c312b21699d2639b89b3aeef6f3baff5543490 1902 unattended-upgrades_1.18.dsc ced9d991542c194e1b4ab5533d74c2fcc345e153 121676 unattended-upgrades_1.18.tar.xz b87fc7a730717af72ad40191008c140d7c520e8c 8475 unattended-upgrades_1.18_source.buildinfo Checksums-Sha256: a539b30a8595e717e983ee848f8ea84eefe19760ac91743b274118131eaa6586 1902 unattended-upgrades_1.18.dsc a752828b917f7be8ae2763a48006bfb1141e9582185e9d4980978aead070e48f 121676 unattended-upgrades_1.18.tar.xz 7d8b39d5f13065a38776bc307dc01745479d8317c7718656532a92a8a5bc34d2 8475 unattended-upgrades_1.18_source.buildinfo Files: c4ac53c7b4eb0d63205c50b3baae04fe 1902 admin optional unattended-upgrades_1.18.dsc 7c000f716e4605f421e20fcdf4256ad3 121676 admin optional unattended-upgrades_1.18.tar.xz 67443c02ba3ad381a2ce4ec16c1d3bf8 8475 admin optional unattended-upgrades_1.18_source.buildinfo -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEI/PvTgXX55rLQUfDg6KBkWslS0UFAl5VbWwACgkQg6KBkWsl S0Wocg//fQvLby+/tdMSLQXOdm5/WPReUKkJki+k3+vLb63c/3ZTrgB5B0UcII4B XCL9qjCjkdSf1wEfhbhxaCjBrMqLOfInY3WV8Ml4zR9iNOGGAhZagVgHp5hfVxhr 9q941LN7ZKno5YYno65WyGjYppCx35tGZlhju9FJn8wHekjR6EvoVtVSBx48A+PO MeyvGjXPW7tBkUA3mUMAx6hyRAU0ZKUyd6sKfYMi73RQuxguXr2I/O8mUfyQC+xz hy+JHZG71BxkEZgQbzRS/uXbiKWgA2eh/iqubbGw+HIwjZCvjujGXXFEGJSgY7Yv BPsPtV6mwpJKk0pz7LeksZK1LMai2XoK+hKHzo/IEeEIeWvAT2q6wuStLar77DzE 5gETKW33zYBW+L9jSta21DtJ+PHaRTsfrMQICm5qZKq7GFG+/iRn9U5Jr5RykHQ4 sAcYXrFQ74eOU21x2BNhd7MbDK2FCszP5K92o0iseSICYx6icm0+mzBdL84K9TZS YdgT17B7a2fOKyiIzO28u4/TpiMPXmb/YIVmHVk2BsLiZ9uxtZP1EgGkyYCGhhi9 jPqnDgDS6Kha7wftGWOKT3pMWmaenw7kAA9H2u7jaBIvExDiEEHsK6z1CzxD7bqh vDCC8iJjr5oQPW+d2BbPxw12qAYNVpv/PBWz4cfcWuUgOXas5lI= =wjcX -----END PGP SIGNATURE-----
--- End Message ---
