On June 20, 2026 11:32:22 AM GMT+02:00, Sebastian Andrzej Siewior <[email protected]> wrote: >On 2026-06-20 10:46:02 [+0200], Fabian Grünbichler wrote: >> I can take care of this, but not right away. > >Don't worry, no need to rush. I just try to collect the data and if it >is a low hanging fruit…
It shouldn't be complicated, just lacking time atm. Because of the need to update the binding crates which are vendored it requires an extra upstream component tarball. We did similar transitions/updates in the past, e.g. for libgit2. I will see if a compatible-with-3.x variant is possible and close the bug when its uploaded. >> rustc IMHO has all the the right metadata for >> knowing it is part of libssl transitions, you >> cannot determine this by looking at things >> depending on openssl? rustc has a b-d on >> libs-dev, and the cargo binary package built >> from this source has a dependency on >> libssl3t64.. > >I picked it up recently thinking due to the libssl-dev dependency. But >cargo depends on libssl3t64. Hmmm. If this has been like that in April >where I did the first rebuild then I might need to check my tooling… I haven't double checked, but it should be like that for basically ever (at least since the rustc cargo source package merger, and before that it would have been true for src:cargo instead :)). Fabian
