On Wed, 30 Jun 2021 21:36:54 +0200 Paul Gevers <elb...@debian.org> 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.000000000 +0200
+++ libgc-7.6.4/debian/changelog	2021-06-30 22:34:37.000000000 +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 <a...@debian.org>  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.000000000 +0200
+++ libgc-7.6.4/debian/control	2021-06-30 22:34:37.000000000 +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

Reply via email to