=== fabbione [i=fabbione@gordian.fabbione.net]  has joined #ubuntu-toolchain
=== chmj [n=chmj@196.44.1.98]  has joined #ubuntu-toolchain
=== doko [n=doko@dslb-088-073-097-177.pools.arcor-ip.net]  has joined #ubuntu-toolchain
[10:30] <doko> infinity, mdz: is edgy already open?
[10:32] <infinity> doko: No.
[10:33] <infinity> doko: Some infrastructure still needs to be verified before it can open, and I'm also planning on hand-holding the new glibc and gcc before I put the buildds into free-for-all mode.
[10:34] <fabbione> infinity: i assume glibc 2.4 ?
[10:36] <infinity> fabbione: yes.
[10:36] <fabbione> infinity: do we have package ready for it?
[10:36] <fabbione> i wouldn't mind to give it a pre-spin on sparc
[10:36] <fabbione> i know gcc-4.1 will break some sparc stuf
[10:36] <infinity> Jeff's still polishing it.  He should be done his tomorrow morning.
[10:36] <fabbione> ok
=== fabbione wonders how much Niagara stuff will break with edgy
[10:39] <infinity> I expect the whole world to break in edgy on every arch, so no big deal.
[10:42] <fabbione> infinity: eheh yea
=== fabbione [i=fabbione@gordian.fabbione.net]  has joined #ubuntu-toolchain
[06:44] <mdz> doko: today is the day
[06:47] <doko> hmm, infinity told that he still needs buildd babysitting 
[06:47] <doko> or should that be builddsitting
[06:54] <doko> infinity: we cannot sync gcc-4.1 and gcj-4.1; sparcv9 patch is missing ...
[09:31] <infinity> doko: Okay, then can you give me a gcc-4.1 and gcj-4.1 on chinstrap somewhere that I can do the chroot bootstrap with as soon as Jeff hands me a final glibc?
[09:32] <doko> infinity: yes, waiting on a final test build
[09:33] <infinity> doko: You rule; thanks.
[11:04] <doko> infinity: chinstrap:~doko/uploads -> gcc-4.1
=== jbailey [n=jbailey@209.217.74.66]  has joined #ubuntu-toolchain
[11:13] <jbailey> Ah, sorry 'bout that.
[11:14] <jbailey> I'm on my laptop so I don't auto-login to all my usual channels.
[11:21] <doko> so maybe it's safer to first build gcc-4.1 and gcj-4.1, then glibc?
[11:21] <doko> I do not want to block edgy for too long
[11:27] <infinity> We're not blocking anything yet.  Don't worry about it.
[11:28] <infinity> Anyhow, I've already got a plan laid out and it should go just fine.
[11:28] <jbailey> sparc did need the same fix, I've added it to my tree.
[11:28] <jbailey> infinity: My biggest weakness right now is that for all but ppc/ppc64 I'm only doing chroot tests for these.
[11:28] <jbailey> And I don't have a sparc.
[11:29] <jbailey> I need to keep my systems pure dapper right now for LSB
[11:29] <infinity> chroot tests are good enough for me.  <shrug>
[11:29] <infinity> We'll find out soon enough if you broke the world anyway.
[11:29] <doko> infinity: gcj-4.1 online as well
[11:29] <jbailey> you know my OCD ;)
[11:30] <infinity> jbailey: It's trivial to run a full GNOME environment from a chroot, if you really want to give it your acid test.
[11:30] <jbailey> How do you get access to X, just bindmount tmp?
[11:30] <infinity> Yeah, bindmount /tmp and don't kill your environment on chroot.
=== jbailey waffles.
[11:31] <infinity> (so, "chroot /chroot su" instead of "su -", or "dchroot -d -c edgy" if using dchroot)
[11:32] <infinity> Alternately, for the full test, kill your X session, chroot into the chroot, then startx from there, so your whole test is ground-up running in the chroot.