Bug#915246: [Aptitude-devel] Bug#931536: aptitude update fails to cope with changed release info

2019-07-07 Thread Francesco Poli
On Sun, 7 Jul 2019 15:54:04 +0200 Axel Beckert wrote:

> Hi Francesco, Michael and Sven,

Hello Axel, thanks for chiming in!

[...]
> I though must admit that we actually were aware of this issue
[...]
> But admittedly I totally underestimated its severity
[...]
> Sorry for that.

It's OK, luckily we have the simple "apt update" workaround (although
many people will have to be informed about it...).

> 
> I hope that Manuel (CCc'ed) can provide a fix which we then can also
> apply to aptitude in Buster in the first minor update which is
> expected in about a month.

I am looking forward to seeing this fix implemented.

Bye!


-- 
 http://www.inventati.org/frx/
 There's not a second to spare! To the laboratory!
. Francesco Poli .
 GnuPG key fpr == CA01 1147 9CD2 EFDF FB82  3925 3E1C 27E1 1F69 BFFE


pgp_A4UmooiTz.pgp
Description: PGP signature


Bug#915246: [Aptitude-devel] Bug#931536: aptitude update fails to cope with changed release info

2019-07-07 Thread Axel Beckert
Hi Francesco, Michael and Sven,

Francesco Poli (wintermute) wrote:
> As you know, Debian buster has been released yesterday and the current
> Debian testing has just been renamed from 'buster' to 'bullseye'.
> 
> Good, but... today I tried to update the repository lists and upgrade
> my Debian testing boxes with aptitude:
[…]
>   E: Repository 'http://deb.debian.org/debian testing InRelease' changed its 
> 'Codename' value from 'buster' to 'bullseye'
>   E: Failed to download some files
>   W: Failed to fetch http://deb.debian.org/debian/dists/testing/InRelease: 
>   E: Some index files failed to download. They have been ignored, or old ones 
> used instead.

Indeed. This also seems to have an impact where buster changed from
"testing" to "stable", see https://bugs.debian.org/931543.

That's actually prompted by a change in libapt (as Sven already
pointed out in #931543) which aptitude indeed hasn't been updated a
for.

I though must admit that we actually were aware of this issue as I ran
into it with a third-party repo a few months ago, see
https://bugs.debian.org/915246. But admittedly I totally
underestimated its severity and especially also its impact at release
time as I didn't think of that exactly the same will happen when
Debian shifts all suite names at release time. Sorry for that.

I hope that Manuel (CCc'ed) can provide a fix which we then can also
apply to aptitude in Buster in the first minor update which is
expected in about a month.

The official workaround is to use "apt update" once inbetween, answer
its questions (with "y" :-) and then continue to use aptitude.

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE