<div dir="ltr">Oh, I see it wasn't at all understood - sorry, I thought when the build profiles stuff was merged onto master that it was moving ahead with the understanding and agreement of the rest of pkg-rust-maintainers :(<br><div><br></div><div>I wrote the README.source text in a sort of future tense, assuming the reader was reading it at a time when rust-1.0 was released, and rustc was in the Debian archive - you can see things like "apt-get source rustc". I was assuming that the uploader had a better idea of the where we were in the rapidly evolving process up to that point, but that obviously failed as soon as the uploader wasn't me :/</div><div><br></div><div>Yes, revert it to whatever state you're comfortable with, and we can always reattempt the build-profile approach _after_ rustc can build itself :/</div></div><br><div class="gmail_quote">On Mon, 9 Mar 2015 at 00:15 Luca Bruno <<a href="mailto:lucab@debian.org">lucab@debian.org</a>> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Sun, 8 Mar 2015 at 22:56 Sylvestre Ledru <<a href="mailto:sylvestre@debian.org" target="_blank">sylvestre@debian.org</a>> wrote:<br>
<br>
> OK. I tried to upload it but I could not bootstrap rustc using the<br>
> dlstage0 package.<br>
><br>
> I reported this issue:<br>
> <a href="https://github.com/rust-lang/rust/issues/23177" target="_blank">https://github.com/rust-lang/<u></u>rust/issues/23177</a><br>
<br>
I think we should communicate a bit better and refrain from opening bugs as<br>
soon as something goes wrong, as this is probably the fourth time we file a<br>
bug for "rustc can't bootstrap itself" and upstream will soon start hating us<br>
:)<br>
<br>
On Sunday 08 March 2015 12:24:04 Angus Lees wrote:<br>
<br>
> As Steve replied, no version of rustc can compile itself yet.<br>
><br>
> Sorry if this is a surprise to people, I've attempted to explain the<br>
> process in several different places but it's awkward to capture how it will<br>
> need to evolve as we go out-of-tree -> in-debian -> rust-1.0.<br>
<br>
This currently means that our packaging efforts are going backward.<br>
I mean, I already spent time documenting in README.source why (in general)<br>
bootstrapping from the same version doesn't work, but *may* once rust1 is<br>
stable. In order to overcome this, we were using a multi-tarball orig.tar.gz<br>
embedding a stage0 and explaining why.<br>
<br>
If you write in the doc...<br>
'This produces the full rust compiler built using your now obsolete<br>
"dlstage0" rustc compiler.'<br>
...I assume you tried and it works now. Which reflects directly into what we<br>
use as orig.tar.gz, which also means we rewrite doc in order to explain ftp-<br>
masters what we do.<br>
<br>
> We're going to need to manually build binary packages (no buildds) until<br>
> presumably in the betas somwhere when rustc stops adding breaking changes.<br>
<br>
I think this wasn't really clear or agreed upon (at least speaking for<br>
myself). You are basically trading off the embedded stage0 with the ability to<br>
build "beta" release channel on Debian infrastructure.<br>
<br>
Ciao, Luca<br>
<br>
--<br>
.''`. ** Debian GNU/Linux ** | Luca Bruno (kaeso)<br>
: :' : The Universal O.S. | lucab (AT) <a href="http://debian.org" target="_blank">debian.org</a><br>
`. `'` | GPG Key ID: 0x4F3BBEBF<br>
`- <a href="http://www.debian.org" target="_blank">http://www.debian.org</a> | Debian GNU/Linux Developer<br>
______________________________<u></u>_________________<br>
Pkg-rust-maintainers mailing list<br>
<a href="mailto:Pkg-rust-maintainers@lists.alioth.debian.org" target="_blank">Pkg-rust-maintainers@lists.<u></u>alioth.debian.org</a><br>
<a href="https://lists.alioth.debian.org/mailman/listinfo/pkg-rust-maintainers" target="_blank">https://lists.alioth.debian.<u></u>org/mailman/listinfo/pkg-rust-<u></u>maintainers</a><br>
</blockquote></div>