[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1103995: marked as done (unblock: rust-debcargo/2.7.8-4)

Your message dated Thu, 08 May 2025 20:22:20 +0000
with message-id <E1uD7l6-00D25E-0x@respighi.debian.org>
and subject line unblock rust-debcargo
has caused the Debian Bug report #1103995,
regarding unblock: rust-debcargo/2.7.8-4
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 owner@bugs.debian.org
immediately.)


-- 
1103995: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1103995
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
Severity: normal
X-Debbugs-Cc: rust-debcargo@packages.debian.org, debian-rust@lists.debian.org, debian@fabian.gruenbichler.email
Control: affects -1 + src:rust-debcargo
User: release.debian.org@packages.debian.org
Usertags: unblock

Please unblock package rust-debcargo

[ Reason ]
until the version desired to be unblocked, debcargo defaulted to generating
packages shipping executables ("bin" packages in debcargo's terminology)
annoted with Multi-Arch:allowed. The patches included in this unblock request
change this default to "foreign", with the option of overriding it via
debcargo.toml.

[ Impact ]
debcargo-generated packages that want to get rid of their 'allowed' annotation
would need to fully override the generated debian/control, making maintenance
more cumbersome and mistakes going forward more likely.

in particular, sqv has https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1103915
filed against it which should be sorted out for Trixie, and this targeted
debcargo update would make this very straight-forward.

[ Tests ]
the usual debcargo tests run fine with this change (the patch adapt the test
case output for the generated d/control). I manually tested both "no" and
"same" and the new default using rust-sequoia-sqv/sqv

[ Risks ]
none of the packages currently maintained by the Rust team (see attached list)
with Multi-Arch:allowed have any reverse-depends annotated with :any, so
switching those to foreign should be fine.

[ Checklist ]
  [x] all changes are documented in the d/changelog
  [x] I reviewed all changes and I approve them
  [x] attach debdiff against the package in testing

[ Other info ]
In case the decargo update is unblocked, please also indicate whether you want
a mass-upload of affected packages with the new default (to get rid of about
1/3 of :allowed Packages in Trixie!), or whether such changes should be
evaluated on a case-by-case base and only packages that either have a good
reason like sqv, or would be uploaded anyway, should be changed.

If preferred, a variant of the proposed changes with a default of "no" would
also be possible (and would still allow sqv to easily switch to "foreign")..

unblock rust-debcargo/2.7.8-4

Attachment: debdiff
Description: Binary data

Attachment: source-packages
Description: Binary data


--- End Message ---
--- Begin Message --- 
Unblocked.

--- End Message ---
Reply to: