Your message dated Tue, 11 Nov 2025 17:35:46 +0000
with message-id <[email protected]>
and subject line Bug#1120499: fixed in fortran-jonquil 0.3.0-3
has caused the Debian Bug report #1120499,
regarding FTBFS: missing files
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 [email protected]
immediately.)
--
1120499: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1120499
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: fortran-jonquil
Version: 0.3.0-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Hi,
fortran-jonquil fails to build from source:
make[1]: Leaving directory '/build/reproducible-path/fortran-jonquil-0.3.0'
dh_install -a
dh_install: warning: Cannot find (any matches for)
"usr/lib/*/fortran/gfortran/libjonquil.a" (tried in ., debian/tmp)
dh_install: warning: libfortran-jonquil-dev missing files:
usr/lib/*/fortran/gfortran/libjonquil.a
dh_install: error: missing files, aborting
make: *** [debian/rules:7: binary-arch] Error 255
dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit
status 2
-- System Information:
Debian Release: 13.1
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 6.12.48+deb13-amd64 (SMP w/128 CPU threads; PREEMPT)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: fortran-jonquil
Source-Version: 0.3.0-3
Done: Alastair McKinstry <[email protected]>
We believe that the bug you reported is fixed in the latest version of
fortran-jonquil, 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 [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Alastair McKinstry <[email protected]> (supplier of updated fortran-jonquil
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 [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Tue, 11 Nov 2025 13:49:21 +0000
Source: fortran-jonquil
Architecture: source
Version: 0.3.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers
<[email protected]>
Changed-By: Alastair McKinstry <[email protected]>
Closes: 1120499
Changes:
fortran-jonquil (0.3.0-3) unstable; urgency=medium
.
* Changes needed for new dh_fortran_lib. Closes: #1120499
Checksums-Sha1:
69addc87424b4fa19a011e021cf36e621f10299e 2175 fortran-jonquil_0.3.0-3.dsc
097e26cd185dfcfaaeaa5fa1c6f5399b1fa98ff1 3164
fortran-jonquil_0.3.0-3.debian.tar.xz
Checksums-Sha256:
4ff793942149e55ee267e5ec01873b540c898e5929e2c7d5df0aaed91d6e3995 2175
fortran-jonquil_0.3.0-3.dsc
77df5270811a73ef126b614b728617028bb0eec3448c2fdc990f4a010b13ca60 3164
fortran-jonquil_0.3.0-3.debian.tar.xz
Files:
ca32c5b1ed5e8c03f8bf45d0e8537fdf 2175 utils optional
fortran-jonquil_0.3.0-3.dsc
d0d9ba889e824592915cd10173b0bdb3 3164 utils optional
fortran-jonquil_0.3.0-3.debian.tar.xz
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEgjg86RZbNHx4cIGiy+a7Tl2a06UFAmkTbmcACgkQy+a7Tl2a
06XPlRAAnHxfC9Pvll8c7KUa5eZzpEw5OOpDb6rkduQATB72dtUYQNzaviXzut6Q
9skid0xXBmRxRMvKz9oiSRGdGj3S2E99iMQiP+B0bXBMicwBjDoMjPGJO8DrHvww
nymcnFQTqrMygHD1rKQbolgtwWz90QvsUBTXTur4l9sMDg+RZxU5GWFp9bkzBYEl
yC6da2YnfcBLJ3UuqvCE67Ghx/zEL8DXdVjHTXKNdTS0KxpklLfBM6pacRM9Ne8G
fFSFvsSnZ7xHAuX0tmz7vVa067MLZpaN4xdwOTr5BQT50CztFh1o6sS/f7yYS+YD
gy8ty1o89KNxi0KRn+GZav5LUJ1VOInyGrbzWL80EAo6W1LeBGTD0uqpUn8BTH31
XVzdKcvhhWrbooPr+JT4q7ctXPi/NyrSgu0AUyuVBRXoSEfQQrYWGy8YssH+S8wC
DyHLh5f6yMW9vU/ZdGI/ZIhPhlrqy0f487RCg9PEdJsQB5WZT0p6h1+qx26wBjW9
0RC7LxL0yspSzpE2D9wEG9MIGwK086hmqktyKLiJFRPh/2hMaTyVkEblttewz6Fg
f0pKhPh6qsNLBuwyillWy4cOKKx3KkymlGtl52x16+g4sI3KmUrsfgCtJP4AWsCo
1K3G1RlF4NIE3IdPcpkg6Ckx6U7W+9Dz97bovGjT5bYnl8DZ70k=
=0Q0S
-----END PGP SIGNATURE-----
pgpcHiiSwXqZX.pgp
Description: PGP signature
--- End Message ---
