[00:03] asac: Unfortunately I've been really busy and will be busy for the next few weeks, so I haven't had time to look at vpnc not working. Not sure if you have had time to take a look... [00:03] johanbr: thats ok. i think there is a real issue. ill test myself as soon as possible === asac_ is now known as asac [00:59] did anyone else get quasi mailbombed at their ubuntu.com address? [01:21] any archive admin could please move the amsn sru to -updates? (at least the hardy one) === beuno is now known as beuno-dinner === beuno-dinner is now known as beuno [02:01] so it wasn't me! [02:06] is intrepid suffering from whats in here? [02:07] http://pavelmachek.livejournal.com/60867.html?view=123331#t123331 [02:07] 2.6.26.1 bug? [02:07] my T42p fan has been going crazy lately [02:11] ask in #ubuntu+1, where the users of intrepid usually hide? [02:11] (although some developers are running intrepid) [02:46] Is anybody else able to boot the latest ubuntu amd64 intrepid daily in kvm under hardy? [02:50] TheMuso, I'm running the latest ubuntu amd64 intrepid on real metal if that helps [02:51] NCommander: No, it doesn't. I am also doing so on another box. [02:56] * NCommander plays with dak === superm1|away is now known as superm1 [03:54] if I have multiple binary packages building from a single source package, should the package name prefix in templates be the source package name, or the binary package name(s)? [03:54] moquist: You mean foo.install, foo.preinst, etc? [03:55] i.e., src pkg moodle builds moodle-mysql and moodle-postgresql. should templates have only moodle/... entires, or moodle-mysql/..., moodle/..., and moodle-postgresql/... ? [03:55] moquist: They should be binary package names. [03:56] I'm not sure what you mean by "templates" in this setting. [03:56] RAOF: OK, so Template: / [03:56] This is debconf, right? I've approximately no experience there :) [03:56] RAOF: http://rafb.net/p/wSgfUZ27.html [03:57] line 62 should maybe read: Template: moodle-mysql/dba_password [03:57] RAOF: yes, debconf [03:59] I'm not sure, but my *guess* is that you'd actually need it to be in a different templates file; one for the moodle-mysql binary package, one for the moodle-postgresql binary package, etc. [03:59] That's a guess based on the behaviour of other tools; I'm not familiar with debconf. [04:01] hey moquist [04:01] I think binary package name is correct [04:01] if there are any that apply to both then you can do shared entries [04:02] So, I've got a question in return: how does one switch the CPU and IO schedulers at runtime? I'd like to see if different schedulers have better than the abysmal interactive performance I'm currently seeing under IO load. [04:02] RAOF: there's a sysfs key [04:02] james_w: I suspected as much. Any details of the top of your head? [04:03] just searching now [04:03] /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor looks pretty good [04:03] for the CPU at least [04:03] That's going to be the CPUFreq governor, not the scheduler [04:04] IE: when should I throttle the CPU back. [04:04] oh, yeah, sorry [04:04] find /sys -name "*sched*" [04:05] that lists a couple of things [04:05] perhaps block device schedulers can be changed, but not others [04:07] Yeah, possibly. [04:07] james_w: hi! and thx [04:07] that was my guess, too [04:08] just one templates file, even though I have moodle.config and moodle-mysql.config, right? [04:08] (it builds, so I'm guessing that's right) [04:10] I'm not sure, I can't remember how it works [04:10] well, I'll test soon. :) [04:11] if you have moodle.templates then try installing -mysql, it will soon fail if you need two [04:11] I'm glad to see you're still fighting away at this === foka_ is now known as foka [04:12] me too...I'm not sure of the timing here, but I still have hopes of getting this into debian in time for it to get pulled into intrepid [04:13] james_w: if you have a moment, I'd appreciate your thoughts on http://revu.ubuntuwire.com/details.py?package=vpnywhere [04:13] Debian is frozen which may be a hiccup [04:13] but there is still time [04:13] moquist: is this related? [04:14] james_w: only in that it's a package I made. we discussed this one a couple times at UDS. *shrug* [04:14] that's fine [04:14] I'll take a look tomorrow. It's late and I've been drinking, not helpful for review. [04:14] james_w: heh - cheers, then. :) [04:18] Is chvt located at /usr/bin/chvt on Ubuntu? [04:19] warren: yep, apparently [04:19] k [04:23] is the indian language hindi possible on irssi? [04:23] or say on x-chat [04:24] any indians in the room [04:25] anyone good with translations [04:25] cathyal: This is an English channel. You might try #ubuntu-in [04:26] thanks [04:30] heya james_w [04:30] hey bryce [04:31] bryce: did you see Federico's patches? [04:31] james_w, couple bzr questions for you if you have a moment? [04:31] sure [04:31] could you come to #inkscape? [04:32] actually nevermind, I'll ask here and just copy answers... [04:32] I can do that [04:32] last time we looked at switching to bzr for Inkscape, the two issues that stopped us were a) Windows UI, and b) EOL handling [04:33] james_w: do you know if the status on either of these has changed drastically in the last few months? [04:34] for a) Mark Hammond (big pywin32 dude) has been contracted to make TortoiseBzr rock, and work is starting to progress on that [04:35] there's also bzr-gtk and bzr-qt, which are improving a lot, especially the latter I believe, which is apparently more windows for some reason [04:36] for b) there is work ongoing, 1.6 out this week will kind of be able to do it, but you would probably want 1.7, out next month to have it work well [04:46] thanks for the answers james. probably when those changes hit, Jon Cruz will take an interest [04:47] cool [04:47] bryce: do you have an opinion on Federico's patches? [04:48] I peeked at the screenshot and it looks like nice eye candy [04:48] we're not to FF yet, so I think we could definitely pull the patch in [04:49] it's up to seb128 though. he might prefer waiting until the patch is upstream [04:50] yeah, it's up to seb128 [04:50] I was going to reply to ask about theming [04:51] I don't know how it picks the colours, but the one in the screen shot wouldn't sit well in Ubuntu [04:52] I'd gotten a suggestion from mirco on how to pick colors from the current theme [04:52] I can find it and forward it if you're interested [04:53] that would be good [04:54] it's something we want anyway, but may help with this [05:35] good morning [05:59] Good morning [06:01] Morning pitti [06:01] hi pitti [06:05] dholbach: btw, no sponsor bugs for me in the next two weeks, please (I'll be on holiday the next two weeks, and wrestle with alpha-4 this week) [06:06] nooooooooo [06:06] what are we going to do without pitti for 2 weeks! [06:06] /o\ [06:06] :D [06:07] pitti: OK [06:07] * dholbach hugs super-pitti [06:07] * nxvl HUGS pitti too [06:08] pitti: what do we do in cases where we sync a new package from debian and it ftbfs, but we have a patch for the ftbfs already? [06:08] sync, then upload the fix? [06:08] get the fix to debian, then sync? [06:08] Does it FTBFS in Debian too? [06:09] bug 256821 [06:09] Launchpad bug 256821 in ubuntu "Please sync glusterfs 1.3.10-1 (universe) from Debian unstable (main)." [Wishlist,New] https://launchpad.net/bugs/256821 [06:09] seems it doesn't [06:09] What's the patch? [06:09] it's in the bug [06:10] Ah, I know why that is [06:10] dholbach: Keybuk told me that it is cleaner to sync and then apply the patch [06:11] dholbach: I suspect that is libc6 2.8 fall out [06:11] pitti: OK, I'll ack then sync then [06:11] dholbach: that's an ubuntu only issue due the compiler flags IIRC [06:11] dholbach: that is, for MoM, otherwise it doesn't matter at all [06:11] * pitti hugs back nxvl and dholbach [06:11] I suspect Debian will hit the same issue when they hit libc6 2.8 [06:12] I forwarded a couple of "glibc 2.8 ftbfs" patches to Debian, they were all gladly accepted [06:12] dholbach: https://wiki.ubuntu.com/CompilerFlags [06:12] dholbach: under -D_FORTIFY_SOURCE=2 [06:13] nxvl: Given the error, I doubt it's because of compiler flags [06:13] StevenK: that error is listed on that wiki [06:13] but i haven't check it closer [06:13] pitti: can you please confirm me about the versioning of this package, i find it odd [06:13] pitti: http://revu.ubuntuwire.com/details.py?package=mythstream-parser-google [06:14] nxvl: So, fix the error. libc likes it when you call functions correctly. [06:15] i have patched it before [06:15] * nxvl looks [06:15] nxvl: indeed it is [06:16] nxvl: two ubuntus in the version number sounds wrong; the uploaded should make up his mind whether it's a native or upstream project [06:16] pitti: thank you, can i quote you on revu? [06:16] sure [06:16] :D === thegodfather is now known as fabbione [06:19] StevenK: taking a closer look to the patch in that bug report is exactly what it says on the wiki [06:19] dholbach: i hardly thing it is an ubuntu only bug [06:20] nxvl: I asked Neil to forward the patch [06:20] s/hardly/really/ [06:21] dholbach: i would test it in debian before sending it, or ask the DM to include it for downstream compatibilty [06:22] because they won't find it as a bug [06:22] found it [06:22] nxvl: I suspect Debian will hit the same issue when they hit libc6 2.8 [06:23] mysql-gui-tools_5.0 has the same problem [06:23] and fixed [06:23] dholbach: yeah, maybe it is a libc issue [06:23] * nxvl checks in experimental [06:23] pitti: how are the alpha4 cd's coming along? [06:24] kirkland: nobody tested the new desktop CDs in the last 7 hours, doing that now; but I hope they'll work now [06:24] kirkland: by and large they should be okay now [06:25] pitti: cool, i'll do some server testing in the morning [06:25] kirkland: servers look pretty good, 9/10 tests done [06:25] pitti: oh, zul must have kicked some butt then :-) [06:25] pitti: when does the archive re-open? when can i get a fix for mdadm sponsored? [06:25] see http://iso.qa.ubuntu.com/qatracker/build/all [06:26] yup [06:26] we urgently need kubuntu testing, and ubuntu desktop [06:31] pitti: okay, i'll see what I can do tomorrow ;-) i'm calling it a night [06:33] StevenK: it builded without problems on sid (libc6 2.7-13) and in experimental (libc6 2.8+20080809-1) so it may be a compiler flag issue [06:34] just tested [06:37] pitti: that reminds me, how are the complierflags, libtool, libc changes managed? thay take place only at the start of the development cycle or at any time? [06:43] pitti, i know i was seeing some gvfsd trash related crash after install on the desktop disks [06:43] i wasn't at a location that i could submit a crash report when i was seeing it though [06:54] superm1: yep, plenty of reports about that one [06:55] nxvl: pretty much at the start usually [06:55] pitti, ah okay then i wont worry about reproducing it again [06:55] nxvl: since they are very prone to break a lot [06:55] superm1: right [06:55] pitti: yes, that why i was thinking about it, since if they change we will need to rebuild a big part of the archive to check for breakages [06:58] nxvl: that is, in Ubuntu we generally limit it to the start of a cycle; in Debian, changes happen during cyles, too, since they are much longer [06:58] :D [06:58] pitti: thank you for clarification [06:59] superm1: ubuntu desktop CD, ubiquity works fine now; thanks again [06:59] pitti, no problem. glad it was easy to identify :) === superm1 is now known as superm1|away === tkamppeter_ is now known as tkamppeter [07:43] * mneptok douses pitti in chocolate and kerosene [07:44] Chocolate *and* kerosene? [07:45] I've heard about dark chocolate, but that's a little much. :-P [07:45] only after you burn it === apachelogger_ is now known as apachelogger === sjoerd_ is now known as sjoerd [08:43] mneptok: owch [08:50] pitti: it's just that i think of you as hot and sweet. or something like that. :P [08:52] mneptok: are you part of the Pitti Fanboy team on launchpad yet then? :) [08:53] mneptok: Crème pitti? :-) [08:53] Treenaks: i refuse to join any club that would have me as a member. i have some prinicples. [08:53] mneptok: maybe you'll be rejected, I'm not the team admin [09:00] re [09:00] * pitti drops a metric ton of gummybears onto mneptok [09:02] * mneptok gleefully frees himself [09:02] NOM NOM NOM [09:14] "NOM NOM NOM"? [09:15] liw: http://www.urbandictionary.com/define.php?term=nom [09:16] thanks [09:16] * lukehasnoname is away: sleep [09:17] lukehasnoname: Thanks a lot for the information! We were just wondering about that. [09:18] liw: The equivalent of "nam" in Finnish. :-) [09:18] Hm, perhaps not exactly. [09:28] pitti: arg, it did it again, bug #257803 [09:28] Launchpad bug 257803 in gedit "gedit crashed with SIGSEGV in g_type_check_instance()" [Undecided,New] https://launchpad.net/bugs/257803 [09:28] pitti: the retracer removed everything including the debug stacktrace [09:35] pitti: bug 195749 doesn't include a DistroRelease field...is that because we need to add it to the kernel hook? [09:35] Launchpad bug 195749 in openjdk-6 "java hangs then crash in libc6/kernel" [Undecided,Incomplete] https://launchpad.net/bugs/195749 === cjo20 is now known as Seeker` [10:14] seb128: hm, if it does that often, maybe stop it for now? [10:15] mdz: that was reported with the aaaaancient kernel hook (which we never really used in our kernel pacakge) [10:16] indeed that one didn't add OS info, like DistroRelease [10:22] pitti: ah, ok [10:22] pitti: that was the first apport-kernel bug I have seen, didn't notice how old it was [10:27] pitti: it just does when retracing again a bug [10:27] pitti: I did retag this one because the retracer didn't have the new gedit version yet [10:30] pitti: I managed to write something which should work with the way you implemented the progress bar in Jockey. I had to subclass apt.Cache. Now I have only a question on progress_cb(phase, current, total): phase is either 'download' or 'install' but what are "current" and "total"? Is current the current percentage of work and total 100% or do you have something different in mind? [10:31] tseliot: the only requirement is that current eventually reaches total [10:31] tseliot: could be number of pacakges, or percent, or whatever you need [10:31] total == 1.0, and current = 0.37, or total = 1000 and current = 372 [10:31] or total == 5 (packages) and current == 2 (second package) [10:32] pitti: great, I'll use the percentage [10:33] pitti: oh, another thing, is it ok if I make the apt part run on a different thread? [10:33] tseliot: sure, if that helps [10:34] pitti: yes, that's what I used in my implementation [10:37] seb128: it's done in apport/crashdb_impl/launchpad.py, close_duplicate(); nowhere else; so I think the duplicate detection is on crack and tries to mark the bug as a dup of itself [10:37] pitti: maybe it needs a "if dup_number == bug_number" case? [10:37] seb128: I think a simple "if id == master: return" at the top of that function should be a good enough patch for the retracers until I'm back from vacation; please report a bug agout it [10:37] seb128: 'zactly :-P [10:37] pitti: ok thanks [10:38] seb128: if you do that in the chroots, the next apport package update will overwrite it, but then we should have a better solution anyway [10:38] pitti: ok, I'll do the change [10:39] thanks! [10:39] * seb128 hugs pitti [10:40] Can anyone please tell me if anyone is working on packaging elisa 0.5.5? [10:41] lool: ^ [10:42] Hey; I'm not currently, but philn might have prepared something in pkg-gstreamer svn [10:42] At least 0.5.4 is ready there [10:42] And 0.5.5 should be easy to get [10:42] slytherin: ^ [10:43] lool: do you know if somebody from the mobile team will do the cheese 2.23 update? [10:45] seb128: Gary said he was interested, but this was a while ago [10:45] seb128: I'm basically the sponsor here; we had hildon bits to push in earlier cheese, but this now all upstream and merged and all [10:46] lool: right, I let the updates on the side because I don't use cheese and you guys do it usually but we had none of the 2.23 update [10:46] I don't even have a webcam, so I'm quite a bad tester for cheese ;) [10:46] right, me neither [10:46] anybody interested to update cheese? [10:46] seb128: If you like, drop tremolux an email and ask him for a status update? [10:46] lool: ok, I'll do that, thanks [10:47] seb128: I'm happy to do the reviewing and sponsoring of his work or of somebody's else; it just doesn't make sense for me to do it as I don't have a webcam to test! [10:47] right [10:52] seb128: I can test cheese on intrepid. I will see if I can update it to but that will be after Monday. [10:52] slytherin: ok, thanks [10:53] lool: Thanks for elisa info. I hope I will find it in repositories before FF. :-) [11:22] seb128, !!! [11:22] Unable to retrieve message [11:22] Cannot create folder lock on /home/ogra/.evolution/mail/local/Inbox: Too many open files [11:22] my evo misbehaves [11:22] hey ogra! nice to see you back, how are you? [11:22] fine, thanks :) [11:23] ogra: close and restart it? [11:23] it seems to leak file descriptors in some cases [11:23] i wasnt actually bad apart from the 15 mins .... they only kept me locked in for a week to do tests [11:23] lets see, closing now [11:24] ah, yeah, better now [11:25] cool, there is a bug about the issue already so no need to open one [11:25] seb128, beyond that it seems to have gotten slower over the last week ... [11:25] since the 2.23.6 update you mean? [11:25] after the initial upgrade from hardy to intrepid it took about 1-2sec switching folders [11:25] that's the first version using sqlite for summary storage [11:25] now that can take up to 5-10 [11:26] there is still some optimization work needed [11:26] they are working on it a lot, wait for tarball next week to see if things are better [11:26] yeah, i just noticed it seems to have degraded since the first upgrade [11:26] the new code was not really optimized for some cases [11:27] I had evo freeze for some seconds when using my bugmails box for example, which was due to the hidden messages handling [11:27] (i'm not complaining, just giving feedback :) ) [11:27] I hide everything which is read there, they fixed the bug in svn [11:27] but there is likely some other non optimized cases [11:28] they are working on it and really responsive to issue reported so file a bug if you still get the issue in the new version [11:30] yeah, i have no hidden msgs ... but lots of folders wih big amounts of mails [11:32] pitti: I get this error now: http://pastebin.com/m4371b4c0 . If I run my program outside of Jockey it works well. Maybe is it because of what you do in dbus_sync_call_signal_wrapper() (in backend). I wouldn't know. Any ideas? It's all in my branch: ~albertomilone/jockey/ubuntu-core-xkit [11:34] seb128, right, i'll wait for the next tarball, lets see :) [11:39] tseliot: what do you try to do? [11:40] tseliot: do you call a function which takes very long to execute? [11:40] pitti: I only clicked on a new driver, typed in the password for policykit and then that error shows up [11:41] pitti: I use python-apt to install the package [11:41] tseliot: maybe d-bus is not thread-safe enough to do that, I don't know :( [11:41] pitti: if you have a look at install_package in oslib you will see what I'm doing [11:42] tseliot: sorry, no time right now [11:42] pitti: ok, no problem. I'll see if I can find something with Google about the error [11:47] tseliot: you are not subscribed to the nvidia-graphics-drivers-177 bugs? [11:48] tseliot: there is quite come crasher for nvidia users in intrepid for some days when using compiz, I've reassigned bugs there [11:49] seb128: yes, I'm subscribed. I've been very busy though. What's the number of the bugreport? [11:49] tseliot: are you sure you are subscribed? you are not listed on bugs [11:50] seb128: I see it in my "bugs" folder in my mail client. I'm part of the X team [11:50] ah ok [11:51] tseliot: https://launchpad.net/ubuntu/+source/nvidia-graphics-drivers-177/+bugs, all the crashes in _nv* [11:52] seb128: ok, let me have a look at those reports [11:53] tseliot: they don't seem really useful, I just wanted to let you know that quite some nvidia users seem to have compiz crashing in intrepid [11:54] seb128: thanks for bringing this to my attention [11:54] you're welcome ;-) [11:59] seb128: BTW do you have a look at my 3 lines patch here? http://bugzilla.gnome.org/show_bug.cgi?id=546969 [11:59] Gnome bug 546969 in Screen resolution "The GUI components do not always reflect the current situation" [Normal,Unconfirmed] [12:00] tseliot: GNOME will roll new tarballs next week, I'll try to get the patch reviewed before that [12:00] seb128: thanks a lot ;) [12:00] thank you for working on the bug ;-) [12:14] hi all ;) [12:15] pitti: when you will have the time, I'm interesting to know how NBS are calculated. [12:15] Indeed, it seems to not look at package dependencies as some times, we have 3 dependecies for one source package. ldd on the binary seems to not put the same result... [12:18] The desktop effects currently doesn't respect ccsm settings, will this be fixed/ [12:18] ? [12:19] I meant if I select advanced/basic there the custom settings are cleared [12:20] I would like to use this dialog to switch between compiz and metacity, but without alerting the settings [12:32] didrocks: NBS is based on declared binary package dependencies. This may not match the current source package (if successful builds have yet to publish (common in cases where the build fails)), and may not match ldd or similar tools depending on both the correctness of the analysis of those tools and the declared dependencies. [12:34] persia: konban-wa [12:35] こんばんは [12:36] persia: the convincing argument. "you can lose weight just by blinking in the summer." [12:37] persia: thanks a lot and that guide me through my second (big) technical questions: how ${shlibs:Depends} are calculated regarding build dependencie, it assumes runtime ones? :) [12:38] didrocks: man dh_shlibdeps for an overview, and read /usr/bin/dh_shlibdeps for the details. [12:38] ok, I will give it a look ;) [12:39] any archive admin could please move the amsn sru to -updates? (at least the hardy one) [12:43] didrocks: if you're looking for insight, https://wiki.ubuntu.com/MOTU/School/LibraryPackaging might be helpful (but it's quite a read) [12:45] sistpoty|work: thanks for the link, I will add it to my reading schedule :) [12:52] I have one quesion, is the 'NEEDED' section needed :-) [12:52] without it linker won't find the symbols? [12:53] MaximLevitsky: well, you could do without, if the shared object defines all the symbols itself I guess, but I wouldn't know a use case for this right now [12:54] sistpoty|work: I don't understand you (I once did a deep research on linking, but forgot most of it now) [12:55] I mean if a library needs a symbol from external library, does it have to add that library as NEEDED ? [12:55] MaximLevitsky: yes [12:55] sistpoty|work: this is great [12:56] sistpoty|work: I remember that I once tried to understand how to write a depends.exe equivalent for linux [12:57] * sistpoty|work wouldn't know what a depends.exe is in the first place *g* [12:57] Long long time ago (about 8 years from now I used and programmed in windows_ [12:58] depends.exe shows you what libraries(dlls) are needed for this application, and for each dll, it shows list of symbols [12:59] that app use, and list of symbols that dll exports [12:59] so a mixture of ldd and objdump, right? [12:59] http://www.dependencywalker.com/ [13:00] more or less, but it gets the information directly from .exe, and .dll [13:00] linking is a bit different there [13:00] each app has a list of dlls that it needs [13:01] and for each dll there is a list of symbols it needs [13:01] here in ELF there is just a list of all symbols [13:02] so to know from where the symbol come, one needs to know what libraries the app needs [13:02] I was thinking that ld.so just searches all libraries on the system for any symbol [13:03] using cache to speed this up [13:05] erm, no. library resolution is done exactly with the NEEDED entries [13:05] sistpoty|work: this is just great [13:06] sistpoty|work: although if I were to write such program, I will probably need to parse outputs of objdump and ldd, right? [13:07] elf probably has platform specific differencies [13:07] MaximLevitsky: sorry, am not 100% sure about ELF internals, but I guess I'd use objdump (or readelf) as a base [13:07] Btw ldd is just a frontend to ld.so [13:08] just a script that exports some env variable, and then runs the program, and this makes ld.so output the depedencies, and exit [13:09] this is what I remember from that old study [13:11] sistpoty|work: another interesting this is that global data variables in a library are reverse exported [13:11] app exports the variable to the library [13:13] sistpoty|work: thanks for information [13:15] Btw, why all devel packages install .a libraries? [13:15] who uses static linking those days? [13:16] As I understand to write code against a library you need .h files and .so normal library, thats all [13:46] Keybuk, if i run telinit 6 (or shutdown -r -now) and get "Unable to send message: Connection refused", do you have a hint for me for what i should look to make that functional ? [13:46] (that shows up recently in my classmate installer out of the blue) [13:47] ogra: not running init? [13:47] right, i run a script that fires up the cmpcinstaller [13:47] but it used to work in the last builds [13:47] (about a week ago) [13:47] anyone interested on an initramfs issue with hardy? or #ubuntu is the way? [13:47] if you're not running Upstart, you obviously can't do things like change the runlevel? [13:48] was there any change in hardy-updates within the last week ? [13:48] i dont need to ... i used to just run "reboot -fp" which should just trgger the kernel [13:48] no, no change [13:48] if you do reboot -f, you are just telling the kernel [13:48] but thats getting stuck ... so i looked at shutdown ... [13:49] if it's getting stuck, that's a kernel bug [13:49] ah, k so it must be a kernel issue [13:49] telinit and shutdown won't work, and I would be surprised if _they_ worked last week ;) [13:49] * ogra waits for smb then [13:49] who apparently built the new classmate kernel for colin last week [13:49] Keybuk, thanks that was the missing info :) [13:50] no, i never used or tried telinit or shutdown ... i just didnt understand why they exposed the msg [13:50] but its logical since i ont use upstart or normal init [13:59] jpds: yay, great to see buildd.py getting so many improvements :) [13:59] pitti: oh? where? [13:59] seb128: ubuntu-dev-tools 0.39ubuntu1 [14:00] ah good [14:00] one thing less to maintain personally in my ~/bin :) [14:01] * pitti kills the one on people.u.c. [14:03] * pitti sobs at the obviously broken listadmin [14:04] And I was looking at launchpad web pages to see buildd status, sigh [14:04] lool: buildd.py does that as well [14:04] I think I'll hack buildd to unset https_proxy though [14:04] pitti: Yeah, that's what I discovered! [14:04] I also have yet another wrapper giveback which calls buildd.py repeatedly with a set of packages [14:04] pitti: That I was stupidly browsing web pages instead of typing a command line! [14:04] but that's trivial [14:05] lool: wiki.ubuntu.com/Specs/GettingRidOfTheDesktop [14:05] pitti: EPAGE [14:06] broken listadmin? :( [14:06] just shows "nothing in queue" for all lists [14:06] ah, yes. [14:07] which made me first think "wow, thanks elmo for installing a great spam filter" [14:07] hahahaha [14:07] yes, that's what i thought, too [14:07] but when I actually looked at the web page, they are full with requests [14:09] who's Chris Coulson? [14:10] Keybuk: he's a bug triager, quite active currently [14:11] does he IRC? === apachelogger_ is now known as apachelogger [14:12] Keybuk: as ChrisCoulson [14:12] apparently [14:16] I may have a bug for you guys, this is ubuntu 8.04, and 8.10 with 1Gig of ram installed, Swap is being heavy used, alot of HD activity. ? [14:17] I know this isnt the support channel, but whats been changed since 7.10? [14:17] "almost everything" is a good guess [14:17] You installed and started the memory-hungry piece of software. [14:18] is there a way to reduce HD load, running a server like this, im ganna go through some HDś [14:19] I know the beauty of ubuntu, but ive never seen it be so HD heavy [14:19] ok, im going to debug a tool i think might be the problem and postbin you the outs.. [14:19]