Skip to content
Commits on Source (2)
......@@ -6,7 +6,7 @@ wishlist! And see the bottom of this file for wishlist bugs someone once
expressed…
for 0.8x, during the buster development cycle:
for 0.9x, during the buster development cycle:
- fix policy reference for old footnote 53, blocked by #879048
......@@ -95,7 +95,7 @@ for 0.8x, during the buster development cycle:
(piuparts), adopting apt's naming
for 0.9x and later:
for 1.0.x and later:
- install from git/Makefile: remove the need for /etc/piuparts
......@@ -121,7 +121,7 @@ for 0.9x and later:
be nice
for 1.xx and later:
for even later:
- find_default_debian_mirrors:
- check whether find_default_debian_mirrors produces something useful if
......
......@@ -14,7 +14,7 @@ because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.
See policy 7.6 at
https://www.debian.org/doc/debian-policy/#overwriting-files-and-replacing-packages-replaces
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces
From the attached log (scroll to the bottom...):
......
......@@ -16,7 +16,7 @@ because it tries to overwrite files that are owned by other packages
without declaring a Breaks+Replaces relation.
See policy 7.6 at
https://www.debian.org/doc/debian-policy/#overwriting-files-and-replacing-packages-replaces
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces
This problem is exposed during the upgrade of the 'EXPOSER'
package, not by upgrading only the buggy package itself.
......
......@@ -16,7 +16,7 @@ because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.
See policy 7.6 at
https://www.debian.org/doc/debian-policy/#overwriting-files-and-replacing-packages-replaces
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces
From the attached log (scroll to the bottom...):
......
......@@ -16,7 +16,7 @@ but then the upgrade to 'wheezy' failed because it tries to overwrite
other packages files without declaring a Breaks+Replaces relation.
See policy 7.6 at
https://www.debian.org/doc/debian-policy/#overwriting-files-and-replacing-packages-replaces
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces
From the attached log (scroll to the bottom...):
......
......@@ -16,7 +16,7 @@ because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.
See policy 7.6 at
https://www.debian.org/doc/debian-policy/#overwriting-files-and-replacing-packages-replaces
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces
From the attached log (scroll to the bottom...):
......
......@@ -16,7 +16,7 @@ because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.
See policy 7.6 at
https://www.debian.org/doc/debian-policy/#overwriting-files-and-replacing-packages-replaces
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces
From the attached log (scroll to the bottom...):
......
......@@ -16,7 +16,7 @@ because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.
See policy 7.6 at
https://www.debian.org/doc/debian-policy/#overwriting-files-and-replacing-packages-replaces
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces
This test intentionally skipped 'testing' to find file overwrite
problems before packages migrate from 'unstable' to 'testing'.
......
......@@ -16,7 +16,7 @@ because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.
See policy 7.6 at
https://www.debian.org/doc/debian-policy/#overwriting-files-and-replacing-packages-replaces
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces
From the attached log (scroll to the bottom...):
......
......@@ -16,7 +16,7 @@ because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.
See policy 7.6 at
https://www.debian.org/doc/debian-policy/#overwriting-files-and-replacing-packages-replaces
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces
From the attached log (scroll to the bottom...):
......
......@@ -16,7 +16,7 @@ because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.
See policy 7.6 at
https://www.debian.org/doc/debian-policy/#overwriting-files-and-replacing-packages-replaces
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces
From the attached log (scroll to the bottom...):
......
......@@ -41,7 +41,7 @@ The following relationships are currently defined:
The following relationships should be added for a clean takeover of
these files
(https://www.debian.org/doc/debian-policy/#overwriting-files-and-replacing-packages-replaces):
(https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces):
Package:
Breaks:
......
......@@ -27,7 +27,7 @@ but the following files have disappeared:
This is a serious bug violating policy 7.6, see
https://www.debian.org/doc/debian-policy/#overwriting-files-and-replacing-packages-replaces
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/]
......
......@@ -21,7 +21,7 @@ https://www.debian.org/doc/debian-policy/#sharing-configuration-files
or policy chapter 6 ("Package maintainer scripts..."), see
https://www.debian.org/doc/debian-policy/#package-maintainer-scripts-and-installation-procedure
or policy 7.6 ("Overwriting files..."), see
https://www.debian.org/doc/debian-policy/#overwriting-files-and-replacing-packages-replaces
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces
If a directory is used by several packages, all should ship it as part
of the package (possibly empty, using $package.dirs to create it), and
......
piuparts (0.92) UNRELEASED; urgency=medium
* ...
* Update TODO.
* Update several URLs pointing to https://www.debian.org/doc/debian-policy
to match the new URLs since debian-policy 4.1.0.
-- Holger Levsen <holger@debian.org> Fri, 07 Sep 2018 19:55:01 +0200
......
......@@ -62,7 +62,7 @@
declaring a replaces relation.
See policy 7.6 at
https://www.debian.org/doc/debian-policy/#overwriting-files-and-replacing-packages-replaces
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces
From the attached log (scroll to the bottom...):
......
......@@ -8,7 +8,7 @@ HEADER='Packages with failed logs because they tried to overwrite other packages
HELPTEXT='
<p>
This is because the package tries to overwrite another packages files without declaring a replaces relation. See policy 7.6 at
<a href="https://www.debian.org/doc/debian-policy/#overwriting-files-and-replacing-packages-replaces" target="_blank">https://www.debian.org/doc/debian-policy/#overwriting-files-and-replacing-packages-replaces</a>.
<a href="https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces" target="_blank">https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces</a>.
</p>
<p>
According to the thread started at <a href="https://lists.debian.org/debian-devel/2009/08/msg00234.html" target="_blank">200908071233.02813.holger@layer-acht.org</a> these bugs are to be filed with severity <b>serious</b>.
......