[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1075163: marked as done (libdigidoc: ftbfs with GCC-14)

Your message dated Wed, 21 Aug 2024 23:36:51 +0000
with message-id <E1sgusl-00Dyzl-Vk@fasolo.debian.org>
and subject line Bug#1075163: fixed in libdigidoc 3.10.5-6
has caused the Debian Bug report #1075163,
regarding libdigidoc: ftbfs with GCC-14
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 owner@bugs.debian.org
immediately.)


-- 
1075163: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075163
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: src:libdigidoc
Version: 3.10.5-5
Severity: important
Tags: sid trixie
User: debian-gcc@lists.debian.org
Usertags: ftbfs-gcc-14

[This bug is targeted to the upcoming trixie release]

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-14/g++-14, but succeeds to build with gcc-13/g++-13. The
severity of this report will be raised before the trixie release.

The full build log can be found at:
http://qa-logs.debian.net/2024/07/01/libdigidoc_3.10.5-5_unstable_gccexp.log
The last lines of the build log are at the end of this report.

To build with GCC 14, either set CC=gcc-14 CXX=g++-14 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-14/porting_to.html

[...]
  138 |   return __builtin___strncat_chk (__dest, __src, __len,
      |          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  139 |                                   __glibc_objsize (__dest));
      |                                   ~~~~~~~~~~~~~~~~~~~~~~~~~
/<<PKGBUILDDIR>>/libdigidoc/DigiDocOCSP.c: In function ‘WriteOCSPResponse’:
/<<PKGBUILDDIR>>/libdigidoc/DigiDocOCSP.c:249:18: error: passing argument 1 of ‘ASN1_i2d_bio’ from incompatible pointer type [-Wincompatible-pointer-types]
  249 |     ASN1_i2d_bio((int (*)(void*, unsigned char**))i2d_OCSP_RESPONSE, bout, (unsigned char*)resp);
      |                  ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
      |                  |
      |                  int (*)(void *, unsigned char **)
In file included from /usr/include/openssl/objects.h:21,
                 from /usr/include/openssl/evp.h:44,
                 from /usr/include/openssl/x509.h:29,
                 from /<<PKGBUILDDIR>>/libdigidoc/DigiDocLib.h:36,
                 from /<<PKGBUILDDIR>>/libdigidoc/DigiDocConfig.h:29,
                 from /<<PKGBUILDDIR>>/libdigidoc/DigiDocOCSP.c:23:
/usr/include/openssl/asn1.h:967:31: note: expected ‘int (*)(const void *, unsigned char **)’ but argument is of type ‘int (*)(void *, unsigned char **)’
  967 | int ASN1_i2d_bio(i2d_of_void *i2d, BIO *out, const void *x);
      |                  ~~~~~~~~~~~~~^~~
/<<PKGBUILDDIR>>/libdigidoc/DigiDocOCSP.c: In function ‘WriteOCSPRequest’:
/<<PKGBUILDDIR>>/libdigidoc/DigiDocOCSP.c:297:18: error: passing argument 1 of ‘ASN1_i2d_bio’ from incompatible pointer type [-Wincompatible-pointer-types]
  297 |     ASN1_i2d_bio((int (*)(void*, unsigned char**))i2d_OCSP_RESPONSE, bout, (unsigned char*)req);
      |                  ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
      |                  |
      |                  int (*)(void *, unsigned char **)
/usr/include/openssl/asn1.h:967:31: note: expected ‘int (*)(const void *, unsigned char **)’ but argument is of type ‘int (*)(void *, unsigned char **)’
  967 | int ASN1_i2d_bio(i2d_of_void *i2d, BIO *out, const void *x);
      |                  ~~~~~~~~~~~~~^~~
/<<PKGBUILDDIR>>/libdigidoc/DigiDocOCSP.c: In function ‘get_authority_key_from_cert’:
/<<PKGBUILDDIR>>/libdigidoc/DigiDocOCSP.c:838:3: warning: ‘ASN1_STRING_data’ is deprecated: Since OpenSSL 1.1.0 [-Wdeprecated-declarations]
  838 |   ret = decodeHex((unsigned char*)hex_to_string(ASN1_STRING_data(val->keyid), ASN1_STRING_length(val->keyid)));
      |   ^~~
