Bug#796285: apache2-module-depends-on-real-apache2-package contradicts dh_apache2

Hi Jakub, On Wed, March 9, 2016 11:50, Jakub Wilk wrote: > * Arno Töll , 2015-08-21, 11:13: >>The fix would be, to raise this Lintian error only if a package depends >>on apache2-bin but not on apache2-api-MMNN. > > There's already separate tag for missing apache2-api-* dep:

Bug#796285: apache2-module-depends-on-real-apache2-package contradicts dh_apache2

Hi, On Fri, 21 Aug 2015 10:19:06 -0700, Russ Allbery wrote: > > we agreed that we should change Lintian to accommodate these > > changes. The fix would be, to raise this Lintian error only if a package > > depends on apache2-bin but not on apache2-api-MMNN. > > Ah, yes, that would work. So,

Bug#775667: lintian: Create a command line to suppress excess tags

On Mon, August 31, 2015 07:46, Niels Thykier wrote: > On 2015-08-30 20:28, Axel Beckert wrote: >> Hi, >> >> Niels Thykier wrote: Moreover minified js is a security risk so removing tag is not really an option >>> >>> The bug is not about removing the tag, it is about the amount of times

Bug#775667: source-is-missing generates excessive amount of tags

Package: lintian Version: 2.5.30 Severity: normal Hi, The 'source-is-missing' check can generate really excessive output of many hundreds of tags when just a single source is missing. Take for example roundcube which currently has 800+ tags which nearly all relate to tinymce missing:

Bug#718862: composer-package-without-pkg-php-tools-builddep should not be a warning

Package: lintian Version: 2.5.15 Severity: normal Hi, Lintian 2.5.15 added a number of tests related to pkg-php-tools. The test composer-package-without-pkg-php-tools-builddep displays a warning on every package containing a composer.json file. This seems over the top to me. My PHP application

Bug#718167: missing-pkg-php-tools-addon thinks I'm using pkg-php-tools

Package: lintian Version: 2.5.15 Severity: normal My package phpmyadmin triggers the following warning: W: phpmyadmin source: missing-pkg-php-tools-addon phpcomposer N: N:The package uses pkg-php-tools but dh command is called without --with N:phppear or --with phpcomposer. A

Bug#711520: non-standard-apache2-module-package-name suggests strange name for libapache2-mod-php5

Package: lintian Version: 2.5.10.4 Severity: normal Hi, On libapache2-mod-php5_5.5.0~rc2+dfsg-2_amd64.deb I get: W: libapache2-mod-php5: non-standard-apache2-module-package-name libapache2-mod-php5 != libapache2-libphp5 E: libapache2-mod-php5: apache2-module-does-not-ship-load-file libphp5

Bug#711193: Mark hardening-wrapper/includes as deprecated build-depends

of these packages. Cheers, Thijs From b7325c04d609f7bde87929c944475a6a3d5f3faa Mon Sep 17 00:00:00 2001 From: Thijs Kinkhorst th...@debian.org Date: Wed, 5 Jun 2013 12:25:14 +0200 Subject: [PATCH] Hardening-wrapper and hardening-includes are deprecated. Packages should not Build-Depend on either

Bug#711193: Mark hardening-wrapper/includes as deprecated build-depends

On Wed, June 5, 2013 18:26, Russ Allbery wrote: Thijs Kinkhorst th...@debian.org writes: Packages should not Build-Depend on either of these packages and their functionality, but rather use the superior dpkg buildflags solution. Attached patch accomplishes that packagers are warned when

Bug#700953: warn about binary packages depending on debhelper, cdbs etc.

Package: lintian Version: 2.5.10.3 Severity: wishlist Hi, I encountered an (example) package that had cdbs not only in its Build-Depends line, but also in its Depends line. This was a mistake. I would have expected that Lintian complained about this. Obviously hardly any package would need to

Bug#698704: Add lua5.2 to list of known lua interpreters.

Package: lintian Version: 2.5.10.3 Severity: normal Tags: patch Hi, lua5.2 is in the archive since 2011-07. Attached patch adds it to the list of known lua interpreters. Cheers, Thijs From b1879b43d57d1707a4ee3b6bace7998d0c72d841 Mon Sep 17 00:00:00 2001 From: Thijs Kinkhorst th...@debian.org

Bug#661778: update Ref for copyright-format checks to current location

' from the check names, since it's no longer a dep, but that has wider implications so I'll leave that up to you. Cheers, Thijs From 1cf0fe084aa0ec24f9ae6f8a83581f93b8440889 Mon Sep 17 00:00:00 2001 From: Thijs Kinkhorst th...@debian.org Date: Thu, 1 Mar 2012 09:27:47 +0100 Subject: [PATCH] update Ref

Bug#661103: binaries-have-file-conflict not marked as experimental

