Your message dated Thu, 12 Mar 2020 23:34:53 +0000 with message-id <[email protected]> and subject line Bug#945837: fixed in unattended-upgrades 2.0 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: 2.0 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: Thu, 12 Mar 2020 22:52:58 +0100 Source: unattended-upgrades Architecture: source Version: 2.0 Distribution: unstable Urgency: medium Maintainer: Michael Vogt <[email protected]> Changed-By: Balint Reczey <[email protected]> Closes: 768087 903875 905877 919046 945837 946491 952569 Launchpad-Bugs-Fixed: 1251228 1434115 1850964 Changes: unattended-upgrades (2.0) unstable; urgency=medium . * Revert relying fully on pinning. APT's resolver can't be fully relied on because sometimes it does not find the solution. * Treat locally installed package versions as coming from a whitelisted origin * Don't list kept packages in dry-run mode. Since the kept packages are calculated based on the final system state all packages that would be upgraded would be listed as kept in dry-run mode. * Try installing/upgrading packages without any adjustment first. The applied pinning should be enough for APT's resolver to find the right candidate most of the time. The candidate version adjustments are still done in cases where APT's resolver fails * Report only higher available allowed versions with higher priority as kept (Closes: #952569) * Drop very long debug message about checking package list file * Honor pinning when listing origin of kept back packages . 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: 2594d736890e7aeabb67dfbe9823f6e613950e5b 1898 unattended-upgrades_2.0.dsc 3b8910655618602005af05f4f7840e5727a5e92d 123840 unattended-upgrades_2.0.tar.xz 7badcf359cd6bd2979e55a4873ed9514f66fc6a2 8398 unattended-upgrades_2.0_source.buildinfo Checksums-Sha256: 571d4dae94668ba91f1bafaf983892e4b2e268102cff6b967b6c01f473a64b0a 1898 unattended-upgrades_2.0.dsc 2e2d206fd37ea6a4f7dd00eaf80cad5ad09d3a0a12418a19202e97c55e026f90 123840 unattended-upgrades_2.0.tar.xz ac9e9093727d5630071a825a55a3a64cf6168a5371b324dd2cf1af8cfd85b15b 8398 unattended-upgrades_2.0_source.buildinfo Files: fde082b73c2a39a35fa1af17529d9ba9 1898 admin optional unattended-upgrades_2.0.dsc f60f8c2ffcdb0716bed7496c2cdc2ef0 123840 admin optional unattended-upgrades_2.0.tar.xz e80b37697ee9bb78879adfa8daf856be 8398 admin optional unattended-upgrades_2.0_source.buildinfo -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEI/PvTgXX55rLQUfDg6KBkWslS0UFAl5qw9IACgkQg6KBkWsl S0VxFhAAqrphXWL/fXe9tms5H1aNIm1BzsUF4KxPJiDosEKRfyeafNo9pnqnYZXa 4JFu9UHr3gDoYagsjJt7bVPFwnw+w6EcciwXYtHQ6S1jI8Y/ttySWFUj/uuTLMEH L0kbDKc7fSeu6S7jucuUAkPRybIomLkci0EFHKmayrybjCuB0rr02UMQqtorNKPf HwHqCnVv9ikVOzsoMUazjKe6DUgnCSmZH+175Qhl7ac8PWBdj7+KXwIlFhJE9Nsz a7P7zYzY+e3krI3GTu1+moIERxNWcb45ZBwGfOBDL+qdQQoXiXuQDE5pOrpvexNE NzpI8+k4jaobKEmyk2XUAxe3BXAmlXWRQ+qQ8os0pQ85/KbA+DTT/Ham7T4WFC4m B0Z+Iu7u2wUsV/2ndv/Ahei5YPuxMAGiWld3pa18aTtvCG2/PMhBwOM7GZ3ZZtZi HRMEDYane38R8eMTZpbL6XGEKFloAVShg6g1YIBp7rtlvUO20Zi3E2Af94zLAzia Nb8sKwIZJN1MZDZ86pGyUaD2SkvU7jB1JheZTO/BpassIzO3ntVV+X8pOptVxvFb P+uDaMi047qC8aP/IsjVRFayvVFCgioebVUQ7EeNxDjdKsfXTlN4pMlzhO7P+OVW VXuQ1J62Mj/s4xAeTv7socaLP6JegNZOPmrnmcsCxXJSq8p/s6Y= =RBw9 -----END PGP SIGNATURE-----
--- End Message ---
