Your message dated Sat, 16 Mar 2024 12:21:03 +0000
with message-id <E1rlT27-004gvA-7v@fasolo.debian.org>
and subject line Bug#1065793: fixed in charliecloud 0.37-2
has caused the Debian Bug report #1065793,
regarding charliecloud: FTBFS on arm{el,hf}: ch_fuse.c:68:19: error: initialization of ‘void (*)(struct fuse_req *, fuse_ino_t, uint64_t)’ {aka ‘void (*)(struct fuse_req *, long long unsigned int, long long unsigned int)’} from incompatible pointer type ‘void (*)(struct fuse_req *, fuse_ino_t, long unsigned int)’ {aka ‘void (*)(struct fuse_req *, long long unsigned int, long unsigned int)’} [-Werror=incompatible-pointer-types]
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 owner@bugs.debian.org
immediately.)
--
1065793: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065793
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: charliecloud: FTBFS on arm{el,hf}: ch_fuse.c:68:19: error: initialization of ‘void (*)(struct fuse_req *, fuse_ino_t, uint64_t)’ {aka ‘void (*)(struct fuse_req *, long long unsigned int, long long unsigned int)’} from incompatible pointer type ‘void (*)(struct fuse_req *, fuse_ino_t, long unsigned int)’ {aka ‘void (*)(struct fuse_req *, long long unsigned int, long unsigned int)’} [-Werror=incompatible-pointer-types]
- From: Sebastian Ramacher <sramacher@debian.org>
- Date: Sat, 9 Mar 2024 22:44:19 +0100
- Message-id: <[🔎] ZezYM7C6qQhB7Tb8@ramacher.at>
Source: charliecloud Version: 0.37-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramacher@debian.org https://buildd.debian.org/status/fetch.php?pkg=charliecloud&arch=armhf&ver=0.37-1&stamp=1709893440&raw=0 gcc -DHAVE_CONFIG_H -I. -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -std=c99 -Wall -Werror -I/usr/include/fuse3 -pthread -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -std=c99 -Wall -Werror -I/usr/include/fuse3 -c -o ch_run-ch_fuse.o `test -f 'ch_fuse.c' || echo './'`ch_fuse.c rm -f ch-run-oci rm -f ch-image sed -E 's|%PYTHON_SHEBANG%|/usr/bin/env python3|' < ch-run-oci.py.in > ch-run-oci sed -E 's|%PYTHON_SHEBANG%|/usr/bin/env python3|' < ch-image.py.in > ch-image chmod +rx,-w ch-run-oci # respects umask chmod +rx,-w ch-image # respects umask ch_fuse.c:68:19: error: initialization of ‘void (*)(struct fuse_req *, fuse_ino_t, uint64_t)’ {aka ‘void (*)(struct fuse_req *, long long unsigned int, long long unsigned int)’} from incompatible pointer type ‘void (*)(struct fuse_req *, fuse_ino_t, long unsigned int)’ {aka ‘void (*)(struct fuse_req *, long long unsigned int, long unsigned int)’} [-Werror=incompatible-pointer-types] 68 | .forget = &sqfs_ll_op_forget, | ^ ch_fuse.c:68:19: note: (near initialization for ‘OPS.forget’) cc1: all warnings being treated as errors make[3]: *** [Makefile:625: ch_run-ch_fuse.o] Error 1 Cheers -- Sebastian Ramacher
--- End Message ---
--- Begin Message ---
- To: 1065793-close@bugs.debian.org
- Subject: Bug#1065793: fixed in charliecloud 0.37-2
- From: Debian FTP Masters <ftpmaster@ftp-master.debian.org>
- Date: Sat, 16 Mar 2024 12:21:03 +0000
- Message-id: <E1rlT27-004gvA-7v@fasolo.debian.org>
- Reply-to: Peter Wienemann <fossdev@posteo.de>
Source: charliecloud Source-Version: 0.37-2 Done: Peter Wienemann <fossdev@posteo.de> We believe that the bug you reported is fixed in the latest version of charliecloud, 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 1065793@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Peter Wienemann <fossdev@posteo.de> (supplier of updated charliecloud 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 ftpmaster@ftp-master.debian.org) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Format: 1.8 Date: Sat, 16 Mar 2024 11:47:02 +0100 Source: charliecloud Architecture: source Version: 0.37-2 Distribution: unstable Urgency: medium Maintainer: Debian HPC Team <debian-hpc@lists.debian.org> Changed-By: Peter Wienemann <fossdev@posteo.de> Closes: 1065793 Changes: charliecloud (0.37-2) unstable; urgency=medium . * Add patch from upstream PR 1859 to fix FTBFS issue on arm{el,hf} (Closes: #1065793) Checksums-Sha1: 98e169153c98e4bdec3ca7002d34c1bfe5aea26c 2661 charliecloud_0.37-2.dsc 5230833f4ac4d0ac367ef04a83107f4105c76ca3 14384 charliecloud_0.37-2.debian.tar.xz fd87c3d098a8d018408ac77c62a4b08006ccacd5 10517 charliecloud_0.37-2_amd64.buildinfo Checksums-Sha256: e6a7240f7ba63e5451423ea7e95c2126d305c67249c6ea935e5c91eaf136949e 2661 charliecloud_0.37-2.dsc d3c7d4fb18c24d1f831113631c9eb04dd621925e81cecce38c5cf1402ee5f8db 14384 charliecloud_0.37-2.debian.tar.xz c764017cfdc5285edcb09f64c22e500feee928164d804b5778fa94a3655ca09e 10517 charliecloud_0.37-2_amd64.buildinfo Files: 06d05d87d62cee67bf28154008f8f470 2661 admin optional charliecloud_0.37-2.dsc 9f08fb5792b9f29681becb5db53bcad8 14384 admin optional charliecloud_0.37-2.debian.tar.xz b0c960df4d532c445876f71f55651092 10517 admin optional charliecloud_0.37-2_amd64.buildinfo -----BEGIN PGP SIGNATURE----- iQKTBAEBCgB9FiEEBrYs08CqJ6RHEajlAuXO5wyFLHsFAmX1gZNfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDA2 QjYyQ0QzQzBBQTI3QTQ0NzExQThFNTAyRTVDRUU3MEM4NTJDN0IACgkQAuXO5wyF LHvT6w//SeajaRHMZf4hxKuIZJuFwJG2/RvIPcOSHpAUy+gbQyY8qgKubLaEym3F Vt377LMqE2hX+r/+EuRDbY9O6N51Gq9hgHJO6+e7VN9Yo4Pbmz/vBGKifl028inQ paPktzwGvXSaf3dZPQoVk+3h01U3ZVyBPi1pUCoeEroqx5ZdvlvbZeHkieWA/XVf u0iNrPtaWRxdhacT0cihOMjgojcmuuvCmm82Ll0lr9t1MbcOddVZUNyyko8eJV+E NXxPDGv8C6QHZNtvYftYeQNs8voiVr0yFccu0YRyAInnx91yMExdxnWeVC/qoqtk cM0Javw0dTEIhuqxj1S5bgjc13wjxvISmnqEzSYCxoOB2c/tgIRbGe7kgks/xuhx fwmdYpaj6/vwS4a37dgAC1Y4mrzcGTrJ6Ggj/cU8AiTCTM1/oXFNaT347r+33WL0 toVRgkiG42l3UKO+zP01s8FD/EdQPm2nnTqSVgSchr+idlsKicZRA0mSLufeVErc LKe68p5+O6DY+Nd2lofSzrlNQRXI2ZAinxoSNdKeXJPHJ2sH3HamVywW4hvPXI0Z u+BTPweH6+eRFDln9txegD1cnJSvAPpmd93+xIhlbK8hpNGVpqHO8POOfkLJdFe0 oHKuvZNdsfAfQ6CCoi9PVUNM/6CLnVF8gSLoXLtD2+YsR2XPlRs= =XDNF -----END PGP SIGNATURE-----Attachment: pgphYVgq4VicK.pgp
Description: PGP signature
--- End Message ---