Bug#1105027: Document that Rust packages require SSE2 on i386

Simon McVittie <[email protected]>
Newsgroups gmane.linux.debian.devel.documentation
Message-ID <aFKR_AhhF2Pt4KTS__6284.17942659638$1750241975$gmane$org@remnant.pseudorandom.co.uk>
Control: forwarded -1 https://salsa.debian.org/ddp-team/release-notes/-/merge_requests/261
Control: tags -1 + patch

On Sat, 10 May 2025 at 11:56:46 +0200, Ansgar 🙀 wrote:
>On Sat, 10 May 2025 08:51:15 +0000 Holger Levsen wrote:
>> I'm reassigning this to release-notes as this needs to be documented
>> for the trixie release. Leaving some context too, but please read the full
>> bug.
>
>As I mentioned on #-release:
>
>I think we should just document that the baseline on i386 now requires
>SSE2 instead of limiting the statement to selected packages. If apt
>requires SSE2 indirectly, it doesn't matter to most users that
>technically it is only sqv.

For what it's worth, I agree.

Even if there was a supportable way to make apt on i386 use some 
gpgv-based signature verification in preference to sqv, if our official 
documentation slightly over-states the requirement, it will make the 
message clearer to the non-experts who need to see this in the 
documentation; similar to the way we make sure to say that skipping a 
release is unsupported, even though a Debian expert can often make it 
work (at their own risk, and perhaps not in the case of trixie).

I've proposed 
https://salsa.debian.org/ddp-team/release-notes/-/merge_requests/261 to 
explicitly call out a semi-modern CPU as being required for i386's 
remaining use-cases.

On Sat, 10 May 2025 at 12:17:21 +0200, Paul Gevers wrote:
>i386 is not supported for upgrades. i386 is only supported to be used 
>as multi-arch or in a i386 chroot (on otherwise more powerful 
>hardware).
>
>See https://salsa.debian.org/ddp-team/release-notes/-/merge_requests/171

(which was subsequently merged, and my MR adds to it)

     smcv
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.