On Sun, Sep 09, 2007 at 08:12:19PM -0700, Russ Allbery wrote:
Luis Furquim [EMAIL PROTECTED] writes:
The problem is that my package is GPLv3 licensed and lintian threw the
error message copyright-should-refer-to-common-license-file-for-gpl and
in my Ubuntu Feisty Fawn box I found no GPLv3
Hi
Ok. When I upgrade to Gutsy the problem will be solved. But as this will
happen
in october, I will probably release new versions before it since I an in a
release
candidate stage and I have one more bug to fix. So, until there, I will
remove the
text refering to the common license directory
Package: lintian
Version: 1.23.28
Severity: minor
Hi,
I tried verifying a package using lintian *.dsc and was very happy that
lintian did not report errors.
Now I noticed that I have to call it with the .changes file! Why isn't
my error not detected?
Jens
-- System Information:
Debian
Jens Seidel [EMAIL PROTECTED] writes:
Package: lintian
Version: 1.23.28
Severity: minor
I tried verifying a package using lintian *.dsc and was very happy that
lintian did not report errors.
Now I noticed that I have to call it with the .changes file! Why isn't
my error not detected?
On Mon, Sep 10, 2007 at 12:29:45PM -0700, Russ Allbery wrote:
Jens Seidel [EMAIL PROTECTED] writes:
Package: lintian
Version: 1.23.28
Severity: minor
I tried verifying a package using lintian *.dsc and was very happy that
lintian did not report errors.
Now I noticed that I have
Jens Seidel [EMAIL PROTECTED] writes:
Mmh, is the manpage still up-to-date?
So far as I know.
There are three ways to specify binary, udeb or source packages for
Lintian to process: by file name, by package name, or by naming a
.changes file.
*.dsc is not a package name and not a .changes
6 matches
Mail list logo