Bug#85270: PROPOSAL] Forbiding debian-revision field for Debian-native source packages
On Thu, Feb 08, 2001 at 02:33:05PM -0200, Henrique M Holschuh wrote:
> 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.
What if upstream has a xx.xx-x version numbering? That's perfectly
legitimate. My suggestion, find the code to dinstall on auric, and patch
it to detect when a new upload changes from debian-revision to native
(going native to Debian revision shouldn't be a problem, and not require
being detected).
IMO, if such a change is valid, and key needs to be added to the .dsc to
let dinstall know it is ok.
--
-----------=======-=-======-=========-----------=====------------=-=------
/ Ben Collins -- ...on that fantastic voyage... -- Debian GNU/Linux \
` bcollins@debian.org -- bcollins@openldap.org -- bcollins@linux.com '
`---=========------=======-------------=-=-----=-===-======-------=--=---'
Reply to: