Your message dated Sat, 12 Sep 2026 21:04:26 +0000
with message-id <[email protected]>
and subject line Bug#1147498: fixed in d-shlibs 0.111
has caused the Debian Bug report #1147498,
regarding d-shlibs: d-devlibdeps fails when gfortran is not installed
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.)


-- 
1147498: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1147498
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: d-shlibs
Version: 0.110
Severity: serious
X-Debbugs-Cc: Andreas Tille <[email protected]>
Control: affects -1 ghmm jellyfish link-grammar

Dear Maintainer,

A recent change to the package (commit c23225c5 [1]) seems to be causing FTBFS 
for gmhh, jellyfish, an link-grammar, at least. These packages invoke 
d-shlibmove in their debian/rules.

I believe that the culprit is this line in the d-devlibdeps script:

    GFORTRAN_DEV=$(command -v gfortran > /dev/null 2>&1 \
        && echo "libgfortran-$(gfortran -dumpversion | cut -d. -f1)-dev")

Although the existence of the gfortran command is asserted (via the "command" 
command), the script runs under "set -e" and the failure in the command 
substitution above appears to cause the entire script to fail silently. I am 
not 100% sure of this diagnosis, because d-shlibs scripts are too convoluted 
for easy debugging.

In any case, the problem disappears when gfortran is installed.

Best,

Rafael Laboissière

[1] 
https://salsa.debian.org/debian/d-shlibs/-/commit/c23225c5eba289587a3f709a30f0b32cefacb28f

--- End Message ---
--- Begin Message ---
Source: d-shlibs
Source-Version: 0.111
Done: Andreas Tille <[email protected]>

We believe that the bug you reported is fixed in the latest version of
d-shlibs, 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.
Andreas Tille <[email protected]> (supplier of updated d-shlibs 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: Sat, 12 Sep 2026 22:33:47 +0200
Source: d-shlibs
Architecture: source
Version: 0.111
Distribution: unstable
Urgency: medium
Maintainer: Jonas Smedegaard <[email protected]>
Changed-By: Andreas Tille <[email protected]>
Closes: 1147498
Changes:
 d-shlibs (0.111) unstable; urgency=medium
 .
   [ Rafael Laboissière ]
   * Avoid failure of d-devlibdeps when gfortran is not installed.
     Closes: #1147498
 .
   [ Andreas Tille ]
   * debhelper-compat (= 14)
Checksums-Sha1:
 9451d000986f76b675cbc70f531774637588c34a 1778 d-shlibs_0.111.dsc
 9ae9634406c8f2842feb097773711101553269af 26120 d-shlibs_0.111.tar.xz
 165b5afcbd97f320a0c16ac6a5d16383b40e3420 5683 d-shlibs_0.111_amd64.buildinfo
Checksums-Sha256:
 3ccde217120f3fdc1e19d0ea6e4e5ed8f4db304ec50ef9b7de77f5de31dc9290 1778 
d-shlibs_0.111.dsc
 413c9a5a8dbaa4a7d025f77991829abbd3d9f9c882d1f1838517142a2b254913 26120 
d-shlibs_0.111.tar.xz
 34ed41242b9480b2c21e3c3eb1a9dc03e36506cf537455a3af784e8a1b2bd515 5683 
d-shlibs_0.111_amd64.buildinfo
Files:
 9c6078bd2b14900dff022b3965b64ebf 1778 utils optional d-shlibs_0.111.dsc
 67e4117aed17b0f94809b6f3c78110bd 26120 utils optional d-shlibs_0.111.tar.xz
 ee0994011d1b046fb0c9c0bdd45083ad 5683 utils optional 
d-shlibs_0.111_amd64.buildinfo

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

iQJFBAEBCgAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmqlt28RHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtFTsA//STx+uEZq5D9KxW3+HWjmYoh2rK5xFYmG
VI0AR0kl2QlxCmAD1g2AEMjHOuHvPUI+fwbDuhD1cLCZple9YKh0zE4v4Ujn+Et7
jSTqlvQ3o/UUVe0mMWy5TgBkQjUJpOQt7MP7FI4ONpc0c2P90yAfWZTkRiMFWcqf
jovQ5jRxEwI3gacyZHQVv36GAaRoKEoTIaU8i/KlBaJGukD08tia+utGk+dtV/wN
QHJbhsvzlY6SlkLRKNpPdPFaLAcRDmZlS+xxeY4PkcR7Zx2OlUtZfhga3J7Lzm1n
ny7R0tkt5hUt5BLfBXBgEk1W+knHchDa0MpIttwUFDG2VIxJL45nUhHekuARRRW1
6Pv3EnODoVrSyC806xwSRFTv5Mv2OKuzRWEbITXypZxjuLY0h+OUjKreEEwFiIhx
puPcek6lWol02S+nk2tnE1w7t4fgG3kRj3PTlmO9KFfUYxYQkC29lXwiWpT0YMdO
eBnjlp4Bt0dHv0y3n7JshaRNBaFPzPY2gKwc1+fuMU7zqYZUfLxfrEs3nNf43cUk
9sFfgOCoOyfk3KPvLbXssR4Yvi16rFLk68V3m6Cq1cK37tzgsaFL/Bi7dEKeWNDx
3ssZten7bCWSVeE66+LVVVDaMB0KlHjI3qSdSwOLLMd7aaQwkCGJBJ1/iHVmhAU4
QlDNrtHdspM=
=EFct
-----END PGP SIGNATURE-----

Attachment: pgppHwE0dViN_.pgp
Description: PGP signature


--- End Message ---

Reply via email to