[Pkg-rust-maintainers] Bug#1103016: incompatibility with gpg causing FTBFS
Rene Engelhard
rene at debian.org
Sun Apr 13 19:50:52 BST 2025
Hi,
Am 13.04.25 um 20:34 schrieb Rene Engelhard:
> $ grep gpg control
> gpg [!alpha !armel !armhf !hppa !i386 !ia64 !kfreebsd-amd64 !kfreebsd-i386 !loong64 !m68k !mips !mipsel !mips64 !mips64el !powerpc !powerpcspe !ppc64 !ppc64el !riscv64 !s390x !sparc !sparc64] <!nocheck>,
> gpg-agent [!alpha !armel !armhf !hppa !i386 !ia64 !kfreebsd-amd64 !kfreebsd-i386 !loong64 !m68k !mips !mipsel !mips64 !mips64el !powerpc !powerpcspe !ppc64 !ppc64el !riscv64 !s390x !sparc !sparc64] <!nocheck>,
> gpgconf [!alpha !armel !armhf !hppa !i386 !ia64 !kfreebsd-amd64 !kfreebsd-i386 !loong64 !m68k !mips !mipsel !mips64 !mips64el !powerpc !powerpcspe !ppc64 !ppc64el !riscv64 !s390x !sparc !sparc64] <!nocheck>,
> libgpg-error-dev,
> libgpgme-dev,
> libgpgmepp-dev,
>
> in Build-Depends-Arch:
>
> The difference between both is that on the buildd gpg-for-sq 0.13.1-3 etc. got installed whereas in my local sbuild build gpg as in gpg 2.4.7-14 was installed,
> and that one passed.
> Indeed, after installing gpg-for-sq in a container which had a working build before makes it fail, removing it makes it work again.
>
To make it explicit: I don't use gpg-from-sq but B-D-A: on gpg.
So that one should have been taken and wasn't due to whatever the resolver did.
(This is probably helped by gpg-from-sq having a Provides: gpg...)
And with gpg-from-sq "standing in" for gpg the failure happens.
Buildlog: https://buildd.debian.org/status/fetch.php?pkg=libreoffice&arch=amd64&ver=4%3A25.2.3~rc1-1&stamp=1744402240&raw=0
> I could do
[...]
> as a workaround, but...
>
Which I probably need to do anyway to fix the build in experimental if the gb picked up gpg-from-sq again.
Regards,
Rene
More information about the Pkg-rust-maintainers
mailing list