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

Bug#1035616: marked as done (release-notes: Duplicate paragraph)

Your message dated Mon, 29 May 2023 15:03:08 +0200
with message-id <beb4dab1-d78e-d792-133d-bb9b008afd3c@debian.org>
and subject line Re: Bug#1035616: release-notes: Duplicate paragraph
has caused the Debian Bug report #1035616,
regarding release-notes: Duplicate paragraph
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.)


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

Dear Maintainer,

 In en/issues.dbk, below paragraphs seem to be duplicated.
 Not all the same, but mostly.

    <section id="before-first-reboot">
      <title>Things to do post upgrade before rebooting</title>
      <!-- If there is nothing to do -->
      <para>
        When <literal>apt full-upgrade</literal> has finished, the
        <quote>formal</quote> upgrade is complete.  For the upgrade to
        &releasename;, there are no special actions needed before
        performing a reboot.
      </para>
      <!-- If there is something to do -->
      <para condition="fixme">
        When <literal>apt full-upgrade</literal> has finished, the <quote>formal</quote> upgrade
        is complete, but there are some other things that should be taken care of
        <emphasis>before</emphasis> the next reboot.
      </para>

--- End Message ---
--- Begin Message --- 
Hi,

On 07-05-2023 11:01, Paul Gevers wrote:

On 06-05-2023 17:35, Hendrik Boom wrote:
These paragraphs use similarity to make it very clear how necessary action differ between the two cases.  I would retain them as is.
The intent of these paragraphs is to remind us to pick *either* before the release. That's why one of them has the fixme condition. 

This has just happened. The fixme is at the right place.

Paul

Attachment: OpenPGP_signature
Description: OpenPGP digital signature


--- End Message ---
Reply to: