Your message dated Wed, 22 Sep 2021 14:50:42 +0000
with message-id <[email protected]>
and subject line Bug#994670: fixed in libdap 3.20.8-1
has caused the Debian Bug report #994670,
regarding libdap-dev: dap-config broken for foreign architectures
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.)
--
994670: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994670
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: libdap-dev
Version: 3.20.7-7
Severity: important
User: [email protected]
Usertags: ftcbfs
Control: affects -1 + src:gadap
Hi Alastair,
your -7 upload of src:libdap included a tiny change that is entirely
missing from debian/changelog: It replaces /usr/bin/dap-config with a
version written by you that works by deferring to pkg-config. You cite
multiarch as a reason to replace dap-config.
Unfortunately, your change has the reverse effect. While dap-config used
to work in a multiarch setting, with your replacement dap-config
multiarch is broken. That may sound surprising, so let me explain.
With the old dap-config, all the architecture-dependent paths were
embeded in /usr/bin/dap-config, whose path is architecture-independent.
For that reason, you couldn't mark libdap-dev Multi-Arch: same. With
your replacement dap-config, it is the same for all architectures, so
you could mark it Multi-Arch: same. Unfortunately, it also completely
breaks dap-config for foreign architectures. Just why?
Your new dap-config defers to pkg-config. It doesn't tell pkg-config
which architecture you are compiling for though, so pkg-config makes
just uses whatever architecture it was installed as. When that
architecture happens to differ from the libdap-dev architecture, it
fails to find any .pc files. So in effect, whenever you install
libdap-dev for a non-native architecture, it is bricked.
In effect, your change made us go from
You can install libdap-dev for any single architecture, but not two.
to
You can install libdap-dev for as many architectures as you want, but
it'll only work on the native one.
In particular, this completely breaks any cross building that uses
libdap-dev.
I see two major options here:
a) Delete dap-config and go without it. Any dap-config users (e.g.
gadap) need to be converted to using pkg-config.
b) Revert your change and drop Multi-Arch: same from libdap-dev. As bad
as this may sound, it doesn't actually break that many practical use
cases as coinstallability of -dev packages is rarely required.
I recommend option a as a long-term fix and option b as a short-term
fix.
Is it also possible to retain M-A:same and keep dap-config?
Unfortunately, no. dap-config needs to know which architecture it was
called for, but that information is not transferred in the dap-config
call. It has no chance knowing. pkg-config solves this by using
<triplet>-pkg-config. It knows the intended architecture from its own
tool prefix. When doing so, you must replace all those AC_PATH_PROG that
search for dap-config with AC_PATH_TOOL, but really, just go
PKG_CHECK_MODULES and be done.
Helmut
--- End Message ---
--- Begin Message ---
Source: libdap
Source-Version: 3.20.8-1
Done: Alastair McKinstry <[email protected]>
We believe that the bug you reported is fixed in the latest version of
libdap, 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 libdap 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: SHA256
Format: 1.8
Date: Tue, 21 Sep 2021 12:55:59 +0100
Source: libdap
Architecture: source
Version: 3.20.8-1
Distribution: unstable
Urgency: medium
Maintainer: Alastair McKinstry <[email protected]>
Changed-By: Alastair McKinstry <[email protected]>
Closes: 994670
Changes:
libdap (3.20.8-1) unstable; urgency=medium
.
* New upstream release
* Drop dap-config.patch
* No longer ship dap-config. Closes: #994670
Checksums-Sha1:
dd26d7bea42a5961bb8bdb15c4c7ec285517547d 2405 libdap_3.20.8-1.dsc
fed541d17663562b2f87b11b84ae58f327a2e70b 1618856 libdap_3.20.8.orig.tar.xz
cafacd740b40596358d7cea241f0b5cd6d4fdf31 13976 libdap_3.20.8-1.debian.tar.xz
Checksums-Sha256:
ee8682133418bc0189adafd6ccee3d0ff23bf57958790047d8280b40a3241355 2405
libdap_3.20.8-1.dsc
ccc1c8f97963d4e07d3d9b4e69e108daae63ecbcc7ec53e991e4aec023011d14 1618856
libdap_3.20.8.orig.tar.xz
06cda9b717acb642b60d96edb21496e9a3bfd7c118a8de227a6fb22346d32cda 13976
libdap_3.20.8-1.debian.tar.xz
Files:
51b7b9588e0cc88851d74d9c671bd027 2405 utils optional libdap_3.20.8-1.dsc
f26939adfd629dc567cae01cd89f2e98 1618856 utils optional
libdap_3.20.8.orig.tar.xz
e69926e95ec3b11a32766bcbab223fb7 13976 utils optional
libdap_3.20.8-1.debian.tar.xz
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEEgjg86RZbNHx4cIGiy+a7Tl2a06UFAmFLPisACgkQy+a7Tl2a
06WY/A/6AtPd5r5P/Lz11tugI/Y6PZTaHmbgXISm+Ht5xK9tNg35YlIbVmvk1koy
RF3gHHNgoVGBJXpm3H2X7woaTf6115wJrCAjy2o5MKifHuLxKoDlwBIiI7MXcea2
KO94iYa4hTc5AWjHH0KNlXr48r1dNUE+bsr5oO35FaYyJ8dSkOgI8yjBvVpRh/qA
czNxOMfo0JonOSrzbPnxosj6ZbpSHI1HXikpRyEqeeZQUviCLxobU5FErjmr5Mcb
TCt/bjiiIk7k8j/wJk7Q9C0hGWfCVtxX4uUcTB9FbODU2EQb6V9fYok/tl5C+fpg
KPRcLvz7vQ6PQmfxCERTp5Niyo3J6YmwfwJnS293McJb67UqOZsoBJQgMIMvDOIL
zMWw8z1xs3g8hEuomaQag4BqXFGsmIIV6w7mRIjZiAqLekVh7lBsxkAdHjA8k3k3
qj8KFECd7h/KC4mBWs3j/MaByExsZ2YZ1KH7pjSuK8+xJGPlSOBegk5rVILHWBWX
ne1LeWBL5GOFoj9PNrGFFI66qMy4DoRapxnMSx6/mPD/oOvDYv15l/mSkRFKsLzp
hSU6ZbzIgEVTFZY/rmzr1mAv5nxGRotiuYHy5PB66C5ki1I5pyCcgBJgp0E+LWdI
igFdXJTN/MWtMp+HVuvNEMCB/O2t0EzyyOkFpWcV3kkDG/q/pKM=
=P0ZD
-----END PGP SIGNATURE-----
--- End Message ---