/usr/include/openssl/asn1.h:683:40: note: declared here
  683 | OSSL_DEPRECATEDIN_1_1_0 unsigned char *ASN1_STRING_data(ASN1_STRING *x);
      |                                        ^~~~~~~~~~~~~~~~
/<<PKGBUILDDIR>>/libdigidoc/DigiDocOCSP.c: In function ‘OCSP_sendreq_bio_withParams’:
/<<PKGBUILDDIR>>/libdigidoc/DigiDocOCSP.c:965:26: error: passing argument 1 of ‘ASN1_i2d_bio’ from incompatible pointer type [-Wincompatible-pointer-types]
  965 |   retcode = ASN1_i2d_bio((int (*)(void*, unsigned char**))i2d_OCSP_REQUEST, b, (unsigned char*)req);
      |                          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
      |                          |
      |                          int (*)(void *, unsigned char **)
/usr/include/openssl/asn1.h:967:31: note: expected ‘int (*)(const void *, unsigned char **)’ but argument is of type ‘int (*)(void *, unsigned char **)’
  967 | int ASN1_i2d_bio(i2d_of_void *i2d, BIO *out, const void *x);
      |                  ~~~~~~~~~~~~~^~~
/<<PKGBUILDDIR>>/libdigidoc/DigiDocOCSP.c: In function ‘verifyOCSPResponse’:
/<<PKGBUILDDIR>>/libdigidoc/DigiDocOCSP.c:1605:31: warning: passing argument 1 of ‘ossl_check_X509_type’ discards ‘const’ qualifier from pointer target type [-Wdiscarded-qualifiers]
 1605 |       sk_X509_push(ver_certs, notCert);
      |                               ^~~~~~~
In file included from /usr/include/openssl/types.h:33,
                 from /usr/include/openssl/x509.h:26:
/usr/include/openssl/x509.h:78:1: note: expected ‘X509 *’ {aka ‘struct x509_st *’} but argument is of type ‘const X509 *’ {aka ‘const struct x509_st *’}
   78 | SKM_DEFINE_STACK_OF_INTERNAL(X509, X509, X509)
      | ^
