Apparently, many uploads of non-native packages without a diff and .orig.tar.gz are happening (i.e: the packages are being wrongly built as native debian packages). We need a machine-enforceable way to avoid this, as talks with other developers implied those broken uploads are rather common. One easy way to do so would be to reject any native packages (no diff and .orig.tar.gz) which have a debian version field in addition to the upstream version field. This could be done both as an lintian error as well as a katie (dinstall) REJECT. However, I could not find anywhere in policy that states that native packages cannot have a debian version field. It clearly states that packages without a debian revision cannot have a '-' in the upstream version field, but that's not the same thing. Are native packages expected to have debian version fields sometimes? If not, policy should probably be clarified, and the required lintian (and maybe katie) modifications done... -- "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
Attachment:
pgp1spjxhsnfu.pgp
Description: PGP signature