Your message dated Sun, 21 Oct 2018 19:07:16 +0000
with message-id <e1gej4g-000iba...@fasolo.debian.org>
and subject line Bug#853643: fixed in ripmime 1.4.0.10.debian.1-2
has caused the Debian Bug report #853643,
regarding ripmime: ftbfs with GCC-7
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.)


-- 
853643: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853643
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:ripmime
Version: 1.4.0.10.debian.1-1
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-7

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-7/g++-7, but succeeds to build with gcc-6/g++-6. The
severity of this report may be raised before the buster release.
There is no need to fix this issue in time for the stretch release.

The full build log can be found at:
http://people.debian.org/~doko/logs/gcc7-20170126/ripmime_1.4.0.10.debian.1-1_unstable_gcc7.log
The last lines of the build log are at the end of this report.

To build with GCC 7, either set CC=gcc-7 CXX=g++-7 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-7/porting_to.html

[...]
dpkg-source: info: using source format '3.0 (quilt)'
dpkg-source: info: building ripmime using existing 
./ripmime_1.4.0.10.debian.1.orig.tar.gz
dpkg-source: info: building ripmime in ripmime_1.4.0.10.debian.1-1.debian.tar.xz
dpkg-source: info: building ripmime in ripmime_1.4.0.10.debian.1-1.dsc
 debian/rules build
dh build 
   dh_testdir
   dh_update_autotools_config
   dh_auto_configure
   dh_auto_build
        make -j1
make[1]: Entering directory '/<<PKGBUILDDIR>>'
cc -Wall -g -I. -O2 -Werror -g -O2 -fdebug-prefix-map=/<<PKGBUILDDIR>>=. 
-fstack-protector-strong -Wformat -Werror=format-security -DRIPOLE -c strstack.c
cc -Wall -g -I. -O2 -Werror -g -O2 -fdebug-prefix-map=/<<PKGBUILDDIR>>=. 
-fstack-protector-strong -Wformat -Werror=format-security -DRIPOLE -c mime.c
mime.c: In function 'MIME_decode_encoding':
mime.c:2431:57: error: '%s' directive output may be truncated writing between 0 
and 1022 bytes into a region of size 128 [-Werror=format-truncation=]
     snprintf( hinfo->filename, _MIMEH_FILENAMELEN_MAX, "%s%s%d", 
glb.blankfileprefix_expliticly_set?glb.blankfileprefix:"", filename_prefix, 
glb.filecount );
                                                         ^~
mime.c:2431:56: note: using the range [1, -2147483648] for directive argument
     snprintf( hinfo->filename, _MIMEH_FILENAMELEN_MAX, "%s%s%d", 
glb.blankfileprefix_expliticly_set?glb.blankfileprefix:"", filename_prefix, 
glb.filecount );
                                                        ^~~~~~~~
mime.c:2431:5: note: format output between 2 and 1034 bytes into a destination 
of size 128
     snprintf( hinfo->filename, _MIMEH_FILENAMELEN_MAX, "%s%s%d", 
glb.blankfileprefix_expliticly_set?glb.blankfileprefix:"", filename_prefix, 
glb.filecount );
     
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
mime.c:2436:57: error: '%s' directive output may be truncated writing between 0 
and 1022 bytes into a region of size 128 [-Werror=format-truncation=]
     snprintf( hinfo->filename, _MIMEH_FILENAMELEN_MAX, "%s%d", 
glb.blankfileprefix, glb.filecount );
                                                         ^~     ~~~
mime.c:2436:56: note: using the range [1, -2147483648] for directive argument
     snprintf( hinfo->filename, _MIMEH_FILENAMELEN_MAX, "%s%d", 
glb.blankfileprefix, glb.filecount );
                                                        ^~~~~~
mime.c:2436:5: note: format output between 2 and 1034 bytes into a destination 
of size 128
     snprintf( hinfo->filename, _MIMEH_FILENAMELEN_MAX, "%s%d", 
glb.blankfileprefix, glb.filecount );
     
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
mime.c:2443:56: error: '%s' directive output may be truncated writing between 0 
and 1022 bytes into a region of size 128 [-Werror=format-truncation=]
    snprintf( hinfo->filename, _MIMEH_FILENAMELEN_MAX, "%s%d", 
glb.blankfileprefix, glb.filecount );
                                                        ^~     ~~~
mime.c:2443:55: note: using the range [1, -2147483648] for directive argument
    snprintf( hinfo->filename, _MIMEH_FILENAMELEN_MAX, "%s%d", 
glb.blankfileprefix, glb.filecount );
                                                       ^~~~~~
mime.c:2443:4: note: format output between 2 and 1034 bytes into a destination 
of size 128
    snprintf( hinfo->filename, _MIMEH_FILENAMELEN_MAX, "%s%d", 
glb.blankfileprefix, glb.filecount );
    
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
cc1: all warnings being treated as errors
Makefile:48: recipe for target 'mime.o' failed
make[1]: *** [mime.o] Error 1
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
dh_auto_build: make -j1 returned exit code 2
debian/rules:8: recipe for target 'build' failed
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2

--- End Message ---
--- Begin Message ---
Source: ripmime
Source-Version: 1.4.0.10.debian.1-2

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

