Package: lintian
Version: 2.5.124
Severity: normal
Dear Maintainer,
I'm trying to figure out why my package (wxpython4.0) is getting flagged for
hardening-no-fortify-functions even though I have
export DEB_BUILD_MAINT_OPTIONS = hardening=+all in my debian/rules and I can see
the
Package: lintian
Some tests check directory transversal issues. Those arise when
control fields contain relative paths. The tests look for Lintian
warnings. They look like this:
warning: tainted [...] package '...', skipping
The warnings are emitted by lib/Lintian/ProcessablePool.pm. While
Hi Andrius,
> > * What if the original code is actually included? How would
> >Lintian find that?
>
> I would expect %.pm to be generated from %.yp, but not necessarily.
How reliable is this?
Naturally, pre-generated parsers should be regenerated during
package build but we can't
Hi Chris,
On 2019-02-01 15:47, Chris Lamb wrote:
> * Can one do this on a subset of filenames? (.pl?)
Yes, it's going to be *.pm (Perl module) files only.
> * What if the original code is actually included? How would
>Lintian find that?
I would expect %.pm to be generated from %.yp, but
Processing commands for cont...@bugs.debian.org:
> tags 921080 + moreinfo
Bug #921080 [lintian] lintian: warn about non-regenerated Parse::Yapp parsers
Added tag(s) moreinfo.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
921080:
tags 921080 + moreinfo
thanks
Hi Andrius,
> look though the package source for Parse::Yapp-added headers
Two quick questions:
* Can one do this on a subset of filenames? (.pl?)
* What if the original code is actually included? How would
Lintian find that?
Regards,
--
,''`.
Package: lintian
Version: 2.5.124
Severity: wishlist
Dear Maintainer,
so I uploaded
https://tracker.debian.org/news/1025869/accepted-anarchism-151-8-source-into-unstable/
and had this line in debian/control:
Vcs-Git: https://salsa.debian.org/debian/anarchism.git.git
It would be nice if
Package: lintian
Severity: wishlist
Hello,
packages sometimes ship pre-generated Parse::Yapp parsers while in principle
they have to be generated from their source (this has already been discussed in
debian-perl@ [1]). A simple check would be to look though the package source
for
Dear Scott,
> Do you have any thoughts on this?
Not quite at this time, alas. May I suggest filing an issue against
the Lintian package with the aforementioned information?
Whilst I understand that you/we are unsure whether it is a false-
positive or not yet (hence not refering to "bug" in the
9 matches
Mail list logo
