Your message dated Thu, 24 Apr 2014 19:12:06 +0200
with message-id <[email protected]>
and subject line Re: [Pkg-systemd-maintainers] Bug#745650: changelog: Do not
use UTF-8 punctuation marks but the ASCII ones
has caused the Debian Bug report #745650,
regarding changelog: Do not use UTF-8 punctuation marks but the ASCII ones
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 [email protected]
immediately.)
--
745650: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=745650
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: init-system-helpers
Version: 1.18
Severity: minor
Tags: patch
Dear Maintainer,
* What led up to the situation?
When reading the changelog file with character map ISO-8859-1, three
bytes are sometimes shown instead of one. Using non-letter characters
with the UTF-8 encoding is a misuse of it.
* What outcome did you expect instead?
I expect simple punctuation marks (for example apostrophe, quotation
mark and ' - ' (or '--', em-dash)), which is readable by any encoding
that supports the ASCII character set. (em-dash is usually used
without surrounding space, en-dash with it.)
That is future proof and clear enough. This file does not contain
any typesetting commands to prepare it for being printed in a book as a
regular text.
Patch:
--- changelog 2014-04-22 21:46:15.000000000 +0000
+++ changelog.new 2014-04-22 21:46:37.000000000 +0000
@@ -1,12 +1,12 @@
init-system-helpers (1.18) unstable; urgency=low
- * d-s-h: add âpurgeâ verb, use it in autoscripts. (Closes: #721244)
+ * d-s-h: add "purge" verb, use it in autoscripts. (Closes: #721244)
-- Michael Stapelberg <[email protected]> Tue, 25 Feb 2014 19:36:18 +0100
init-system-helpers (1.17) unstable; urgency=low
- * d-s-h: donât error out when masking a service is not possible because
+ * d-s-h: don't error out when masking a service is not possible because
/etc/systemd/system/<service> already exists (but is not a symlink).
(Closes: #739090)
@@ -14,7 +14,7 @@ init-system-helpers (1.17) unstable; urg
init-system-helpers (1.16) unstable; urgency=low
- * Donât delete /etc/systemd/, only the hierarchy below
/etc/systemd/system/.
+ * Don't delete /etc/systemd/, only the hierarchy below /etc/systemd/system/.
This is necessary to fix piuparts warnings since we ship
/etc/systemd/system since i-s-h 1.15 (Thanks Andreas Beckmann).
@@ -25,7 +25,7 @@ init-system-helpers (1.15) unstable; urg
* ship /etc/systemd/system to avoid piuparts warnings
* d-s-h: add spaces to allow the manpage to break lines with MANWIDTH=80
* i-s-h: override lintian warning spelling-error-in-manpage, we cannot
- rename the upstream command âsystemctl reenableâ into âre-enableâ
+ rename the upstream command "systemctl reenable" into "re-enable"
* bump standards-version to 3.9.5 (no changes necessary)
-- Michael Stapelberg <[email protected]> Fri, 07 Feb 2014 20:18:34 +0100
@@ -45,7 +45,7 @@ init-system-helpers (1.13) unstable; urg
init-system-helpers (1.12) unstable; urgency=low
* dh_systemd: lower generated dependency from 1.11 to 1.11~
- * d-s-h: Donât print action(s) to stderr, no news are good news
+ * d-s-h: Don't print action(s) to stderr, no news are good news
(Closes: #723727)
-- Michael Stapelberg <[email protected]> Mon, 04 Nov 2013 19:52:10 +0100
@@ -122,7 +122,7 @@ init-system-helpers (1.4) unstable; urge
init-system-helpers (1.3) unstable; urgency=low
* deb-systemd-helpe): replicate /etc/systemd/system in state dir
- * deb-systemd-helper: delete state file on remove if user didnât disable
+ * deb-systemd-helper: delete state file on remove if user didn't disable
service
* deb-systemd-helper: always store .dsh-also state, not only when creating
links
@@ -133,7 +133,7 @@ init-system-helpers (1.3) unstable; urge
init-system-helpers (1.2) unstable; urgency=low
* split dh_systemd into dh_systemd_start and dh_systemd_enable. This makes
- each helper much easier and allows us to do the right thing â we need to
+ each helper much easier and allows us to do the right thing -- we need to
run parts of the code _before_ dh_installinit and parts of the code
_afterwards_.
* deb-systemd-helper: only remove state file on purge.
-- System Information:
Debian Release: jessie/sid
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500,
'testing'), (500, 'stable')
Architecture: i386 (i586)
Kernel: Linux 3.2.53-rt75-1
Locale: LANG=is_IS, LC_CTYPE=is_IS (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash
Versions of packages init-system-helpers depends on:
ii perl 5.18.2-2+b1
init-system-helpers recommends no packages.
init-system-helpers suggests no packages.
-- no debconf information
--
Bjarni I. Gislason
--- End Message ---
--- Begin Message ---
Hi Bjarni,
Bjarni Ingi Gislason <[email protected]> writes:
> Package: init-system-helpers
> Version: 1.18
> Severity: minor
> Tags: patch
>
> Dear Maintainer,
>
> * What led up to the situation?
>
> When reading the changelog file with character map ISO-8859-1, three
> bytes are sometimes shown instead of one. Using non-letter characters
> with the UTF-8 encoding is a misuse of it.
>
> * What outcome did you expect instead?
>
> I expect simple punctuation marks (for example apostrophe, quotation
> mark and ' - ' (or '--', em-dash)), which is readable by any encoding
> that supports the ASCII character set. (em-dash is usually used
> without surrounding space, en-dash with it.)
>
> That is future proof and clear enough. This file does not contain
> any typesetting commands to prepare it for being printed in a book as a
> regular text.
I don’t think this is necessary or beneficial. Since debian-policy
3.6.0, changelog files should be UTF-8 encoded, since 3.8 (from 2009!),
they _must_ be. See also http://bugs.debian.org/241333
If your setup can’t handle that, please fix your setup.
If some tool has trouble with that, please report a bug against the
tool.
--
Best regards,
Michael
--- End Message ---
