Commit 2e455394 authored by Holger Levsen's avatar Holger Levsen

htdocs/news.tpl: explain the result of these changes.

Signed-off-by: Holger Levsen's avatarHolger Levsen <holger@layer-acht.org>
parent b705a3c6
...@@ -13,6 +13,7 @@ piuparts (0.95) UNRELEASED; urgency=medium ...@@ -13,6 +13,7 @@ piuparts (0.95) UNRELEASED; urgency=medium
- conf/crontab-master.in: run detect_well_known_errors, piuparts-report - conf/crontab-master.in: run detect_well_known_errors, piuparts-report
and piuparts-analyze through the new master_shell_runner script. and piuparts-analyze through the new master_shell_runner script.
- piuparts-report.py: add navigation link to https://piuparts.d.o/logs/ - piuparts-report.py: add navigation link to https://piuparts.d.o/logs/
- htdocs/news.tpl: explain the result of these changes.
[ Andreas Beckmann ] [ Andreas Beckmann ]
* Clarify errors from installing objects over existing symlinks. * Clarify errors from installing objects over existing symlinks.
......
...@@ -6,9 +6,13 @@ ...@@ -6,9 +6,13 @@
</tr> </tr>
<tr class="normalrow"> <tr class="normalrow">
<td class="contentcell2"> <td class="contentcell2">
<b>2018-10-19</b>: Three and a half years after stopping linking to packages.qa.debian.org(which was called <em>PTS</em>) we finally drop all references to the PTS and use <em>tracker.d.o</em> instead. <b>2018-11-28</b>: The output of various maintenance scripts is now available at <a href="https://piuparts.debian.org/logs/" target="_blank">https://piuparts.debian.org/logs/</a> instead of sending it via mails to the piuparts.d.o maintainers only.
</td> </td>
</tr> </tr>
<tr class="normalrow">
<td class="contentcell2">
<b>2018-10-19</b>: Three and a half years after stopping linking to packages.qa.debian.org (which was called <em>PTS</em>) we finally drop all references to the PTS and use <em>tracker.d.o</em> instead.
</td>
</tr> </tr>
<tr class="normalrow"> <tr class="normalrow">
<td class="contentcell2"> <td class="contentcell2">
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment