Your message dated Wed, 13 Mar 2024 18:06:43 +0000
with message-id <e1rkszz-007zyl...@fasolo.debian.org>
and subject line Bug#1066137: fixed in gnupg2 2.2.40-2
has caused the Debian Bug report #1066137,
regarding gnupg2: -Werror=implicit-function-declaration failure testing for 
ldap_open
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1066137: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1066137
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gnupg2
Version: 2.2.40-1.1
Severity: serious
Justification: ftbfs
X-Debbugs-Cc: t...@mirbsd.de

Trying to binNMU gnupg2 to make it installable during t64 transition,
I notice the following configury output:

[…]
checking for library containing dn_skipname... none required
checking whether the resolver is usable... yes
checking whether LDAP via "-lldap" is present and sane... no
checking whether I can make LDAP be sane with lber.h... no
checking whether LDAP via "-lldap -llber" is present and sane... no
checking whether I can make LDAP be sane with lber.h... no
checking whether LDAP via "-lldap -llber -lresolv" is present and sane... no
checking whether I can make LDAP be sane with lber.h... no
checking whether LDAP via "-lwldap32" is present and sane... no
checking whether I can make LDAP be sane with lber.h... no
checking for ber_free in -llber... yes
configure: WARNING:
***
*** Building without LDAP support.
*** No CRL access or X.509 certificate search available.
***
checking for sendmail... no
[…]

This matches the following failure mode at the end of the build:

19:50⎜<cbmuser:#debian-ports> I can't build gnugpg2:
19:50⎜<cbmuser:#debian-ports>    dh_install -a -O--builddirectory=build
19:50⎜<cbmuser:#debian-ports> dh_install: warning: Cannot find (any matches for)
     ⎜    "debian/tmp/usr/lib/gnupg/dirmngr_ldap" (tried in ., debian/tmp)
19:50⎜<cbmuser:#debian-ports> dh_install: warning: dirmngr missing files:
     ⎜    debian/tmp/usr/lib/gnupg/dirmngr_ldap
19:50⎜<cbmuser:#debian-ports> dh_install: error: missing files, aborting

The cause in config.log:

configure:11580: checking whether LDAP via "-lldap" is present and sane
configure:11600: gcc -o conftest -g -O2 -Werror=implicit-function-declaration 
-ffile-prefix-map=/tmp/buildd/gnupg2-2.2.40=. 
-specs=/usr/share/dpkg/pie-compile.specs -fstack-protector-strong -Wformat 
-Werror=format-security  -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 
-D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2  
-specs=/usr/share/dpkg/pie-link.specs -Wl,-z,relro -Wl,-z,now conftest.c -lldap 
  >&5
conftest.c: In function 'main':
conftest.c:96:1: error: implicit declaration of function 'ldap_open'; did you 
mean 'ldap_turn'? [-Werror=implicit-function-declaration]
   96 | ldap_open("foobar",1234);
      | ^~~~~~~~~
      | ldap_turn
cc1: some warnings being treated as errors
configure:11600: $? = 1
configure: failed program was:
[…]
| /* end confdefs.h.  */
| 
| #ifdef _WIN32
| #include <winsock2.h>
| #include <winldap.h>
| #else
| #include <ldap.h>
| #endif
| 
| int
| main (void)
| {
| ldap_open("foobar",1234);
|   ;
|   return 0;
| }
configure:11608: result: no


Prototypes are now mandatory, both for C23 and because the t64 transition
can only work if prototypes are properly used.

bye,
//mirabilos

--- End Message ---
--- Begin Message ---
Source: gnupg2
Source-Version: 2.2.40-2
Done: Andreas Metzler <ametz...@debian.org>

We believe that the bug you reported is fixed in the latest version of
gnupg2, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1066...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andreas Metzler <ametz...@debian.org> (supplier of updated gnupg2 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Wed, 13 Mar 2024 18:27:10 +0100
Source: gnupg2
Architecture: source
Version: 2.2.40-2
Distribution: unstable
Urgency: medium
Maintainer: Debian GnuPG Maintainers <pkg-gnupg-ma...@lists.alioth.debian.org>
Changed-By: Andreas Metzler <ametz...@debian.org>
Closes: 1066137
Changes:
 gnupg2 (2.2.40-2) unstable; urgency=medium
 .
   * Team upload.
   * ldap-implicit.diff: Fix FTBFS with -Werror=implicit-function-declaration
     due to using ldap deprecated interfaces in autoconf tests.
     Closes: #1066137
Checksums-Sha1: 
 293c5e7b55eb392565a736c75ea6338e7dbb5610 3824 gnupg2_2.2.40-2.dsc
 0fe00340fb7401f9141feee20cf59c440acff79f 62656 gnupg2_2.2.40-2.debian.tar.xz
Checksums-Sha256: 
 3440b1de877c780420063f8056814a8d7cc58ac610db7f49536bdb72f1a91946 3824 
gnupg2_2.2.40-2.dsc
 e4c57f6336c0226107484eb7615031d2b08e3b92e1f4760e0b7caff00f69aaad 62656 
gnupg2_2.2.40-2.debian.tar.xz
Files: 
 a8e61e24fd546b7d50309a6fb77d2c82 3824 utils optional gnupg2_2.2.40-2.dsc
 fa8b44a9720ba816a6737fbef0fa7647 62656 utils optional 
gnupg2_2.2.40-2.debian.tar.xz

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEE0uCSA5741Jbt9PpepU8BhUOCFIQFAmXx5bsACgkQpU8BhUOC
FIR4ww//S/WXEL/3PP83hOPdpdX3z0YNdWk/dSPCAYQdjz3s6BIJZE3m/BoWJoni
eYqwUaC7QsErI8Uput4O8OjTzw/bQYIfR2z6ap04+giAApWRpB0azSltXjhMj3Xo
cCGiFb7dw9/dfVHhkQk+s+lXh5iB3j/0cs9iYCRUWyZXpoMDZBb5akdPmbbQyGGS
/xRW1QvRgRkAXIShkMkLynAqPjaJB1+szRMDHSNyPFqbKu1XRjeSBqPG+9Q9Hw0z
7kLJ0/b64T5aSEn2yDSMtP75OQ6LPduhVzPDhYHDFGWdpJLpuVGKvVRbpTYl7MDL
xZk2CGvASFqvXuQtFTGBvzAIkOChsAUfEWSqolTCalqYh/Umew4rM1Q5WNXGDkKz
YCNPvLH3h1/0XtR+ady0+aFooERrEO5qBEuRa6sR46VHsFwImPWotibfmsTMUnUL
izC8oYOBtbI1NmAR1p04nDXtCELeJYm/boXx30PEpzCfU8pXAXWKXjDwgg/Quj/0
mKzo82vZmS2+24vZ5AlaptCor1S6qH2nixOeMoEtPbxGqZJiOBDvWsj5GSwAlCTH
K69vfbUZMUm/99q7HGkBeK8bLohRPCbaP4a3TX/TCL7a+g56ekVg6bn9QIu82Vvk
9l0OQjCMpZT0QGeri1MMbUJq82NJNr0TysrVpVvsZc9HK/YaOJM=
=qf+D
-----END PGP SIGNATURE-----

Attachment: pgpSPmeQChF1R.pgp
Description: PGP signature


--- End Message ---

Reply via email to