Your message dated Fri, 09 Aug 2024 09:16:27 +0000
with message-id <[email protected]>
and subject line Bug#1075609: fixed in unrar-free 1:0.3.1-1
has caused the Debian Bug report #1075609,
regarding unrar-free: 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 [email protected]
immediately.)


-- 
1075609: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075609
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: src:unrar-free
Version: 1:0.3.0-0.1
Severity: important
Tags: sid trixie
User: [email protected]
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/unrar-free_0.3.0-0.1_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

[...]
checking whether ln -s works... yes
checking whether make sets $(MAKE)... (cached) yes
checking for stdio.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for strings.h... yes
checking for sys/stat.h... yes
checking for sys/types.h... yes
checking for unistd.h... yes
checking for archive.h... yes
checking for archive_entry.h... yes
checking for fcntl.h... yes
checking for stdlib.h... (cached) yes
checking for string.h... (cached) yes
checking for unistd.h... (cached) yes
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for libarchive... yes
checking for an ANSI C-conforming const... yes
checking for size_t... yes
checking for int64_t... yes
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking for GNU libc compatible malloc... yes
checking for GNU libc compatible realloc... yes
checking for error_at_line... yes
checking whether lstat correctly handles trailing slash... yes
checking for atexit... yes
checking for getpass... yes
checking for localtime_r... yes
checking for memset... yes
checking for mkdir... yes
checking for realpath... yes
checking for setenv... yes
checking for strchr... yes
checking for strdup... yes
checking for strrchr... yes
checking for strstr... yes
checking that generated files are newer than configure... done
configure: creating ./config.status
config.status: creating Makefile
config.status: creating src/Makefile
config.status: creating config.h
config.status: executing depfiles commands
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
   dh_auto_build
        make -j8
make[1]: Entering directory '/<<PKGBUILDDIR>>'
make  all-recursive
make[2]: Entering directory '/<<PKGBUILDDIR>>'
Making all in src
make[3]: Entering directory '/<<PKGBUILDDIR>>/src'
gcc -DHAVE_CONFIG_H -I. -I..   -Wdate-time -D_FORTIFY_SOURCE=2 
-fno-strict-aliasing -g -O2 -Werror=implicit-function-declaration 
-ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -c -o 
unrar_free-unrar.o `test -f 'unrar.c' || echo './'`unrar.c
gcc -DHAVE_CONFIG_H -I. -I..   -Wdate-time -D_FORTIFY_SOURCE=2 
-fno-strict-aliasing -g -O2 -Werror=implicit-function-declaration 
-ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -c -o 
unrar_free-opts.o `test -f 'opts.c' || echo './'`opts.c
unrar.c: In function ‘main’:
unrar.c:548:43: error: assignment to ‘const char **’ from incompatible pointer 
type ‘char **’ [-Wincompatible-pointer-types]
  548 |     arguments.unrar.multivolume_filenames = pglob.gl_pathv;
      |                                           ^
make[3]: *** [Makefile:389: unrar_free-unrar.o] Error 1
make[3]: *** Waiting for unfinished jobs....
make[3]: Leaving directory '/<<PKGBUILDDIR>>/src'
make[2]: *** [Makefile:443: all-recursive] Error 1
make[2]: Leaving directory '/<<PKGBUILDDIR>>'
make[1]: *** [Makefile:341: all] Error 2
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
dh_auto_build: error: make -j8 returned exit code 2
make: *** [debian/rules:10: build] Error 25
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2

--- End Message ---
--- Begin Message ---
Source: unrar-free
Source-Version: 1:0.3.1-1
Done: Ying-Chun Liu (PaulLiu) <[email protected]>

