[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#991721: marked as done (release-notes: mention known RC bugs in bullseye)

Your message dated Wed, 4 Aug 2021 20:40:30 +0200
with message-id <957a385f-857d-b7fd-dda3-34618c960067@debian.org>
and subject line Re: Bug#991721: release-notes: mention known RC bugs in bullseye
has caused the Debian Bug report #991721,
regarding release-notes: mention known RC bugs in bullseye
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
991721: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991721
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release-notes
Severity: normal
Tags: patch

I want to collect RC bugs worth mentioning in the release
notes. Here's a proposal for the text and table. Obviously I'll be
filing the table soon and automated.

Paul

>From 801cc2747e4ffbf67125f4985a3249ec586cc487 Mon Sep 17 00:00:00 2001
From: Paul Gevers <elbrus@debian.org>
Date: Fri, 30 Jul 2021 21:50:32 +0200
Subject: [PATCH] issues.dbk: known RC bugs

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

diff --git a/en/issues.dbk b/en/issues.dbk
index ec8b75e8..0ea1b121 100644
--- a/en/issues.dbk
+++ b/en/issues.dbk
@@ -862,4 +862,40 @@ Pin-Priority: 900
       </para>
     </section>
   </section>
+  <section id="rc-bugs">
+    <title>Known severe bugs</title>
+    <para>
+      Although Debian releases when it's ready, that unfortunately
+      doesn't mean there are no known bugs. As part of the release
+      process all the bugs of severity serious or higher are actively
+      tracked by the Release Team, so an <ulink
+      url="&url-bts;tag:bullseye-ignore">overview of those
+      bugs</ulink> that were tagged to be ignored in the last part of
+      releasing &releasename; can be found in the <ulink
+      url="&url-bts;">Debian Bug Tracking System</ulink>. The
+      following bugs were affecting &releasename; at the time of the
+      release and worth mentioning in this document:
+    </para>
+    <informaltable pgwide="1">
+      <tgroup cols="3">
+	<colspec align="justify"/>
+	<colspec align="justify"/>
+	<colspec align="justify"/>
+	<thead>
+	  <row>
+	    <entry>Bug number</entry>
+	    <entry>Package (source or binary)</entry>
+	    <entry>Description</entry>
+	  </row>
+	</thead>
+	<tbody>
+	  <row arch="armhf">
+	    <entry><ulink url="&url-bts;982794">982794</ulink></entry>
+	    <entry><systemitem role="package">firefox-esr</systemitem></entry>
+	    <entry>firefox-esr/armhf: fails on non-NEON systems</entry>
+	  </row>
+	</tbody>
+      </tgroup>
+    </informaltable>
+  </section>
 </chapter>
-- 
2.30.2

--- End Message ---
--- Begin Message --- 
On 04-08-2021 12:06, Justin B Rye wrote:
> This and #988963 look okay to me [...]
So, closing.

Paul

Attachment: OpenPGP_signature
Description: OpenPGP digital signature


--- End Message ---
Reply to: