Dear Balint,
I am sorry for the late reply.
Am 14.12.20 um 12:22 schrieb Balint Reczey:
On Mon, Dec 14, 2020 at 12:06 PM Paul Menzel <pmen...@molgen.mpg.de> wrote:
Am 14.12.20 um 11:58 schrieb Balint Reczey:
On Mon, Dec 14, 2020 at 10:03 AM Paul Menzel <pmen...@molgen.mpg.de> wrote:
[…]
On one user laptop with Debian sid/unstable, unattended-upgrades does
not find upgradable packages.
From a dry run:
```
2020-12-14 09:51:17,335 INFO Checking if system is running on battery is
skipped. Please install powermgmt-base package to check power status and skip
installing updates when the system is running on battery.
2020-12-14 09:51:17,339 INFO Starting unattended upgrades script
2020-12-14 09:51:17,339 INFO Allowed origins are:
origin=Debian,codename=buster,label=Debian,
origin=Debian,codename=buster,label=Debian-Security,
origin=Debian,codename=buster-security,label=Debian-Security
2020-12-14 09:51:17,339 INFO Initial blacklist:
2020-12-14 09:51:17,339 INFO Initial whitelist (not strict):
2020-12-14 09:51:22,899 INFO No packages found that can be upgraded unattended
and no pending auto-removals
2020-12-14 09:51:22,900 INFO The list of kept packages can't be calculated in
dry-run mode.
```
But upgradable packages are there:
```
$ apt list --upgradable
Listing... Done
autoconf/unstable,unstable 2.69-12 all [upgradable from: 2.69-11.1]
dde-qt5integration/unstable 5.0.0-2.1+b2 amd64 [upgradable from: 5.0.0-2.1+b1]
fonts-font-awesome/unstable,unstable 5.0.10+really4.7.0~dfsg-4 all [upgradable
from: 5.0.10+really4.7.0~dfsg-2]
gcc-8-base/unstable 8.4.0-5 amd64 [upgradable from: 8.3.0-7]
gir1.2-gdkpixbuf-2.0/unstable 2.42.2+dfsg-1 amd64 [upgradable from:
2.40.0+dfsg-10]
...
systemd/unstable 247.1-4 amd64 [upgradable from: 247.1-3]
udev/unstable 247.1-4 amd64 [upgradable from: 247.1-3]
$ sudo apt upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages were automatically installed and are no longer
required:
libboost-filesystem1.71.0 libboost-iostreams1.71.0
Use 'sudo apt autoremove' to remove them.
The following NEW packages will be installed:
libboost-filesystem1.74.0 libboost-iostreams1.74.0
libboost-thread1.74.0 libdeflate0
The following packages have been kept back:
gcc-8-base libboost-dev
The following packages will be upgraded:
autoconf dde-qt5integration fonts-font-awesome gir1.2-gdkpixbuf-2.0
...
systemd-timesyncd udev
116 upgraded, 4 newly installed, 0 to remove and 2 not upgraded.
Need to get 101 MB of archives.
After this operation, 6,711 kB of additional disk space will be used.
Do you want to continue? [Y/n]
```
Is that expected, or am I missing something?
This (or something like that) is expected in unstable due to the fix in #960966.
Please change /etc/apt/apt.conf.d/50unattended-upgrades if you want
u-u to try very hard to upgrade things:
...
// When APT fails to mark a package to be upgraded or installed try adjusting
// candidates of related packages to help APT's resolver in finding a solution
// where the package can be upgraded or installed.
// This is a workaround until APT's resolver is fixed to always find a
// solution if it exists. (See Debian bug #711128.)
// The fallback is enabled by default, except on Debian's sid release because
// uninstallable packages are frequent there.
// Disabling the fallback speeds up unattended-upgrades when there are
// uninstallable packages at the expense of rarely keeping back packages which
// could be upgraded or installed.
// Unattended-Upgrade::Allow-APT-Mark-Fallback "true";
Thank you for the hint, but I still do not understand, why it works on
other systems. Are the kept back packages a problem? Could a log message
be added to `unattended-upgrades.log`?
APT found the upgrades on those, probably because different packages
are installed.
Yes, kept back packages are the ones making APT's work harder in
finding the upgradable ones.
When running without --dry-mode u-u already prints out more
information about held back packages.
More explanation _could_ be added, but this workaround is on by
default only in Sid and people using Sid are expected to figure out
things on their own thus I don't plan working on that part. Patches
are still welcome.
I also ran into the problem with no held back packages involved. Could
the problem be that the allowed origins for some reason do not match *sid*?
2020-12-14 09:51:17,339 INFO Allowed origins are:
origin=Debian,codename=buster,label=Debian,
origin=Debian,codename=buster,label=Debian-Security,
origin=Debian,codename=buster-security,label=Debian-Security
or
2021-06-18 11:22:11,763 INFO Erlaubte Ursprünge sind:
origin=Debian,codename=bullseye,label=Debian,
origin=Debian,codename=bullseye,label=Debian-Security,
origin=Debian,codename=bullseye-security,label=Debian-Security
`apt-cache policy show` contains:
500 http://mirror.netzwerge.de/debian sid/main amd64 Packages
release o=Debian,a=unstable,n=sid,l=Debian,c=main,b=amd64
origin mirror.netzwerge.de
and `/etc/apt/apt.conf.d/50unattended-upgrades` contains:
"origin=Debian,codename=${distro_codename},label=Debian";
"origin=Debian,codename=${distro_codename},label=Debian-Security";
"origin=Debian,codename=${distro_codename}-security,label=Debian-Security";
`debian_version` is also mentioned in the configuration file comment.
$ more /etc/debian_version
11.0
So, is the wrong codename derived on the suite sid/unstable?
Kind regards,
Paul
