Your message dated Mon, 22 Apr 2024 09:19:20 +0000
with message-id <e1ryppy-003zwa...@fasolo.debian.org>
and subject line Bug#1069465: fixed in libeatmydata 131-2
has caused the Debian Bug report #1069465,
regarding libeatmydata: 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.)


-- 
1069465: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069465
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libeatmydata
Version: 131-1
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):
> /bin/bash ./libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I.   
> -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time 
> -D_FORTIFY_SOURCE=2   -DBUILDING_LIBEATMYDATA -g -O2 
> -Werror=implicit-function-declaration -ffile-prefix-map=/<<PKGBUILDDIR>>=. 
> -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Werror=format-security -c -o libeatmydata/la-libeatmydata.lo `test -f 
> 'libeatmydata/libeatmydata.c' || echo './'`libeatmydata/libeatmydata.c
> libtool: compile:  gcc -DHAVE_CONFIG_H -I. -D_LARGEFILE_SOURCE 
> -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 
> -DBUILDING_LIBEATMYDATA -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -c 
> libeatmydata/libeatmydata.c  -fPIC -DPIC -o 
> libeatmydata/.libs/la-libeatmydata.o
> In file included from /usr/include/features.h:393,
>                  from /usr/include/arm-linux-gnueabihf/sys/types.h:25,
>                  from libeatmydata/libeatmydata.c:22:
> /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[2]: *** [Makefile:1046: libeatmydata/la-libeatmydata.lo] Error 1


The full build log is available from:
http://qa-logs.debian.net/2024/04/20/libeatmydata_131-1_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: libeatmydata
Source-Version: 131-2
Done: Mattia Rizzolo <mat...@debian.org>

We believe that the bug you reported is fixed in the latest version of
libeatmydata, 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.
Mattia Rizzolo <mat...@debian.org> (supplier of updated libeatmydata 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: Mon, 22 Apr 2024 10:29:08 +0200
Source: libeatmydata
Architecture: source
Version: 131-2
Distribution: unstable
Urgency: medium
Maintainer: Mattia Rizzolo <mat...@debian.org>
Changed-By: Mattia Rizzolo <mat...@debian.org>
Closes: 1069465
Changes:
 libeatmydata (131-2) unstable; urgency=medium
 .
   * Bump Standards-Version, no changes needed.
   * Add patch to fix FTBFS on 32 bits with a t64 env.  Closes: #1069465
Checksums-Sha1:
 0059cd6ef31d493053eb411251613e5770d603b3 2512 libeatmydata_131-2.dsc
 69e350b8d1bac5b2fa636d24e705e914b1c4bfb1 16292 libeatmydata_131-2.debian.tar.xz
 58416273fac16a3b85a65e6ca48835ceb890cbdc 6844 
libeatmydata_131-2_amd64.buildinfo
Checksums-Sha256:
 9aaa429091a5e5cdc877dc041cb8745b5b06cd26c81a7743eeed29fe790f40ce 2512 
libeatmydata_131-2.dsc
 feebec922ff3f3819b7ba0595300bc14574fa05b2decadd5d0f3763304b70da3 16292 
libeatmydata_131-2.debian.tar.xz
 e8e3fb788c4e809e813dbc6bd9b5389a2d542563cb96ead1b89f984b3348f3e9 6844 
libeatmydata_131-2_amd64.buildinfo
Files:
 e368bcafeae15234aa0fd7dd0f548c9d 2512 utils optional libeatmydata_131-2.dsc
 e8e79e772170d4f531e5c2b21b5dfb38 16292 utils optional 
libeatmydata_131-2.debian.tar.xz
 7fea39a94b1a85b963167d6185f859c1 6844 utils optional 
libeatmydata_131-2_amd64.buildinfo

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

iQIzBAEBCgAdFiEEi3hoeGwz5cZMTQpICBa54Yx2K60FAmYmIEMACgkQCBa54Yx2
K62uDA/+LXQvo/INSSEWiX0BOoFJgG0gGqeD+n8qco7rAPNVlfskqr+J8LNkirUu
AIAG+HV/CNOYG3BqV8XFicnPWcx/Kgh+Y1PBjbwW93bWUOgs7/fNn3HOudDyp/hz
E+OswfNdtEFlTcmjTeGEo2CuYb5pBy+EzPRYd/T4YBoizqcGosN4bKsysEQtpwv9
lU2cjn9rHqrrxOHdrl3o6yZWjGEkYEePGN6GtNfTL6QCt0kYJ0jd9IYQPHXBX2VV
9YAJL8f2MKDNDLB2nZYGuFgf5grcJJewteUmf/iLSxXJnz/I7WlBGQuSztRadaPa
hX9qN1ZBwBiTh19XiPDvWXGBLgFue0R52ugMylr7K2XCLZHZF92DisiA4tR+1CYs
yItHuPmEQKRW21YipKn47yHTbaWNP/KEC0Zyn9LkRr+gg/m3VUOry2vPHVe9c1gF
5vtaZRXoSzJ5LwhGzAUKf91Hb1XCb7EPfbBMKAtiUPFhSa0XDqqgOcrk6U8kUMBL
BhO9AZUbOb9v9oqKhQFT8rSajcPG7mrjqWMFCHrlCc/HP3Tl9Dbe2vDe+BUIpfMO
wctZyIeXW91u+gsxsg2GIQ3L8Exd+wzMLYA3nsjUHYBk96Nmt0oBQVQH9Liv78Tn
GNfOhvnuaDgSBtklTIt40JawfwvUc153IjyvuM+zMng1zNpT68U=
=8XKD
-----END PGP SIGNATURE-----

Attachment: pgpMmNMxtJoU6.pgp
Description: PGP signature


--- End Message ---

Reply via email to