/srv/irclogs.ubuntu.com/2005/06/09/#ubuntu-toolchain.txt

=== doko_ [~doko___@dsl-082-082-199-023.arcor-ip.net] has joined #ubuntu-toolchain
fabbionemorning07:17
lamontelmo: yellow has been behaving, yes07:52
=== \sh [~shermann@server3.servereyes.de] has joined #ubuntu-toolchain
elmodoko_: ?10:18
fabbionehey elmo10:19
doko_morning10:19
doko_elmo: hi10:19
elmodoko: dude, why are we still blacklisting apps?10:20
dokobecause I didn't do my homework yet to reduce the cxxapps list10:20
elmono, I mean, in general10:20
dokonot all libs in universe are already converted10:21
elmoright, but the same question I asked the other day, applys - couldn't we not blacklist stuff and once we've done the transition determine what we need to recompile?10:21
elmoAFAICS, the only thing we'll miss is stuff linking statically with C++, and I'm not sure missing that is worth the pain of managing the c++ apps list on the buildds10:22
=== chmj [~d3vic3@dumbledore.hbd.com] has joined #ubuntu-toolchain
dokohmm, let me reduce the list today for one time, please. for another reason it's a bad time to push all the packages to the buildd's now: uninstallability of xbase-clients will break all kde builds10:24
elmothe blacklist is a BIG BLOODY HAMMER, we shouldn't be using it to avoid random breakage10:25
dokoyes, and a clean reduction seems to be doable and easy10:26
elmoI'm talking in general, I don't think the app blacklist is the right way to handle this10:26
elmoI think we can assume that someone is uploading an app, it's their responsiblity to ensure that everything it's built against is transitioned10:27
elmoI don't mind the sync blacklist, but the buildd blacklist is just PAIN10:27
elmoand this concept is entirely not going to work for Debian, I can tell you that right now10:27
dokoI know, the right way are modified build deps, but we didn't want this at the start. I know that it doesn't work for Debian, but we didn't want to modify the 800 blocked packages. that was the price10:28
elmolamont: dude, why on earth didn't we use NFU?10:40
dokoNFU?10:40
elmonot-for-us10:41
elmothe wanna-build state10:41
elmorather than altering 18 config files on buildds10:41
dokojbailey: have a 32bit libgcj working, but 21 test suite failures, 1 is a bug in the testcase, the others all signal related :(10:58
jbaileydoko: This is amd64?12:47
lamontelmo: IIRC, NFU still gets a should-I-build message, which we told buildd to just answer 'ok'.02:33
lamontOTOH, I could have dep-waited them on 'cxxlibs' or something02:33
lamontand it's only 15 config files (across 6 architectures)02:42
lamontand sed -i does a reasonable job.  At the same time, I was given to expect that we'd be adding/removing the list as a unit (haven't decided if I should reasonably have expected that or not...)02:43
lamonthaving looked, NFU doesn't seem to get a should-build msg, but I seem to remember something annoying with email related to that state, etc.02:45
elmothat's fails02:45
elmonfu is fairly permanent02:45
elmodep-wait would have worked too02:46
lamontelmo: I'll burn some time today and switch the blacklist into a breezy NFU state03:02
lamontor maybe a dep-wait on something bogus03:02
lamontor better yet, if doko does his homework and tells me which version of which package each thing is actually blocked by, then I can use a real depwait....03:02
lamontbut right now, I need to get ready and go to work.03:03
infinityNFU would have worked fantastically for this purpose.03:26
lamontgcc-3.3 ICE in debian.  sigh.04:01
infinityGCC never ICEs, you must be imagining things.04:31
=== lamont__ [~lamont@15.238.6.24] has joined #ubuntu-toolchain
dokojbailey: yes, amd6404:54
jbaileydoko: 'kay.  So I need to get on with getting Tollef's multiarch stuff in and happy, I guess.04:55
jbaileydoko: He mentioned a baz patchset that he thinks needs to be applied.  I haven't looked at it yet.04:56
lamont__doko: so are you going to work through the list of what each cxxapp should d-w on?04:56
infinitylamont__ : If he does, I can implement it.05:08
=== Seveas [~seveas@seveas.demon.nl] has joined #ubuntu-toolchain
dokolamont__, yes, working on it now ...05:37
lamont__infinity: it's just a slew of wanna-build --dep-wait commands, followed by dropping the massive sledge hammer that is @no_auto_build06:12
infinity<nod>06:13
infinityS'what I assumed.06:13
infinityAnd I'm pretty darned fast at doing mass dep-waits. :)06:14
infinitySomeone used to send me complete lists of build-order for gnome uploads on m68k.06:14
lamont__especially when they can be scripted... :-)06:14
infinityWhich was pretty handy.  I wish more maintainers were that nice.06:14
lamont__infinity: of course, if the packages just had correctly versioned build-deps, then it doesn't really matter, modulo download speed06:15
=== lamont__ discovers that he needs to reconfigure the serial port on his laptop, so that the 3rd ide controller is usable
infinityYeah, the gnome team moved from hand-massaging to tighter build-deps.06:15
infinityThough the hand-massaging actually worked better anyway.06:16
infinity(Well, if there was communication, obviously.. Otherwise, it all blew up horribly)06:16
lamont__feh06:16
infinity3rd IDE controller on your laptop?... Dude, where would you even plug in a third IDE drive?06:17
lamont__docking station06:17
infinityThat seems excessive to me.06:17
lamont__ide1 at 0x170-0x177,0x376 on irq 1506:17
lamont__ide2: I/O resource 0x3EE-0x3EE not free.06:17
lamont__ide2: ports already in use, skipping probe06:17
infinityAhh.  Right.  I forgot people still had those.06:17
infinityThat's a werid place to put a serial port.06:18
lamont__the current solution for a desktop for me is a laptop+docking station06:18
infinityweird, too.06:18
lamont__serial is 3f8-3fe, 3e8-3ee06:18
lamont__hrm... maybe that's just the kernel being excessive...06:19
infinityCOM1/COm2 is 2f8-2fe/3f8-3fe, aren't they?06:19
lamont__lspci only shows one IDE interface06:19
infinity(Or reversed from that)06:19
=== lamont__ ponders the meaning of /proc/ide/ide0/mate
infinityStill, 3ee is very not normal to be used by... Anything.06:20
lamont__0170-0177 : ide106:20
lamont__01f0-01f7 : ide006:20
lamont__0376-0376 : ide106:20
lamont__03e8-03ef : serial06:20
lamont__03f6-03f6 : ide006:20
lamont__03f8-03ff : serial06:20
lamont__but yeah.06:20
lamont__and OT anyway06:20
infinitySure, it is. :)06:21
infinity(If that's two ports, reconfigure the first one in the BIOS to 2f8-2fe where it belongs)06:21
infinityAnd now I stop being OT.06:21
\shlamont__: u have the nc6000? it's not the serial, it's the irda port u should fix06:29
\sh3ee comes from this nasty irda chip..the chipset is in the kernel, but on the wrong sir/fir addr..i tried to patch it to work..but no success06:30
lamont__\sh: ah, cool.06:33
\shlamont__: hp bugged06:34
\shlamont__: another thing, u mentioned the portreplicator...06:37
\shlamont__: don't use it, it will kill your laptop at some time...in our company we're using now those nc6000 with portreps...and 3 of them died using it...if it's not connected properly :(06:38
lamont__\sh: when it kills the laptop, I'll make 'em get me a new one....06:39
=== lamont__ is using the multi-bay replicator
lamont__is pretty common in the lab here - doesn't seem to be a big issue for folks06:40
\shlamont__: yeah...this one i have, too..it killed my mainboard and cpu and ram at the same time...for the other 2 it was only the mainboard and cpu06:41
fabbionere06:42
\shlamont__: sometimes the connectors are not fitting correctly and as we found out, it's a common failure of this hw06:42
fabbionelamont__: did you already do the de-wait magic?06:42
infinityfabbione : For the CXX stuff?06:43
fabbioneyeah06:43
infinityNope.06:43
infinitydoko's supposed to be making a list. :)06:44
dokoinfinity: shhtt ...06:46
infinitydoko : You're missing an "i" in there somewhere.06:47
dokonfnty: which one? ;-)06:48
infinityBetween the hh and tt, I'd say. :)06:48
infinity(or, perhaps in place of one of each...)06:48
lamont__infinity: if you want to handle the DC buildd's that'd be cool.  hppa/sparc still need me/fabbione though...06:48
infinitylamont__ : Yup.  I can do the DCs and provide a script for the others, if you guys feel lazy.06:50
dokoinfinity, lamont__: are you allowed to build a package without one build dependency?06:52
fabbioneinfinity: yes :)06:52
fabbionei am lazy to death06:52
infinitydoko : Define "allowed".  I could build it for bootstrap purposes, but not upload it.  It'd have to be rebuilt for uploading.06:53
dokoinfinity: trying to find a way to build zlib without updating ia32-libs two times.07:10
infinitydoko : Just waste the CPU and bandwidth and do it twice?07:11
lamont__infinity: laziness is next to godliness07:13
lamont__doko: dpkg-buildpackage fails if debian/control lists a build-dep that isn't resolved.07:13
dokohmm, ok07:14
lamont__why would building zlib requre building ia32-libs twice?07:14
dokoyou currently cannot build it, because of a broken dependency (missing lib32z1), but you need it for the 32bit libc07:15
doko1) upload old ia32-libs, 2) build zlib, 3) redo the ia32-libs change07:18
infinitySo just do it?... It would have been done in the time you spent talking about it.07:19
dokoahh, yes, that's not m68k speed07:21
infinitydoko : Also, I give up on your java stuff. :)07:22
infinitydoko : E: Package libant1.6-java has no installation candidate07:22
infinity(From ecj-bootstrap)07:22
doko?07:22
infinityOh, feh.  ecj-bootstrap went to main.  Was it supposed to be in universe?07:23
infinity(I assume that libant is in universe)07:23
dokoit is in universe ...07:24
infinityecj-bootstrap appears to be in main.  Did someone re-seed it?07:25
dokowe should really have the java stuff still in main ... that's development work.07:25
infinityAt any rate, until ecj-bootstrap gets seeded back to universe, or libant moves to main, this build will go nowhere.07:25
infinitySo, I suggest you get that fixed. :)07:25
dokojava-gcj-compat was in main, AFAIK, because OOo2 needed it07:25
=== Mithrandir [~tfheen@vawad.err.no] has joined #ubuntu-toolchain
=== infinity decides to go back to bed in an effort to get back on his own timezone.
infinitydoko : If you work out the CXX transition build-dep/dep-wait tree, can you mail it to me, and I'll do the DC buildds when I wake up (in 5 or 6 hours) and forward the script off to lamont and fabbione for the private buildds.07:32
infinitydoko : If you don't get around to it, I'll just bug you about it again tomorrow. :)07:32
dokoinfinity: let's see ;-)07:34
dokolamont__, infinity: are the buildd's running? zlib, ia32-libs08:53
=== rtcm [~jman@217.129.142.72] has joined #ubuntu-toolchain
fabbionelamont__: you around?10:44
fabbionejbailey; ?10:44
lamont__fabbione: yeah10:45
fabbionelamont__: how are you hadling xbse-client fuckups on the buildd?=10:46
lamont__clarify10:46
fabbionei get some FTBFS because xbase-clientes 6.8.2-21 is not installable10:46
fabbioneor better10:46
fabbioneit fails to install10:47
lamont__ah...  generally speaking, I've just been giving back everything that didn't build due to build-deps a couple times, then bitching about it..... (truth be told)10:47
lamont__but in the ideal world, one would determine why it wasn't installable, and then dep-wait on the right thing10:47
fabbioneok about dep-wait..10:48
fabbionei do the same too10:48
fabbionebut right now kde* can't build because xbase-client doesn't install10:48
fabbioneand it's not due to dependencies10:48
fabbionebut because it fails to unpack or something10:49
lamont__gack10:49
jbaileyfabbione: Hey!10:49
jbaileyfabbione: Oh, you replyied to my ping earlier too, hmm.  Lemme dig that up.10:49
fabbionejbailey: i saw you did ping me before...10:49
fabbioneyeah i have only a few minutes...10:49
fabbioneand i need to go away10:49
fabbionei just passed to give a huge kickback on sparc10:49
jbaileylustre patches...10:50
jbaileyApparently their goal is to get everything in kernel.10:50
jbaileySo the person I was talking with thinks that they might be willing to provide recent versions / security fixes and such.10:50
fabbionejbailey: ok.. we need to go in details for that.. can we do it when i wake up in few hours or tomorrow that my wife is away?10:51
jbaileyYup.  Tuesdays and Thursdays are support days for me, anyway.  I've been making about avoiding hacking on them and am trying to be better about it. =)10:51
fabbioneehhehe ok :)10:51
jbaileyg'n =)10:51
fabbionefor me tuesday/thursday are userland days :)10:52
fabbionewed is a mis ;)10:52
fabbionemonday/friday kernel10:52
jbaileyYup, Monday is my mix day.10:52
jbaileyCatch up from the weekend and such.10:52
fabbioneehhe10:52
fabbionei am off than10:52
jbaileyThu/Fri hacking days.10:52
jbaileySee you!10:52
fabbionegood night folks10:52
fabbionecya in few hours10:53
dokolamont, lamont__, infinity: new frozen app list (2nd column): chinstrap:~doko/frozenapps.txt10:59

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!