Bug#514853: lintian: Distribution field conforming to standard is not accepted
On Wed, 2009-02-11 at 15:28 +, Adam D. Barratt wrote: Kiss Gabor (Bitman) wrote, Wednesday, February 11, 2009 2:13 PM It seems that this elsif statement does NOT conform with Debian Policy Manual. It accepts this: Distribution: no-such-distro-backports foo bar but refuses reasonable list of distributions. The fact that the above is currently accepted is a bug in a couple of the regexes; I'll fix that. (Well, no-such-distro-backports may still be accepted, at least in the short term, but that won't stop foo and bar being rejected as invalid). Uploading a single package to multiple distributions has been deprecated for a number of years. It was used in the past to allow uploads to unstable and the old frozen distribution, before the current testing implementation was introduced; since testing was introduced, packages that would be suitable for both distributions are instead uploaded to unstable and migrate to testing (possibly with some assistance from the Release Team). As a matter of interest, I asked one of the FTP-team to check when the feature was last used. There were three uploads using multiple distributions in 2003 and one in 2004, which was the last one to date. A quick update for you, the bug, and anyone else who isn't following the -policy list. I filed bug #514919 against Policy to clarify the situation with respect to multiple distribution handling in .changes files. Although the discussion is still ongoing, the likely result is that a statement will be added to the relevant section of Policy indicating that the use of multiple distributions is valid in general, but not supported by the Debian archive. (It is currently supported, although deprecated, and no-one has any idea whether it actually works; it's likely to become unsupported in the near future). In terms of Lintian, this means that for a Distribution field such as testing unstable, you will lose the warnings about the distributions being invalid, as each individual distribution will be checked against the known list. There will, however, be a new error tag (activated once the archive has been changed) indicating that Debian does not accept such uses of Distribution. If you're using the package in an environment which accepts the syntax and not intending to upload it to Debian then an override would be appropriate. Regards, Adam -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#514853: lintian: Distribution field conforming to standard is not accepted
Package: lintian Version: 1.24.2.1 Severity: normal Debian Policy Manual section 5.6.14 Distribution writes: In a .changes file or parsed changelog output this contains the (space-separated) name(s) of the distribution(s) where this version of the package should be installed. However this line is refused by lintian: Distribution: testing stable $ lintian ../kmt_0.5-1_i386.changes E: kmt_0.5-1_i386.changes: bad-distribution-in-changes-file testing stable $ If I delete word stable or testing it works well. Gabor -- System Information: Debian Release: 5.0 APT prefers testing-proposed-updates APT policy: (500, 'testing-proposed-updates'), (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.26-1-686 (SMP w/2 CPU cores) Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/bash Versions of packages lintian depends on: ii binutils2.18.1~cvs20080103-7 The GNU assembler, linker and bina ii diffstat1.45-2 produces graph of changes introduc ii dpkg-dev1.14.25 Debian package development tools ii file4.26-1 Determines file type using magic ii gettext 0.17-4 GNU Internationalization utilities ii intltool-debian 0.35.0+20060710.1Help i18n of RFC822 compliant conf ii libdigest-sha-perl 5.47-1 Perl extension for SHA-1/224/256/3 ii libparse-debianchan 1.1.1-2 parse Debian changelogs and output ii libtimedate-perl1.1600-9 Time and date functions for Perl ii liburi-perl 1.35.dfsg.1-1Manipulates and accesses URI strin ii man-db 2.5.2-4 on-line manual pager ii perl [libdigest-sha 5.10.0-19Larry Wall's Practical Extraction lintian recommends no packages. Versions of packages lintian suggests: pn binutils-multiarchnone (no description available) pn libtext-template-perl none (no description available) ii man-db2.5.2-4on-line manual pager -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#514853: lintian: Distribution field conforming to standard is not accepted
Gabor Kiss wrote, Wednesday, February 11, 2009 11:57 AM [...] Debian Policy Manual section 5.6.14 Distribution writes: In a .changes file or parsed changelog output this contains the (space-separated) name(s) of the distribution(s) where this version of the package should be installed. However this line is refused by lintian: Distribution: testing stable That section of Policy also claims that frozen is a valid distribution and that one can't upload to testing (although it could be argue that tpu isn't testing), so it could possibly do with some attention. :-/ Whilst testing stable is technically valid, I'm not entirely sure that all parts of the archive software would do the right thing with such a package. Regards, Adam -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#514853: lintian: Distribution field conforming to standard is not accepted
That section of Policy also claims that frozen is a valid distribution and
that one can't upload to testing (although it could be argue that tpu isn't
testing), so it could possibly do with some attention. :-/
Whilst testing stable is technically valid, I'm not entirely sure that all
parts of the archive software would do the right thing with such a package.
Actually I'm unable to find a pair of distributions that would be accepted:
E: kmt_0.5-2_i386.changes: bad-distribution-in-changes-file stable unstable
E: kmt_0.5-2_i386.changes: bad-distribution-in-changes-file stable experimental
E: kmt_0.5-2_i386.changes: bad-distribution-in-changes-file unstable
experimental
E: kmt_0.5-2_i386.changes: bad-distribution-in-changes-file unstable frozen
Could you show a working example please?
Code snippet from /usr/bin/lintian:
} elsif (! (($data-{distribution} eq 'stable')
or ($data-{distribution} eq 'testing')
or ($data-{distribution} eq 'unstable')
or ($data-{distribution} eq 'experimental')
or ($data-{distribution} =~ /\w+-backports/)
or ($data-{distribution} =~ /\w+-proposed-updates/)
or ($data-{distribution} =~ /\w+-security/))
) {
# bad distribution entry
tag(bad-distribution-in-changes-file,
$data-{distribution});
}
It seems that this elsif statement does NOT conform with Debian Policy Manual.
It accepts this:
Distribution: no-such-distro-backports foo bar
but refuses reasonable list of distributions.
Regards
Gabor
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#514853: lintian: Distribution field conforming to standard is not accepted
Kiss Gabor (Bitman) wrote, Wednesday, February 11, 2009 2:13 PM That section of Policy also claims that frozen is a valid distribution and that one can't upload to testing (although it could be argue that tpu isn't testing), so it could possibly do with some attention. :-/ Whilst testing stable is technically valid, I'm not entirely sure that all parts of the archive software would do the right thing with such a package. Actually I'm unable to find a pair of distributions that would be accepted: [...] Could you show a working example please? I meant that it was technically valid according to Policy, not that it would work with Lintian. It seems that this elsif statement does NOT conform with Debian Policy Manual. It accepts this: Distribution: no-such-distro-backports foo bar but refuses reasonable list of distributions. Uploading a single package to multiple distributions has been deprecated for a number of years. It was used in the past to allow uploads to unstable and the old frozen distribution, before the current testing implementation was introduced; since testing was introduced, packages that would be suitable for both distributions are instead uploaded to unstable and migrate to testing (possibly with some assistance from the Release Team). As a matter of interest, I asked one of the FTP-team to check when the feature was last used. There were three uploads using multiple distributions in 2003 and one in 2004, which was the last one to date. As I mentioned in my earlier mail, I'm inclined to suggest that this is a bug in Policy, as there's next to no practical application for such uploads. A package built for testing is unlikely to be suitable for direct installation (in the archive sense) in to stable. Out of interest, what is your use case for this feature? Regards, Adam -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
