On Sun, Aug 15, 2021 at 04:00:07PM +0100, Adam D. Barratt wrote: > On Sun, 2021-08-15 at 16:08 +0200, Csillag Tamas wrote: [...] > > E: Repository 'http://security.debian.org buster/updates InRelease' > > changed its 'Suite' value from 'stable' to 'oldstable' > > N: This must be accepted explicitly before updates for this > > repository can be applied. See apt-secure(8) manpage for details. > > E: Repository 'http://deb.debian.org/debian buster InRelease' changed > > its 'Suite' value from 'stable' to 'oldstable' > > N: This must be accepted explicitly before updates for this > > repository can be applied. See apt-secure(8) manpage for details. > > E: Repository 'http://ftp.de.debian.org/debian buster InRelease' > > changed its 'Suite' value from 'stable' to 'oldstable' > > N: This must be accepted explicitly before updates for this > > repository can be applied. See apt-secure(8) manpage for details. > > > > 100 # cat /etc/debian_version > > 10.9 > > At the risk of asking a possibly silly question, why are you not > running 10.*10*, which was released in June and contained an APT > package that downgraded that particular change to a notice?
That is a fair question and the reason is: I have machines auto upgrading and rebooting when they have their uptime over 30 days however this automation was temporary disabled for a few weeks because I had my wedding. (It is staggered and made with some ansible and a cronjob.) If 10.10 fixes apt-get that explains why I see this only on a handful of machines (most are on 10.10). This also means that indeed the ad-hoc fix should be only needed once and last, but not for future releases. This is good. Thanks, cstamas --
