Your message dated Thu, 22 May 2025 17:04:17 +0000
with message-id <e1ui9l7-006woh...@fasolo.debian.org>
and subject line Bug#1105138: fixed in autogen 1:5.18.16-7
has caused the Debian Bug report #1105138,
regarding autogen: loss of Multi-Arch: foreign breaks cross building of
complexity
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.)
--
1105138: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1105138
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: autogen
Version: 1:5.18.16-6
User: debian-cr...@lists.debian.org
Usertags: ftcbfs
Control: affects -1 + src:complexity
X-Debbugs-Cc: debian-cr...@lists.debian.org
Hi Andreas,
the removal of Multi-Arch: foreign breaks cross building complexity.
This is not asking you to just put it back. The reasons for removing it
are sound. This is reporting the failure and looking for better
solutions.
One of the primary reasons for turning dropping M-A:foreign is its .pc
file being located on an arch-dependent path. Fundamentally, that .pc
file should not reside in a package marked Multi-Arch: foreign and one
way to get there indeed is removing Multi-Arch: foreign from the
package.
Another way of looking at this is saying that autogen.pc should not
reside in the autogen binary package. The right place to locate this
file is difficult, because it describes both /usr/bin/autogen as
contained in autogen and libopts.a contained lib libopts25-dev.
Arguably, neither place is fully correct.
While looking at this, I observe that libopts25-dev does not depend on
autogen and therefore discovering libopts.a using pkgconf does not work
reliably by issuing a dependency on libopts25-dev. Mayb autogen.pc
should rather be contained in libopts25-dev?
Let me also provide some wider context. autogen is not the only package
that combines a library with a tool. Other examples include flex
(libfl-dev) and bison (libbison-dev). There are two main ways of
approaching this problem. The way chosen by bison and flex (and vaguely
also autogen) is to have client packages depend on *both* the tool and
the library (though libfl-dev Depends on flex). This tends to be error
prone as it regularly happens that client packages forget to depend on
the library. Not all client packages do use those libraries and there
are a number of users that actually need the tool only, so that extra
dependency actually is beneficial. The other way of approaching this is
turning things around. The main package name (autogen in this case) can
install the library (what now is libopts25-dev) and also depend on the
package containing tool (what now is autogen). The tool package would
become an implementation detail and users should never depend on that
directly and always go via the main package name. As such, installing
autogen would still provide /usr/bin/autogen, but the way it does is by
depending on another package that actually contains it rather than
installing it itself. This latter approach is beneficial if you expect
that all users of the package need the libopts.a library.
I suggest that the restructuring discussed here is inappropriate for
trixie and that it be considered for forky instead. Meanwhile, I agree
that technically speaking M-A:foreign is wrong, but practically speaking
dropping it breaks stuff that used to work, so maybe issuing a subtly
wrong M-A:foreign for trixie is the lesser evil.
Please let me know what you think. I'm happy to work on patches both for
trixie and for forky.
Helmut
--- End Message ---
--- Begin Message ---
Source: autogen
Source-Version: 1:5.18.16-7
Done: Andreas Metzler <ametz...@debian.org>
We believe that the bug you reported is fixed in the latest version of
autogen, 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 1105...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andreas Metzler <ametz...@debian.org> (supplier of updated autogen 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: Thu, 22 May 2025 18:52:45 +0200
Source: autogen
Architecture: source
Version: 1:5.18.16-7
Distribution: unstable
Urgency: medium
Maintainer: Andreas Metzler <ametz...@debian.org>
Changed-By: Andreas Metzler <ametz...@debian.org>
Closes: 1105138
Changes:
autogen (1:5.18.16-7) unstable; urgency=medium
.
* Revert "Stop labeling autogen Multi-Arch: foreign." for trixie.
(Closes: #1105138)
Checksums-Sha1:
39c080bb258606ea3c5bf9fb027bb082e56ee59c 2385 autogen_5.18.16-7.dsc
18399baca5cf0c43020355939ee17f0953966f03 25404 autogen_5.18.16-7.debian.tar.xz
42cac125189dcd00fecf4e765043c5b0919ba462 5405
autogen_5.18.16-7_source.buildinfo
Checksums-Sha256:
16b02963a1b38a13beec593f2e1330e2c431c2621ef8b43924dd1029a20a5783 2385
autogen_5.18.16-7.dsc
f2a1fee251b5f6b967ed1f87b5cd4430c574c69f3eb5e3b90481758be6950915 25404
autogen_5.18.16-7.debian.tar.xz
4c14d293737d49511092bcd7081215c34c6d6d66b744b4451b2ccfdb6ecc4588 5405
autogen_5.18.16-7_source.buildinfo
Files:
d6d9967f60fd57ca50951570578c6191 2385 devel optional autogen_5.18.16-7.dsc
d5fcb0db8696252e5f4db84545285477 25404 devel optional
autogen_5.18.16-7.debian.tar.xz
9f9a7d23d6ab1081326ae50963c7ecc7 5405 devel optional
autogen_5.18.16-7_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEE0uCSA5741Jbt9PpepU8BhUOCFIQFAmgvVsQACgkQpU8BhUOC
FIQtfg//aiGZIe27Z1v0xjm7nt+JYyueSb8hyFw5XYC8rp3lNH9NGh3hd1CA95LN
gErFndKU2amIHJdd79i/nr0T3JeuvgssiVxY5Eeu6yR+8EE1lW1XcjyravlxxJDm
teEPFeqHZYLrrsZHiRjOCFMudw8S10K2TGL3U1KFqbo5mQt7oQxXm22KSLAI0w3V
U5vDwNL/ywn8u84wDbH2DOx6jgXkWWeeuK8z/iXJn689QwhjbCyCuWSpKknL/JS0
OUVbDBNV03ZbaddOHD5rBC/uo32Tt6I93+mch7BRsOl/wHoliAgeqArS5A0dFkDb
egkJmp5ZdcV9TQ/vGxhVYey3iV9iW88GjP2ZpZIHeG18wIRAu+TQICT+tECnKCw4
IntzV0ue3JLteLaJajz/IQz1IF+ZuPPA7s2DWYDCCtftdFz2vU5Itg0PjIWZF3qX
sSTjGnuwy7Taw/1kETQUKCj4qWnwU8Cu/0hJDj0wJ5etYR1FJ+QbHthBVbmcjCD2
8WWtZN9kQqkELMryKlN+Bb1XO38vItmcl4xWWg0Tj7yw6Sbzet7TRVaIionCUsQl
RY314LClAgzscOuteEcmLmB0uxdbnfoFNsrvndJAi4hk+LgbbE/Bz9Hv4GZvSCTr
s9qZjtSMbHoi1l6ReRSFUl4cev2y4DyDG7ZPqWVPMz4IdPpgojs=
=IWGy
-----END PGP SIGNATURE-----
pgpu13t09sOMq.pgp
Description: PGP signature
--- End Message ---
