Control: close -1 On 2024-08-23 Santiago Vila <sanv...@debian.org> wrote: > reassign 1076905 libgpg-error-dev > affects 1076905 + src:poldi > found 1076905 1.49-2 > fixed 1076905 1.50-3 > thanks
> Hello. > The configure error which I reported here does not > happen anymore, but the poldi version has not changed at all. > Therefore this seems to be (or was) a bug in one of > the build-dependencies. > I believe that it was libgpg-error-dev, because of these > differences in the build log (before = ftbfs, after = ok). > -Preparing to unpack .../29-libgpg-error-dev_1.49-2_amd64.deb ... > -Unpacking libgpg-error-dev:amd64 (1.49-2) ... > +Preparing to unpack .../30-libgpg-error-dev_1.50-3_amd64.deb ... > +Unpacking libgpg-error-dev:amd64 (1.50-3) ... > checking for gpg-error-config... no > -checking for GPG Error - version >= 0.7... no > +configure: Use gpgrt-config with /usr/lib/x86_64-linux-gnu as > gpg-error-config > +checking for GPG Error - version >= 0.7... yes (1.50) > but I'm not 100% sure (there is also a new autoconf), so I hope you > can confirm this and then close the bug. Hello Santiago, it is not caused by libgpg-error on its own, poldi 0.4.2+git20161115.553060d-1.4 was built successfully against libgpg-error-dev_1.49-2 (both locally and on the autobuilders). However if I downgrade libgpg-error to 1.49-2 on up to date sid I get the error, too, even installing libgpg-error-dev_1.50 and overwriting /usr/share/aclocal/gpg-error.m4 with the 1.49 version lets the bug appear. So yes, it looks like there was some m4 breakage that has been fixed. 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'
