Bug#988963: libgc1c2: please drop obsolete Conflicts/Replaces on libgc1 in buster, it interferes with upgrades to bullseye

Hi, On 19-07-2021 15:12, Andreas Beckmann wrote: > On Wed, 30 Jun 2021 21:36:54 +0200 Paul Gevers wrote: >> Hi libgc maintainers, > >> Can you please comment? We missed the 10.10 point release already and >> 10.11 may happen after we release bullseye, but at least we could >> improve the

Bug#988963: libgc1c2: please drop obsolete Conflicts/Replaces on libgc1 in buster, it interferes with upgrades to bullseye

On Wed, 30 Jun 2021 21:36:54 +0200 Paul Gevers wrote: Hi libgc maintainers, Can you please comment? We missed the 10.10 point release already and 10.11 may happen after we release bullseye, but at least we could improve the upgrade for people upgrading after 10.11. Do you agree with me doing

Bug#988963: libgc1c2: please drop obsolete Conflicts/Replaces on libgc1 in buster, it interferes with upgrades to bullseye

Hi libgc maintainers, On Thu, 27 May 2021 21:01:18 +0200 Paul Gevers wrote: > I'd expect our Stable Release Managers to be fine with an update like > this. I can even do it via an NMU if that's preferred. Please reassign > to the release-notes pseudo package if fixing this is unacceptable to >

Bug#988963: libgc1c2: please drop obsolete Conflicts/Replaces on libgc1 in buster, it interferes with upgrades to bullseye

Control: reassign -1 libgc1c2 1:7.6.4-0.4 Control: retitle -1 libgc1c2: please drop obsolete Conflicts on libgc1 Dear libgc maintainers, tl;dr: it was discovered that in certain cases, a full-upgrade from buster to bullseye ends with certain packages not upgraded. We found out that's caused by a