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 upgrade for people upgrading after 10.11. Do you agree with >> me doing an NMU to fix this issue? > > I've been running my local piuparts buster->bullseye upgrade tests with > the attached patch applied to src:libgc in buster. Except for some > corner cases this has resolved the majority of the upgrade paths where > the circular Conflicts previously prevented libgc1 and guile-X.Y-libs > to be upgraded. For information for all those following this bug, one of the stable release managers mentioned on IRC that they weren't convinced this bug is worth fixing for bullseye considering the timing this late in the freeze and the severity of the issue. Which means we probably should assign this bug to release-notes... Paul OpenPGP_signature Description: OpenPGP digital signature
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 an NMU to fix this issue?
I've been running my local piuparts buster->bullseye upgrade tests with
the attached patch applied to src:libgc in buster. Except for some
corner cases this has resolved the majority of the upgrade paths where
the circular Conflicts previously prevented libgc1 and guile-X.Y-libs
to be upgraded.
Andreas
diff -Nru libgc-7.6.4/debian/changelog libgc-7.6.4/debian/changelog
--- libgc-7.6.4/debian/changelog 2018-09-09 15:25:27.0 +0200
+++ libgc-7.6.4/debian/changelog 2021-06-30 22:34:37.0 +0200
@@ -1,3 +1,12 @@
+libgc (1:7.6.4-0.4+deb10u1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * libgc1c2: Downgrade 'Conflicts+Replaces: libgc1' to
+'Breaks+Replaces: libgc1 (<< 1:8)' to avoid circular Conflicts on upgrades
+to bullseye. (Closes: #988963)
+
+ -- Andreas Beckmann Wed, 30 Jun 2021 22:34:37 +0200
+
libgc (1:7.6.4-0.4) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru libgc-7.6.4/debian/control libgc-7.6.4/debian/control
--- libgc-7.6.4/debian/control 2018-09-08 17:50:13.0 +0200
+++ libgc-7.6.4/debian/control 2021-06-30 22:34:37.0 +0200
@@ -17,8 +17,8 @@
Architecture: any
Pre-Depends: ${misc:Pre-Depends}
Depends: ${misc:Depends}, ${shlibs:Depends}
-Conflicts: libgc1
-Replaces: libgc1, libgc1c3
+Breaks: libgc1 (<< 1:8)
+Replaces: libgc1 (<< 1:8), libgc1c3
Multi-Arch: same
Description: conservative garbage collector for C and C++
Boehm-Demers-Weiser's GC is a garbage collecting storage allocator that is
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 > you, but please elaborate why in that case. 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 an NMU to fix this issue? Paul OpenPGP_signature Description: OpenPGP digital signature
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 circular Conflicts. libgc1c2 (buster) conflicts with libgc1 (a package long gone; 2005), and libgc1 (bullseye) conflicts with libgc1c2. The reasonable way to fix this is in buster. On 27-05-2021 20:25, Bill Allombert wrote: > On Thu, May 27, 2021 at 09:48:29AM +0200, Paul Gevers wrote: >> On 26-05-2021 23:21, Bill Allombert wrote: >>> On Wed, May 26, 2021 at 07:50:53PM +, 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). >> >> Do I understand you correctly that we're ready to reassign this bug to >> libgc1c2 and ask for the fix in buster? > > To me there are two options: > - do nothing and document this in the release note > - fix it in stable. > but this is to the release team to decide. > > We can reassign this bug to libgc1 but it is likely to be ignored > because it cannot be fixed in testing. 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 you, but please elaborate why in that case. Paul OpenPGP_signature Description: OpenPGP digital signature
