Package: debian-policy
Version: 3.5.0.0
Severity: wishlist
Currently it is impossible to verify when a source package is mistakenly
uploaded in debian-native source format (.tar.gz + .dsc) instead of
non-native source format (.orig.tar.gz + .diff.gz + .dsc).
Such broken uploads are reasonably common (someone gave me a figure of about
10 per dinstall run in IRC). They not only make a mess in the archive, but
also cause bandwidth loss as the next upload will have to include the entire
source .tar.gz (or .orig.tar.gz if the maintainer notices the mistake and
tries to go back to non-native source format).
Should debian-native *source* packages (.tar.gz + .dsc) be forbidden to
include a debian revision field, the problem would be detectable, and both
lintian and katie (dinstall) could be made to flag such uploads as improper.
Universal diff of the proposed change in policy text is attached below.
-- System Information
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux godzillah.rivendell.sol 2.2.18 #1 Thu Dec 28 19:08:58 BRST 2000
i586
Versions of packages debian-policy depends on:
ii fileutils 4.0.37-1 GNU file management utilities.
--
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot
Henrique Holschuh
--- policy.text.pristine Thu Feb 8 13:30:22 2001
+++ policy.text Thu Feb 8 13:37:50 2001
@@ -1114,6 +1114,8 @@
Debian binary package, and so there is only one `debianization'
of it and therefore no revision indication is required.
+ Debian-native source packages cannot have a <debian-revision>.
+
It is conventional to restart the <debian-revision> at `1' each
time the <upstream-version> is increased.
