Your message dated Sat, 18 May 2024 13:35:29 +0000
with message-id <e1s8kdh-00bkbd...@fasolo.debian.org>
and subject line Bug#1071039: fixed in iptux 0.9.1-2
has caused the Debian Bug report #1071039,
regarding iptux FTBFS on 32bit with 64bit time_t
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.)
--
1071039: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071039
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: iptux
Version: 0.9.1-1
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/logs.php?pkg=iptux&ver=0.9.1-1
...
FAILED: src/iptux-core/libiptux-core.so.0.9.1.p/internal_SendFileData.cpp.o
c++ -Isrc/iptux-core/libiptux-core.so.0.9.1.p -Isrc/iptux-core
-I../src/iptux-core -Isrc -I../src -Isrc/api -I../src/api
-I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include
-I/usr/include/sysprof-6 -I/usr/include/jsoncpp -I/usr/include/sigc++-2.0
-I/usr/lib/arm-linux-gnueabihf/sigc++-2.0/include -fdiagnostics-color=always
-D_GLIBCXX_ASSERTIONS=1 -Wall -Winvalid-pch -Wextra -Wpedantic -std=c++14
-Werror=format -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=.
-fstack-protector-strong -fstack-clash-protection -Wformat
-Werror=format-security -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64
-D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -MD -MQ
src/iptux-core/libiptux-core.so.0.9.1.p/internal_SendFileData.cpp.o -MF
src/iptux-core/libiptux-core.so.0.9.1.p/internal_SendFileData.cpp.o.d -o
src/iptux-core/libiptux-core.so.0.9.1.p/internal_SendFileData.cpp.o -c
../src/iptux-core/internal/SendFileData.cpp
../src/iptux-core/internal/SendFileData.cpp: In member function ‘void
iptux::SendFileData::SendDirFiles()’:
../src/iptux-core/internal/SendFileData.cpp:205:16: error: format ‘%lx’ expects
argument of type ‘long unsigned int’, but argument 8 has type ‘__time64_t’ {aka
‘long long int’} [-Werror=format=]
205 | "0000:%s:%.9" PRIx64 ":%lx:%lx=%lx:%lx=%lx:", dirname,
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../src/iptux-core/internal/SendFileData.cpp:205:16: error: format ‘%lx’ expects
argument of type ‘long unsigned int’, but argument 10 has type ‘__time64_t’
{aka ‘long long int’} [-Werror=format=]
205 | "0000:%s:%.9" PRIx64 ":%lx:%lx=%lx:%lx=%lx:", dirname,
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../src/iptux-core/internal/SendFileData.cpp:243:36: error: format ‘%lx’ expects
argument of type ‘long unsigned int’, but argument 6 has type ‘__time64_t’ {aka
‘long long int’} [-Werror=format=]
243 | "0000:.:0:%lx:%lx=%lx:%lx=%lx:", IPMSG_FILE_RETPARENT,
| ~~^
| |
| long unsigned int
| %llx
../src/iptux-core/internal/SendFileData.cpp:243:44: error: format ‘%lx’ expects
argument of type ‘long unsigned int’, but argument 8 has type ‘__time64_t’ {aka
‘long long int’} [-Werror=format=]
243 | "0000:.:0:%lx:%lx=%lx:%lx=%lx:", IPMSG_FILE_RETPARENT,
| ~~^
| |
| long unsigned int
| %llx
../src/iptux-core/internal/SendFileData.cpp:264:32: warning: cast between
incompatible function types from ‘int (*)(DIR*)’ to ‘GFunc’ {aka ‘void
(*)(void*, void*)’} [-Wcast-function-type]
264 | g_queue_foreach(&dirstack, GFunc(closedir), NULL);
| ^~~~~~~~~~~~~~~
cc1plus: some warnings being treated as errors
...
FAILED: src/iptux-core/libiptux-core.so.0.9.1.p/internal_TcpData.cpp.o
c++ -Isrc/iptux-core/libiptux-core.so.0.9.1.p -Isrc/iptux-core
-I../src/iptux-core -Isrc -I../src -Isrc/api -I../src/api
-I/usr/include/glib-2.0 -I/usr/lib/arm-linux-gnueabihf/glib-2.0/include
-I/usr/include/sysprof-6 -I/usr/include/jsoncpp -I/usr/include/sigc++-2.0
-I/usr/lib/arm-linux-gnueabihf/sigc++-2.0/include -fdiagnostics-color=always
-D_GLIBCXX_ASSERTIONS=1 -Wall -Winvalid-pch -Wextra -Wpedantic -std=c++14
-Werror=format -g -O2 -ffile-prefix-map=/<<PKGBUILDDIR>>=.
-fstack-protector-strong -fstack-clash-protection -Wformat
-Werror=format-security -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64
-D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -MD -MQ
src/iptux-core/libiptux-core.so.0.9.1.p/internal_TcpData.cpp.o -MF
src/iptux-core/libiptux-core.so.0.9.1.p/internal_TcpData.cpp.o.d -o
src/iptux-core/libiptux-core.so.0.9.1.p/internal_TcpData.cpp.o -c
../src/iptux-core/internal/TcpData.cpp
../src/iptux-core/internal/TcpData.cpp: In member function ‘void
iptux::TcpData::RecvSublayer(uint32_t)’:
../src/iptux-core/internal/TcpData.cpp:146:35: error: format ‘%lx’ expects
argument of type ‘long unsigned int’, but argument 7 has type ‘time_t’ {aka
‘long long int’} [-Werror=format=]
146 | snprintf(path, MAX_PATHLEN, "%s" PIC_PATH "/%" PRIx32 "-%" PRIx32
"-%lx",
|
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
147 | g_get_user_cache_dir(), inAddrToUint32(pal->ipv4()),
count++,
148 | time(NULL));
| ~~~~~~~~~~
| |
| time_t {aka long long int}
../src/iptux-core/internal/TcpData.cpp:152:16: error: format ‘%lx’ expects
argument of type ‘long unsigned int’, but argument 7 has type ‘time_t’ {aka
‘long long int’} [-Werror=format=]
152 | "%s" IPTUX_PATH "/%" PRIx32 "-%" PRIx32 "-%lx",
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
153 | g_get_user_cache_dir(), inAddrToUint32(pal->ipv4()),
count++,
154 | time(NULL));
| ~~~~~~~~~~
| |
| time_t {aka long long int}
cc1plus: some warnings being treated as errors
...
--- End Message ---
--- Begin Message ---
Source: iptux
Source-Version: 0.9.1-2
Done: Boyuan Yang <by...@debian.org>
We believe that the bug you reported is fixed in the latest version of
iptux, 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 1071...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Boyuan Yang <by...@debian.org> (supplier of updated iptux 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: Sat, 18 May 2024 09:09:19 -0400
Source: iptux
Architecture: source
Version: 0.9.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Chinese Team <chinese-develop...@lists.alioth.debian.org>
Changed-By: Boyuan Yang <by...@debian.org>
Closes: 1071039
Changes:
iptux (0.9.1-2) unstable; urgency=medium
.
* debian/patches/backport/e048ff79f3fd2738f6d83d780135a3afdf56d0c0.patch:
Apply upstream patch to fix FTBFS on armel and armhf. (Closes: #1071039)
Checksums-Sha1:
9114d26c85034ce587d6061967ce5f26f02453a6 2120 iptux_0.9.1-2.dsc
db9b4adb07f175880df1a25f8f5a95f02f9039d5 680478 iptux_0.9.1.orig.tar.gz
60ed3626dbcdfe751e6c5a53dff0b2017ff24a0f 7444 iptux_0.9.1-2.debian.tar.xz
5304dfc8b96aa4e17eaca993b390ed0cb2b034b4 16892 iptux_0.9.1-2_amd64.buildinfo
Checksums-Sha256:
c4dfc4e44530106ae8f6035d9631d41b4074c2e8e88be156e0c64821579d22da 2120
iptux_0.9.1-2.dsc
51c1fc58070979ffc6eb0af4b6ac26492b82fb230a9cbcc06f21c4eede398ce2 680478
iptux_0.9.1.orig.tar.gz
f4579de04cf211d7dd5ae07a15816dd6355077e22f3619e10d2f059a5322186f 7444
iptux_0.9.1-2.debian.tar.xz
a6671525f7ba407087f376f553c4d9886768576fea5f3a355425eae4ea4884b9 16892
iptux_0.9.1-2_amd64.buildinfo
Files:
d17a4c3cf2fbf51f80b7b2d6a2172686 2120 net optional iptux_0.9.1-2.dsc
895ae377d19c111f2cf0d13f40201b05 680478 net optional iptux_0.9.1.orig.tar.gz
7f13132b202c61ed8f05a43d44377030 7444 net optional iptux_0.9.1-2.debian.tar.xz
bf583a5f418b2488a7ee45e32e9f73cf 16892 net optional
iptux_0.9.1-2_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAmZIqbIACgkQwpPntGGC
Ws6XjQ/9H4mvSp9Ev1V4ysVOiumhwvfJul440jVYOSiuyG7W3HglN/ZkKy41A4qI
9CMglIschozccOrItSK4IZMvxeMoyahrOojf2x/vZc9ADmV8/WfCoFyKDhFGG8cR
0XQpQ2li6dIwqf/tycmrrgILxs5/hR3LTUkHqwPUP/VOjiQ5tZ5L20SvlqnnyN/Q
4auSHSHPi78Xig2VM4CgqVfv4tT93l33vemJhtssIULgKnPZbjGC64PJPYSAKT+d
nMQuqCchUTuYaolUt8MkzEKnVb+El1H911xwFAGRiP94vylcPOTtq3Hy6qC1c1V6
ikhTig9Yh+ImJNJCJVGLqZOC1WIzi8cgApwKLQWuSHVYz6CbmtHHIFhxvqql0buY
JwCHz96W7kvM99O0ajOxmoGgh9Z/dqRz0yA4ZSVl+VVffbupiK7rG9G7R/n9ziOn
UR69gDHUm3Cl+Wg3y4fFWg0gSrKH4ysccxESyxRITN2GqL2vAUT+aVrz42tB/dEw
cehON7Wha6aBAnoAwrmU/0esSgptYt8PzprUSWl7crBplEZNz9KHeFp1aa4qpVyR
nmGB8H7iOifbvv44zrp/Hs7E8HARF2lpGglO+fWYaesDjJ7IZTEu8r/o4H8rQHVB
4R230BwTLECyglxi6YBnxIsEvlrGCfNEuCcDwHKxoxpZ828Erz4=
=3yVD
-----END PGP SIGNATURE-----
pgpp8PiTL9FHr.pgp
Description: PGP signature
--- End Message ---
