Bug#1001651: marked as done (lintian: changelog-file-missing-explicit-entry: false positives with successive stable uploads)
Your message dated Mon, 20 Jun 2022 14:34:13 + with message-id and subject line Bug#941656: fixed in lintian 2.115.0 has caused the Debian Bug report #941656, regarding lintian: changelog-file-missing-explicit-entry: false positives with successive stable uploads to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 941656: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941656 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: lintian Version: 2.104.0 Severity: important Hi, This is similar to #941656, but I wanted to have it tracked separately, with a slightly higher priority, as that's affecting people performing regular uploads to stable. I would expect this to apply to backports and security as well but I didn't perform any checks there. Anyway, in this particular case, preparing the debian-installer upload for bullseye, I received: W: debian-installer source: changelog-file-missing-explicit-entry 20210731+deb11u1 -> 20210731 (missing) -> 20210731+deb11u2 while the changelog is clearly what it should be: ,--- | debian-installer (20210731+deb11u2) bullseye; urgency=medium | | * Bump Linux kernel ABI to 5.10.0-10. | | -- Cyril Brulebois Mon, 13 Dec 2021 16:23:43 +0100 | | debian-installer (20210731+deb11u1) bullseye; urgency=medium | | * Set USE_PROPOSED_UPDATES=1 for the bullseye stable branch. | * Update USE_UDEBS_FROM default from unstable to bullseye, so that | users don't have to know about the debian/rules heuristics when | performing manual, local builds. | * Bump Linux kernel ABI to 5.10.0-9. | | -- Cyril Brulebois Mon, 04 Oct 2021 10:07:27 +0200 | | debian-installer (20210731) unstable; urgency=medium | | [ Cyril Brulebois ] | * Update translation-status for the release. | | [ Steve McIntyre ] | * Make mini.iso work with UEFI boot | * Bump Linux kernel ABI to 5.10.0-8 | | -- Cyril Brulebois Sat, 31 Jul 2021 06:20:00 +0200 `--- Cheers, -- Cyril Brulebois (k...@debian.org)<https://debamax.com/> D-I release manager -- Release team member -- Freelance Consultant --- End Message --- --- Begin Message --- Source: lintian Source-Version: 2.115.0 Done: Axel Beckert We believe that the bug you reported is fixed in the latest version of lintian, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 941...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Axel Beckert (supplier of updated lintian package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 20 Jun 2022 13:23:02 +0200 Source: lintian Architecture: source Version: 2.115.0 Distribution: unstable Urgency: medium Maintainer: Debian Lintian Maintainers Changed-By: Axel Beckert Closes: 657390 932634 941656 963099 989381 995286 996740 999768 999810 1000234 1000977 1001655 1002828 1003131 1003272 1003353 1003456 1003668 1003817 1003913 1003941 1004231 1004239 1004240 1004660 1005046 1005184 1005762 1006390 1006859 1007140 1007257 1012090 Changes: lintian (2.115.0) unstable; urgency=medium . The Lintian Resurrection Release. . * Summary of tag changes: + Added: - alien-tag - chown-with-dot - conflicting-test-fields - declare-python-versions-for-test - drop-python-version-declaration - invalid-override-restriction - missing-prerequisite-for-pyproject-backend - old-devhelp-standard - stray-devhelp-documentation - test-leaves-python-version-untested - uses-poetry-cli + Removed: - crossing-screens - debhelper-compatibility-level-not-a-number - debian-tests-control-and-control-autodep8 - exclusive-runtime-tests-field - package-contains-devhelp-file-without-symlink . [ Axel Beckert ] * Adopting Lintian. (Changes #1012289 from ITA to pure RFH.) + Remove Chris Lamb from Uploaders (see #1012289) and re-add myself. * Workarounds until https://github.com/Perl-Critic/Perl-Critic/issues/925 is fixed: + Replace all occurrences of "Copyright ©" with "Copyright (C)" again. + Remove unn
Processed: Re: Bug#1001651: lintian: changelog-file-missing-explicit-entry: false positives with successive stable uploads
Processing control commands: > forcemerge 941656 -1 Bug #941656 [lintian] lintian: changelog-file-missing-explicit-entry not working properly Bug #941656 [lintian] lintian: changelog-file-missing-explicit-entry not working properly Marked as found in versions lintian/2.104.0. Bug #1001651 [lintian] lintian: changelog-file-missing-explicit-entry: false positives with successive stable uploads Severity set to 'normal' from 'important' Marked as found in versions lintian/2.24.0. Merged 941656 1001651 > severity 941656 important Bug #941656 [lintian] lintian: changelog-file-missing-explicit-entry not working properly Bug #1001651 [lintian] lintian: changelog-file-missing-explicit-entry: false positives with successive stable uploads Severity set to 'important' from 'normal' Severity set to 'important' from 'normal' -- 1001651: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001651 941656: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941656 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1001651: lintian: changelog-file-missing-explicit-entry: false positives with successive stable uploads
Control: forcemerge 941656 -1 Control: severity 941656 important Hi, On Mon, Dec 13, 2021 at 11:00 AM Cyril Brulebois wrote: > > W: debian-installer source: changelog-file-missing-explicit-entry > 20210731+deb11u1 -> 20210731 (missing) -> 20210731+deb11u2 Your case from stable was already mentioned in the other bug. [1] Merging. A better course of action might have been to retitle the bug to describe the failure better. I did that now. I also upgraded the priority to your requested level of 'important'. On a side note, version parsing is one of the more complex subjects in Debian. Thanks! Kind regards Felix Lechner [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941656#20
Bug#1001651: lintian: changelog-file-missing-explicit-entry: false positives with successive stable uploads
Package: lintian Version: 2.104.0 Severity: important Hi, This is similar to #941656, but I wanted to have it tracked separately, with a slightly higher priority, as that's affecting people performing regular uploads to stable. I would expect this to apply to backports and security as well but I didn't perform any checks there. Anyway, in this particular case, preparing the debian-installer upload for bullseye, I received: W: debian-installer source: changelog-file-missing-explicit-entry 20210731+deb11u1 -> 20210731 (missing) -> 20210731+deb11u2 while the changelog is clearly what it should be: ,--- | debian-installer (20210731+deb11u2) bullseye; urgency=medium | | * Bump Linux kernel ABI to 5.10.0-10. | | -- Cyril Brulebois Mon, 13 Dec 2021 16:23:43 +0100 | | debian-installer (20210731+deb11u1) bullseye; urgency=medium | | * Set USE_PROPOSED_UPDATES=1 for the bullseye stable branch. | * Update USE_UDEBS_FROM default from unstable to bullseye, so that | users don't have to know about the debian/rules heuristics when | performing manual, local builds. | * Bump Linux kernel ABI to 5.10.0-9. | | -- Cyril Brulebois Mon, 04 Oct 2021 10:07:27 +0200 | | debian-installer (20210731) unstable; urgency=medium | | [ Cyril Brulebois ] | * Update translation-status for the release. | | [ Steve McIntyre ] | * Make mini.iso work with UEFI boot | * Bump Linux kernel ABI to 5.10.0-8 | | -- Cyril Brulebois Sat, 31 Jul 2021 06:20:00 +0200 `--- Cheers, -- Cyril Brulebois (k...@debian.org)<https://debamax.com/> D-I release manager -- Release team member -- Freelance Consultant
Bug#950189: lintian: In test suite, please generate full uploads only when source-only uploads are insufficient
Package: lintian Severity: wishlist Hi, Depending on the skeleton selected, the test suite generates full uploads even in situations when the tag being tested arises solely from a source package. Please build full uploads, which include installation packages, only when source-only uploads are insufficient. The entry points in Lintian checks, i.e. 'source' or 'binary', could potentially be used to determine the need for a full upload. Kind regards Felix Lechner
Bug#934982: marked as done (latest-debian-changelog-entry-without-new-version triggered for buster/stable uploads)
Your message dated Wed, 21 Aug 2019 17:25:13 + with message-id and subject line Bug#934982: fixed in lintian 2.19.0 has caused the Debian Bug report #934982, regarding latest-debian-changelog-entry-without-new-version triggered for buster/stable uploads to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 934982: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934982 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: lintian Version: 2.18.0 Severity: normal Hi, I have a package where I want to prepare a stable/buster upload. In this case it is systemd, where the current version in buster is 241-5. I want to upload 241-7 from unstable/testing as-is to buster. For that I added a changelog entry like this: systemd (241-7~deb10u1) buster; urgency=medium * Rebuild for buster -- Michael Biebl Sat, 17 Aug 2019 11:00:59 +0200 systemd (241-7) unstable; urgency=medium ... This now triggers a warning from lintian: W: systemd: latest-debian-changelog-entry-without-new-version Looking at https://release.debian.org/proposed-updates/stable.html there are quite a few packages which use this naming scheme for uploading unstable/testing versions as-is to stable/buster. Would it be possible to make lintian not warn in such a case? See also the related bug report https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934980 Regards, Michael -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (200, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.2.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages lintian depends on: ii binutils 2.32.51.20190813-1 ii bzip21.0.6-9.2 ii diffstat 1.62-1+b1 ii dpkg 1.19.7 ii dpkg-dev 1.19.7 ii file 1:5.37-5 ii gettext 0.19.8.1-9 ii gpg 2.2.17-3 ii intltool-debian 0.35.0+20060710.5 ii libapt-pkg-perl 0.1.36+b1 ii libarchive-zip-perl 1.64-1 ii libcapture-tiny-perl 0.48-1 ii libcgi-pm-perl 4.44-1 ii libclass-accessor-perl 0.51-1 ii libclone-perl0.41-1+b1 ii libdigest-sha-perl 6.02-1+b1 ii libdpkg-perl 1.19.7 ii libemail-valid-perl 1.202-1 ii libfile-basedir-perl 0.08-1 ii libfile-find-rule-perl 0.34-1 ii libio-async-loop-epoll-perl 0.20-1 ii libio-async-perl 0.74-1 ii libipc-run-perl 20180523.0-1 ii liblist-compare-perl 0.53-1 ii liblist-moreutils-perl 0.416-1+b4 ii libmoo-perl 2.003004-2 ii libpath-tiny-perl0.108-1 ii libtext-levenshtein-perl 0.13-1 ii libtimedate-perl 2.3000-2 ii libtry-tiny-perl 0.30-1 ii libtype-tiny-perl1.004004-1 ii liburi-perl 1.76-1 ii libxml-simple-perl 2.25-1 ii libyaml-libyaml-perl 0.79+repack-2 ii man-db 2.8.6.1-1 ii patchutils 0.3.4-2+b1 ii perl 5.28.1-6 ii t1utils 1.41-3 ii xz-utils 5.2.4-1 Versions of packages lintian recommends: ii libperlio-gzip-perl 0.19-1+b5 Versions of packages lintian suggests: pn binutils-multiarch ii libhtml-parser-perl3.72-3+b3 ii libtext-template-perl 1.55-1 -- no debconf information --- End Message --- --- Begin Message --- Source: lintian Source-Version: 2.19.0 We believe that the bug you reported is fixed in the latest version of lintian, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 934...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Chris Lamb (supplier of updated lintian package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash
Bug#934982: latest-debian-changelog-entry-without-new-version triggered for buster/stable uploads
Package: lintian Version: 2.18.0 Severity: normal Hi, I have a package where I want to prepare a stable/buster upload. In this case it is systemd, where the current version in buster is 241-5. I want to upload 241-7 from unstable/testing as-is to buster. For that I added a changelog entry like this: systemd (241-7~deb10u1) buster; urgency=medium * Rebuild for buster -- Michael Biebl Sat, 17 Aug 2019 11:00:59 +0200 systemd (241-7) unstable; urgency=medium ... This now triggers a warning from lintian: W: systemd: latest-debian-changelog-entry-without-new-version Looking at https://release.debian.org/proposed-updates/stable.html there are quite a few packages which use this naming scheme for uploading unstable/testing versions as-is to stable/buster. Would it be possible to make lintian not warn in such a case? See also the related bug report https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934980 Regards, Michael -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (200, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.2.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages lintian depends on: ii binutils 2.32.51.20190813-1 ii bzip21.0.6-9.2 ii diffstat 1.62-1+b1 ii dpkg 1.19.7 ii dpkg-dev 1.19.7 ii file 1:5.37-5 ii gettext 0.19.8.1-9 ii gpg 2.2.17-3 ii intltool-debian 0.35.0+20060710.5 ii libapt-pkg-perl 0.1.36+b1 ii libarchive-zip-perl 1.64-1 ii libcapture-tiny-perl 0.48-1 ii libcgi-pm-perl 4.44-1 ii libclass-accessor-perl 0.51-1 ii libclone-perl0.41-1+b1 ii libdigest-sha-perl 6.02-1+b1 ii libdpkg-perl 1.19.7 ii libemail-valid-perl 1.202-1 ii libfile-basedir-perl 0.08-1 ii libfile-find-rule-perl 0.34-1 ii libio-async-loop-epoll-perl 0.20-1 ii libio-async-perl 0.74-1 ii libipc-run-perl 20180523.0-1 ii liblist-compare-perl 0.53-1 ii liblist-moreutils-perl 0.416-1+b4 ii libmoo-perl 2.003004-2 ii libpath-tiny-perl0.108-1 ii libtext-levenshtein-perl 0.13-1 ii libtimedate-perl 2.3000-2 ii libtry-tiny-perl 0.30-1 ii libtype-tiny-perl1.004004-1 ii liburi-perl 1.76-1 ii libxml-simple-perl 2.25-1 ii libyaml-libyaml-perl 0.79+repack-2 ii man-db 2.8.6.1-1 ii patchutils 0.3.4-2+b1 ii perl 5.28.1-6 ii t1utils 1.41-3 ii xz-utils 5.2.4-1 Versions of packages lintian recommends: ii libperlio-gzip-perl 0.19-1+b5 Versions of packages lintian suggests: pn binutils-multiarch ii libhtml-parser-perl3.72-3+b3 ii libtext-template-perl 1.55-1 -- no debconf information
Bug#905467: marked as done (lintian: Please detect source-only non-free uploads w/o opt-in autobuild)
Your message dated Tue, 07 Aug 2018 13:50:29 +
with message-id
and subject line Bug#905467: fixed in lintian 2.5.95
has caused the Debian Bug report #905467,
regarding lintian: Please detect source-only non-free uploads w/o opt-in
autobuild
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
905467: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905467
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: lintian
Version: 2.5.94
Severity: wishlist
Hi!
I recently did a source-only QA upload for snmp-mibs-downloader, a
non-free package. And didn't notice until way later that the package
had not been migrated [M], because of the missing binaries, due to the
package not having opted into the non-free autobuild network.
[M] <https://tracker.debian.org/pkg/snmp-mibs-downloader>
I think lintian should at least warn (or perhaps even error) on
source-only non-free uploads that do not declare the Autobuild:yes
field. [A]
[A]
<https://www.debian.org/doc/manuals/developers-reference/ch05.en.html#non-free-buildd>
Thanks,
Guillem
--- End Message ---
--- Begin Message ---
Source: lintian
Source-Version: 2.5.95
We believe that the bug you reported is fixed in the latest version of
lintian, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 905...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Chris Lamb (supplier of updated lintian package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Tue, 07 Aug 2018 13:02:08 +
Source: lintian
Binary: lintian
Architecture: source all
Version: 2.5.95
Distribution: unstable
Urgency: medium
Maintainer: Debian Lintian Maintainers
Changed-By: Chris Lamb
Description:
lintian- Debian package checker
Closes: 904623 904817 904886 904936 904985 905030 905258 905423 905467 905635
Changes:
lintian (2.5.95) unstable; urgency=medium
.
* Summary of tag changes:
+ Added:
- debhelper-compat-virtual-relation
- depends-on-python2-and-python3
- no-op-testsuite
- r-package-not-arch-all
- source-only-upload-to-non-free-without-autobuild
.
* checks/debhelper.{desc,pm}:
+ [CL] Support "debhelper-compat (= X)" build-dependency as a
replacement for "debhelper (>= X~)". (Closes: #904886)
* checks/changes-file.{desc,pm}:
+ [CL] Detect source-only uploads to non-free uploads that will not be
autobuilt by default. (Closes: #905467)
* checks/control-file.desc:
+ [AB] Fix duplicate word "the" in tag description.
* checks/cruft.pm:
+ [CL] Don't emit mentions-deprecated-usr-lib-perl5-directory for
debian/*.install files as they are used as source directories.
(Closes: #905635)
* checks/fields.{desc.pm}:
+ [CL] Warn about R packages incorrectly set to "Architecture:
any". (Closes: #904985)
* checks/files.{desc,pm}:
+ [CL] Whitelist files in /usr/share/doc and /usr/share/locale for the
missing-depends-on-sensible-utils tag and update testsuite to match.
(Closes: #904936)
+ [CL] Add Suggests and Pre-Depends as potential relations with the
sensible-utils package. Thanks to Guillem Jover for the idea.
* checks/python.{desc,pm}:
+ [CL] Check for Python packages that have a relation on both Python 2
and Python 3. (Closes: #904817)
* checks/testsuite.{desc,pm}:
+ [CL] Warn about packages that have a single, no-op autopkgtest.
(Closes: #905030)
+ [CL] Move list of known fields, "Restriction" fields and testsuites
to files under data/testsuite/.
+ [CL] Improve the long description of the
testsuite-autopkgtest-missing tag; in particular, reference that
autopkgtest results now influence migration from unstable to testing.
.
* data/debhelper/filename-config-files:
+ [NT] Add mime and sharedmimeinfo as known debhelper config files.
* data/scripts/interpreters:
+ [CL] Prevent ruby-script-but-no-ruby-dep false positives by also
accepting ruby:any as a dependency. Thanks to Marc Dequènes
Bug#905467: lintian: Please detect source-only non-free uploads w/o opt-in autobuild
Chris Lamb wrote: > Updated in: > > […] That should have been: https://salsa.debian.org/lintian/lintian/commit/adf09be624fc450738f40613bd5098d056a678e2 Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Bug#905467: lintian: Please detect source-only non-free uploads w/o opt-in autobuild
Hi Guillem & Niels, > > I seem to recall that "XS-Autobuild: Yes" requires being added to a > > whitelist as well […] > Yes, this is item 3 from the dev-ref link I provided. And I agree it's > probably worth mentioning, or just pointing people to read the dev-ref > for the most up-to-date process. Updated in: https://salsa.debian.org/lintian/lintian/commit/d01efe67b351a4af3cd735c264774422c4f1c251 Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Bug#905467: lintian: Please detect source-only non-free uploads w/o opt-in autobuild
On Sun, 2018-08-05 at 08:06:00 +, Niels Thykier wrote: > Chris Lamb: > > tags 905467 + pending > > thanks > > > > Implemented in Git, pending upload: > > > > > > https://salsa.debian.org/lintian/lintian/commit/514313860d51930c986bbcb3eca6ec4ac7905852 > I seem to recall that "XS-Autobuild: Yes" requires being added to a > whitelist as well as having the header (A slightly dated reference: > https://lwn.net/Articles/211820/ - given it is using ".net" and not ".org") Yes, this is item 3 from the dev-ref link I provided. And I agree it's probably worth mentioning, or just pointing people to read the dev-ref for the most up-to-date process. Thanks, Guillem
Bug#905467: lintian: Please detect source-only non-free uploads w/o opt-in autobuild
Chris Lamb: > tags 905467 + pending > thanks > > Implemented in Git, pending upload: > > > https://salsa.debian.org/lintian/lintian/commit/514313860d51930c986bbcb3eca6ec4ac7905852 > > checks/changes-file.desc | 12 > checks/changes-file.pm | 8 +++- > debian/changelog | 3 +++ > t/changes/changes-file-source-only-non-free.changes.in | 18 > ++ > t/changes/changes-file-source-only-non-free.desc | 5 + > t/changes/changes-file-source-only-non-free.log| 1 + > t/changes/changes-file-source-only-non-free.tags | 1 + > 7 files changed, 47 insertions(+), 1 deletion(-) > > > Regards, > I seem to recall that "XS-Autobuild: Yes" requires being added to a whitelist as well as having the header (A slightly dated reference: https://lwn.net/Articles/211820/ - given it is using ".net" and not ".org") Thanks, ~Niels
Processed: Re: lintian: Please detect source-only non-free uploads w/o opt-in autobuild
Processing commands for cont...@bugs.debian.org: > tags 905467 + pending Bug #905467 [lintian] lintian: Please detect source-only non-free uploads w/o opt-in autobuild Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 905467: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905467 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#905467: lintian: Please detect source-only non-free uploads w/o opt-in autobuild
tags 905467 + pending thanks Implemented in Git, pending upload: https://salsa.debian.org/lintian/lintian/commit/514313860d51930c986bbcb3eca6ec4ac7905852 checks/changes-file.desc | 12 checks/changes-file.pm | 8 +++- debian/changelog | 3 +++ t/changes/changes-file-source-only-non-free.changes.in | 18 ++ t/changes/changes-file-source-only-non-free.desc | 5 + t/changes/changes-file-source-only-non-free.log| 1 + t/changes/changes-file-source-only-non-free.tags | 1 + 7 files changed, 47 insertions(+), 1 deletion(-) Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-
Bug#905467: lintian: Please detect source-only non-free uploads w/o opt-in autobuild
Package: lintian Version: 2.5.94 Severity: wishlist Hi! I recently did a source-only QA upload for snmp-mibs-downloader, a non-free package. And didn't notice until way later that the package had not been migrated [M], because of the missing binaries, due to the package not having opted into the non-free autobuild network. [M] <https://tracker.debian.org/pkg/snmp-mibs-downloader> I think lintian should at least warn (or perhaps even error) on source-only non-free uploads that do not declare the Autobuild:yes field. [A] [A] <https://www.debian.org/doc/manuals/developers-reference/ch05.en.html#non-free-buildd> Thanks, Guillem
[lintian] 01/02: c/changes-file: Use "~bpo7+N" as the suffix for wheezy-backports-sloppy uploads
This is an automated email from the git hooks/post-receive script.
jwilk pushed a commit to branch master
in repository lintian.
commit f678d88e765b198b1bf117aec6833e1cd74f2e51
Author: Jakub Wilk <jw...@debian.org>
Date: Tue Jan 5 21:25:43 2016 +0100
c/changes-file: Use "~bpo7+N" as the suffix for wheezy-backports-sloppy
uploads
---
checks/changes-file.pm | 7 +--
debian/changelog | 4
2 files changed, 9 insertions(+), 2 deletions(-)
diff --git a/checks/changes-file.pm b/checks/changes-file.pm
index 4761d09..a9b8c46 100644
--- a/checks/changes-file.pm
+++ b/checks/changes-file.pm
@@ -72,8 +72,11 @@ sub run {
my $distnumber = $1;
my $bpoversion = $2;
if (
- ($dist eq 'squeeze' && $distnumber ne '60')
-||($dist eq 'wheezy' && $distnumber ne '70')
+($dist eq 'squeeze' && $distnumber ne '60')
+||($distribution eq 'wheezy-backports'
+&& $distnumber ne '70')
+||($distribution eq 'wheezy-backports-sloppy'
+&& $distnumber ne '7')
# TODO version number for jessie?
||($dist eq 'jessie' && $distnumber !~ /^8\d*/)
) {
diff --git a/debian/changelog b/debian/changelog
index 0c96622..e293643 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -2,6 +2,10 @@ lintian (2.5.40) UNRELEASED; urgency=medium
XXX: generate tag summary
+ * checks/changes-file.pm:
++ [JW] Use "~bpo7+N" as the suffix for wheezy-backports-sloppy
+ uploads. Thanks to Vincent Bernat for the bug report. (Closes:
+ #810028).
* checks/cruft.pm:
+ [BR] Pass information about minified javascript down to tag.
(Closes: #804147).
--
Alioth's /usr/local/bin/git-commit-notice on
/srv/git.debian.org/git/lintian/lintian.git
Bug#582741: marked as done (lintian: [checks/nmu] Team uploads.)
Your message dated Mon, 28 Jun 2010 05:32:10 +
with message-id e1ot6x0-00033h...@ries.debian.org
and subject line Bug#582741: fixed in lintian 2.4.2
has caused the Debian Bug report #582741,
regarding lintian: [checks/nmu] Team uploads.
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
582741: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=582741
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: lintian
Version: 2.4.1
Severity: wishlist
Tags: patch
Dear Lintian maintainers,
the concept of team uploads has been discussed a couple of times on
debian-devel, and is finally making its way in the Developers Reference. You
can find more informations in the following wiki page:
http://wiki.debian.org/TeamUpload
I attached to this report a patch to lintian, that integrates team uploads in
checks/nmu.
Have a nice day,
--
Charles Plessy
Tsurumi, Kanagawa, Japan
diff --git a/checks/nmu b/checks/nmu
index 76e6304..59f5522 100644
--- a/checks/nmu
+++ b/checks/nmu
@@ -42,6 +42,7 @@ my $info = shift;
my $changelog_mentions_nmu = 0;
my $changelog_mentions_local = 0;
my $changelog_mentions_qa = 0;
+my $changelog_mentions_team_upload = 0;
# This isn't really an NMU check, but right now no other check looks at
# debian/changelog in source packages. Catch a debian/changelog file that's a
@@ -60,7 +61,7 @@ my $changes = $entry-Changes;
$changes =~ s/^(\s*\n)+//;
my $firstline = (grep /^\s*\*/, split('\n', $changes))[0];
-# Check the first line for QA and NMU mentions.
+# Check the first line for QA, NMU or team upload mentions.
if ($firstline) {
local $_ = $firstline;
if (/\bnmu\b/i or /non-maintainer upload/i) {
@@ -70,6 +71,8 @@ if ($firstline) {
}
$changelog_mentions_local = 1 if /\blocal\s+package\b/i;
$changelog_mentions_qa = 1 if /orphan/i or /qa (?:group )?upload/i;
+ $changelog_mentions_team_upload = 1 if / \* Team upload./;
+
}
my $version = $info-field(version);
@@ -111,6 +114,9 @@ if ($maintainer =~ /packag...@qa.debian.org/) {
if $version_nmuness == 1;
tag changelog-should-mention-qa,
if !$changelog_mentions_qa;
+} elsif ($changelog_mentions_team_upload) {
+ tag team-upload-has-incorrect-version-number, $version
+ if $version_nmuness == 1;
} else {
# Local packages may be either NMUs or not.
unless ($changelog_mentions_local || $version_local) {
diff --git a/checks/nmu.desc b/checks/nmu.desc
index c2515ee..b552a40 100644
--- a/checks/nmu.desc
+++ b/checks/nmu.desc
@@ -18,6 +18,13 @@ Certainty: certain
Info: A QA upload (uploading an orphaned package without adopting it) is
always a maintainer upload: it should not get a NMU revision number.
+Tag: team-upload-has-incorrect-version-number
+Severity: normal
+Certainty: certain
+Info: A team upload (uploading a package from the same team without adding
+ onself as maintainer or uploader) is a maintainer upload: it should not get a
+ NMU revision number.
+
Tag: source-nmu-has-incorrect-version-number
Severity: normal
Certainty: certain
---End Message---
---BeginMessage---
Source: lintian
Source-Version: 2.4.2
We believe that the bug you reported is fixed in the latest version of
lintian, which is due to be installed in the Debian FTP archive:
lintian_2.4.2.dsc
to main/l/lintian/lintian_2.4.2.dsc
lintian_2.4.2.tar.gz
to main/l/lintian/lintian_2.4.2.tar.gz
lintian_2.4.2_all.deb
to main/l/lintian/lintian_2.4.2_all.deb
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 582...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Russ Allbery r...@debian.org (supplier of updated lintian package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.8
Date: Sun, 27 Jun 2010 22:08:59 -0700
Source: lintian
Binary: lintian
Architecture: source all
Version: 2.4.2
Distribution: unstable
Urgency: low
Maintainer: Debian Lintian Maintainers lintian-ma...@debian.org
Changed-By: Russ Allbery r...@debian.org
Description:
lintian- Debian package checker
Closes: 575661 580082 580494 580700 581314 582353 582741 582804 583555 584743
586877 586984 587209
Changes:
lintian (2.4.2) unstable; urgency=low
.
The Policy 3.9.0 release.
.
* Summary of tag changes:
+ Added:
- arch
Bug#582741: lintian: [checks/nmu] Team uploads.
Package: lintian
Version: 2.4.1
Severity: wishlist
Tags: patch
Dear Lintian maintainers,
the concept of team uploads has been discussed a couple of times on
debian-devel, and is finally making its way in the Developers Reference. You
can find more informations in the following wiki page:
http://wiki.debian.org/TeamUpload
I attached to this report a patch to lintian, that integrates team uploads in
checks/nmu.
Have a nice day,
--
Charles Plessy
Tsurumi, Kanagawa, Japan
diff --git a/checks/nmu b/checks/nmu
index 76e6304..59f5522 100644
--- a/checks/nmu
+++ b/checks/nmu
@@ -42,6 +42,7 @@ my $info = shift;
my $changelog_mentions_nmu = 0;
my $changelog_mentions_local = 0;
my $changelog_mentions_qa = 0;
+my $changelog_mentions_team_upload = 0;
# This isn't really an NMU check, but right now no other check looks at
# debian/changelog in source packages. Catch a debian/changelog file that's a
@@ -60,7 +61,7 @@ my $changes = $entry-Changes;
$changes =~ s/^(\s*\n)+//;
my $firstline = (grep /^\s*\*/, split('\n', $changes))[0];
-# Check the first line for QA and NMU mentions.
+# Check the first line for QA, NMU or team upload mentions.
if ($firstline) {
local $_ = $firstline;
if (/\bnmu\b/i or /non-maintainer upload/i) {
@@ -70,6 +71,8 @@ if ($firstline) {
}
$changelog_mentions_local = 1 if /\blocal\s+package\b/i;
$changelog_mentions_qa = 1 if /orphan/i or /qa (?:group )?upload/i;
+ $changelog_mentions_team_upload = 1 if / \* Team upload./;
+
}
my $version = $info-field(version);
@@ -111,6 +114,9 @@ if ($maintainer =~ /packag...@qa.debian.org/) {
if $version_nmuness == 1;
tag changelog-should-mention-qa,
if !$changelog_mentions_qa;
+} elsif ($changelog_mentions_team_upload) {
+ tag team-upload-has-incorrect-version-number, $version
+ if $version_nmuness == 1;
} else {
# Local packages may be either NMUs or not.
unless ($changelog_mentions_local || $version_local) {
diff --git a/checks/nmu.desc b/checks/nmu.desc
index c2515ee..b552a40 100644
--- a/checks/nmu.desc
+++ b/checks/nmu.desc
@@ -18,6 +18,13 @@ Certainty: certain
Info: A QA upload (uploading an orphaned package without adopting it) is
always a maintainer upload: it should not get a NMU revision number.
+Tag: team-upload-has-incorrect-version-number
+Severity: normal
+Certainty: certain
+Info: A team upload (uploading a package from the same team without adding
+ onself as maintainer or uploader) is a maintainer upload: it should not get a
+ NMU revision number.
+
Tag: source-nmu-has-incorrect-version-number
Severity: normal
Certainty: certain
Bug#483845: lintian: could warn about uploads to wrong targets
Package: lintian Severity: wishlist Some of us are not so good at remembering to set the upload target (unstable/experimental/stable/whatever) correctly. It would be handy if lintian could warn about this. For example (names changed): foo liw: we have bar 3.0.x series in unstable and 3.2.x in experimental foo this week, I was working on 3.0.30 which I uploaded to unstable foo then today I wanted to upload a new 3.2 to experimental foo just before building it, I changed UNRELEASED to unstable in debian/changelog without thinking, built...and uploaded ... liw I guess one could have a heuristic like this: if changelog indicates a new upstream version, warn if the upload target is not experimental, but don't warn, if the changelog entry says new upstream version uploaded to unstable liw although I guess that would be best done by a lintian check liw possibly even enabled only if there is a debian/lintian-me-harder file in the source tree? :) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#483845: lintian: could warn about uploads to wrong targets
Lars Wirzenius [EMAIL PROTECTED] writes: liw I guess one could have a heuristic like this: if changelog indicates a new upstream version, warn if the upload target is not experimental, but don't warn, if the changelog entry says new upstream version uploaded to unstable I might be missing something here, but wouldn't this essentially always be wrong when looking at the whole archive? Almost no one uploads new upstream versions to experimental first. liw although I guess that would be best done by a lintian check liw possibly even enabled only if there is a debian/lintian-me-harder file in the source tree? :) You'd need some way to request only that specific check, I think, since even people who normally want lintian to be as verbose as possible aren't going to want that. -- Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#483845: lintian: could warn about uploads to wrong targets
la, 2008-05-31 kello 11:08 -0700, Russ Allbery kirjoitti: You'd need some way to request only that specific check, I think, since even people who normally want lintian to be as verbose as possible aren't going to want that. Yeah, thus the debian/lintian-me-harder suggestion: only do the check for packages that request that. I don't know if lintian has the infrastructure for that, but if not, perhaps it (and the proposed check) can be added at some future date, when more important stuff has been taken care of. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#483845: lintian: could warn about uploads to wrong targets
Wouldn't this be more suitable in dput/dupload? Those already have similar options, some of which are disabled by default, but available anyway. Cheers, -- Atomo64 - Raphael Please avoid sending me Word, PowerPoint or Excel attachments. See http://www.gnu.org/philosophy/no-word-attachments.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#483845: lintian: could warn about uploads to wrong targets
[Please do not CC me, I read the list] Lars Wirzenius wrote: la, 2008-05-31 kello 16:47 -0500, Raphael Geissert kirjoitti: Wouldn't this be more suitable in dput/dupload? Those already have similar options, some of which are disabled by default, but available anyway. It seems to me that it's the kind of static checking that belongs to lintian, so I'd like to see it in lintian, rather than every upload tool separately. If nothing else, it would help find problems even when things are not uploaded, just (re)built. The thing is that just like Russ said, almost no one uploads new versions to experimental first just for the sake of it being a new version. There are of course some cases that's desired (e.g. major changes), but that's not the common rule. And adding extra enable-on-demand checks IMHO is not something that belongs to lintian. But I'll better let the lintian maintainers speak for themselves. I just wanted to suggest another possible way to achieve the same goal, with higher (IMHO) chances to get added. Cheers, -- Atomo64 - Raphael Please avoid sending me Word, PowerPoint or Excel attachments. See http://www.gnu.org/philosophy/no-word-attachments.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Uploads
On Fri, Jun 23, 2006 at 01:28:45PM -0700, Russ Allbery wrote: Raphael Hertzog [EMAIL PROTECTED] writes: (moving to lintian-maint) On Fri, 23 Jun 2006, Russ Allbery wrote: Raphael Hertzog [EMAIL PROTECTED] writes: I tend to think that you're doing too much checks here. Having too much in Build-Depends is not *that* bad. You'd better check only for the contrary ie missing Build-Depends because they are used in the clean rule... well IMO of course. This would be a good thing to send to lintian-maint rather than just to me. I didn't add the check in the first place; I just tried to fix all of the false positives in a check that was already in lintian before I started working on it. I agree with you that it's not completely clear it's worth it, although at this point there aren't many false positives left. I have nothing to add, just wanted to share my initial comment with the other maintainers as suggested by Russ. What would the other lintian maintainers think about downgrading the build-depends-without-arch-dep tag to info from warning? We are getting a *lot* of false positives with it, and while I'm quashing them as I see them, this is a style thing more than it's really a policy requirement. Yeah, makes sense to me. --Jeroen -- Jeroen van Wolffelaar [EMAIL PROTECTED] (also for Jabber MSN; ICQ: 33944357) http://Jeroen.A-Eskwadraat.nl -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Uploads
(moving to lintian-maint) On Fri, 23 Jun 2006, Russ Allbery wrote: Raphael Hertzog [EMAIL PROTECTED] writes: FWIW, packages using CDBS and the python-distutils class and Build-Depending on python-dev have a similar warning... and yet they need python-dev for the clean target. Yeah, fixed that already. Good! I tend to think that you're doing too much checks here. Having too much in Build-Depends is not *that* bad. You'd better check only for the contrary ie missing Build-Depends because they are used in the clean rule... well IMO of course. This would be a good thing to send to lintian-maint rather than just to me. I didn't add the check in the first place; I just tried to fix all of the false positives in a check that was already in lintian before I started working on it. I agree with you that it's not completely clear it's worth it, although at this point there aren't many false positives left. I have nothing to add, just wanted to share my initial comment with the other maintainers as suggested by Russ. Cheers, -- Raphaël Hertzog Premier livre français sur Debian GNU/Linux : http://www.ouaza.com/livre/admin-debian/
Re: Uploads
Raphael Hertzog [EMAIL PROTECTED] writes: (moving to lintian-maint) On Fri, 23 Jun 2006, Russ Allbery wrote: Raphael Hertzog [EMAIL PROTECTED] writes: I tend to think that you're doing too much checks here. Having too much in Build-Depends is not *that* bad. You'd better check only for the contrary ie missing Build-Depends because they are used in the clean rule... well IMO of course. This would be a good thing to send to lintian-maint rather than just to me. I didn't add the check in the first place; I just tried to fix all of the false positives in a check that was already in lintian before I started working on it. I agree with you that it's not completely clear it's worth it, although at this point there aren't many false positives left. I have nothing to add, just wanted to share my initial comment with the other maintainers as suggested by Russ. What would the other lintian maintainers think about downgrading the build-depends-without-arch-dep tag to info from warning? We are getting a *lot* of false positives with it, and while I'm quashing them as I see them, this is a style thing more than it's really a policy requirement. -- Russ Allbery ([EMAIL PROTECTED]) http://www.eyrie.org/~eagle/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#326732: lintian: Added checks that prevent ftp-master uploads
| --=-=-= | Content-Transfer-Encoding: quoted-printable | | On 10403 March 1977, Jari Aalto wrote: | | | While they are listed in there at the page, they seem to be | | rejection criterias. At least my package jwm submittal was | | refused for upload until extra # dh_* lines were removed. | | Hrm, and this was the only reason it was rejected? | Yes. If I remember correct. I do not have the mail at hand any more, | but the indication to leave those extra template added # dh_ | statements were not tolerated. | | Now, if you would actually check whats going on with your package you | would see that it went in on 01.09.2005! | | The only reject you got was automatic as you havent uploaded the | orig.tar.gz with the first upload. I remember that , thanks. But in addition to this I remember receiving a message where someone (?) instructed to remove all extra # dh_* lines. There reasoning was something like patch being difficult to read and therefore I should clean up the debian/rules file I would myself kept those lines in there, because if more features were added to the package later it would help to just uncomment relevant lline and not need to read for separate dh_* pages. Anyway, If I remember incorrectly that the dh_ episode was instructional only, I may have interpreted is as rejection criteria. If so, then the W: is correct in lintian. Thanks for clearance, Jari -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#326732: lintian: Added checks that prevent ftp-master uploads
Package: lintian Version: 1.23.12 Severity: wishlist There is now rejection criterias outlined in: http://ftp-master.debian.org/REJECT-FAQ.html One of the criterias are extra # dh_* templates which now seem to have to be removed. Currently this is W: in lintian, it should probably be raised to E: Please add or ajust new chekcs according to that FAQ. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.12-1-686 Locale: LANG=C, LC_CTYPE=C (charmap=ISO-8859-1) (ignored: LC_ALL set to en_US) Versions of packages lintian depends on: ii binutils 2.16.1-3The GNU assembler, linker and bina ii diffstat 1.41-1 produces graph of changes introduc ii dpkg-dev 1.13.11 package building tools for Debian ii file 4.12-1 Determines file type using magic ii gettext 0.14.5-2GNU Internationalization utilities ii intltool-debian 0.34.1+20050828 Help i18n of RFC822 compliant conf ii libparse-debianchangelog 0.7-1 parse Debian changelogs and output ii man-db 2.4.3-2 The on-line manual pager ii perl [libdigest-md5-perl 5.8.7-4 Larry Wall's Practical Extraction lintian recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#326732: lintian: Added checks that prevent ftp-master uploads
On Mon, Sep 05, 2005 at 02:40:03PM +0300, Jari Aalto wrote: There is now rejection criterias outlined in: http://ftp-master.debian.org/REJECT-FAQ.html One of the criterias are extra # dh_* templates which now seem to have to be removed. Currently this is W: in lintian, it should probably be raised to E: Nah, they are in the categorie Minor issues, I don't think that qualifies... Unless one of my co-maintainers objects I will close this bug. Gruesse, -- Frank Lichtenheld [EMAIL PROTECTED] www: http://www.djpig.de/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#326732: lintian: Added checks that prevent ftp-master uploads
On Mon, Sep 05, 2005 at 04:07:48PM +0300, Jari Aalto wrote: | On Mon, Sep 05, 2005 at 02:40:03PM +0300, Jari Aalto wrote: | There is now rejection criterias outlined in: | | http://ftp-master.debian.org/REJECT-FAQ.html | | One of the criterias are extra # dh_* templates which now seem to | have to be removed. Currently this is W: in lintian, it should | probably be raised to E: | | Nah, they are in the categorie Minor issues, I don't think that | qualifies... While they are listed in there at the page, they seem to be rejection criterias. At least my package jwm submittal was refused for upload until extra # dh_* lines were removed. Hrm, and this was the only reason it was rejected? Gruesse, -- Frank Lichtenheld [EMAIL PROTECTED] www: http://www.djpig.de/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#326732: lintian: Added checks that prevent ftp-master uploads
| On Mon, Sep 05, 2005 at 02:40:03PM +0300, Jari Aalto wrote: | There is now rejection criterias outlined in: | | http://ftp-master.debian.org/REJECT-FAQ.html | | One of the criterias are extra # dh_* templates which now seem to | have to be removed. Currently this is W: in lintian, it should | probably be raised to E: | | Nah, they are in the categorie Minor issues, I don't think that | qualifies... While they are listed in there at the page, they seem to be rejection criterias. At least my package jwm submittal was refused for upload until extra # dh_* lines were removed. Perhaps ftp masters can corrdinate this issue better. I've CC'd them. Jari -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#326732: marked as done (lintian: Added checks that prevent ftp-master uploads)
Your message dated Mon, 5 Sep 2005 15:00:31 +0200 with message-id [EMAIL PROTECTED] and subject line Bug#326732: lintian: Added checks that prevent ftp-master uploads has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) -- Received: (at submit) by bugs.debian.org; 5 Sep 2005 11:40:08 + From [EMAIL PROTECTED] Mon Sep 05 04:40:08 2005 Return-path: [EMAIL PROTECTED] Received: from fep02-0.kolumbus.fi (fep02-app.kolumbus.fi) [193.229.0.44] by spohr.debian.org with esmtp (Exim 3.36 1 (Debian)) id 1ECFKZ-0002ow-00; Mon, 05 Sep 2005 04:40:08 -0700 Received: from bongo.cante.net ([81.197.0.130]) by fep02-app.kolumbus.fi with ESMTP id [EMAIL PROTECTED] for [EMAIL PROTECTED]; Mon, 5 Sep 2005 14:40:06 +0300 Received: from fw.cante.net ([192.168.1.3] helo=cante) by bongo.cante.net with esmtp (Exim 4.52) id 1ECFKY-0002Y4-0x; Mon, 05 Sep 2005 14:40:06 +0300 Received: from jaalto by cante with local (Exim 4.52) id 1ECFKW-st-2T; Mon, 05 Sep 2005 14:40:04 +0300 Content-Type: text/plain; charset=us-ascii MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: Jari Aalto [EMAIL PROTECTED] To: Debian Bug Tracking System [EMAIL PROTECTED] Subject: lintian: Added checks that prevent ftp-master uploads X-Mailer: reportbug 3.17 Date: Mon, 05 Sep 2005 14:40:03 +0300 Message-Id: [EMAIL PROTECTED] Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Level: X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE autolearn=no version=2.60-bugs.debian.org_2005_01_02 Package: lintian Version: 1.23.12 Severity: wishlist There is now rejection criterias outlined in: http://ftp-master.debian.org/REJECT-FAQ.html One of the criterias are extra # dh_* templates which now seem to have to be removed. Currently this is W: in lintian, it should probably be raised to E: Please add or ajust new chekcs according to that FAQ. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.12-1-686 Locale: LANG=C, LC_CTYPE=C (charmap=ISO-8859-1) (ignored: LC_ALL set to en_US) Versions of packages lintian depends on: ii binutils 2.16.1-3The GNU assembler, linker and bina ii diffstat 1.41-1 produces graph of changes introduc ii dpkg-dev 1.13.11 package building tools for Debian ii file 4.12-1 Determines file type using magic ii gettext 0.14.5-2GNU Internationalization utilities ii intltool-debian 0.34.1+20050828 Help i18n of RFC822 compliant conf ii libparse-debianchangelog 0.7-1 parse Debian changelogs and output ii man-db 2.4.3-2 The on-line manual pager ii perl [libdigest-md5-perl 5.8.7-4 Larry Wall's Practical Extraction lintian recommends no packages. -- no debconf information --- Received: (at 326732-done) by bugs.debian.org; 5 Sep 2005 13:00:33 + From [EMAIL PROTECTED] Mon Sep 05 06:00:33 2005 Return-path: [EMAIL PROTECTED] Received: from a-eskwadraat.nl [131.211.39.72] by spohr.debian.org with esmtp (Exim 3.36 1 (Debian)) id 1ECGaP-CK-00; Mon, 05 Sep 2005 06:00:33 -0700 Received: from jeroen by a-eskwadraat.nl with local (Exim 4.50) id 1ECGaN-0001JV-2z; Mon, 05 Sep 2005 15:00:31 +0200 Date: Mon, 5 Sep 2005 15:00:31 +0200 To: Jari Aalto [EMAIL PROTECTED], [EMAIL PROTECTED] Subject: Re: Bug#326732: lintian: Added checks that prevent ftp-master uploads Message-ID: [EMAIL PROTECTED] References: [EMAIL PROTECTED] Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: [EMAIL PROTECTED] User-Agent: Mutt/1.5.9i From: Jeroen van Wolffelaar [EMAIL PROTECTED] Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Level: X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER autolearn=no version=2.60-bugs.debian.org_2005_01_02 On Mon, Sep 05, 2005 at 02:40:03PM +0300, Jari Aalto wrote: Package: lintian Version: 1.23.12 Severity: wishlist There is now rejection criterias outlined in: http
Bug#326732: lintian: Added checks that prevent ftp-master uploads
| On Mon, Sep 05, 2005 at 04:07:48PM +0300, Jari Aalto wrote: | | On Mon, Sep 05, 2005 at 02:40:03PM +0300, Jari Aalto wrote: | | There is now rejection criterias outlined in: | | | | http://ftp-master.debian.org/REJECT-FAQ.html | | | | One of the criterias are extra # dh_* templates which now seem to | | have to be removed. Currently this is W: in lintian, it should | | probably be raised to E: | | | | Nah, they are in the categorie Minor issues, I don't think that | | qualifies... | | While they are listed in there at the page, they seem to be | rejection criterias. At least my package jwm submittal was | refused for upload until extra # dh_* lines were removed. | | Hrm, and this was the only reason it was rejected? Yes. If I remember correct. I do not have the mail at hand any more, but the indication to leave those extra template added # dh_ statements were not tolerated. Jari -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