/<<PKGBUILDDIR>>/libdigidoc/DigiDocOCSP.c: In function ‘checkNonceAndCertbyOCSP’:
/<<PKGBUILDDIR>>/libdigidoc/DigiDocOCSP.c:1668:32: warning: passing argument 1 of ‘get_authority_key’ discards ‘const’ qualifier from pointer target type [-Wdiscarded-qualifiers]
 1668 |   if((ikey = get_authority_key(X509_get0_extensions(cert))) != NULL) {
      |                                ^~~~~~~~~~~~~~~~~~~~~~~~~~
/<<PKGBUILDDIR>>/libdigidoc/DigiDocOCSP.c:766:60: note: expected ‘struct stack_st_X509_EXTENSION *’ but argument is of type ‘const struct stack_st_X509_EXTENSION *’
  766 | unsigned char *get_authority_key(STACK_OF(X509_EXTENSION) *exts)
      |                                                            ^
make[3]: *** [libdigidoc/CMakeFiles/digidoc.dir/build.make:317: libdigidoc/CMakeFiles/digidoc.dir/DigiDocOCSP.c.o] Error 1
make[3]: *** Waiting for unfinished jobs....
make[3]: Leaving directory '/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu'
make[2]: *** [CMakeFiles/Makefile2:131: libdigidoc/CMakeFiles/digidoc.dir/all] Error 2
make[2]: Leaving directory '/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu'
make[1]: *** [Makefile:139: all] Error 2
make[1]: Leaving directory '/<<PKGBUILDDIR>>/obj-x86_64-linux-gnu'
dh_auto_build: error: cd obj-x86_64-linux-gnu && make -j8 "INSTALL=install --strip-program=true" VERBOSE=1 returned exit code 2
make: *** [debian/rules:12: binary] Error 25
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2

--- End Message ---
--- Begin Message --- 
Source: libdigidoc
Source-Version: 3.10.5-6
Done: Andreas Beckmann <anbe@debian.org>

We believe that the bug you reported is fixed in the latest version of
libdigidoc, 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 1075163@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andreas Beckmann <anbe@debian.org> (supplier of updated libdigidoc 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 ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Thu, 22 Aug 2024 01:09:19 +0200
Source: libdigidoc
Architecture: source
Version: 3.10.5-6
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group <packages@qa.debian.org>
Changed-By: Andreas Beckmann <anbe@debian.org>
Closes: 1075163
Changes:
 libdigidoc (3.10.5-6) unstable; urgency=medium
 .
   * QA upload.
   * Fix building with GCC 14.  (Closes: #1075163)
   * Improve docs installation.
   * Enable all hardening flags.
Checksums-Sha1:
 903b90f5fbe5f42595fa0a8d979c2f7a935af79f 2233 libdigidoc_3.10.5-6.dsc
 a2151a7335f22fb1f82ec300cfa9783bb1b86e42 5092 libdigidoc_3.10.5-6.debian.tar.xz
 fc591250c8091908948bdc5e13c0387b1d4250a8 6810 libdigidoc_3.10.5-6_source.buildinfo
Checksums-Sha256:
 9ebb7e278f6999606e42083cb8e9e0d05f0101b70ac287693bb7959511241007 2233 libdigidoc_3.10.5-6.dsc
 339956acf1666c0ac4932c20b2450d5881dbd81a131ac463bc0fdc8b1cdd1dd6 5092 libdigidoc_3.10.5-6.debian.tar.xz
 3ddae555768626fc2810a06f1662e9023a3d707de0d537359336277596b85643 6810 libdigidoc_3.10.5-6_source.buildinfo
Files:
 267eb3acbd2f51ae01769d7a1f6900d0 2233 libs optional libdigidoc_3.10.5-6.dsc
 6e1b75df3128afa1f1d0d279c40484c0 5092 libs optional libdigidoc_3.10.5-6.debian.tar.xz
 e2911320ea624b009e72e946b7124dde 6810 libs optional libdigidoc_3.10.5-6_source.buildinfo

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

iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAmbGdX0QHGFuYmVAZGVi
aWFuLm9yZwAKCRBfsz+TWentCIRkEACaEa9VhHoo1sVm/ETdjOIqIW7b7bKuBjaI
yZfZQOQUgiA8uZcs4fy1B+hW/vgXSxW9vQdEhSa62MyRUtpU/tR4y5878u9afITW
lQ1bmCQYvNkuWuetQZ4XddGpo+1sr/f/3KMChxvpteheXZIOXMryvddwwaqojkh9
YtmleSJn+ShkS8k1kd4yp6odmgq443bZFp0xKyKIn4+n0r7NvhkAdYR4u6YqEt7o
0spW4QKuxmTBg52mQrzm/uZ7zRD8uFSN8y4bersjlPXM5fVxFrwKiaSql5Tsz8kr
Oszn8b+IS0iAj5OE8ekQb5wn8dBjjM9lbqRoFxBl637ACXNroe1+XM+kWZa7NXIx
djIDCX72rv5pSAvVmIZhY0LfKQ5IOEp82pDlyoPzshptSr+jbORkpBGL8x2LNu9x
PNQp3RCF94BGj28YVwIry0pDxnwdRJNzRnXrVldhOMuPqWy7d8rNLQWLI111vEiu
ygvJl0laccKrvuus4RdOTNtyR6ewlfLZr8RMBCxpQJGG0wKOsrvuZLLngF79K4i5
dsDic3wDGuGtt3wXAgGinFvSc6E3OULQWRgzS6yAm7NwV2coJWk5KRc5yWfDBSP3
pZ/cf7IArFRxYs56XvuMVz5ShJ8FOF4NciL6hgqx5fsJytRQC9Yqj+GfMN0Q+icS
FOG+r2FLFQ==
=vsB7
-----END PGP SIGNATURE-----

Attachment: pgpQ8dU5Du2UZ.pgp
Description: PGP signature


--- End Message ---
Reply to: