On Mon, Mar 11, 2024 at 09:07:17PM -0500, Steven Robbins wrote: > Peter convincingly argues (details in bug) that manual intervention is needed > for package "cargo":
> On Sun, 10 Mar 2024 00:48:32 +0000 Peter Michael Green <plugw...@debian.org> > wrote: > > This will require manual intervention to resolve, either through > > cross-building or through building manually in a hacked-up build > > environment. > > I've certainly seen mention of rustc on #debian-devel recently, > > so I think the people handling the time_t transition are already > > aware of this. > I'm wondering if the time_t people or the rust people could comment on this? > This build failure has a surprisingly (to me) long chain of casualties. Is > this an easy thing to fix or is going to take weeks? The quickest fix for this based on what we've done in Ubuntu is: - unpack cargo and libstd-rust debs to the root via dpkg-deb -x - use equivs to mock up packages by these names with no dependencies and install those - bootstrap - enjoy -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer https://www.debian.org/ slanga...@ubuntu.com vor...@debian.org
signature.asc
Description: PGP signature
