Package: lintian
Version: 2.2.9
Severity: normal
Lintian reports problems with debhelper dependency when using 6 in
compat and build-depending on debhelper version 5.0.44.
Debhelper itself claims support for compat version 6 in its changelog
entry for version 5.0.44, which is the reason this
Package: lintian
Version: 2.2.9
Severity: important
When using python-central to handle Python packages potentially targeted
for multiple Python versions, library files are moved to a central
location and replaced with symlinks at install time.
Lintian complains with the following:
E:
Hi all,
I've been thinking that it might be a good idea for lintian to not emit
the NMU warnings when the changelog has a Foo team upload message at
the beginning. I realise this would be a fairly major change for Debian.
It would make me much more comfortable doing more QA and more uploads
Package: lintian
Version: 2.2.9
Severity: minor
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
There is a small typo in out-of-date-standards-version tag description.
verison-version
You canf find attached, a diff shows what files are concerned.
- -- System Information:
Debian Release:
Package: lintian
Version: 2.2.9
Severity: normal
The warning about the Breaks field is not required anymore, because Lenny
supports it.
Quote:
N:This package uses the Breaks control field. This control field should
N:not be used until the stable release of Debian supports Breaks.
On Sun, 2009-04-05 at 11:58 +0200, Jonas Smedegaard wrote:
Lintian reports problems with debhelper dependency when using 6 in
compat and build-depending on debhelper version 5.0.44.
Debhelper itself claims support for compat version 6 in its changelog
entry for version 5.0.44, which is the
Paul Wise p...@debian.org writes:
I've been thinking that it might be a good idea for lintian to not emit
the NMU warnings when the changelog has a Foo team upload message at
the beginning. I realise this would be a fairly major change for Debian.
It would make me much more comfortable doing
On Sun, 2009-04-05 at 17:01 +0200, Guillaume Delacour wrote:
There is a small typo in out-of-date-standards-version tag description.
verison-version
You canf find attached, a diff shows what files are concerned.
Thanks; I've committed your patch to the repository.
Regards,
Adam
--
To
Jonas Smedegaard d...@jones.dk writes:
Lintian reports problems with debhelper dependency when using 6 in
compat and build-depending on debhelper version 5.0.44.
Debhelper itself claims support for compat version 6 in its changelog
entry for version 5.0.44, which is the reason this version
Processing commands for cont...@bugs.debian.org:
#lintian (2.2.10) UNRELEASED; urgency=low
#
# * checks/standards-version.desc:
#+ [ADB] Fix a couple of spelling mistakes (verison - version).
# Thanks, Guillaume Delacour. (Closes: #522643)
#
package lintian
Ignoring bugs not
Processing commands for cont...@bugs.debian.org:
reassign 522613 cdbs
Bug#522613: lintian: false positive
package-lacks-versioned-build-depends-on-debhelper 6 (5.0.44 is new enough)
Bug reassigned from package `lintian' to `cdbs'.
retitle 522613 dh compat 6 must depend on v6 (not v5.0.44)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
reassign 522613 cdbs
retitle 522613 dh compat 6 must depend on v6 (not v5.0.44)
thanks
On Sun, Apr 05, 2009 at 08:38:46PM +0100, Adam D. Barratt wrote:
On Sun, 2009-04-05 at 11:58 +0200, Jonas Smedegaard wrote:
Lintian reports problems with
On Sun, 2009-04-05 at 12:54 -0700, Russ Allbery wrote:
I'm not sure what the drawback is to adding yourself to Uploaders. Could
you elaborate?
Well, it means that in various places I'll be marked as maintaining the
package rather than having done a once-off upload to bring the packaging
up to
Paul Wise p...@debian.org writes:
On Sun, 2009-04-05 at 12:54 -0700, Russ Allbery wrote:
I'm not sure what the drawback is to adding yourself to Uploaders.
Could you elaborate?
Well, it means that in various places I'll be marked as maintaining the
package rather than having done a once-off
On Sun, 2009-04-05 at 20:36 -0700, Russ Allbery wrote:
Hm. So it's sort of a team NMU -- you're not planning on taking ongoing
responsibility for the package except as just another member of the team.
Yeah, a team upload is a good way of putting it. You're uploading it as a
member of the
15 matches
Mail list logo
