Hi Martin-Éric Racine, Martin-Éric Racine <[email protected]> ezt írta (időpont: 2020. febr. 2., V, 15:54): > > su 2. helmik. 2020 klo 16.50 Bálint Réczey ([email protected]) kirjoitti: > > Martin-Éric Racine <[email protected]> ezt írta (időpont: > > 2020. febr. 2., V, 15:33): > > > > > > Package: unattended-upgrades > > > Version: 1.17 > > > Severity: important > > > > > > -----BEGIN PGP SIGNED MESSAGE----- > > > Hash: SHA256 > > > > > > Since a few days, MOTD includes the following stanza: > > > > > > 1 updates could not be installed automatically. For more details, > > > see /var/log/unattended-upgrades/unattended-upgrades.log > > > > > > The log doesn't show any failure. It only shows a succesful upgrade for a > > > handful of packages. > > > > > > Additionally, there doesn't seem to be any way to make this mention > > > disappear from MOTD. > > > > The list of packages can be found in /var/lib/unattended-upgrades/kept-back > > There is one package mentioned there. It however seems to be > up-to-date. Shouldn't kept-back have been cleared once the situation > resolved itself? > > > There are bugs open about explaining why packages are kept back in the log: > > #903874 , LP: #1850964 > > I'm not looking for the explanation for why they were kept back. > > > Is yours a case where a package is kept back or a different one? > > My case is a persistent MOTD notice about a kept back package that > evidently is no longer kept back and not being able to make the > incorrect notice disappear.
The next successful run of unattended-upgrades is expected to clear the kept-back file and as a result make the MOTD notice disappear. Could you please run u-u with --verbose --debug to see if it removes the file or tell why it does not do so? Thanks, Balint
