[12:18] <doko> infinity: when will the new gcc-defaults available on the buildd's?
[12:32] <infinity> When it's installible?
[12:33] <infinity> (hint: depending on compilers newer than what we have isn't helpful)
[12:37] <doko> infinity: hint: we don't have any mechanism to avoid that
[12:40] <infinity> Sure we do.  Make it build-dep on all the same packages/versions that it will eventually depend on. :)
[12:41] <infinity> Then it'll be FTBFS until they're available.
[12:42] <infinity> (Yes, it's ugly, but it would work)
[12:44] <infinity> Anyhow, the alternate solution is for you to merge gcc-4.0_4.0.2-3. :)
[01:32] <doko> I'm not supposed to merge things, if no merge is needed :-P
[01:32] <doko> infinity: ^^^
[01:37] <infinity> Well, then you better upload a new gcc-defaults_1.29ubuntu1 that drops that compiler dependencies again for now.
[01:37] <infinity> s/that/the/
[01:38] <doko> well, then I do prefer a gcc-4.0_4.0.2-3build1
[01:40] <elmo> err, what?
[01:40] <elmo> for fuck's sake, will you guys chill out
[01:41] <elmo> the sync stuff is running full time, catching up with the backlog, and I'm running around trying to get ready to fly tomorrow
[01:41] <elmo> the world's not going to end if we don't sync a new gcc in the next 24 hours
[01:43] <doko> elmo: no it doesn't end, just that the new gcc-defaults is already built, and gcc depending on gcc-4.0 (>= 4.0.2)
[01:45] <elmo> so nothing's building?
[01:49] <doko> that was the question: what happens, if the buildd's are updated to the new gcc and g++. currently nothing should build which uses gij/gcj/gfortran/gobjc
[02:03] <infinity> The buildds can't be updated, since gcc is uninstallable. :)
[02:04] <infinity> elmo : Anyhow, this has nothing to do with syncs, unless gcc-4.0 is meant to be synced (looks to me like it shold be merged..)
[02:04] <infinity> Oh, unless doko requested a sync-with-overwrite.
[02:06] <infinity> Whatever's going on, you'll get your new GCC when you get it.
[05:47] <lamont-away>   g77: Depends: cpp (>= 4:4.0.2-1) but 4:4.0.1-3 is to be installed
[04:27] <lamont> Oct 26 07:57:11 buildd: Starting build (dist=dapper) of:
[04:27] <lamont> Oct 26 07:57:11 buildd: gcc-3.3_1:3.3.6-10 gcc-3.4_3.4.4-9 gcc-4.0_4.0.2-3 dash_0.5.2-8 nessus-core_2.2.5-2
[04:27] <lamont> cries, even
[04:28] <lamont> gcc-3.3:                04:24:26 (1 entry, sigma 00:00:00)
[04:28] <lamont> gcc-3.4:                11:34:22 (2 entries, sigma 00:44:39)
[04:28] <lamont> gcc-4.0:                06:49:38 (2 entries, sigma 00:49:37)
[04:28] <lamont> not much in the way of hppa uploads for the next 20 hours or so
[05:45] <doko> why does gcc-3.4 takes so long?
[05:46] <doko> lamont: and disable it for gcc-4.1 and gcc-snapshot as well ...
[05:47] <lamont> 3.4 is just lucky or something... could be the expect bug
[05:47] <lamont> s/expect/"expect"/.
[05:47] <lamont> doko: that's true on all architectures, yes?
[05:48] <lamont> well, ok... I don't need or care about mips, but it has the same issue. :-)
[05:59] <lamont> doko: remind me to hurt you if your next gcc-3.3 upload still uses expect instead of expect-tcl8.3 on hppa, k? :-)
[05:59] <doko> lamont: well, it should be on all archs
[05:59] <lamont> ok - I'll change the default gcc-opt config then
[05:59] <doko> lamont: I think I did fix it ...
[06:00] <lamont> expect (>= 5.38.0) [!hurd-i386] , 
[06:00] <lamont> gcc-3.3_1\:3.3.6-10
[06:01] <doko> ahh, no. will do it. the debian expect maintainer seems to be mia
[06:02] <lamont> well, it's not properly an expect bug... iz kernel bug (I think)
[06:02] <lamont> but the name sticks
[07:32] <lamont> doko: I think 3.4's long time may be related to logwatch not exiting
[07:32] <lamont> or maybe that's the "expect bug" again.
[08:02] <lamont> hi elmo