Package: lintian Version: 2.5.5 Severity: minor Hi, I got these new warnings when checking a package (false positives, btw): W: gnupg source: binaries-have-file-conflict gnupg gnupg-curl usr/lib/gnupg/gpgkeys_curl W: gnupg source: binaries-have-file-conflict gnupg gnupg-curl

Bug#615072: [checks/files] apply run-parts-cron-filename-contains-full-stop also to /etc/cron.d

Package: lintian Version: 2.4.3 Severity: wishlist Tags: patch Hi, Files under /etc/cron.d must conform to the same filename specs as those in the cron.{hourly,daily,weekly} dirs, so it would be nice to check those for dots aswell. Attached patch accomplishes that. One could perhaps consider

Bug#574826: example-interpreter-not-absolute false positive for non-executable files

Package: lintian Version: 2.3.3 Severity: minor Hi, My package triggered the following info-level Lintian tests: I: eekboek: example-interpreter-not-absolute ./usr/share/doc/eekboek/examples/Kasverkoop.pm #!perl I: eekboek: example-wrong-path-for-interpreter

Bug#529924: duplicate-short-description between deb and udeb

Package: lintian Version: 2.2.10 Severity: minor Hi, My package 'gnupg' generates the following info-level tag: duplicate-short-description gnupg gnupg-udeb I believe this may be inappropriate where the description overlap is between the deb and its associated udeb. In the Lintian report

Bug#517899: internal error: command failed with error code 123 in collect info file-info

