Re: python-pysam version lagging
Le Tue, Jun 09, 2015 at 12:38:31AM -0700, Afif Elghraoui a écrit :
>
> I was able to build it and clean it up a little more, but the package still
> has some lint:
Hi Afif, thanks a lot for all this work.
> W: python-pysam source: dep5-copyright-license-name-not-unique (paragraph at
> line 40)
>
> I'm actually not sure what to do about this one.
Try public-domain instead of PublicDomain. "public-domain" is a special case
in the machine-readable specification, so if the Lintian warning stays, I would
consider it a false positive.
https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
> I: ...hardening-no-fortify-functions...
>
> I think these are false positives since the CPPFLAGS for fortification look
> like they're correctly set as I watch the package build.
I have seen such apparent false positives in other packages. If you have time,
maybe it is worth asking for comments on the debian-mentors mailing list ?
> I: ...spelling-error-in-binary...
>
> This is maybe not worth fixing.
Maybe the easiest way to get rid of it is a pull request to upstream on GitHub ?
> I: python-pysam-tests: package-contains-timestamped-gzip
> usr/share/doc/python-pysam/tests/pysam_data/ex1.sam.gz
>
> I'm not sure what to do about this, either. Does it really affect
> ReproducibleBuilds if it's an upstream-provided compressed file?
This is a false positive: there is a timestamp, but it will not change
unless Upstream updates the file, hence the build of a given Debian package
for Pysam is reproductible for that file.
Please let us know when you need an upload.
Have a nice day,
--
Charles Plessy
Debian Med packaging team,
http://www.debian.org/devel/debian-med
Tsurumi, Kanagawa, Japan
Reply to: