TODO

@@ -8,8 +8,6 @@ expressed…
 
 for 0.9x, during the buster development cycle:
 
-- fix policy reference for old footnote 53, blocked by #879048
-
 - README_server.txt: rewrite style a bit more. its super easy to setup now!
 
 - ==== piuparts.debian.org specific configuration
@@ -27,10 +25,6 @@ for 0.9x, during the buster development cycle:
     on the master arch to slaves of different archs ->
     "schedule-evenly-to-slaves = no"
 
-- once that works, update README_pejacevic: search for "soon shall go into operation..."
-
-- piuparts-master: keep track of to whom a reservation was given
-
 - more stats and graphs:
   - new section stats page:
     - packages processed per day and section, master writes submissions.txt
@@ -44,10 +38,6 @@ for 0.9x, during the buster development cycle:
   If master does that remove that sentence from README_server.txt again,
   same with slave and tmp.
 
-- piuparts.conf.pejacevic: maybe use mirror via nfs (faster)
-
-- maybe compress all logfiles
-
 - if it weren't for 'slave-bin/slave_cleanup', the slave would only need
   rights to run "sudo piuparts" but nothing else. If we can clean this up,
   the sudoers.d should recommend sudo (lsof|kill|umount) for admins.
@@ -97,6 +87,12 @@ for 0.9x, during the buster development cycle:
 
 for 1.0.x and later:
 
+- piuparts.conf.pejacevic: maybe use mirror via nfs (faster)
+
+- maybe compress all logfiles
+
+- piuparts-master: keep track of to whom a reservation was given
+
 - install from git/Makefile: remove the need for /etc/piuparts
 
 - accept a PIUPARTS_CONF environment variable everywhere to point to a different

bug-templates/postinst_uses_usr_share_doc.mail

@@ -13,7 +13,7 @@ a test with piuparts revealed that your package uses files from
 /usr/share/doc in its maintainer scripts which is a violation of
 Policy 12.3: "Packages must not require the existence of any files in
 /usr/share/doc/ in order to function."
-https://www.debian.org/doc/debian-policy/#additional-documentation
+https://www.debian.org/doc/debian-policy/ch-docs.html#additional-documentation
 
 These files must be moved to /usr/share/$PACKAGE and may be symlinked
 from /usr/share/doc/$PACKAGE.

bug-templates/removal_makes_files_disappear.mail

@@ -28,9 +28,8 @@ but the following files have disappeared:
 
 This is a serious bug violating policy 7.6, see
 https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces
-and also see the footnote that describes this incorrect behavior
-https://www.debian.org/doc/debian-policy/ (old: footnotes.html#f53)
-[footnote permalink broken (#879048), search for /To see why/]
+and also see the footnote that describes this incorrect behavior:
+https://www.debian.org/doc/debian-policy/ch-relationships.html#id13
 
 The $OFFENDER package has the following relationships with $VICTIM:
 

bug-templates/removes_files_installed_by_other_package.mail

@@ -17,9 +17,9 @@ they may have been shipped or created by a dependency.
 
 This could be a violation of policy 10.7.4 ("Sharing configuration
 files"), see
-https://www.debian.org/doc/debian-policy/#sharing-configuration-files
+https://www.debian.org/doc/debian-policy/ch-files.html#sharing-configuration-files
 or policy chapter 6 ("Package maintainer scripts..."), see
-https://www.debian.org/doc/debian-policy/#package-maintainer-scripts-and-installation-procedure
+https://www.debian.org/doc/debian-policy/ch-maintainerscripts.html
 or policy 7.6 ("Overwriting files..."), see
 https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces
 

known_problems/cron_error_after_removal_error.conf

@@ -7,7 +7,7 @@ ISSUE=0
 HEADER='Packages with failed logs because a cron file has output and/or exits with error after the package has been removed'
 HELPTEXT='
 <p>
-From <a href="https://www.debian.org/doc/debian-policy/#cron-jobs" target="_blank">https://www.debian.org/doc/debian-policy/#cron-jobs</a>
+From <a href="https://www.debian.org/doc/debian-policy/ch-opersys.html#cron-jobs" target="_blank">https://www.debian.org/doc/debian-policy/ch-opersys.html#cron-jobs</a>
 </p>
 
 <pre>