Package: lintian
Version: 2.24.0~bpo9+2
Severity: serious
thanks
Hi Chris,
the lintian version in Stretch backports seems to be broken:
debian@devel:~/tmp/lintian$ grep -R ""
lintian-2.24.0~bpo9+2/checks/fields.pm:<<< HEAD
lintian-2.24.0~bpo9+2/checks/fields.pm:<<< HEAD
Hi Chris,
On Thu, 12 Jul 2018, Chris Lamb wrote:
The description of pyicloud contains the name of a software called "Find
My iPhone".
I think this is a case for an override rather than a change in Lintian
as it will never be able to reliably know that this is a false positive
without
Package: lintian
Version: 2.5.84
Severity: normal
The description of pyicloud contains the name of a software called "Find
My iPhone".
So in this case "My" is not a using-first-person-in-description ...
Thorsten
Package: lintian
Version: 2.5.82~bpo9+1
Severity: normal
git.dgit.debian.org seems to be within *.debian.org, so this looks like a
false positive ...
lintian check for python-ofxhome_0.3.3-2.dsc
W: python-ofxhome source:
orphaned-package-not-maintained-in-debian-infrastructure
Package: lintian
Version: 2.5.80
Severity: normal
For osmo-trx 0.2.0 I get:
I: osmo-trx: spelling-error-in-binary usr/bin/osmo-trx wIH with
But there is no wIH in the source:
debian@devel:~/move-to-salsa/mobcom/osmo-trx/osmo-trx-0.2.0$ grep -R wIH
Hi Chris,
On Sun, 15 Apr 2018, Chris Lamb wrote:
I could have sworn that already not all files in the patch/ directory
trigger such a message. But as I understand you right now, this is not the
case yet. So I am fine with it ...
Sorry, I don't understand what you mean here. :) Can you
Hi Chris,
On Sun, 15 Apr 2018, Chris Lamb wrote:
This might be a language thing but I would not know what "patch
back" would mean out of context. Indeed, even when I am pretty
sure what you are trying to achieve (temporarily ignore a patch?)
yes, thats what I wanted.
I could have sworn that
Package: lintian
Version: 2.5.80
Severity: wishlist
My outreachy mentee renamed an old patch to:
02_set_version_explicitly.patch_back
lintian complained about that with:
W: libosmo-sccp source: patch-file-present-but-not-mentioned-in-series
02_set_version_explicitly.patch_back
I would like
Package: lintian
Version: 2.5.67
Severity: normal
A soon to be available package gives:
I: osmocom-analog: spelling-error-in-binary usr/bin/amps Rouge Rogue
This is a false positive as it comes from:
osmocom-analog-0.0.1/src/amps/stations.c: { 85, 0, "Baton Rouge",
Package: lintian
Version: 2.5.67
Severity: normal
According to the maintainer of libplacebo this is false positive.
md5sum :0ea16a2c4b94f0c1a83d11278655ac9f ./libplacebo-0.4.0/demos/lena.jpg
sha1sum :14045bb11fbccdfa9a522cf74ced9385f02307d8
./libplacebo-0.4.0/demos/lena.jpg
Package: lintian
Version: 2.5.72
Severity: wishlist
Please extend the long description of maintainer-script-should-not-use-service
Especially it is not clear what to do in case a package changes the
config of another package and would like to reload the config during
installation.
For
Package: lintian
Version: 2.5.52
Severity: normal
The license of package oysttyer contains an example, which gives a false
positive for "copyright-year-in-future":
* If you choose to create and distribute a derivative work based on
this package, your derivative work must clearly
Hi Niels,
On Sun, 22 Jun 2014, Niels Thykier wrote:
AFAICT this license explicitly forbids modification and therefore fails
to meet the DFSG ยง3. If you disagree with our assertion, then I
recommend we pass it by the FTP masters, who are the authority on this.
Should they disagree with our
Package: lintian
Severity: normal
User: alteh...@debian.org
thanks
Dear Maintainer,
I am very sure that I did not put any RFC into debian/copyright of the
scheme48 package. So I am afraid this error is a false positive.
Thanks!
Thorsten
--
To UNSUBSCRIBE, email to
Package: lintian
Version: 2.5.22.1
Severity: normal
As already mentioned in #736992 something like:
LINK rel=Bookmark title=Ab Initio Physics Home Page
href=http://ab-initio.it.edu;
doesn't seem to be any privacy breach ...
Thorsten
--
To UNSUBSCRIBE, email to
Package: lintian
Version: 2.5.8
Severity: important
Tags: patch
While checking for duplicate-updaterc.d-calls-in-postinst the character +
is not allowed as a valid name of the package.
Attached is a patch to solve this problem but I guess that it might occur
somewhere else.
Thorsten
--
Package: lintian
Version: 2.5.1
Severity: normal
Hi,
assuming that there is a python package containing some ksh-scripts which
are started from the python scripts (please don't ask for the purpose of
this, it is an example from real life).
The Build-Depends: of the source packages does not need
17 matches
Mail list logo
