=== d33p__ is now known as luisbg === LongPointyPony is now known as LongPointyStick === LongPointyStick is now known as GoldenPony === `23meg is now known as mgunes === huahua is now known as Lige === Lige is now known as lige [04:10] cjwatson: yea know about the issue wrt OOo been working on it along with several other fixes for several days now [04:10] cjwatson: last bit left is to determine what feisty did for broffice splash and fix up gutsy's and then upload [04:11] * calc was off today for national holiday [04:12] cjwatson: did you get my email last night about the openoffice.org-cd-reduction blueprint? [04:13] cjwatson: i was unable to post it since launchpad was down for a prolonged (longer than specified) outage which extended until very late local time === GoldenPony is now known as Hobbsee [04:15] * Hobbsee curses at hardy's borkenness [04:15] Hobbsee: whats broken for you? [04:15] calc: my X keeps freezing [04:16] Hobbsee: threaten it with the DOOM stick [04:16] * Hobbsee wonders what this laptop is even running [04:17] Hobbsee: oh :( [04:17] edgy, it appears [04:17] and if it doesnt blow up, i'll be in luck [04:19] Hobbsee: rofl [04:19] lifeless: i almost renamed this machine to OnFire for a reason! [04:20] because it plays Frets? [04:21] no... [04:23] lifeless: i've had this thing up to 89C before [04:23] Hobbsee: miaow! [04:23] nice [04:23] only 89? [04:24] I suppose, it is a laptop [04:24] Hobbsee: that would probably kill a Core 2 [04:24] Hm. When does the autosync run again? I'd like git-core to be installable again :) [04:24] highest I've seen on one of my systems was 93 [04:24] that box is now dead, of course :) [04:24] and update-manager autofreezes. yay [04:24] * RAOF 's GPU hits 95 under load. [04:24] my laptop keep shutting off a ~ 90C [04:25] *kept [04:25] I've not seen how hot this machine gets [04:25] LaserJock: Tell it to push through the pain barrier! [04:25] RAOF: I cracked it open and cleaned out the fan an put on fresh thermal paste [04:25] now it's running 40-50C [04:25] it feels like beer o'clock [04:26] that reminds me of our wonder uni Apple support [04:26] my labmate had an iMac that was constantly overheating and shutting down [04:26] and she'd have to leave it of for a couple hours [04:26] she called the help desk people and had the support guy come over [04:27] i think i'll upgrade X, and see what happens [04:27] and he said "huh, why don't you just put a fan behind it?" [04:27] so she ran it with a fan blowing on the back of it until it got fried in a power outage [04:27] the highest i've seen a cpu was in a desktop and that was in the 80s [04:28] was the regular operating temperature for the chip though [04:28] Heh. That'd be one of the pentium 4s, right? [04:28] geeze [04:28] an athlon 1200 (iirc) [04:28] my desktop procs don't get above 50C [04:28] sounds about right [04:28] somewhere around 185F [04:28] my one that got to 93C was an athlon xp [04:28] calc: did you check the thermal grease/tape? [04:29] it still did that temp even with a lapped heatsink and good thermal compound [04:29] it was on my dad's pc so i checked it out and apparently it was within specs [04:29] my athlon XP 1800+ dropped ~20C avg temp after I redid the thermal compound [04:29] iirc the top temp it was rated for was ~ 95C [04:30] it wasn't an XP it was original athlon (chip based not slot) [04:30] my XP was much lower temps [04:30] iirc the max my XP got to was around 60C [04:30] ah [04:30] that sounds like mine [04:30] but that was many years ago so i am not certain about its exact load temp [04:31] * calc wants a core octo ;) [04:31] build OOo faster! [04:31] my athlon XP is my fastest machine still [04:31] calc: what, in only 18 hours? [04:31] calc: Then buy an 8-core Niagra [04:31] i have a core 2 duo 2.8GHz [04:32] isn't niagra a bunch of low end cores? [04:32] in any case sun hardware is way to expensive [04:33] calc: Eight 1.4GHz SPARCv9 cores [04:33] * calc wishes wine could run Adobe CS 3 already [04:34] ah, i thought they were crippled in some way to achieve that, maybe i am misremembering [04:35] sigh. X broke. [04:36] LaserJock: You need an amd64 [04:37] StevenK: I do [04:37] I just got a "new" machine [04:37] a 1.7GHz P4 [04:37] LaserJock: And we need ponies [04:37] yep, working on it [04:38] ah well, at least my computing situation isn't as bad as imbrandon [04:40] i'm going to try to hold out on upgrading until dec 2009 [04:41] of course i love new machines so that will be hard, heh [04:41] I should be graduating this spring [04:41] Why until then? [04:41] StevenK: 3 years since my last new machine [04:41] and my reward is going to be a new laptop [04:41] hard drives and ram increases are so pathetic for the past 5 years that it probably won't even be worthwhile until then anyway [04:42] cpu are getting faster but not that much either [04:42] i bought a 2gb hard drive in spring 1996 and 100gb drive in oct 2001 [04:42] I'm just getting a bit behind with everything [04:43] and the largest available hard drive is still only 1TB now [04:43] it appears that gnome-control-center needs a rebuild. [04:43] it should be up to like 100TB by now [04:44] calc: I'd say we are starting to hit the upper limits of current technologies. [04:44] no, a merge [04:44] TheMuso: yea way past the limit, heh [04:44] calc: There's also a price factor: 1TB today isn't very expensive. [04:44] from 5MB ~ 1985 to 100GB in 2001 to 1TB in 2006 [04:45] persia: it costs more than 100GB in 2001 [04:46] calc: I'll trust you: I haven't purchased a TB storage device since 1997, but it was expensive then. [04:46] 1TB in 1997 would probably have been in the 150K range (i would guess) [04:46] er $150K USD [04:47] hmm, I could by a new laser for that [04:47] calc: We paid about 200k USD, but that included the routing HW, Digital support, etc. [04:47] i helped install a large 2 rack 250GB (max) worm drive system back around 1994 [04:47] i bet that cost a large sum of money back then [04:48] 2 racks? Anything with 2 racks is still expensive :) [04:48] looks like 1TB drive still costs ~ $280 USD now [04:48] persia: yea they were 12" WORM discs iirc [04:49] * persia is amused that 1TB drives are currently cheaper than 10GB drives, which frequently sell for > 100,000 yen [04:57] why would anyone buy a 10GB drive, is anyone even still making them? [04:58] IMO small drives still have their uses. Pitty they aren't as fast as the drives of today however. [05:01] calc: People seem to like them for vast farms of SparcStation 2s. These are common in factory automation environments, etc. [05:01] well if they were manufactured long ago they are more likely to fail... so just buy the smallest modern drive, 100gb or whatever [05:03] calc: Not supported by ancient Solaris. [05:04] ancient solaris isn't supported either... is it? [05:05] Interesting issue: xchat2 icon in the notification panel has just zoomed it's icon about 500% so all I can see is the top half of the X, and it is about 3x normal width... what'd cause that? [05:05] calc: Not by Sun, but turnkey vendors support it for the turnkey systems, as it's cheaper than porting to keep up, when one can just release a new turnkey, and migrate customers after the 8-10 year depreciation has finished. [05:05] ah [05:08] * Hobbsee ponders if it's worth attempting to fixthis today [05:11] aww, crap [05:11] what am i supposed to do if ia have no more gnome-screensaver, and the machine has gone into powersave? [05:13] ah, shut it down remotely. got it. === Hobbsee is now known as GoldenPony === LaserJock is now known as LaserRock === Hobbsee_ is now known as Hobbsee [06:26] Good morning [06:26] morning pitti! [06:27] hey Hobbsee [06:27] hi thegodfather [06:27] thegodfather: why are you titled as such, today? [06:27] Hobbsee: new nick [06:27] well, obviously, but why? [06:28] you are gonna have to guess that :) [06:29] :P [06:40] thegodfather: because you're now a godfather? [06:40] slangasek: i was before as well :) [06:41] because you've opened a pizza delivery service? [06:49] slangasek: :) [06:59] thegodfather: you are now in the waste management business?-) [07:00] tjaalton: pizza delivery :) [07:02] thegodfather: so in a sense, yes :) [07:07] pitti: are you aorund ? [07:08] pitti: you'd told me that to change locale in kubuntu one needs to edit /etc/environment .. in that file on my machine i've put LANG="en_US.utf8" .. yet in konsole echo $LANG shows en_IN [07:09] DaBonBon: hm, there might be something in KDE which overrides it, I'm not sure; but KDE certainly has its own language selector? Hobbsee? [07:13] pitti: pass. [07:19] good morning [07:45] can somebody please sync traverso from sid? === gouki_ is now known as gouki [07:49] pitti: can you sync traverso from sid? [07:53] pitti: i don't think kde has it's own [07:54] wow, i guess i missed something.. brb. [07:54] dholbach: done [07:55] pitti: thanks a lot, now I can close ONE of the 247684276426 needs-packaging bugs [07:55] :) [07:55] http://people.ubuntu.com/~dholbach/sponsoring exploded [07:55] oh, was it a new package from Debian? [07:55] yeah [07:55] ah; please don't ask me to do that for a particular package in the future [07:56] I was going to sync all new stuff from Debian today anyway [07:56] ok good :) [07:56] and it's easier that way with source NEW etc. [07:56] * pitti news [07:56] * dholbach hugs pitti [07:56] * pitti hugs dholbach *knuddel* [07:57] pitti: sorry for the extra-work - I got desperate, when I looked at the list :) [07:57] NP [07:59] pitti: my fault, i didn't notice it .. it's deep somewhere in kcontrol .. [07:59] ty anyway :) [08:00] though shouldn't the system follow LANG from /etc/environment ? [08:00] DaBonBon: i suspect kde localisation is borked. [08:01] well after selecting US English from Kcontrol -> Regional and language settings -> System language -> Dialog box i could set it :D [08:01] Hobbsee: borked in what way ? [08:03] as in, doesn't work [08:04] oh ok .. [08:04] actually it's highly irritating that the installer sets the locale automatically .. atleast in the "Expert Settings" mode an option should be given to modify the locale :-/ === huahua_ is now known as Huahua === elkbuntu_ is now known as elkbuntu [08:25] https://bugs.launchpad.net/bugs/164648 -- :) [08:25] Launchpad bug 164648 in ubiquity "Allow user to select preferred locale" [Undecided,New] [08:26] Greetings everybody! === DaBonBon_ is now known as DaBonBon [08:44] hey MacSlow [08:48] Tag pitti [08:48] Hum. [08:49] The new gimp provides is own printing plugin, conflicts with gimp-print, and now gimp-print is gimp-gutenprint [08:49] * StevenK merges gutenprint [08:53] https://bugs.edge.launchpad.net/ubuntu/+source/sun-java6/+bug/127053 could someone triage this and mark it as New if required ? [08:53] Launchpad bug 127053 in sun-java6 "Problem in sun-java6-jdk documentation" [Low,Fix released] [08:54] (sorry, I meant that for #ubuntu , not here ! ) === \sh_away is now known as \sh [09:22] cjwatson: regarding your question from yesterday evening, what I pointed out was that ckbcomp will be run at boot (via setupcon --save) *unless* the init.d script detects itself being run by init. the mobile folks have observed (via bootchart) ckbcomp running, so I inferred that that logic was not working [09:23] Hi all! [09:24] hello, i have a bug to report, who do i turn to? [09:27] <\sh> milos, http://www.launchpad.net/ [09:27] hi warp10 [09:27] thc [09:27] thx === elkbuntu_ is now known as elkbuntu [09:28] pitti: hi martin! I got your mail, thanks. :) [09:31] whoops [09:31] \sh can you give me a direct link to the official kubuntu section? [09:31] sorry guys for the source NEW spam on -changes (new sources from Debian, forgot to disable mail) [09:31] there are a lot of ubuntu/kubuntu entries, i don`t know where to post my problem [09:32] <\sh> milos, there is no special kubuntu section...you need to know the package name and search for it...and file the bug against the package [09:33] well.. what is the package that runs the bootcd installer? :) [09:33] <\sh> pitti, debian removed ircii-pana from their archive....can we remove it from hardy as well now? there is a bug filed already [09:33] <\sh> milos, debian-installer? [09:33] not that one [09:33] the graphical one [09:33] <\sh> ubiquity [09:33] \sh: I'll do some mass-removal processing soon [09:34] pitti: I fail to see a problem in changes going to -changes. [09:34] \sh: as well as traverse the bug list [09:34] ok [09:34] <\sh> pitti, cool thx :) [09:34] Fujitsu: traditionally we don't mention autosyncs from Debian [09:34] and for kubuntu? [09:34] (the same thing happens in both distros) [09:34] <\sh> milos, it's the same... [09:34] thx! [09:34] pitti: Right, which I think is a bit strange. [09:34] you have been very helpful! [09:34] <\sh> milos, ubiquity has a gnome and a kde frontend...it's the same package [09:37] ubiquity does not use Launchpad as its bug tracker. [09:37] :/ [09:37] meh, nevermind [09:37] i`m prolly the only one that has that problem :( [09:37] i`ll just use alternative cd and debian-installer [09:43] pitti: I agree with Fujitsu. I realise it would increase the volume significantly, but I subscribe to *-changes to see what changes in Ubuntu, and new stuff (new packages or just new versions of packages) from Debian that gets imported is still a change to Ubuntu. [09:44] pitti: If I really wasn't interested, it would not be that hard to make a procmail rule that discarded any mail to *-changes that didn't have "ubuntu" in the subject. [09:44] that's a lot of mail for autosyncs, especially for the first one (some 2000 mails!) [09:44] milos: its "upstream" project page does say it doesn't use lp for bugs, but you can still file bugs at https://bugs.launchpad.net/ubuntu/+source/ubiquity/ [09:44] and if you are interested, you better read debian-changes [09:44] 2000 interesting mails, IMO :) [09:45] soren: by the same argument we don't get changelogs from other upstreams either [09:45] pitti: Hm? [09:45] soren: well, that list is meant to describe changes Ubuntu folks did to Ubuntu, not our upstreams [09:47] pitti: Updating package foo from version 1.0-1 to 2.0-1 in Ubuntu is a change to Ubuntu. Regardless of the origin of the update. [09:48] pitti: Ok, rephrasing: I'd really like to have some way of getting notified about *every* upload to Ubuntu, and I really consider *-changes the most suitable place for that sort of thing. Maybe we could add some additional headers to the mails there, so that people could more easily filter out automatic syncs or whatever. [09:49] pitti: I've not completely understood your argument about other upstreams.. Which other upstreams are we talking about? Could you give an example? [09:49] then I think we should revive https://lists.ubuntu.com/archives/ubuntu-changes-auto/ [09:50] soren: we don't put the changelogs from OO.o, Gnome, etc. to that list either [09:50] just Debian's changelogs for autosyncs (which we don't do usually) [09:50] pitti: Indeed, but there's a mail on that list when there's a new oo.o upload.. If I'm interested in the details, I can look them up. [09:51] having a separate ML seems more appropriate to me, and you can sort them into the same folder if you want [09:53] pitti: The difference between OO.o, GNome, etc. and Debian is that a change in OO.o doesn't change anything in Ubuntu until someone uploads said change, but a change in Debian does. [09:53] right [09:53] soren: so WDYT about -changes-auto@? [09:54] pitti: It would indeed solve my problem. [09:54] pitti: I'm just still puzzled why it's a separate list. [09:54] pitti: I don't think automatic changes are any less relevant than UBuntu specific ones are. [09:55] most people are interested about things Ubuntu devs change in Ubuntu, and getting 2000 mails on one day is not generally considered nice by many people [09:56] so providing an opt-in with -changes-auto seems better to me than starting to spam people [09:56] soren: they aren't less releavant [09:57] for the functioning of Ubuntu [09:57] pitti: I don't know "most people", so I can't say anything about what they're interested in. I can only say that if I subscribe to hardy-changes that early in the release cycle I wouldn't be one bit surprised to get a massive flood of mails about stuff that gets imported. I'd expect it. [09:57] but they are less interesting to many people to read the details about them [09:57] pitti: I don't think we'll get much further with this discussion. Reviving auto-changes will give me the info I want, so that's fine. [09:57] ok, great [09:58] I reserve the right to think it's odd, though :) [10:06] * Hobbsee finds it annoying that the merge bugs are just filled with "remaining ubuntu changes" but you rarely tend to see what *debian* has changed [10:06] pitti: While I tend to read changelogs from sources other than the mailing list, finding Debian changelogs with which I disagree is a common prompt for me to make an Ubuntu upload. I'm only interested in a subset of packages, but for someone with wider scope, the ML may be a strong point. [10:06] Hobbsee: Kick it back if they don't include the Debian changelog. [10:06] but that may well be because of the options used for merging [10:06] persia: it's auto-accepting [10:06] as in, debian changelog is there, but not shown in the mails to -changes [10:07] Hobbsee: If people don't debuild -v someone should politely tell them to do so. [10:07] Hobbsee: If it's not shown in the mail, the uploader made a mistake: one should always generate a changelog containing all changes since the last Ubuntu release. I use `debuild -S -v(last ubuntu version)` for that. [10:08] soren: or have keybuk yelling, yes. [10:09] Hobbsee: Well, yes, depending on who did it. [10:09] Hobbsee: If it's one of his minions, sure :) [10:09] * Hobbsee taught this room a whole new expletive that day... [10:09] soren: he doesn't only blast his minions for it [10:09] unless i'm suddenly a minion, without realising. [10:10] Hobbsee: oh :) [10:15] When did I yell? [10:17] Keybuk: a while ago, when i didnt use MoM at all. [10:17] I bet I didn't tell [10:17] yell [10:17] see, I can't even spell yell [10:18] sure? [10:23] I remember cjwatson telling someone about -v [10:31] I have a package I am trying to merge, which is a frontend for another package in the archive. The backend package in question uses libgcrypt11, which recently had its .la file moved from /lib to /usr/lib. The frontend FTBFS on this, as the .la can't be found in /lib. However, attempting to rebuild the backend package results in the package still assuming that the .la file is in /lib, when its in /usr/lib. [10:31] The libgcrypt11 .la file is listed in several .la files in the backend package, in the dependency_libs field. [10:31] I've noticed that libgcrypt11 uses clean-la.mk for use with cdbs. I am wondering whether I should re-upload the backend package with this code in debian/rules, to clean the .la files. I've tested this, and it allows the frontend package (my merge), to build. I am wondering however, whether this is the right approach to take. [10:32] TheMuso: cleaning .la files is fine, on a general basis [10:34] Mithrandir: Ok. I guess the only other question then, is whether this code will be put into something else that is usable by packages that use staright debhelper, which this backend package does. If not, I'll copy/paste and modify the clean-la.mk cdbs code accordingly for the package. [10:35] straight* [10:42] TheMuso: I added the sed to gnutls13, which doesn't use cdbs (AFAIR) [10:42] TheMuso: it took us about 5 uploads until we tamed those *($#$# .la files enough to not break libgpg-error/gnutls13/libgcrypt11 any more [10:42] TheMuso: unfortunately we had to put it back [10:42] TheMuso: but putting it into /lib is useless, libtool doesn't find it there [10:42] pitti: why did we have to pit it back? [10:42] put, even [10:43] doko: hello! I'm currently checking my stuff to forward to debian and noticed that python-gamin-dbg is something we may want to forward. is there a spec or anything that explains a bit about the rational for the python-dbg packages? I would like to have something to point people at when sending the diff to debian [10:43] I forgot, someone else did that; /me checks changelog [10:44] hm, StevenK, why did you put back the .la to libgpg-error again? [10:44] libgpg-error (1.4-2ubuntu7) hardy; urgency=low [10:44] * Add symlink from /lib/libgpg-error.la to /usr/lib/libgpg-error.la [10:44] since /lib is where other .la files expect it to be [10:44] -- Jonathan Riddell Thu, 15 Nov 2007 23:19:09 +0000 [10:44] TheMuso: ^ maybe you have to do that as well, but this is REALLY EVIL [10:44] pitti: heh, it does sound rather evil. [10:45] if I have been evil, it is because I was standing on the shoulder of evil giants [10:45] * pitti hugs Riddell [10:45] it seems that three long-experienced developers haven't found a proper way to make .la files work for stuff in /ilb [10:46] /lib even [10:46] Riddell: standing on the thin and shaky evil libtool ground? :) [10:46] Sounds wonderful. [10:47] we could, like, clean out those other .la files. [10:47] I'd recommend that, especially now that we're in free-fire-mode. [10:51] In the case of the backend package, nothing goes into /lib, but its .la files point to the libgcrypt11 .la which it still thinks is in /lib, which it isn't... If the autotools foo was rebuilt for that package, would that change anything? Or, should I just clean the .la files and be done with it? [10:52] TheMuso: if it works without a .la at all, then this is preferable IMHO [10:52] TheMuso: but we need to remove .la files top-to-bottom, and clean their stated dependencies bottom-to-top [10:53] Right. [10:55] But if the .la files were removed from the backend -dev package, what is the likelyhood of something needing to be changed in the frontend package? [10:55] To not rely on the .la files === gasp1 is now known as gaspa [10:56] TheMuso: AFAIK, in the worst case, it FTBFSes and you need to remove the .la files from the reverse dependencies, too [10:56] mvo: have to write this p [10:56] mvo: the rationale is to provide an extension to be used with the python-dbg interpreter [10:57] pitti: I'm not that knowledgable with autotools.. What reverse dependencies are you referring to in this context? [10:57] TheMuso: reverse build dependencies I mean [10:57] pitti: Ah ok. [10:57] doko: thanks, I found https://wiki.ubuntu.com/PyDbgBuilds [10:57] TheMuso: e. g. if we would remove the .la files from libgpg-error-dev, then we would likely break the build of everything that build-depends on libgpg-error-dev [10:57] doko: it would have been cool to get a mail about this to ubuntu-deve-announce, it looks incredible useful [10:58] pitti: Yep, I understand now. [10:58] TheMuso: which is why we just remove the 'dependencies' line from its .la, so that it does not spread any superfluous dependencies any more and not pull in the lower-level .la files any more [10:58] .. and then we can get rid of the .la files in the next round. [10:58] right [10:59] pitti: Ok, so I'll just clean the .la files. Thanks for your explanations and help. [10:59] TheMuso: you're welcome; for non-cdbs; please look at gnutls13 [10:59] pitti: Will do, thanks again. [11:00] TheMuso: hm, no, it wasn't gnutls13, that's cdbs, too [11:00] TheMuso: but well, it's just copying the sed -i, so it's no big deal [11:00] mvo: hmm, didn't we do this for feisty? [11:01] pitti: But I didn't... [11:01] libgpg-error (1.4-2ubuntu4) hardy; urgency=low [11:01] * Install the .la again. Libtool, I will have my revenge! [11:01] pitti: Yeah, figured as much. [11:01] -- Steve Kowalik Mon, 05 Nov 2007 10:13:41 +1100 [11:01] StevenK: I know there was a reason for it, but I forgot [11:02] pitti: Oh right, um, because it meant libtool went looking for it and then bitched it couldn't find it [11:03] doko: I can't find it here, maybe I overlooked it, but it seems to be not in my mailbox [11:06] doko: right, it's create load of extra work, would be nice to write some announce mail to debian about those and send the patches we have to the bts [11:07] it should have been made much early, we have lot of packages patches for that an often the debian/rules is changes are not trivial === stdin__ is now known as stdin_ === stdin_ is now known as stdin [11:25] mr_pouit: Has the patch to stop gimp segfaulting with murrine been sent upstream. (It is in the debian package though) === dholbach_ is now known as dholbach [11:52] MOTU Meeting in 8 minutes in #ubuntu-meeting === sladen_ is now known as sladen [12:00] pitti: MOTU Meeting :) [12:00] dholbach: joined, thanks [12:00] thanks pitti [12:04] * highvoltage also attends for a change === stu1 is now known as stub [12:10] pitti: hi [12:10] pitti: sorry for bother you again... what's the status of language pack generation? [12:10] carlos: they should all be in PPA, and I got some initial good feedback [12:11] are they in proposed already? [12:30] mr_pouit: There is a major issue with the murrine package [12:30] mr_pouit: the debian package does _not_ clean the patches when it builds the package. Afaict, it is in the debian rules, but was not called by the DD when it originally created [12:35] thanks pitti [12:35] my pleasure, not much to do :) [12:36] carlos: I'll do that now [12:37] Fujitsu: i see what you mean about this -intel driver being rather tempramental [12:37] Hobbsee: Yeees. [12:37] Dieing on me a lot tonight. [12:37] Hobbsee: Why did you upgrade? [12:38] Fujitsu: because of something else i upgraded, which gave me random syslocks. [12:38] Ah. [12:38] as in, X would entirely freeze, at random, with no way of fixing it, it appears [12:38] yeah, 20 mins, and it had already crashed. [12:38] -intel does that too, but with the added bonus of killing everything regularly. [12:38] heh [12:38] wonderful [12:38] Although you can sysrq and suspend out of it, which is good. [12:38] Hahahah. [12:39] seb128: new bug-buddy requires libelf-dev, which needs a MIR [12:39] Hobbsee: Again? [12:40] MOTU Q&A Session in #ubuntu-classoom in 20 minutes [12:40] there we go. [12:40] twice in 25 mins. this could get fun. [12:40] pitti, uuuh, we'll have pulse in desktop now ? [12:41] * ogra just sees the changelog for edubuntu-desktop ... thanke for uploading btw [12:41] ogra: yes; you don't want it in edubuntu? I thought you were yearning for it [12:41] ogra: I merged your seeds, BTW (I think I didn't screw them up too badly) [12:41] pitti, i'm not sure the ltsp alsa emu works if pulse is installed locally [12:41] ogra: well, feel free to kick it out again [12:41] i dont care, i still have some months to fix them :) [12:42] Hobbsee: I've had it within 5 minutes of restarting twice tonight. [12:42] welll, there wont be an edubuntu desktop like you knew it anymore after we redid the edubuntu CD design [12:42] And sometimes suspending doesn't work, which is annoying. [12:42] the point is that i will just depend on ubuntu-desktop and edubuntu-desktop only adds artwork and a basic set of edu apps [12:44] Fujitsu: bring on the new kernel :) [12:44] Hobbsee: Why? [12:45] Fujitsu: because then we get the new -intel [12:45] Hobbsee: I have the new -intel. [12:45] It doesn't actually need the new kernel. [12:45] Fujitsu: doesn't it require something or other from the kernel? [12:45] that any better? presumably not. [12:45] It says it does, but apparently not. [12:45] No, it's really not. [12:45] pitti, i actually thoght we were beyond the time where we need sound daemons [12:45] Though I have had a couple of periods where it has gone for upwards of 12 hours. [12:45] what for do we add pulse ? only for the system sounds ? [12:46] But other times just a few minutes or seconds. [12:46] ogra: apparently not, see the PulseAudio spec (lots of use cases) [12:46] * ogra goes looking ... [12:47] seb128: FYI, I'm traversing through http://people.ubuntu.com/~ubuntu-archive/testing/hardy_outdate.txt and give back some failed buids on the way [12:49] hrm ... no hal or consolekit on ltsp clients ... that will get tricky [12:52] doko: the ocaml merge blocks some packages from getting built; however, do we really need ocaml-native-compilers on lpia? (that's our only change) [12:53] pitti: I don't think we care about ocaml on lpia [12:53] Mithrandir: the interpreter still works, and few packages need the native compiler [12:53] Mithrandir: so ok to sync that? [12:54] (nothing in main b-deps on -native-compilers) [12:54] pitti: I don't mind, at least. [12:54] let's do it then, for the sake of avoiding unnecessary work [12:54] Mithrandir: thanks [12:54] Mithrandir, pitti: As long as we don't have a simple way to sort out the packages in main not needed for lpia I would prefer to have the package be buildable, or else these show up as build failures [12:55] pitti: please don't, you create extra work for buildd admins [12:55] doko: how so? it's simply not built for lpia then [12:55] pitti: but other packages do fail? [12:55] doko: which? as I said, there's exactly one rdepends in the entire universe [12:55] ahh, ok [12:56] (dag2html) [12:56] this won't be built on lpia then either [12:56] but *shrug* [12:56] doko: your call, though, if you want to do the merge, I don't object :) [12:57] pitti: no, I don't care about universe build failures anymore =) these can be sorted out now with the help of new mail headers [12:57] ok [12:58] pitti: ok, thanks [13:01] seb128: eww, and gnome-games wants guile-1.8 now; MIR or drop that feature? [13:02] * StevenK tries to sort out gutenprint [13:02] drop gnome-games ;p [13:07]