[Debian-med-packaging] Bug#1022087: jellyfish: FTBFS with pkgconf

Andreas Metzler ametzler at bebt.de
Fri Oct 21 18:01:05 BST 2022


On 2022-10-21 Andreas Metzler <ametzler at bebt.de> wrote:
> On 2022-10-20 Nilesh Patra <nilesh at debian.org> wrote:
>> On Wed, 19 Oct 2022 21:11:12 +0100 Andrej Shadura <andrewsh at debian.org> wrote:
>> > Source: jellyfish
> [....]

>> I took a look at this one, and this seems to FTBFS with pkgconf
>> because pkgconf does not seem to honor atleast PKG_CONFIG_SYSROOT_DIR
>> which is set in d/rules for this package[1]
> [...]
>> with old pkg-config:

>> $ PKG_CONFIG_PATH=. PKG_CONFIG_SYSROOT_DIR=debian/tmp/ pkg-config --cflags jellyfish-2.0
>> -Idebian/tmp//usr/include/jellyfish-2.3.0

>> with pkgconf:

>> $ PKG_CONFIG_PATH=. PKG_CONFIG_SYSROOT_DIR=debian/tmp/ pkg-config --cflags jellyfish-2.0
>> -I/usr/include/jellyfish-2.3.0
> [...]

> Hello,

> Looks like this could be https://github.com/pkgconf/pkgconf/issues/267
> which was fixed in June
> https://github.com/pkgconf/pkgconf/commit/a61193c7236f5b240585c4f8eef6f452f1d9a7ee
> but has not hit a release yet.

Indeed applying the upstream patch fixes the testcase Nilesh provided.

I have not tried rebuilding jellyfish with patched pkgconf.

cu Andreas

-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'



More information about the Debian-med-packaging mailing list