We believe that the bug you reported is fixed in the latest version of
unrar-free, 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 [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ying-Chun Liu (PaulLiu) <[email protected]> (supplier of updated unrar-free 
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 [email protected])


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

Format: 1.8
Date: Fri, 09 Aug 2024 15:47:20 +0800
Source: unrar-free
Architecture: source
Version: 1:0.3.1-1
Distribution: unstable
Urgency: low
Maintainer: Ying-Chun Liu (PaulLiu) <[email protected]>
Changed-By: Ying-Chun Liu (PaulLiu) <[email protected]>
Closes: 1075609
Changes:
 unrar-free (1:0.3.1-1) unstable; urgency=low
 .
   * New upstream release.
     - Fix FTBFS for GCC-14 (Closes: #1075609)
Checksums-Sha1:
 d62a8627bf196e04ecf4468eed73a18f69934ab9 1924 unrar-free_0.3.1-1.dsc
 e60b6f7543f9ca660b4ec227a700c2c04e560961 17624 unrar-free_0.3.1.orig.tar.xz
 3aaf7c28acd2bb9f6c04123bd41a1cfeb3745964 4892 unrar-free_0.3.1-1.debian.tar.xz
 cbc22663f12e6ac254eef27f4084fc989c283c8f 7374 
unrar-free_0.3.1-1_source.buildinfo
Checksums-Sha256:
 383056c88c7860a60871d932d03a1259244f197578ef20e6c27abf0a8db669b2 1924 
unrar-free_0.3.1-1.dsc
 d73a24b688287a094d15b45e8c75d503a91bc0f7adfa72eeca592d1d2fa8ab53 17624 
unrar-free_0.3.1.orig.tar.xz
 c0c7c8f8e14dac675483dd2f3e582876edafaa70e1e93b95ca6c11b5ea7ab9c8 4892 
unrar-free_0.3.1-1.debian.tar.xz
 5d78255241ba63129e7bedc78efd86e1580efe46402ff014f9078a2f6a4c6205 7374 
unrar-free_0.3.1-1_source.buildinfo
Files:
 931ce838e6507ed1059ab948e6678bb2 1924 utils optional unrar-free_0.3.1-1.dsc
 41c0aa44412ec3c1fe9f2fc8515ed4fb 17624 utils optional 
unrar-free_0.3.1.orig.tar.xz
 ef90c447cb33d1d41d177d93f05f040a 4892 utils optional 
unrar-free_0.3.1-1.debian.tar.xz
 4af6ae9e28815c4edfb93deda97ce041 7374 utils optional 
unrar-free_0.3.1-1_source.buildinfo

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

iQJHBAEBCgAxFiEEo2h49GQQhoFgDLZIRBc/oT0FiIgFAma1yuwTHHBhdWxsaXVA
ZGViaWFuLm9yZwAKCRBEFz+hPQWIiIrYEACEM+FI3dwPVOG3JKhEYKFnU9lsbfW5
IL6PzR0JEcxKwX3zDjQEzUmmtbYeKieBQAE5ESdpJFD4uwwcoeCB1p0dqA2TjrCT
4cKp+HbOkT3B6QXwlxJhGZNV9O2lbxHhBmV7BV0yHfMZDVfyNgXQLe8s3LHf54FK
ALmrOwxfU/uBl9Jc2stGW5WyxKEnmHSerCECaAKcg9rKL5Y70sgwyXZkYdryGWnn
YQmD09DN83tqt1Eu0smKu3Sx83txfZn081fdcjxJX3Ti3C1eyzCeY1yaerTjiTMm
Sjzc/opZSKPFe/4m8YFxjg8tzAmMmVK0xslCGQ3aqMRUV4Hj5Vqr8py2EMO2jeyi
6yPA7Elrl4w0nfT66ly+sqOOjWHYXjnSfXin3y3yz63wz6s167am415056cKV5tj
WZTklaEQlMudiExq/DDc46Gkb2XYzxdVXDS9b4nXCnsgJiG4SFi3DUVyF/LcPHZC
PlutQL1j28gHv+SuDy0FGvPKyINhyFTDz6H18qLhdzDnuFU2+CkZBdsPL/XmBi6Q
S4aDmXIyQTq4GaEcc2mTHO/DbH/tc1wx09fBGUUuHA8aI1y+k5cKiCJ6GyahlIwp
VqR7SZxnatCrv9U0gz2gofNPe4wGgZdzFZytwfmfk06CA4NzNSxf9gPanNfuRZD/
FZO7i0uoRX+6dg==
=er7J
-----END PGP SIGNATURE-----

Attachment: pgpPv9mc2nzMX.pgp
Description: PGP signature


--- End Message ---

Reply via email to