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

Bug#1034473: marked as done (release-notes for Bookworm: additional line-break within command)

Your message dated Mon, 17 Apr 2023 06:35:34 +0200
with message-id <CB5DD98E-F55A-46C6-BA39-403557E7DE7D@mailbox.org>
and subject line Re: Bug#1034473: release-notes for Bookworm: additional line-break within command
has caused the Debian Bug report #1034473,
regarding release-notes for Bookworm: additional line-break within command
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.)


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


Chapter 5.1.5 of the release-notes has two command examples, which contain an
additional line-break, so the command does not work - strictly spoken:
https://www.debian.org/releases/testing/amd64/release-notes/ch-information.de.html#changes-to-system-logging
The whole command should be on one line instead.

The reason for this is a line-break within the <programlisting> ... </programlisting>
tags in the issues.dbk file.
Keeping the whole commandline in one line in issues.dbk fixes the issue.

A patch is attached.


Holger



-- 
Holger Wansing <hwansing@mailbox.org>
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076

diff --git a/en/issues.dbk b/en/issues.dbk
index 47eeb67a..1de96461 100644
--- a/en/issues.dbk
+++ b/en/issues.dbk
@@ -184,9 +184,11 @@
         role="package">rsyslog</systemitem> is no longer installed by
         default. If you do not want to continue using
         <literal>rsyslog</literal>, after the upgrade you can mark it
-        as automatically installed with <programlisting>apt-mark auto
-        rsyslog</programlisting> and then an <programlisting>apt
-        autoremove</programlisting> will remove it, if possible. If you have
+        as automatically installed with
+        <programlisting>apt-mark auto rsyslog</programlisting>
+        and then an
+        <programlisting>apt autoremove</programlisting>
+        will remove it, if possible. If you have
         upgraded from older Debian releases, and not accepted the
         default configuration settings, the journal may not have been
         configured to save messages to persistent storage:

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

Am 16. April 2023 21:28:41 MESZ schrieb Paul Gevers <elbrus@debian.org>:
>Dear Holger,
>
>On 16-04-2023 12:39, Holger Wansing wrote:
>> Chapter 5.1.5 of the release-notes has two command examples, which contain an
>> additional line-break, so the command does not work - strictly spoken:
>> https://www.debian.org/releases/testing/amd64/release-notes/ch-information.de.html#changes-to-system-logging
>> The whole command should be on one line instead.
>> 
>> The reason for this is a line-break within the <programlisting> ... </programlisting>
>> tags in the issues.dbk file.
>> Keeping the whole commandline in one line in issues.dbk fixes the issue.
>> 
>> A patch is attached.
>
>Thanks for noticing. For future reference, these kind of issues you are allowed to fix directly without a bug report or merge request. You're not changing the text or meaning here.

Ok, fixed in git.
Closing this bug

Holger


-- 
Sent from /e/ OS on Fairphone3

--- End Message ---
Reply to: