Bug#988963: upgrade-reports: upgrade process requires a second "apt full-upgrade"

Holger Levsen <[email protected]> Wed, 26 May 2021 19:50:53 +0000
Newsgroups gmane.linux.debian.user.testing
Message-ID <20210526195053.GA17256__12587.74881005$1622058689$gmane$org@layer-acht.org>
On Wed, May 26, 2021 at 12:00:46PM +0200, Bill Allombert wrote:
> One way to fix that is to update libgc1c2 in stable to not 
> Conflict/Replaces with libgc1.
 
while this is true, this is also not the most desireable fix, because
it should be possible to update from *any* stable installation
to the next stable, not just from the latest stable point release.

that said, it's definitly much better than not fixing this issue at all.
after all, most people will upgrade to the latest point release before
switching the release :)


-- 
cheers,
	Holger

 ⢀⣴⠾⠻⢶⣦⠀
 ⣾⠁⢠⠒⠀⣿⡁  holger@(debian|reproducible-builds|layer-acht).org
 ⢿⡄⠘⠷⠚⠋⠀  OpenPGP: B8BF54137B09D35CF026FE9D 091AB856069AAA1C
 ⠈⠳⣄

Because things are the way they are, things will not stay the way they are.
(Bertolt Brecht)
signature.asc (application/pgp-signature, 833 B)
-----BEGIN PGP SIGNATURE-----

iQIzBAABCgAdFiEEuL9UE3sJ01zwJv6dCRq4VgaaqhwFAmCupp0ACgkQCRq4Vgaa
qhymtg//R7cdGgxDxAylydZXK5PeHaW23birTDkMqE36QIXOxWrZHSywigYGBO76
E/r1jgOAb1mrgjbL7qYywUy+X7y5Bkh3Wlyak5jtt2xsusJ1wpFqirNJbu08DxUS
1k6ktM1zLUH1iZOVjQn73HTq4mFoRAU05WHDQvHvKe8n0H2bnewV8vKAiIOanP63
lgqwKWX9nJ1yD89GuzX2m23+e9ro/BUEDytPsOr9aEvFH8K5TruI0GWKBGXwf3bc
0glwjC3TRXijmxoVU0W6gcaHkfiNyYDhDsybh5mQdhfGj0Lo7mAB64LEqJdQXTag
ZYpa7rRQLLpFU4b4jX3889aHH2XNUWtglArolb8wL48SRikp+XRh4tCZahNFNKjq
S67P1uDdnbI3e1Bc+WHfO0kQBW+Ahz8we3fENksoA1LMA8elfr5i3iDb2q+AAn8C
dox8qLmb9/9WYnkjFODfIo7Qq0KTerVsVy3o9IWg9IbYMA8H4L5nLBtXpTKJfGdG
gEpREtpRqkMrbn0Jvbuwv5UOtj6M8u4nJhB3HP6UaAn1Zub/hHye8B7kEfkymahn
xGXJAOet4rHq71aYf7FfezhejmwMHroAcnJ9kwXzc+2asSjOT2WSJSCR9rD+Fe02
huAcz06dc2eeQL4/2YT2U3XoSwKqIpM6QGGFaiKKWOWspZ+JkDI=
=Cebn
-----END PGP SIGNATURE-----