Your message dated Tue, 06 May 2025 12:19:47 +0000
with message-id <[email protected]>
and subject line Bug#1103920: fixed in rust-debcargo 2.7.8-4
has caused the Debian Bug report #1103920,
regarding debcargo makes rust packages violate future Debian policy by default
by issuing Multi-Arch: allowed
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.)
--
1103920: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1103920
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: debcargo
Version: 2.7.8-3
Severity: serious
Justification: causes lots of policy violations
X-Debbugs-Cc: [email protected], [email protected]
Hi,
we are writing down policy about Multi-Arch in #749826 and it is close
to completion. A significant aspect there is that the "allowed" value
should be used sparingly, because removing its use later tends to cause
installability issues. It should be the exception, not the norm.
Therefore policy asks uses of allowed to be discussed with
[email protected].
debcargo does the opposite. It issues allowed by default in stark
contrast to what the present policy draft requires. I request that
debcargo drops the issuance of the allowed value. Rust applications tend
to not load dynamic shared libraries and that is the case for which the
allowed value is reserved.
apt-cache show "*" | grep-dctrl -FMulti-Arch allowed -sPackage -n
gives a list of packages carrying "Multi-Arch: allowed". It is about
390. Of those, about 60 are from the Python ecosystem (most of which
with reason). Another 50 are due to binutils (which offers loading
plugins into the linker). Then there are 80 from the erlang/ejabberd
ecosystem where we may have to have a similar discussion. What remains
is 200 packages many of which (I guess more than 100) come from the Rust
ecosystem and many of which should not be M-A:allowed.
Given the huge chilling effects of this default, I think it should be
reverted as soon as possible and for trixie in particular. Individual
crates can override it in control.debcargo.hint to avoid breaking
reverse dependencies.
In many (but not all) cases, the packages should be Multi-Arch: foreign
instead. From a quick glance, sqv should be M-A:foreign.
Helmut
--- End Message ---
--- Begin Message ---
Source: rust-debcargo
Source-Version: 2.7.8-4
Done: Peter Michael Green <[email protected]>
We believe that the bug you reported is fixed in the latest version of
rust-debcargo, 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.
Peter Michael Green <[email protected]> (supplier of updated rust-debcargo
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, 06 May 2025 10:42:52 +0000
Source: rust-debcargo
Architecture: source
Version: 2.7.8-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Rust Maintainers
<[email protected]>
Changed-By: Peter Michael Green <[email protected]>
Closes: 1103920
Changes:
rust-debcargo (2.7.8-4) unstable; urgency=medium
.
* Team upload.
* Package debcargo 2.7.8 from crates.io using debcargo 2.7.8
.
[ Fabian Grünbichler ]
* Package debcargo 2.7.8 from crates.io using debcargo 2.7.8
* Default no M-A value for bin packages (Closes: #1103920)
* Change M-A to no annotation instead of allowed
Checksums-Sha1:
3ff31a79c7bb6afce31657a51071d8a755d744e4 3303 rust-debcargo_2.7.8-4.dsc
7631842c08e96c367988304cca4adaa84c442de1 6972
rust-debcargo_2.7.8-4.debian.tar.xz
78394d0bf36ec2cae5a21d1c384d20ef2d7a579d 8519
rust-debcargo_2.7.8-4_source.buildinfo
Checksums-Sha256:
1666d9af00d694493ea19a2525e9b4f4f043f9d873bb47a455eda028bb2ea992 3303
rust-debcargo_2.7.8-4.dsc
50732cd3127597db1d055f16f9fbd6f83420a8c1542e7c2d9248195852124963 6972
rust-debcargo_2.7.8-4.debian.tar.xz
fde168761e12517f9c5639e82f57be5b69784a184fd04fb1fb819e2141234f27 8519
rust-debcargo_2.7.8-4_source.buildinfo
Files:
af6ff1ffd38d492cf141c228f2554b4c 3303 rust optional rust-debcargo_2.7.8-4.dsc
ca988ef96b8bd84c548c801838d19953 6972 rust optional
rust-debcargo_2.7.8-4.debian.tar.xz
698ba18d0d5ed721f14bf2e4aa48acf1 8519 rust optional
rust-debcargo_2.7.8-4_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQJIBAEBCAAyFiEEU0DQATYMplbjSX63DEjqKnqP/XsFAmgZ+2MUHHBsdWd3YXNo
QGRlYmlhbi5vcmcACgkQDEjqKnqP/XvLuw//cxfe8AxFcv1Z18swDGmzi+lWHVMr
2cBcb5Yy8KOvQSQyzaJBlZrki1el7Z92Y+gwnPBB7Gpa4Yrssdks3vrUKkg/bubZ
GTOWoBRCdrujx3Vol/rxuiZQD9OZTUaDsgne4zpvKDkI/YzJsbRaIGddQKLZwoCy
K77GzSmh6MluIFHGFGl3nnJynL2vlWab+CrO7adwhhaoX+Kf9omlkoOaIMV5OlkH
dMHZD2caL9qagW0T7WYnSsgKgrCm0CFOEXWfjMxv7ljnKsucP4XgxwehLjOFp6zR
eZChyLbvttqo1vQ3IwKD9BSELtwyHFIDJBMyPa5RgwPxpHx108wtrfgjiOEZthyK
bYWFjrnd2XyTPaJNHmSpAKQO1EtbldznH/03duxEHvtEejYwYibhDRpVtqMFaZFF
4oe6HnECz4ado93Ywhydvd1vwOHb1lSowAQdkSFxxwkOoU3fmWTEg5/LR1tJedA4
hIfwQBXmdy5T40jB69gO9hEYxOSbuxGjioafczkMeMslvdKtuOisGgucLfkljEQD
r69P6MNXsNTbQP+ohzAw1OAuOsuGseWmFh/CkYIhO/omRQSxEshN4ZB9saf5x1iN
npKe0z/wBcNxc61YBTL8PN+EsUtIXX5PgIjRCdLP4zIRxfYzep2ahM8oumtg8Uxq
X7uTr9+R16nwUrs=
=EkFT
-----END PGP SIGNATURE-----
pgpPVXtMJqdOo.pgp
Description: PGP signature
--- End Message ---
