Erwan Prioul: > Hi, > I've noticed big progress upstream. I'm able to compile on ppc64el \o/ > What would be the next steps to have it packaged? First, I guess, is to have > a new tag/version upstream, but then? >
Hi Erwan, see https://anonscm.debian.org/cgit/pkg-rust/rust.git/tree/debian/README.Debian#n60 If everything is good, we should be able to just create that orig-dl tarball, then do the rest of the upload as normal. Are you (or anyone else on this list) able to confirm that the following are correct triplets? $ for i in armhf ppc64 ppc64el s390x mips mipsel mips64el; do make -s --no-print-directory -f debian/architecture-test.mk rust-for-deb_$i; done armhf armv7-unknown-linux-gnueabihf ppc64 powerpc64-unknown-linux-gnu ppc64el powerpc64le-unknown-linux-gnu s390x s390x-unknown-linux-gnu mips mips-unknown-linux-gnu mipsel mipsel-unknown-linux-gnu mips64el mips64el-unknown-linux-gnuabi64 If so, we should just be able to run $ upstream_bootstrap_arch="armhf ppc64 ppc64el s390x mips mipsel mips64el" debian/rules source_orig-dl it will create a rustc_1.xx.yy+dfsg1.orig-dl.tar.xz tarball and give you a list of things to manually do. After this, things should "just work" if we include it in the next upload - all the other logic should already be in place, to detect the necessary conditions to use the extra orig-dl tarball. X -- GPG: ed25519/56034877E1F87C35 GPG: rsa4096/1318EFAC5FBBDBCE https://github.com/infinity0/pubkeys.git