Bug#988963: release-notes: document libgc1c2 situation

[Paul Gevers <elbrus@debian.org>]

Package: libgc1c2
Followup-For: Bug #988963
X-Debbugs-Cc: debian-doc@lists.debian.org
Control: reassing -1 release-notes

Hi,

Please find attached my proposal how to document the issue with
libgc1c2 upgrades.

Paul

>From ace0b20825c99c394844233b73c5601cb09d2bb1 Mon Sep 17 00:00:00 2001
From: Paul Gevers <elbrus@debian.org>
Date: Fri, 30 Jul 2021 22:17:56 +0200
Subject: [PATCH] issues.dbk: libgc1c2 can be hold back

---
 en/issues.dbk | 12 ++++++++++++
 1 file changed, 12 insertions(+)

diff --git a/en/issues.dbk b/en/issues.dbk
index ec8b75e8..ad632266 100644
--- a/en/issues.dbk
+++ b/en/issues.dbk
@@ -451,6 +451,18 @@ data = ${lookup{$local_part}lsearch{/some/path/$domain_data/aliases}}
     </para>
   </section>
 
+  <section id="libgc1">
+    <title>Upgrades involving libgc1c2 need two runs</title>
+    <para>
+      Packages that depend on <systemitem
+      role="package">libgc1c2</systemitem> in buster may be held back
+      during the first full upgrade run to bullseye. Doing a second
+      upgrade normally solves the issue. The background of the issue
+      can be found in <ulink url="&url-bts;988963">bug
+      #988963</ulink>.
+    </para>
+  </section>
+
   <section id="before-first-reboot">
       <title>Things to do post upgrade before rebooting</title>
       <!-- If there is nothing to do -->
-- 
2.30.2