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

release note: issue.dbk has 404 link to backports


JP translation team spotted two links to backports page returned 404 in peer review.


I think following fix it if https://backports.debian.org/backports, which is disappeared, originally pointed at the top page of backports. If this was not intended, could someone direct them to a correct page ?

diff --git a/en/issues.dbk b/en/issues.dbk
index 50211ccc..6ab0b15c 100644
--- a/en/issues.dbk
+++ b/en/issues.dbk
@@ -168,7 +168,7 @@ password [success=1 default=ignore] pam_unix.so obscure yescrypt
        NEWS file</ulink>. Transfer processes between systems running different
        Debian releases may require the buster side to be upgraded to a version
        of <systemitem role="package">rsync</systemitem> from the <ulink
-       url="" href="https://backports.debian.org/backports">https://backports.debian.org/backports">backports</ulink>
+       url="" href="https://backports.debian.org">https://backports.debian.org">backports</ulink>
@@ -329,7 +329,7 @@ kernel.unprivileged_userns_clone = 0
         only) to the version which is in bullseye. The <literal>Ruby
         Extras</literal> Maintainers are following upstream closely
         and will be releasing a version via <ulink
-        url="" href="https://backports.debian.org/backports">https://backports.debian.org/backports">backports</ulink>
+        url="" href="https://backports.debian.org">https://backports.debian.org">backports</ulink>
         as soon as it is released and they have working packages. If
         you can't wait for this to happen before upgrading, you can
         use a VM or container running buster to isolate this specific

Best Regards

Reply to: