On Wed, May 26, 2021 at 07:50:53PM +0000, Holger Levsen wrote: > 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.
I agree with you, but this is a general issue with circular dependencies (and circular conflicts) that they can only be fixed cleanly by updating stable and not testing. That is why I have always strongly recommended to avoid them. (We could of course fix it in testing by renaming libgc1 to libgc1c4 or whatever but that would create a much larger disruption than removing a useless Conflict from stable). Cheers, -- Bill. <ballo...@debian.org> Imagine a large red swirl here.