[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#1036884: transition: time64_t



On Tue, Mar 12, 2024 at 05:55:59PM +0100, Emanuele Rocca wrote:
> [ debian-rust added to CC ]
> 
> Hi,
> 
> On 2024-03-12 11:03, Simon McVittie wrote:
> > In the medium term, cargo needs re-bootstrapping on the affected
> > architectures (armel and armhf, plus a bunch of -ports architectures
> > where as far as I can see cargo was never available in the past) -
> > that's #1065787, and Steve already replied to that bug describing how
> > Ubuntu did this.
> 
> I don't think Ubuntu actually fixed cargo yet, at least if the data in
> UDD is reliable -- and if I'm looking in the right place. :-)
>
> udd=> select source,version,date from ubuntu_upload_history where source='cargo' order by date desc limit 2;
>  source |                  version                   |          date          
> --------+--------------------------------------------+------------------------
>  cargo  | 0.67.1+ds0ubuntu0.libgit2-0ubuntu0.20.04.2 | 2023-07-05 09:36:28+00
>  cargo  | 0.67.1+ds0ubuntu0.libgit2-0ubuntu0.22.04.2 | 2023-07-05 09:36:27+00
> (2 rows)
> 
> Maybe when Steve mentioned the work done in Ubuntu on
> https://bugs.debian.org/1065787#22 he meant other packages?

possibly the "Ubuntu did this" was referring to post-cargo/rustc-merge?

we've planned that as well, and it's about 75% prepared, but I didn't
manage to finish in Debian in time for t64 to kick off so I held off
finalizing it until the dust settles. in hindsight, that might have been
a mistake - src:rustc (the target of the source package merge) comes
with builtin (re)bootstrap support from upstream statically linked
stage0 ;)

> > Is there a porter who can take responsibility for that?
> 
> I did manage to get cargo to build in a armhf chroot by manually
> installing the various deps, see the build artifacts at
> https://people.debian.org/~ema/cargo/. I can work on armel next. The
> tests are green but maybe there's some more meaningful validation we can
> do before uploading? Anyone from debian-rust has ideas or comments?

if the tests are green, you could try a rebuild of rustc and/or cargo
with the built cargo next? I don't think anything else that is packaged
exercises anywhere near that amount of the functionality of cargo ;)

thanks for taking care of this! don't hesitate to holler here or in
#debian-rust/dev/release (ping me for the latter two, I don't read the
full backlog there).

Fabian


Reply to: