[Pkg-rust-maintainers] Upstream has changed the bootstrap process

[Ximin Luo]

Angus Lees:
> So long as we can build from both rustc-1.9 and rebuild the resulting
> rustc-1.10 from rustc-1.10 (ie: once rustc-1.9 is replaced in the archive),
> then I agree, there's no reason to delay an upload.
> 
> You have a bunch of make_orig-dl_tarball changes in your commit - are we
> still using a dl tarball at all with this release?
> 

We don't need to, and I was going to upload without it. But I kept the script in there so we have the option to, if we needed to bootstrap again in the future, or if another distro needs to do that. (For example my beta/nightly scripts, see debian/build-preview-dsc.sh, autobuild on Launchpad which doesn't have a rustc).

> Re bootstrap key: yes, that's the one.  Chasing through where
> CFG_BOOTSTRAP_KEY is used in the makefiles, I *think* we can avoid
> modifying stage0.txt by using ./configure --enable-local-rebuild if
> rebuilding with the same version.  If that doesn't work, we may be able to
> just pass CFG_BOOTSTRAP_KEY=e8edd0fd env var to makefiles directly, or
> patch the makefiles until one of those works ;)    That key is the same
> CFG_FILENAME_EXTRA used on libraries, fwiw.  If we want to calculate it
> ourselves, it's: `printf '%s' 1.10.0 | md5sum | cut -c 1-8`
> 

I couldn't find enable-local-rebuild, do you mean enable-local rust? We are already setting that (to pick up the system rust), but it still uses the bootstrap key from src/stage0.txt. Arguably this is an upstream bug, so perhaps instead of editing debian/rules to patch src/stage0.txt, I will patch the upstream Makefiles to read the bootstrap key directly from enable-local-rust if that is set.

X

-- 
GPG: ed25519/56034877E1F87C35
GPG: rsa4096/1318EFAC5FBBDBCE
https://github.com/infinity0/pubkeys.git