Re: Hard Rust requirements from May onward

--00000000000027a29d06428913de
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

:wq

On Sat, Nov 1, 2025, 10:10=E2=80=AFAM Paul Tagliamonte <[email protected]>=
 wrote:

> Thanks for your hard work on this -
>
> This will impact unofficial ports, which have already had to contend with
> Rusts widespread adoption of rust in lieu of C in places like Rust's cryp=
to
> ecosystem
>


Sorry typo on my phone

> contend with rust's widespread adoption in lieu of C in places like
python's crypto ecosystem



> However, it's definitely more of a symptom rather than a cause of port
> bitrot - the impact of rust on ports has a simple solution -- help
> maintaining the port with rust upstream. I would encourage anyone upset b=
y
> this -- frankly -- welcome news to help ensure rust has a stable port on
> your favorite arch.
>
> Paul
>
> :wq
>
> On Fri, Oct 31, 2025, 4:49=E2=80=AFPM Julian Andres Klode <[email protected]=
> wrote:
>
>> Hi all,
>>
>> I plan to introduce hard Rust dependencies and Rust code into
>> APT, no earlier than May 2026. This extends at first to the
>> Rust compiler and standard library, and the Sequoia ecosystem.
>>
>> In particular, our code to parse .deb, .ar, .tar, and the
>> HTTP signature verification code would strongly benefit
>> from memory safe languages and a stronger approach to
>> unit testing.
>>
>> If you maintain a port without a working Rust toolchain,
>> please ensure it has one within the next 6 months, or
>> sunset the port.
>>
>> It's important for the project as whole to be able to
>> move forward and rely on modern tools and technologies
>> and not be held back by trying to shoehorn modern software
>> on retro computing devices.
>>
>> Thank you for your understanding.
>> --
>> debian developer - deb.li/jak | jak-linux.org - free software dev
>> ubuntu core developer                              i speak de, en
>>
>

--00000000000027a29d06428913de
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto"><div><div><br></div><div><br></div><div data-smartmail=3D=
"gmail_signature">:wq</div><br><div class=3D"gmail_quote gmail_quote_contai=
ner"><div dir=3D"ltr" class=3D"gmail_attr">On Sat, Nov 1, 2025, 10:10=E2=80=
=AFAM Paul Tagliamonte &lt;<a href=3D"mailto:[email protected]">paultag@de=
bian.org</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D=
"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D=
"auto"><div>Thanks for your hard work on this -</div><div dir=3D"auto"><br>=
</div><div dir=3D"auto">This will impact unofficial ports, which have alrea=
dy had to contend with Rusts widespread adoption of rust in lieu of C in pl=
aces like Rust&#39;s crypto ecosystem</div></div></blockquote></div></div><=
div dir=3D"auto"><br></div><div dir=3D"auto"><br></div><div dir=3D"auto">So=
rry typo on my phone</div><div dir=3D"auto"><br></div><div dir=3D"auto">&gt=
; contend with rust&#39;s widespread adoption in lieu of C in places like p=
ython&#39;s crypto ecosystem</div><div dir=3D"auto"><br></div><div dir=3D"a=
uto"><br></div><div dir=3D"auto"><div class=3D"gmail_quote gmail_quote_cont=
ainer"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-=
left:1px #ccc solid;padding-left:1ex"><div dir=3D"auto"><div dir=3D"auto"><=
br></div><div dir=3D"auto">However, it&#39;s definitely more of a symptom r=
ather than a cause of port bitrot - the impact of rust on ports has a simpl=
e solution -- help maintaining the port with rust upstream. I would encoura=
ge anyone upset by this -- frankly -- welcome news to help ensure rust has =
a stable port on your favorite arch.=C2=A0</div><div dir=3D"auto"><br></div=
><div dir=3D"auto">Paul</div><div><br></div><div data-smartmail=3D"gmail_si=
gnature">:wq</div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" cla=
ss=3D"gmail_attr">On Fri, Oct 31, 2025, 4:49=E2=80=AFPM Julian Andres Klode=
 &lt;<a href=3D"mailto:[email protected]" target=3D"_blank" rel=3D"noreferrer"=
>[email protected]</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" s=
tyle=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi a=
ll,<br>
<br>
I plan to introduce hard Rust dependencies and Rust code into<br>
APT, no earlier than May 2026. This extends at first to the<br>
Rust compiler and standard library, and the Sequoia ecosystem.<br>
<br>
In particular, our code to parse .deb, .ar, .tar, and the<br>
HTTP signature verification code would strongly benefit<br>
from memory safe languages and a stronger approach to<br>
unit testing.<br>
<br>
If you maintain a port without a working Rust toolchain,<br>
please ensure it has one within the next 6 months, or<br>
sunset the port.<br>
<br>
It&#39;s important for the project as whole to be able to<br>
move forward and rely on modern tools and technologies<br>
and not be held back by trying to shoehorn modern software<br>
on retro computing devices.<br>
<br>
Thank you for your understanding.<br>
-- <br>
debian developer - <a href=3D"http://deb.li/jak" rel=3D"noreferrer noreferr=
er noreferrer" target=3D"_blank">deb.li/jak</a> | <a href=3D"http://jak-lin=
ux.org" rel=3D"noreferrer noreferrer noreferrer" target=3D"_blank">jak-linu=
x.org</a> - free software dev<br>
ubuntu core developer=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 i speak de, en<br>
</blockquote></div>
</blockquote></div></div></div>

--00000000000027a29d06428913de--