On tiisdei 3 Maart 2009, Russ Allbery wrote: Thijs Kinkhorst th...@debian.org writes: I get the following output when I check a mailman source package. $ lintian mailman_2.1.12-1.dsc Use of uninitialized value $_ in substitution (s///) at /usr/share/lintian/collection/file-info line 50

Bug#517899: internal error: command failed with error code 123 in collect info file-info

Package: lintian Version: 2.2.6 Severity: normal Hi, I get the following output when I check a mailman source package. $ lintian mailman_2.1.12-1.dsc Use of uninitialized value $_ in substitution (s///) at /usr/share/lintian/collection/file-info line 50, INDEX line 1. Use of uninitialized

Bug#517899: internal error: command failed with error code 123 in collect info file-info

On moandei 2 Maart 2009, Adam D. Barratt wrote: The error suggests that the index file which Lintian has generated of the orig tarball contains a line in an unexpected format as the first line - specifically, it does not contain at least six space-separated fields. Unfortunately I'm

Bug#515689: duplicate-font-file X also in ttf-aenigma, bad advice?

Package: lintian Version: Hi, On my package 'serendipity' I now get the following Lintian warning: W: serendipity: duplicate-font-file usr/share/serendipity/www/plugins/serendipity_event_spamblock/chumbly.ttf also in ttf-aenigma N: N:This package appears to include a font file that is

Bug#515690: embedded-javascript-library: not so certain

Package: lintian Version: 2.2.0 Severity: minor Hi, In my package 'serendipity' I get the following warning: W: serendipity: embedded-javascript-library usr/share/serendipity/www/templates/default/YahooUI/treeview/YAHOO.js [...] N:Severity: normal, Certainty: certain This YAHOO.js is a

Bug#498617: package with only I tags is displayed on normal report and PTS

Package: lintian Version: 1.24.4 Severity: minor Hi, I have a package (php-net-socket) that currently just has two info-level lintian tags. On the page http://lintian.debian.org/maintainer/[EMAIL PROTECTED] it is listed in the bulleted list near the top but the anchor doesn't go anywhere.

Bug#494723: command-with-path-in-maintainer-script: misparses command

Package: lintian Version: 1.24.3 Severity: minor Hi, This is a cosmetic issue only. The test command-with-path-in-maintainer-script misparses the command it detected. See e.g. in phpmyadmin: command-with-path-in-maintainer-script * postrm:12 /usr/sbin/lighty * postinst:13

Bug#487515: lintian.debian.org: doesn't show results for package in contrib

Package: lintian Version: 1.23.28 Severity: minor Hi, My lintian.debian.org page doesn't list the package 'msttcorefonts' I maintain which is in contrib. I guess this is because contrib and non-free packages are not checked. I see no good reason to not do that; other Debian QA tools list those

Bug#471751: False positive: unknown-section base

On Thursday 20 March 2008 00:21, Russ Allbery wrote: lintian is slightly ahead of Policy, but base is gone; ftpmaster has already moved all packages out of base and it will be removed from the next Policy release.  Please change the section. Good to know, I've updated the package. Thanks,

Bug#471751: False positive: unknown-section base

Package: lintian Version: 1.23.46 Hi, Lintian produces a warning unknown-section base, but the description of that warning is: |The `Section:' field in this package's control file is not one of the |sections in use on the ftp archive. Valid sections are currently admin, |base,

Bug#460964: issues unknown unknown-interpreter tag

Package: lintian Version: 1.23.42 Hi! Lintian issues the tag unknown-interpreter at two places: ./checks/infofiles:189: tag unknown-interpreter, $script, $interp; ./checks/menus:563: tag unknown-interpreter, $script, $interp; But this tag is not a known tag resulting in: Tried

Bug#460966: uninitialized values when having empty prerm script

Package: lintian Version: 1.23.42 Severity: minor Hi, I accidentally created a zero-byte 'debian/prerm' script in my package. That of course was not intentional or useful, but the output of lintian contained quite some 'uninitialized value's and was unclear as to the source of this problem:

Re: New lintian pages available for testing

On Thu, January 3, 2008 10:00, Lars Wirzenius wrote: That would mean that it gets harder to get one or the other version of the page: it's no longer enough to just go to the page, you also have to go click on something else as well. For something that is a simple report page, I don't think

Re: New lintian pages available for testing

Hi Russ, On Thursday 3 January 2008 01:16, Russ Allbery wrote: http://lintian.debian.org/reports-testing/ This looks good in general, it's a clear improvement over what we have. * The HTML pages are now templatized (using Text::Template). The core of many of the pages is still

Bug#455211: improperly encoded and symbols in descriptions

Package: lintian Version: 1.23.38 Severity: minor Tags: patch Hi! The new malformed-override tag introduces some unencoded and in the description, making the text unreadable. This has only partially been fixed in SVN. Attached patch fixes that description fully, plus some other instances of

Bug#454239: symlink-should-be-relative: warning instead of error

Package: lintian Version: 1.23.36 Severity: minor Tags: patch Hi! In my package mailman, I have converted two symlinks from relative to absolute. The relative symlinks gave trouble for a number of different users that had symlinked the targets themselves, and linking to relative links gives

Bug#449257: warn on non-increasing changelog version numbering

Package: lintian Version: 1.23.36 Severity: wishlist Hi, I received a package from a sponsoree that contained two changelog sections both with the exact same version number, which was obviously a mistake but lintian didn't catch it. I assume that all version numbers in the changelog should be

Bug#448677: lintian: Please include copyright-contains-dh_make-todo-boilerplate

Hi, (BTW, isn't lintian maintained in a public $VCS? Being able to debcheckout it would be great. ;-)) Yes it is, I've added the following Vcs-* fields to debian/control just now: Vcs-Svn: http://svn.wolffelaar.nl/lintian/trunk/ Vcs-Browse: http://svn.wolffelaar.nl/wsvn/lintian/ Thijs

Bug#438860: debconf-error-requires-versioned-depends too strict

Package: lintian Severity: wishlist Version: 1.23.34 Hi, The debconf-error-requires-versioned-depends test is triggered on my package: I: msttcorefonts: debconf-error-requires-versioned-depends msttcorefonts/baddldir Its description says: N: Since error types were added after debconf-2.0,

Bug#437925: source-nmu-has-incorrect-version-number mentions old binNMU style

Package: lintian Version: 1.23.34 Severity: minor Tags: patch Hi, The description for source-nmu-has-incorrect-version-number reads: N: A source NMU should have a Debian revision of '-x.x'. This is to N: prevent stealing version numbers from the maintainer (and the -x.x.x N: version

Bug#434744: Downgrade source-contains-CVS-dir to info

Package: lintian Version: 1.23.31 Severity: wishlist Hi, I'm getting the following warnings for one of my packages: W: phpgedview source: source-contains-CVS-dir places/IDN/CVS W: phpgedview-places binary: package-contains-CVS-dir usr/share/phpgedview/www/places/IDN/CVS/ While I can and

Bug#424164: lintian: don't complain about README/LICENSE files in zope Products

reopen 424164 thanks Hi, + [RA] Don't warn about LICENSE files in Zope products, since they may be used for runtime display. (Closes: #424164) I'm wondering about the background of this change. I've read the original request, which was that some applications like to display the licence

Bug#424164: lintian: don't complain about README/LICENSE files in zope Products

On Tuesday 5 June 2007 17:07, Bernd Zeimetz wrote: we're talking about zope template files here, not just a stupid text file living somewhere. It doesn't make sense to read a Zope template on it's own, and it's not possible to drop a simple text file into it's place instead. *.pt files are

Bug#423171: possible-missing-colon-in-closes should not check ancient entires

On Thursday 10 May 2007 17:28, Russ Allbery wrote: I suggest to only check the topmost changelog entry, as some other tests already do aswell if I remember correctly. None that I could find, and I couldn't see a way of doing that without some structural changes, although I could look again.

Bug#406349: lintian: Some tests contain 'usr-doc' which should be 'usr-share-doc'

Package: lintian Version: 1.23.27 Severity: minor Tags: patch Hi, The following tests: usr-doc-symlink-points-outside-of-usr-doc usr-doc-symlink-without-dependency usr-doc-symlink-to-foreign-package cannot-check-whether-usr-doc-symlink-points-to-foreign-package

Bug#394104: lintian: Use of uninitialized value in concatenation in checks/fields

Package: lintian Version: 1.23.25 Severity: minor Hi, Lintian outputs a warning when checking update-manager_0.42.2ubuntu22-5.dsc as available from the archive: $ lintian update-manager_0.42.2ubuntu22-5.dsc E: update-manager source: missing-build-dependency python | python-dev | python-all-dev

Bug#388824: select-with-translated-default-field may be a bit overzealous

On Tue, 2006-09-26 at 21:20 -0700, Russ Allbery wrote: Attached is a patch that checks source packages instead of binary packages. There are different advantages for this solution: This sounds good, thanks Thomas for the patch and Russ for swiftly applying it. Thijs signature.asc

Bug#388824: select-with-translated-default-field may be a bit overzealous

Package: lintian Version: 1.23.24 Severity: minor Hello, Our package uses a translated DefaultChoice field in the debconf templates, exactly as described in DevRef 6.5.4.4. Lintian triggers a warning on this: select-with-translated-default-field. Since the warning doesn't apply, I'm overriding

Bug#382477: too-long-extended-description-in-templates: rather fix the tool than condense a description

reassign 382477 developers-reference retitle 382477 Sect 6.5.3.2: rather fix the tool than condense a description thanks On Fri, 2006-08-11 at 07:28 -0700, Russ Allbery wrote: Thijs Kinkhorst [EMAIL PROTECTED] writes: Package: lintian Version: 1.23.22 Hello, On the mailman package

Bug#382477: too-long-extended-description-in-templates: rather fix the tool than condense a description

Package: lintian Version: 1.23.22 Hello, On the mailman package I received this lintian warning: W: mailman: too-long-extended-description-in-templates mailman/queue_files_present N: N: Some debconf interfaces cannot deal very well with descriptions of N: more than about 20 lines, so try

Bug#368206: lintian: Should not warn for writing style in untranslatable templates

reopen 368206 thanks Hi, When trying to resolve some lintian warnings of a package, I encountered this same situation: the template is for internal use and thus has no description, however I still get a warning: E: dbconfig-common: no-template-description dbconfig-common/internal/reconfiguring

Bug#374167: lintian: [unnoticed] debian/conpyright: It was downloaded from fill in http/ftp site

The following line goes unnoticed by Lintian: It was downloaded from fill in http/ftp site lintian should check if there is 'http://', 'ftp://' URL and warn if no valid looking URL link was found on the upload line. Well, there's of course a large list of protocols one could use to

Bug#377616: lintian: Mention Lintian version in standard page footer

Package: lintian Version: 1.23.22 Severity: wishlist Tags: patch Hello, Here's a simple patch to mention the Lintian version used in the standard page footer of the HTML output. Thijs -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500,

Bug#375638: lintian: deb-created-with-broken-tar: typos and tar version clarification

Package: lintian Version: 1.23.21 Severity: minor Tags: patch Hello, The explanation of deb-created-with-broken-tar says that some versions of tar are broken. I've added to the message a summary of which (Debian) versions this concerns. Furthermore the description has two typos, s/make/makes/,

Bug#348864: please check if man page is in right section

Collin Watson [EMAIL PROTECTED] wrote: All that said, while I can think of valid examples where a program is in bin with a man page in section 8, I can't think of any valid examples where a program is in sbin with a man page in section 1. I think a check for the latter would probably be

Bug#350114: Please add ubuntu upload targets to frontend/lintian

Reinhard Tartler [EMAIL PROTECTED] wrote: in order to get rid of this patch in ubuntu, please include it in the next lintian upload. Attached the patch we have in ubuntus lintian. That doesn't seem right. We can assume that someone packaging on a Debian system (i.e. running lintian from Debian)

Bug#324490: lintian.debian.org: Typo in lintian 404 page

Package: lintian Severity: minor Lintian.debian.org 404 pages (Either there's no record of packages from that maintainer...) have a small error at their footer: the mailto: link contains two wrongly-escaped quotes (\) and there's an extra quote at the end of the document. Thijs -- To

Bug#317277: copyright-lists-upstream-authors-with-dh_make-boilerplate is overly nitpicky - please remove

On Fri, July 8, 2005 19:29, Goswin von Brederlow wrote: It points out a minor shortcomming in the phrasing of the text. Like people reporting typos or spelling mistakes. This is certainly no RC bug but something that is easily fixable and should be fixed non the less. Well, it's not even a