Your message dated Sat, 12 Oct 2024 13:05:20 +0000
with message-id <e1szbo8-00avrj...@fasolo.debian.org>
and subject line Bug#1077390: fixed in fort77 1.15-13
has caused the Debian Bug report #1077390,
regarding fort77: FTBFS: configure: error: installation or configuration
problem: C compiler cannot create executables.
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.)
--
1077390: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1077390
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: fort77
Version: 1.15-12
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240728 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules build
> ./configure --prefix=/usr
> creating cache ./config.cache
> checking for gcc... gcc
> checking whether the C compiler (gcc ) works... no
> configure: error: installation or configuration problem: C compiler cannot
> create executables.
The full build log is available from:
http://qa-logs.debian.net/2024/07/28/fort77_1.15-12_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240728;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20240728&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: fort77
Source-Version: 1.15-13
Done: Mark Brown <broo...@debian.org>
We believe that the bug you reported is fixed in the latest version of
fort77, 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 1077...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Mark Brown <broo...@debian.org> (supplier of updated fort77 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, 12 Oct 2024 13:41:48 +0100
Source: fort77
Architecture: source
Version: 1.15-13
Distribution: unstable
Urgency: low
Maintainer: Mark Brown <broo...@debian.org>
Changed-By: Mark Brown <broo...@debian.org>
Closes: 1077390
Changes:
fort77 (1.15-13) unstable; urgency=low
.
* Clean up GCC breakage by rerunning autotools (closes: #1077390)
Checksums-Sha1:
88b862c3490cee24266fdb2dfad553207e76dcf1 1305 fort77_1.15-13.dsc
36639780c92be3ee3dd946c0cc184812ca0e0b05 4628 fort77_1.15-13.diff.gz
Checksums-Sha256:
5e0a007d61b7252ac93d9b9bcc68207dd771926e331efad638b721563f6f62de 1305
fort77_1.15-13.dsc
46f1b239458ee66910282c79c72caf02f368cb2e07896daf8d8bebe44f8d4bc1 4628
fort77_1.15-13.diff.gz
Files:
4f2897ccc758d81875c84efea2ebe47d 1305 devel optional fort77_1.15-13.dsc
9cacb87dfd5ba2dbd7273fb095924028 4628 devel optional fort77_1.15-13.diff.gz
-----BEGIN PGP SIGNATURE-----
iQFHBAEBCgAxFiEEreZoqmdXGLWf4p/qJNaLcl1Uh9AFAmcKcCUTHGJyb29uaWVA
ZGViaWFuLm9yZwAKCRAk1otyXVSH0OZ4CACGzQeqYGmnsujcl1frqxMTanyfPP0X
TNN43zFwSfbfavZrgqYodbK40PmYDTl5xv+lKRtUXZAvSBF7R+BbS/D+bJs4zWr1
idxLJFweuCc5H8IL2avcZu7QZLE60vkMI6nBcplkgPKTaRCQ6f+TCnHcDWbusoxS
U1YrzyRYtEtlCmdvtzaKFNqfEMGE6lw9lXsAxvPK1FQ/D1crcU2NpZLdCQPQUt3r
9kkNFa0U/HTDOhG/lX4yF12OsqU8yVOz8awgWbDB+C413scYPU3ehp2p6nJ/BFu/
JaTRXLJGBdOKN9AYco5nVDyi9JRFCihmXBSP5+MvrzAcit94bF+Sns2k
=us31
-----END PGP SIGNATURE-----
pgpkWiV605OVd.pgp
Description: PGP signature
--- End Message ---