Debian distribution maintenance software
pp.
Phil Brooke <p...@debian.org> (supplier of updated ripmime 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: SHA256

Format: 1.8
Date: Sun, 21 Oct 2018 16:05:22 +0100
Source: ripmime
Binary: ripmime
Architecture: source amd64
Version: 1.4.0.10.debian.1-2
Distribution: unstable
Urgency: medium
Maintainer: Phil Brooke <p...@debian.org>
Changed-By: Phil Brooke <p...@debian.org>
Description:
 ripmime    - Extract attachments out of MIME encoded emails
Closes: 767270 812250 853643
Changes:
 ripmime (1.4.0.10.debian.1-2) unstable; urgency=medium
 .
   * Fix typo in description inside control file (closes: #767270).
     Thank you for the report, Green.
   * Fix FTBFS with gcc-7 by applying patch from Juhani Numminen
     (closes: #853643) -- thank you!
   * Fix FTBFS with Clang by applying patch from Arthur Marble
     (closes: #812250) -- thank you!
   * Bump standards-version to 4.2.1.
Checksums-Sha1:
 dfc4051aca0dc58c0f9e96246184d8e2d14fb8e0 1779 ripmime_1.4.0.10.debian.1-2.dsc
 7d9495a48f2a087fa47a7547ad7cffa03af5f6a0 8228 
ripmime_1.4.0.10.debian.1-2.debian.tar.xz
 d3859d9e7e47a690dc68873ce48ac436caf5d8df 114032 
ripmime-dbgsym_1.4.0.10.debian.1-2_amd64.deb
 89ce85e2eb7f6468138fab31a68e1942c4a3ea3d 6027 
ripmime_1.4.0.10.debian.1-2_amd64.buildinfo
 f01017282552faabd0a3d1d75c7523b467d19b18 83636 
ripmime_1.4.0.10.debian.1-2_amd64.deb
Checksums-Sha256:
 a7c84016e6cabed30842c9ace5e98a8e903db13d9883899a355c0f58266e9a6a 1779 
ripmime_1.4.0.10.debian.1-2.dsc
 57adc5a5eb7bf0d4faa2027696a605cd44eab0bd919e1a0618a9713248538050 8228 
ripmime_1.4.0.10.debian.1-2.debian.tar.xz
 2d4a9f1530d0dfad59beaa1fb9f646f9b450e36ec56330ec571f5dcc5fa1f7fd 114032 
ripmime-dbgsym_1.4.0.10.debian.1-2_amd64.deb
 3bf765c3c218922dbb3b9b61b518bd76638a723accb2bfcfe8327a82adfbe88a 6027 
ripmime_1.4.0.10.debian.1-2_amd64.buildinfo
 9368828accd414e54fef332698b9192f35c24279559c2555124132d35881d8bf 83636 
ripmime_1.4.0.10.debian.1-2_amd64.deb
Files:
 f9c4c09f95965a6da8aa8f3e2a2a65ed 1779 mail optional 
ripmime_1.4.0.10.debian.1-2.dsc
 95b2b2359312b1a22a414979edce68a6 8228 mail optional 
ripmime_1.4.0.10.debian.1-2.debian.tar.xz
 b924032c2194673981dc17265ac2529e 114032 debug optional 
ripmime-dbgsym_1.4.0.10.debian.1-2_amd64.deb
 992d7ce453429fa107454f65930cf14c 6027 mail optional 
ripmime_1.4.0.10.debian.1-2_amd64.buildinfo
 e30b4ded238a7437d7fad28f4ad1efa3 83636 mail optional 
ripmime_1.4.0.10.debian.1-2_amd64.deb

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

iQIzBAEBCAAdFiEEKCMADj+pj/jrfBAKgZ0nig5vmSoFAlvMx+4ACgkQgZ0nig5v
mSouIQ/9FgKNwRdzAB7fhOWnTfArFE2jmqn7gTOR2mF2Y+K7wbFNu8uhjEJrS4Qs
53gCTp6c7X6EuwW1MkBusuqHHJfmYiak0oaTFBSrpgqN/KoeqHMyX2DVfSd8GlEj
vVGzkgQau9LLi2QnTj2aaEBXBtqZYrdvh1yJ+84jqm0nNkNYA5d2my2VgzCqFpxr
RcZPwudvOMsS/LqSFTXIdaNiy9u8Tf/NV18kEcvs26ZfQLDA4CGCfll/7nbKhdyK
7uN4XutLvJpfaNMFaK0hmdoMtoH8g0D04zHVy37dqWlgfZnOkaW+0UJcdCzffQsy
PxFWJK05zGZoYXTmm91OkMN5uD7F4RGWJOeXdA8ZaMttvaKdCX+qbQIm8q/gCAcX
lR4kAZppg8j6XrxLxgJvTBAi0VQcQBDCPwMFbf9QYeLl18TR8rDHcvpC4ERFJjBm
ruWwaunY8mGcUImBqA0U4vNyanXCct0SPBO56fkCG1ucxfF3VuD9MH8iMPmL0lz8
ILoSvgV0JKzmj7uHbAWlszW3xAL6rAtE9QKyRcOpTsZM7ln462PZrCLndFm0iz8b
syWSZnFbquG0k6x2+qjxB6VkolLU7b51qOse4m76Sk38oE3ofy+xIsIe7M9K6QrY
Qv53JJoMLYZbInokdgMxjBhSLhD7iy/Kum4D1jIfoGU0mkRnJHE=
=aCmp
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to