Your message dated Sun, 25 May 2025 14:34:15 +0000
with message-id <e1ujcqz-004b6y...@fasolo.debian.org>
and subject line Bug#1069505: fixed in tmperamental 1.6
has caused the Debian Bug report #1069505,
regarding tmperamental: FTBFS on armhf: features-time64.h:26:5: error: #error
"_TIME_BITS=64 is allowed only with _FILE_OFFSET_BITS=64"
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.)
--
1069505: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069505
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: tmperamental
Version: 1.4
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240420 ftbfs-trixie ftbfs-t64-armhf
Hi,
During a rebuild of all packages in sid, your package failed to build
on armhf.
Relevant part (hopefully):
> cc -g -O2 -Werror=implicit-function-declaration
> -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 -Wall
> -fPIC -DPIC -c -o out/tmperamental.o src/tmperamental.c
> sed -e "s,@pkglibdir@,/usr/lib/tmperamental,g" <src/tmperamental.in
> >out/tmperamental
> chmod +x out/tmperamental
> In file included from /usr/include/features.h:393,
> from /usr/include/dlfcn.h:22,
> from src/tmperamental.c:30:
> /usr/include/features-time64.h:26:5: error: #error "_TIME_BITS=64 is allowed
> only with _FILE_OFFSET_BITS=64"
> 26 | # error "_TIME_BITS=64 is allowed only with _FILE_OFFSET_BITS=64"
> | ^~~~~
> make[1]: *** [Makefile:34: out/tmperamental.o] Error 1
The full build log is available from:
http://qa-logs.debian.net/2024/04/20/tmperamental_1.4_unstable-armhf.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240420;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20240420&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: tmperamental
Source-Version: 1.6
Done: Paul Tagliamonte <paul...@debian.org>
We believe that the bug you reported is fixed in the latest version of
tmperamental, 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 1069...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Paul Tagliamonte <paul...@debian.org> (supplier of updated tmperamental 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: Sun, 25 May 2025 10:19:34 -0400
Source: tmperamental
Architecture: source
Version: 1.6
Distribution: unstable
Urgency: medium
Maintainer: Paul Tagliamonte <paul...@debian.org>
Changed-By: Paul Tagliamonte <paul...@debian.org>
Closes: 1069505
Changes:
tmperamental (1.6) unstable; urgency=medium
.
* Ok, ok. Actually solve it this time. I didn't unset _TIME_BITS
in the tests; so this FTBFS agian. This worked this time in an
armhf chroot, let's take another bite of the apple here.
(Closes: #1069505)
Checksums-Sha1:
f28dd602f52c1b09640e86a523823f8e024d15d2 1387 tmperamental_1.6.dsc
ae44b179ea49ee8ce630b6319175d4c6c13266eb 5892 tmperamental_1.6.tar.xz
b7033fd4073c05881ec385c1cc50332a7a6a7b97 5379 tmperamental_1.6_source.buildinfo
Checksums-Sha256:
158823b11a4cb6866d0fdf1c32f567fe9b65ed9de2e2b4f498d4039a4f06c904 1387
tmperamental_1.6.dsc
7193a0e96e1fdbf46b668588f8df7d0e1484d60c1c588e78004414dfbaa1156a 5892
tmperamental_1.6.tar.xz
5bda3461f70cd9c96c6b1d238d9614276c9c2724306870d79983b45da1ea9e9c 5379
tmperamental_1.6_source.buildinfo
Files:
39b7d2354ad18bc13837b4b0fff623f2 1387 misc optional tmperamental_1.6.dsc
87e88d1b12ab01a53c7b0fd95d611424 5892 misc optional tmperamental_1.6.tar.xz
b1f42c612e6073df2e94b5ad80b08a36 5379 misc optional
tmperamental_1.6_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQFHBAEBCgAxFiEE8rctyP6kE7DHa+fOytLPCmgIXzIFAmgzJ0QTHHBhdWx0YWdA
ZGViaWFuLm9yZwAKCRDK0s8KaAhfMoArCACFCiSp1Nl+KsstSsf69tSBYfvbzVZI
xTy0zr3IGNuv3NP+SWTUsz7+I53Z9hllbiNRoeCn9tVb8AJE1ZvvJR3Rux3TiZpo
iVbq+VB/8/onUbJVuoXsyA0YA+I5jb74jJeC9IqYfV+dhhUDrAee+mboSceIL5h+
RdROXFocRJALHSONL+inn0wwD3scb0qZtmPycUCEjTE6OS3LtrMwTqK3F9UugeD/
0g+KJXwwnAMuS5kZXKuFSSufbo9CW20nuc2ARBCyLmvhA0AmT81Q4txC272yJWDO
ibDAYA+uCytL+3aMgVjL7eVdrBlMxsQ/UlyPNuI3hBGr3jg+2mnuPazV
=7UPU
-----END PGP SIGNATURE-----
pgpdtKg5Hsihu.pgp
Description: PGP signature
--- End Message ---
