Bug#1110218: marked as done (release-notes: debian-security sources in trixie shows URI not formated correctly on the PDF)
Your message dated Fri, 1 Aug 2025 18:11:14 +0200
with message-id <[🔎] 20250801181114.0986f85266e286c4d4298b29@mailbox.org>
and subject line Re: Bug#1110218: release-notes: debian-security sources in trixie shows URI not formated correctly on the PDF
has caused the Debian Bug report #1110218,
regarding release-notes: debian-security sources in trixie shows URI not formated correctly on the PDF
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.)
--
1110218: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1110218
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: release-notes
Severity: normal
X-Debbugs-Cc: guillermotorres1998@hotmail.es
Dear Maintainer,
* What led up to the situation?
I was reading the release notes and the URI was like https://security.debian.org/debian\unhbox\voidb@x\kern\z@\char‘\protect\
discretionary{\char\defaulthyphenchar}{}{}security when it should probably be https://security.debian.org/debian-security
* What exactly did you do (or not do) that was effective (or
ineffective)?
I wrote the correct debian.sources correctly and it worked but it wouldn't have worked with the documented settings
--- End Message ---
--- Begin Message ---
Hi,
Chris Hofstaedtler <zeha@debian.org> wrote (Fri, 1 Aug 2025 16:39:30 +0200):
> > -.. parsed-literal::
> > +.. code-block:: console
> >
> > Types: deb
> > URIs: https://deb.debian.org/debian
> > Suites: |RELEASENAME| |RELEASENAME|-updates
>
> This is now rendered literally. `parsed-literal` is required to
> interpolate |RELEASENAME|.
>
> Some other way will have to be found.
Hrr, you are right, I should look better.
But I found it's as easy as escaping the hyphen with a backslash.
Just pushed to git, so closing this bug.
Holger
--
Holger Wansing <hwansing@mailbox.org>
PGP-Fingerprint: 496A C6E8 1442 4B34 8508 3529 59F1 87CA 156E B076
--- End Message ---
Reply to: