On Fri, May 2, 2025, at 1:16 PM, Sebastian Ramacher wrote: > Control: tags -1 confirmed > > On 2025-04-24 08:20:50 +0200, Fabian Grünbichler wrote: >> On Thu, Apr 24, 2025 at 07:29:27AM +0200, Fabian Grünbichler wrote: >> > On Thu, Apr 24, 2025, at 2:13 AM, Peter Green wrote: >> > >> >> > >> If preferred, a variant of the proposed changes with a default of "no" >> > >> would >> > >> also be possible >> > > >> > > I think the default (for bin packages) should be not to generate a >> > > multi-arch: >> > > field at all. >> > > >> > > This is behaviorally equivalent to multi-arch: no, but it IMO has >> > > different >> > > implications, it implies "noone has thought about multi-arch for this >> > > package" >> > > rather than "sometime has thought about multi-arch for this package and >> > > rejected it" >> > >> > Thanks for the quick feedback! >> > >> > Helmut Grohne raised a similar objection on IRC, and like I noted in >> > unblock >> > request, that works just as well. Having "no" as default is easiest, having >> > no default (which like you say, is "behaviorally equivalent") means a bit >> > more code changes, but can be supported as well. >> >> debdiff for the "set no value by default" variant attached, rationale >> remains identical to initial report. > > Please go ahead with the version no value per default.
done, and rust-sequoia-sqv pending in git with the switch to foreign as well, as requested in #1103915 what should we do about the other packages which are (mistakenly) marked as 'allowed' in Trixie atm? just fix up those that would get an upload anyway, or do targeted uploads to fix them all? Fabian
