On 09/23/2016 01:15 AM, Marius Bakke wrote:
Ben Woodcroft <b.woodcr...@uq.edu.au> writes:

Subject: [PATCH 1/3] gnu: python-pysam: Update to
I'm not sure whether this is a product of the upgrade or not, but I
notice this in the build log. I think it is harmless though, WDYT?

starting phase `validate-runpath'
validating RUNPATH of 10 binaries in
warning: RUNPATH contains bogus entries: ("pysam" "."
I don't see this in the previous version, so it is a regression.
However, it should be mostly harmless. Readelf reports (when compiled
with external htslib, see below):

  0x000000000000001d (RUNPATH)            Library runpath: 

Compared to the runpath of the same file currently in Guix:

  0x000000000000001d (RUNPATH)            Library runpath: 

If a folder named "$CWD/build/lib.linux-x86_64-3.4/pysam exists, it
could potentially allow for code injection, which is troubling.

I opened an issue on their tracker, but don't think it's worth holding
the patch: https://github.com/pysam-developers/pysam/issues/347
Thanks, I agree.

Also, I notice that pysam bundles htslib, bcftools and samtools C code.
Hopefully it should be straightforward enough to remove htslib as there
are install instructions, I'm not sure about the other two. This
shouldn't block the patch here, but would you mind taking a look?
I had a go at this, and also enabled tests since I was reading the build
system anyway. Samtools and bcftools does not seem possible to un-bundle
at this time, but htslib was straightforward.
OK. I don't think it needs to be propagated though, right? Also, would you mind separating the change to modify-phases syntax and unbundling of htslib into two patches please? Other than that this whole series LGTM.

Sorry, I keep asking one more thing..

Reply via email to