[12:55] <ohmega_> is there a maintainer or something like that for the dapper distribution?
[12:56] <bhale> there are only Stable Release Updates, done by anyone, and security updates by security team
[12:59] <ohmega_> hm. i reported a bug a long time ago that causes dapper to fail to boot randomly, but persistentently once it has failed, depending on the number of free inodes you happen to have on your root filesystem.
[01:01] <ohmega_> i think it's kind of weird that this never got fixed.
[01:04] <ohmega_> or isn't that considered serious enough? it seems like most people who run into it have to reinstall since they can't figure out what went wrong.
[01:06] <ohmega_> LP: 37528
[01:06] <bryce> ohmega_: I haven't seen the bug you've described, but I know in general there's a number of pretty serious bugs in various open source projects, that ubuntu suffers from.  Ubuntu fixes as many as they can with the manpower they have, but they try to keep tightly to the regular release schedule 
[01:07] <bryce> I think the thinking is, rather than wait a long time to make a perfect release, to make a series of increasingly better releases on a reliable schedule
[01:07] <ohmega_> bryce: well, there is even a link to a patch in launchpad so this shouldn't be too tough.
[01:08] <Kmos> bug 37528
[01:08] <ubotu> Launchpad bug 37528 in klibc "Dapper: persistent boot failure - ext3 filesystem not detected" [Medium,Confirmed]  https://launchpad.net/bugs/37528
[01:08] <Mithrandir> looks easy enough to test.
[01:08] <Mithrandir> uh, fix
[01:08] <ohmega_> the fix is in edgy since it was fixed in upstream
[01:09] <jovans> hello it woud be nice when the ubuntu team prepare backport for Faisty thunderbird 2 i think Feisty's support is 18 Month. I don't want thunderbird-1.5-10ubuntu_1_"__$_% i want thunderbird 2
[01:09] <bryce> ohmega_: ok if it's a kernel thing, you should talk with BenC
[01:09] <Mithrandir> bryce: it's klibc.
[01:09] <ohmega_> it's klibc, not the kernel.
[01:10] <bryce> well the patch in that LP ticket is from kernel.org
[01:11] <ohmega_> the klibc repository is just on the same server
[01:11] <bryce> (I don't know who is in charge of klibc)
[01:11] <bryce> ok I'll shut up now.
[01:12] <Mithrandir> bryce: the kernel team, as of this cycle.
[01:13] <ohmega_> hm, isn't Dapper LTS, then there should be an LTS team or at least _someone_?
[01:13] <Mithrandir> ohmega_: no, there is not a single person dedicated to 6.06 maintenance.
[01:14] <mjg59> Mithrandir: Uh, I think that's a slightly unfortunate phrasing
[01:14] <mjg59> You make it sound like nobody carries out any LTS maintenance
[01:14] <Mithrandir> mjg59: true.  English is hard.
[01:14] <crimsun> s/not a/no one/
[01:14] <mjg59> ohmega_: LTS support is handled by the entire maintenance team, depending on who seems appropriate for a specific issue. There are no people who are dedicated to LTS support.
[01:15] <bhale> 'no single person' is pretty much what you meant
[01:15] <ohmega_> OK
[01:15] <Mithrandir> bhale: indeed.  I blame it being after 1 o'clock in the middle of the night.
[01:17] <ohmega_> So who should I talk to?
[01:22] <Mithrandir> I'll take a look at it tomorrow.
[01:22] <ohmega_> Nice :)
[01:22] <ohmega_> Thanks.
[06:10] <fabbione> morning guys
[06:11] <gouki> Hi
[07:32] <pitti> Good morning
[08:30] <siretart> anyone using ndiswrapper around?
[08:37] <dholbach> good morning
[08:42] <Mithrandir> pitti: what do you think about getting bug 64695 fixed in an SRU?  It's a one-line change.
[08:42] <ubotu> Launchpad bug 64695 in kdebase "If GDM is the default display manager KDE logout dialog is missing shutdown and restart options" [Medium,Confirmed]  https://launchpad.net/bugs/64695
[08:44] <pitti> Mithrandir: hm, title doesn't sound particularly urgent to me; those options are in gdm/kdm as well, and sometimes people don't see the logout dialog at all; but if it's confusing many people, I'm ok with it
[08:44] <pitti> Mithrandir: I'd like to see a patch before, though
[08:45] <Mithrandir> it's a regression though, which is mainly why I think it's reasonable to get it fixed.
[08:45] <Mithrandir> just a moment, I'll boot my laptop
[08:47] <pitti> I agree to the regression part
[08:48] <Hobbsee> it's certainly annoying, it seems
[08:51] <Treenaks> Hobbsee: yes, you can
[08:51] <Hobbsee> ah, good
[08:52] <Treenaks> you can also reboot.. don't know about suspend
[08:53] <pitti> Treenaks: sure, you can do that as well
[08:54] <Treenaks> pitti: I just close my laptop lid for suspend ;)
[08:54] <pitti> so do I :)
[08:57] <Mithrandir> pitti: http://err.no/patches/kdebase_fix_gdm_socket_path.diff is a debdiff
[08:57] <pitti> Mithrandir: aah, it's *that* change
[08:58] <pitti> Mithrandir: yes, I'm all for fixing that, since it also looks like a (very  small) DoS
[08:58] <pitti> and we did it for a bunch of other programs
[08:59] <pitti> Mithrandir: please mention the SRU bug # in the changelog, though
[09:00] <Mithrandir> pitti: sure, I just wanted to run it past you first.
[09:00] <pitti> Mithrandir: and a short explanation of the impact in the changelog would be nice, since it's read by many users
[09:01] <pitti> Mithrandir: thanks for prep'ing
[09:13] <Mithrandir> pitti: should I just upload it or do you want to see the debdiff before?
[09:13] <Mithrandir> Riddell: ^^ ; you should make sure to fix this in gutsy too.
[09:14] <pitti> Mithrandir: if you just beautified the changelog, just go ahead and upload it
[09:20] <Mithrandir> pitti: ok, uploaded.
[09:38] <mario> siretart, poke?
[09:39] <siretart> hi pygi 
[09:39] <pygi> siretart, I have three debdiffs for main, needed in feisty-updates and gutsy probably
[09:39] <pygi> possible? :)
[09:39] <pitti> Mithrandir: btw, the patch that you attached to bug 64695 is not at all about kde ;)
[09:39] <ubotu> Launchpad bug 64695 in kdebase "If GDM is the default display manager KDE logout dialog is missing shutdown and restart options" [Medium,Confirmed]  https://launchpad.net/bugs/64695
[09:39] <siretart> depends. your bug nos?
[09:40] <pygi> siretart, gksu, libgksu, and software-properties
[09:40] <pygi> ah, numbers!
[09:40] <pygi> sec :)
[09:40] <siretart> yes :)
[09:40] <Mithrandir> pitti: indeed.   That's what I get for not paying attention
[09:40] <pygi> siretart, I'll have a couple more coming in today :)
[09:41] <pygi> bug #66518
[09:41] <ubotu> Launchpad bug 66518 in gksu "[Edgy + Feisty]  Startup Notification broken" [Medium,Confirmed]  https://launchpad.net/bugs/66518
[09:41] <pygi> bug #111137
[09:41] <ubotu> Launchpad bug 111137 in software-properties "Software properties has duplicate gksu" [Undecided,Confirmed]  https://launchpad.net/bugs/111137
[09:41] <pygi> siretart, those ^_^
[09:41] <Mithrandir> pitti: thanks, fixed.
[09:41] <siretart> pygi: I don't think I'm the best qualified person to sponsor gnome SRU uploads, perhaps seb128 or someone can help out?
[09:42] <pygi> siretart, sure, I'll bug him then :P
[09:42] <pygi> when he's around :)
[09:42] <pygi> siretart, what about brasero fixes that I'll have ready today?
[09:42] <siretart> I just want to be sure that gnome upstream is informed, maybe they'll handle them in a point release. 
[09:42] <pygi> got it
[09:43] <siretart> pygi: your bugo to brasero?
[09:43] <pygi> bug #107499
[09:43] <ubotu> Launchpad bug 107499 in brasero "Brasero will not burn " [High,Confirmed]  https://launchpad.net/bugs/107499
[09:43] <pygi> one of them :)
[09:43] <pygi> that's universe tho
[09:43] <pygi> for now^_^
[09:44] <siretart> sure. please attach your debdiff. looks like brasero is looking for a not installed mkisofs, right?
[09:44] <siretart> oh, and we should fix it in gutsy first!
[09:44] <pygi> siretart, for gutsy, I'll have new packages ready today/tomorrow
[09:44] <pygi> (new release)
[09:45] <pygi> siretart, problem is that current brasero doesn't depend n-c-b, genisoimage, and wodim
[09:45] <pygi> siretart, sure, thanks. I'll attach my debdiff today
[09:46] <pygi> siretart, did you upload libburn 0.3.6 and libisofs 0.3.4 in gutsy? I'd need those for brasero
[09:47] <pygi> but oh well, I guess you should expect to see even more bug fixes over time :P
[09:47] <siretart> yes, libburn&libisofs is in my todo pipe for today
[09:47] <pygi> great, thanks
[09:48] <pygi> ergh, it was libisofs 0.2.4, not 0.3.4 o.O
[09:49] <siretart> ah, so only libburn is new, ok
[09:52] <pygi> nod ^_^
[09:53] <siretart> pygi: and you're going to stay with soname 4? ;)
[09:53] <pygi> siretart, ;)
[09:53] <pygi> siretart, as long as I don't break ABI, sure :P
[09:53] <siretart> great! :) - I'm going to rename the packages then, it will go through NEW therefore
[09:53] <pygi> siretart, great :)
[09:54] <pygi> siretart, now that I learned how to actually make it stay the same ... ^_^
[09:54] <siretart> pygi: what's up with libburn version 0.2-2. do we want to keep or replace it?
[09:54] <pygi> siretart, nah, 0.2 is three years old, not mine, and isn't working
[09:55] <siretart> ok, then let's break the world :)
[09:55] <pygi> siretart, you can remove every all the current libisofs, libburn and stuff we currently have in archives for gutsy
[09:55] <pygi> haha ^_^
[09:56] <pygi> ergh, for new brasero I need to pull a couple of patches from svn
[09:56] <pygi> that scsi lib is a bit unstable in the release :(
[09:59] <pygi> I'm afraid I gotta run soon, but I'll be sure to bug you later today
[10:01] <pygi> siretart, and please do tell seb I've got an idea how we can workaround that hal bug in n-c-b for gutsy until hal applies the patch in their BTS
[10:01] <siretart> pygi: I'd suggest you subscribe him to the relevant bugno
[10:02] <pygi> siretart, he is subscribed already, and he knows what I'm talking about ^_^
[10:02] <siretart> he'll see it then, I'm sure :)
[10:18] <siretart> pygi: libburn currently doesn't build on gutsy because of linux-headers b0rkage. will retry when its fixed. the packages themselves do build fine, I've just pushed my changes to launchpad
[10:18] <siretart> at least on debian/lenny
[10:50] <dholbach> pitti: I plan to upload a python-launchpad-bugs (source) to the archive soon - can you move that to main without a MIR? and maybe move bughelper to universe?
[10:51] <dholbach> (separate source package)
[10:51] <pitti> dholbach: of course; it's not new code after all
[10:52] <dholbach> a few changes are in there, but nothing earth shatterin
[10:52] <dholbach> g
[10:52] <dholbach> i'll let you know, when i uploaded it
[10:52] <dholbach> pitti: you rock
[11:23] <saispo> ho
[11:23] <saispo> s/ho/hi/
[11:23] <saispo> gutsy debootstrap will be backported to feisty ?
[11:23] <cjwatson_> saispo: yes; I tried to do it the other day but something's broken in Launchpad so it failed
[11:24] <saispo> ok, thanks cjwatson 
[11:24] <saispo> it's for building gutsy iso :p
[11:24] <cjwatson> in the meantime it's utterly trivial to build the source from gutsy
[11:24] <cjwatson> and don't even bother building a gutsy CD image; you're wasting your time
[11:25] <Mithrandir> or just copy the feisty script to gutsy.
[11:25] <Mithrandir> cjwatson: failed as in, wasn't accepted or failed to build?
[11:25] <cjwatson> Mithrandir: wasn't accepted
[11:25] <Mithrandir> hm, maybe the pockets aren't open yet?
[11:25] <cjwatson> looks like there's some .changes parsing which breaks on the ~ in the version number
[11:25] <cjwatson> no, it's much weirder than that
[11:26] <cjwatson> 09:25:20 DEBUG   Rejected:
[11:26] <cjwatson> 09:25:20 DEBUG   Mismatch in sourcefulness. (arch) True != (files) False
[11:26] <cjwatson> 09:25:20 DEBUG   Mismatch in binaryfulness. (arch) False != (files) True
[11:26] <cjwatson> 09:25:20 DEBUG   Sourceful upload without a diff or native tar
[11:26] <cjwatson> 09:25:20 DEBUG   Unsupported custom section name 'admin'
[11:26] <cjwatson> 09:25:20 DEBUG   Unsupported custom section name 'admin'
[11:26] <cjwatson> 09:25:20 DEBUG   Unable to find the dsc file in the sourceful upload?
[11:26] <Mithrandir> ugh, ok.
[11:30] <cjwatson> ah, the custom upload format checks are wrong
[11:30] <cjwatson> it thinks that priority "-" in a .changes file must mean a custom upload, whereas actually it can be produced by a source package that doesn't have Priority in the first stanza of debian/control
[11:32] <dholbach> pitti: uploaded :)
[11:57] <cbx33> kbrooks: so...onto the config problem....hi all
[11:57] <cbx33> eek
[11:57] <cbx33> ignore
[11:57] <cbx33> dholback pointed me here after I asked a question ;)
[11:58] <cjwatson> https://bugs.launchpad.net/soyuz/+bug/111202 describes the problem preventing debootstrap backports, FWIW
[11:58] <ubotu> Launchpad bug 111202 in soyuz "custom upload test is broken and catches some source packages" [Undecided,Unconfirmed]  
[11:58] <cbx33> my GSoC student mentioned it would be great if he and the other GSoC students could either blog on planetubuntu or have an ubuntu GSoC blog...so people could read about their progress
[11:58] <cbx33> is this a possibility?
[12:00] <cjwatson> cbx33: yes, that's been done before; any Ubuntu member can add to Planet Ubuntu
[12:00] <cjwatson> 'bzr checkout sftp://bazaar.launchpad.net/~planet-ubuntu/config/main/' and edit
[12:00] <cjwatson> ... and commit, obviously
[12:01] <cbx33> but some of these guys are not ubunutu members
[12:01] <cjwatson> they're not, but presumably the mentors are
[12:01] <cbx33> yes
[12:01] <cbx33> I am
[12:01] <cjwatson> well then
[12:01] <cjwatson> the mentor can add their student's feed and leave a comment in the file indicating that they're a GSoC student
[12:02] <cbx33> ahhh
[12:02] <cbx33> awesome
[12:02] <cbx33> is there a file for that?
[12:03] <Nafallo> cbx33: bzr branch :-)
[12:03] <cbx33> no no
[12:03] <cbx33> I meanthe comment
[12:04] <Nafallo> there is a bzrbranch for the config. just add a comment in there :-)
[12:08] <cjwatson> Nafallo: 'bzr checkout' is more convenient than 'bzr branch' here
[12:09] <cjwatson> (there's no point having a branch with a separate existence here; you want centralised revision control)
[12:09] <cjwatson> # Google Summer of Code student, mentored by kamion
[12:09] <cjwatson> [http://www.evalicious.com/blog/feed/] 
[12:09] <cjwatson> name = Evan Dandrea
[12:09] <cjwatson> nick = evand
[12:09] <cbx33> ok
[12:09] <cbx33> thats cool
[12:10] <cjwatson> e.g. - though this is no longer true and Evan's a member in his own right, so I'll change that
[12:11] <Nafallo> cjwatson: ah. right. I meant launchpad has a bzr branch though... :-)
[12:11] <cjwatson> ah
[12:50] <Riddell> Mithrandir, seb128: is that gdm fix in kdm a change in gdm upstream so it should go in kdm upstream too?
[12:52] <seb128> Riddell: what gdm fix in kdm?
[12:52] <cjwatson> the gdm socket path
[12:52] <seb128> kdm uses the gdm socket?
[12:52] <seb128> no, it's a distro change
[12:53] <Mithrandir> no, but the kde logout dialogue does.
[12:53] <Riddell> seb128: apparantly so, see Mithrandir's fix here http://librarian.launchpad.net/7474982/kdebase_fix_gdm_socket_path.diff
[12:53] <seb128> upstream uses /tmp/.gdm_socket
[12:53] <Riddell> right, ksmserver then
[12:53] <Riddell> seb128: why the change in ubuntu?
[12:53] <seb128> because /tmp is not secure
[12:54] <seb128> /var/run is the right location for the socket
[12:54] <Riddell> ok, let me know if that changes upstream (or you change it again in ubuntu) :)
[12:54] <seb128> will do
[12:54] <seb128> I did try to update package using it
[12:54] <seb128> I didn't think that KDE was looking for the gdm socket though :/
[12:55] <Riddell> it's a newish feature, it didn't used to
[12:55] <seb128> ok
[12:56] <Riddell> Mithrandir: how come feisty-proposed unapproved packages don't appear at http://people.ubuntu.com/~ubuntu-archive/queue/feisty/unapproved/ ?
[12:56] <cjwatson> it's a different queue
[12:57] <cjwatson> Riddell: I can make that be published
[12:58] <ogra> gs-job.c:110: error: 'EINTR' undeclared (first use in this function)
[12:58] <ogra> grmbl
[12:58] <cjwatson> unfortunately it's a bit expensive to publish the lot - connecting to the LP queue is pretty slow
[12:59] <StevenK> ogra: Known.
[12:59] <cjwatson> ogra: I posted to ubuntu-devel explaining this
[12:59] <StevenK> ogra: Although the FTBFS logs are pretty amusing.
[12:59] <ogra> cjwatson, ah, ok i thougt that was only for the buildds ... 
[01:00] <cjwatson> if you've upgraded to gutsy locally, you have the same problem
[01:00] <ogra> but indeed why should my pbuilder do better :)
[01:00] <Nafallo> ogra: you're working on that one? in that case, should I update DesktopTeam/TODO for you? :-)
[01:00] <cjwatson> the buildds are building the fixed linux-source-2.6.22 now
[01:00] <StevenK> cjwatson: Actually, I had a question about that. Did linux-source-2.6.22 1.5 actually fail to build due to the problem it is trying to fix?
[01:00] <ogra> Nafallo, whats that ? 
[01:00] <cjwatson> StevenK: yes, but it's been worked around
[01:00] <Nafallo> ogra: https://wiki.ubuntu.com/DesktopTeam/TODO
[01:00] <Nafallo> :-)
[01:00] <cjwatson> StevenK: (manual downgrade of linux-libc-dev in the buildd chroot)
[01:01] <StevenK> cjwatson: Ahhh. Sneaky. :-)
[01:01] <cjwatson> we knew that was going to happen
[01:01] <ogra> Nafallo, hmm, was that announced somewhere ? 
[01:01] <cjwatson> you hose the system compiler, you get to bootstrap :)
[01:02] <Nafallo> ogra: topic of -desktop atleast :-P
[01:02] <ogra> heh, well
[01:02] <Nafallo> ogra: that's where I found it :-)
[01:02] <StevenK> cjwatson: Yup. :-)
[01:02] <cjwatson> Riddell: http://people.ubuntu.com/~ubuntu-archive/queue/feisty-proposed/unapproved/ is there now
[01:02] <Nafallo> cjwatson: hi! care to sponsor new irssi? you were the last one on it :-)
[01:03] <Nafallo> http://home.nafallo.info/debdiffs/
[01:03] <Riddell> cjwatson: ooh, thanks
[01:03] <cjwatson> Nafallo: not especially :)
[01:03] <StevenK> Nafallo, cjwatson: I can do it, if you like.
[01:04] <Nafallo> StevenK: please :-)
[01:04] <ogra> seb128, any particular reason that gnome-power-manager is not on https://wiki.ubuntu.com/DesktopTeam/TODO ?
[01:04] <cjwatson> I have a load of performance reviews to do that I've been procrastinating - probably don't need more distractions ;)
[01:04] <seb128> ogra: the list is a copy of packages to which ones desktop-bugs is subscribed
[01:04] <ogra> ah, k
[01:05] <seb128> ogra: gnome-power-manager gets enough bug to justify having its own team ;)
[01:05] <seb128> especially than most bugs there are linux, acpi and other things not really desktopish 
[01:05] <ogra> lol, yes
[01:05] <Nafallo> seb128: then we might want to remove ekiga? isn't that the voip-team now? :-)
[01:06] <seb128> Nafallo: yeah, that's the goal, there is a discussion running on the mailing list
[01:06] <Riddell> ogra: gnome-screensaver looks compiled according to launchpad
[01:06] <Nafallo> seb128: right. no answers on your mail yet :-)
[01:07] <ogra> Riddell, ??
[01:07] <seb128> Nafallo: which one?
[01:07] <ogra> Riddell, who built a new package ? 
[01:07] <Riddell> ogra: I presume there's a new version somewhere though that I'm not seeing?
[01:07] <Riddell> ogra: nobody, it's just the version from feisty
[01:07] <ogra> should be 2.19.x
[01:07] <seb128> Nafallo: Ekiga mail sent on saturday
[01:07] <seb128> Nafallo: there is a voip team npw
[01:07] <seb128> now
[01:07] <Nafallo> seb128: "Call for Desktop Team contributors" :-)
[01:08] <Nafallo> seb128: seems to mention those teams in it :-)
[01:08] <seb128> Nafallo: there is a new Ekiga thread on desktop-list
[01:08] <vciaglia> hello *
[01:08] <seb128> anyway, lunch time
[01:08] <Nafallo> :-)
[01:08] <ogra> Riddell, thats an old version, i just built the package from the new upstream source on the weekend
[01:09] <Riddell> ogra: ok
[01:11] <StevenK> Nafallo: This has to wait for the new linux-libc-dev. If I uploaded it, it would get requeued, and I'd rather see it sucessfully build here first.
[01:11] <Nafallo> StevenK: oh. I built it before the b0rkage then... :-)
[01:11] <Nafallo> StevenK: or rather, aurora isn't updated ;-)
[01:12] <Nafallo> which is a GoodThing(tm) :-)
[01:12] <Amaranth> that reminds me
[01:12] <StevenK> Although the failure of "network.c:296: error: 'SO_REUSEADDR' undeclared (first use in this function)
[01:12] <StevenK> " does make me giggle.
[01:12] <Amaranth> since gnome-power-manager development is stalled will we have 2.18 or try to make the 2.19.x stuff work?
[01:13] <StevenK> Nafallo: Maybe imbrandon's mirror isn't updating?
[01:13] <StevenK> Nafallo: You mean you don't have a fast machine to build on sitting ~40cm to your right? :-P
[01:14] <Nafallo> StevenK: yes I do, but I'm to lazy to set up a pbuilder :-)
[01:14] <Nafallo> StevenK: I meant pbuilder-gutsy update isn't run for a while :-)
[01:21] <StevenK> Nafallo: I can throw you a base tarball and a set of scripts if you like. :-)
[01:22] <Nafallo> StevenK: hehe. I actually have everything needed to set it up, I'm just to lazy :-)
[01:22] <Nafallo> StevenK: and it would be i386 instead of amd64 and kind of pointless to do atm ;-)
[01:22] <Nafallo> StevenK: what I really need to do is to work some magic on the box :-)
[01:22] <StevenK> Nafallo: I can do both amd64 and i386.
[01:23] <Nafallo> StevenK: but you have amd64 as a base, right?
[01:23] <Nafallo> StevenK: my plan is to reinstall to amd64 and start playing with virtual instances :-)
[01:23] <StevenK> Nafallo: The base install on this machine is 64-bit, yes. I have a 32 bit chroot for mplayer.
[01:24] <lifeless> mmm, my new 64 bit machine is coming up well
[01:24] <lifeless> PITA migrating settings though
[01:24] <Nafallo> StevenK: fix it :-)
[01:25] <StevenK> I've been planning on.
[01:36] <mario> hi folks
[01:36] <pygi> seb128, around?
[01:39] <Nafallo> morning sabdfl 
[01:40] <pygi> o Nafallo is around again :P
[01:40] <Nafallo> pygi: always here, never says anything :-)
[01:40] <Nafallo> ;-)
[01:42] <pygi> Nafallo, ^_^
[01:43] <Nafallo> morning Keybuk :-)
[01:43] <Keybuk> morniing
[01:43] <pygi> ha, Keybuk !
[01:47] <sabdfl> moin moin Nafallo
[01:47] <Nafallo> sabdfl: that a wiki ;-)
[01:47] <sabdfl> have a wiki wiki day!
[01:47] <Nafallo> hehe :-)
[01:47] <Keybuk> sabdfl: you're up early
[01:48] <seb128> pygi: sort of, why?
[01:49] <sabdfl> Keybuk: my laptop clock says it's 50 to 1 in the afternoon!
[01:49] <sabdfl> erk
[01:49] <sabdfl> 12:49 PM, that is
[01:49] <pygi> seb128, I need three uploads to main (for now, will have more)
[01:49] <Keybuk> "50 to 1", that sounds like a gameshow
[01:49] <Mithrandir> sabdfl: your laptop believes you are in the UK, then. :-P
[01:50] <sabdfl> Mithrandir: so does a large part of my lizard brain
[01:50] <sabdfl> Keybuk: it is, and the bonus prize round is this afternoon ;-)
[01:51] <sabdfl> holy crap, whatever spellchecker Gaim uses doesn't know "prize"
[01:51] <sabdfl> that's an award-winning omission
[01:51] <pygi> sabdfl, submit a bug :P
[01:52] <StevenK> If you fold, you /quit, but then again it's very easy to keep a poker face.
[01:53] <pygi> seb128, just poke me when you are here completely. I have some things to discuss with you as wel
[01:53] <pygi> well*
[02:00] <sabdfl> wow, Ubuntu Weekly News is amazing this week
[02:03] <seb128> pygi: I'm around now, what do you want to discuss?
[02:03] <pygi> seb128, I have fixes for software-properties, libgksu, and gksu that I want in feisty. That's one.
[02:03] <seb128> please ping mvo about them
[02:04] <pygi> seb128, second, I've got an idea how can we temporarily workaround hal bug in n-c-b for gutsy until hal upstream fixes it
[02:04] <pygi> seb128, I will ^_^
[02:04] <seb128> or ping me on wednesday
[02:04] <pygi> nah, I'll bug mvo for that :)
[02:04] <seb128> I'm on holiday today and I don't want to spend the afternoon working ;)
[02:04] <pygi> ah! Ok, sorry then ^^
[02:04] <seb128> ah, cool
[02:04] <seb128> that's ok, I would not be on IRC otherwise ;)
[02:04] <pygi> the hal thingy can wait then ^_^
[02:05] <seb128> can't we get the hal patch used in gutsy?
[02:05] <pygi> seb128, we could, yes :)
[02:05] <seb128> something to discuss with pitti then
[02:05] <pygi> ok, ok :)
[02:05] <pygi> but I guess not today :)
[02:06] <pygi> I have a lot of patches targeting main ready, and a few more in preparation
[02:06] <seb128> just open bugs and attach them ;)
[02:06] <pygi> will see what I can do with gnomebaker in this cycle as well, since it's unmaintained
[02:06] <pygi> but I do have access to the upstream repository, so ...
 will see what I can do with gnomebaker in this cycle as well, since it's unmaintained
 but I do have access to the upstream repository, so ...
[02:11] <seb128> pygi: just take over it ;)
[02:11] <pygi> seb128, no point since brasero is actively developed and no time.
[02:12] <seb128> k, makes sense then
[02:12] <pygi> + the burning arena is bad since everybody wants everything, and nobody wants to contribute :P
[02:12] <saispo> hi all :)
[02:12] <pygi> but that's how everything is :)
[02:13] <seb128> lu saispo
[02:13] <pygi> seb128, we just need to make sure to iron some existing bugs. I hope the debian package can help there. texeira has a lot of patches in his package, perhaps I can roll them in and make a point release of GB.
[02:13] <pygi> need to mail him, he's trying to join ubuntu burning team
[02:13] <seb128> cool
[02:13] <pygi> seb128, o yes, I had another question :)
[02:13] <pygi> can we blacklist packages that we DON'T want imported from debian?
[02:13] <seb128> yes
[02:14] <pygi> great, who do I bug about that?
[02:14] <seb128> Mithrandir or cjwatson probably
[02:14] <pygi> ok, thanks
[02:14] <Mithrandir> pygi: sure, which one?
[02:14] <pygi> Mithrandir, brasero for now
[02:15] <pygi> Mithrandir, their packaging is very ugly, don't want them to ruin the work we did here
[02:15] <Mithrandir> blacklisted
[02:15] <pygi> thanks
[02:16] <pygi> I hope new brasero will fix a lot of bugs we have, it should at least
[02:18] <pygi> well, enough of bugging for now
[02:18] <pygi> thanks seb128 and Mithrandir 
[02:19] <seb128> no problem ;)
[02:24] <cjwatson> dholbach: at-spi in gutsy as Maintainer: Maintainer: Ubuntu Accessibility Developers <ubuntu-accessibility-devel@lists.ubuntu.com>
[02:24] <cjwatson> s/as/has/
[02:25] <doko> pitti: please promote the gfortran and gfortran-4.1 binaries to main
[02:25] <dholbach> cjwatson: thanks, will fix that
[02:25] <pitti> doko: ugh, fortran in main?
[02:26] <doko> pitti: gutsy goal, and you already did move gfortran-4.2 to main ;-p
[02:26] <dholbach> fixed
[02:26] <cjwatson> pitti: g77 has always been in main
[02:27] <ogra> we already have gutsy goals ? 
[02:27] <cjwatson> pitti: this is just replacing that ...
[02:27] <cjwatson> ogra: for the toolchain, yes
[02:27] <ogra> ah, right
[02:27] <pitti> dholbach: alright, thanks; promoted
[02:31] <dholbach> pitti: thanks A LOT
[02:32] <Amaranth> doesn't gfortran break ABI?
[02:32] <dholbach> pitti: the API is still the same - I'll notifiy you if there are changes
[02:32] <pitti> dholbach: erk, sorry, that was supposed to go to doko
[02:32] <pitti> dholbach: I'll handle your's in a bit
[02:32] <dholbach> ah ok
[02:32] <dholbach> pitti: take your time
[03:03] <zyga> hello, has anyone noticed any regressions with regards to python2.5 and gettext under feisty with default language packs?
[03:03] <zyga> it seems tht lp patch breaks translation lookup as lp takes precedense over anything else
[03:04] <zyga> lp == langpack patch
[03:05] <Fujitsu> lp == launchpad, so best not to use that abbreviation in that context.
[03:06] <pygi> pitti, be prepared for hal bugging :P
[03:06] <zyga> ok
[03:06] <pitti> pygi: no problem; poke me about it, I'm slow ATM with keeping up to date in Malone 
[03:07] <pygi> pitti, no worries, I have some patches that we'll need for now in gutsy
[03:08] <zyga> pitti: do you know who patched python2.5 to grok language packs?
[03:08] <pitti> zyga: not off-hand, can you please check the changelog?
[03:08] <zyga> oh, good idea!
[03:10] <zyga> doko did
[03:10] <zyga> and mvo wrote it initially
[03:10] <zyga> :-)
[03:19] <zyga> hmm, it's buggy all right, I can reproduce it now :)
[04:03] <pitti> dholbach: p-lp-bugs NEWed into main; it shouldn't need binary/NEW
[04:03] <Hobbsee> hiya pitti 
[04:03] <siretart> pygi: do you happen to have some brasero 0.5.0 package for my to try?
[04:05] <Mithrandir> hiya Hobbsee
[04:06] <Hobbsee> hey Mithrandir!
[04:07] <Solarion> so, what do I need to do to figure out why gnome-panel is eating my RAM for breakfast?
[04:08] <Solarion> I'm capable of fixing and providing patch, but I want to find where that sucker is lurking, and I am not certain how to get a stack trace from it
[04:10] <Hobbsee> no idea, sorry.  seb128/dholbach should know, but arent here
[04:10] <Hobbsee> or some others
[04:11] <Solarion> I also can't get a crash report out of OOo 2.2; is there something I need to enable to get it?  It just pops a file recovery dialog
[04:13] <Solarion> if anyone knows, please msg me and I'll read it when I get back to the kb.
[04:13] <Solarion> like I said, I'll fix it if I can get some help to do so.
[04:14] <Solarion> and as a bonus, I'll be that much more able to help fix bugs in the future, so it's a win-win.
[04:15] <Solarion> Hobbsee: thanks for your response at least.  It's better than I've gotten for a while.  :(
[04:16] <cjwatson> doko: can you point Solarion in the right direction?
[04:19] <doko> Solarion: when do you see this crash?
[04:23] <sladen> wow, a Simira.
[04:23] <Hobbsee> yay, Simira!
[04:30] <dholbach> Solarion: I'd install the relevant -dbgsym packages (http://wiki.ubuntu.com/DebuggingProgramCrash) and use valgrind to find out what happens (http://wiki.ubuntu.com/Valgrind)
[04:30] <sbalneav> elmo: Quick question for you, does the Canonical asterisk server support video connections via ekiga?
[04:30] <dholbach> Solarion: also, can you try if it happens with a new user?
[04:31] <Hobbsee> heya dholbach 
[04:31] <dholbach> hey Hobbsee
[04:33] <smithj> so the file(s) /usr/share/doc/splat/copyright - do you have some magic policy to put those there, or is it a manual process for every package?
[04:34] <Hobbsee> smithj: it's sourcedir/debian/copyright, for each sourcepackage, which is done manually for every source package.
[04:34] <Hobbsee> (it's installed automatically, yes)
[04:34] <smithj> so how do you keep it up to date if the license changes? just update manually?
[04:35] <Mithrandir> yes
[04:35] <smithj> i was kind of hoping there was some magic method already in existance to do it without manual munging :)
[04:35] <Hobbsee> nope
[04:35] <smithj> ok, thanks all
[04:37] <elmo> sbalneav: err, I don't know to be honest, AFAIK, no one's ever tried
[04:48] <pygi> siretart, brasero 0.5.0? hm?
[04:48] <pygi> why?
[04:50] <pygi> (sorry, was away
[04:50] <pygi> )
[04:52] <ogra> cjwatson, do you have the ubuntu-server-thin-client spec on LP somewhere ? i'd like to subscribe to it 
[04:53] <ogra> (and i know a bunch of others that are intrested)
[04:53] <cjwatson> ogra: we haven't gone through and registered everything from the core schedule on LP yet
[04:53] <ogra> ok
[04:53] <cjwatson> though since you're listed as an attendee on that on the core schedule, we'll probably subscribe you in the process
[04:53] <pygi> siretart, I'll look around, perhaps I've got them somewhere
[04:53] <pygi> siretart, once you're back ,poke
[04:59] <siretart> pygi: oh, I just looked at the brasero page and noticed that 0.5.0 seems to be the current upstream version
[04:59] <siretart> pygi: I tought I could give braser a try with the new libburn
[04:59] <pygi> siretart, which page?
[04:59] <siretart> pygi: http://perso.orange.fr/bonfire/
[04:59] <pygi> I think you were looking at wrong page siretart ^_^
[04:59] <pygi> siretart, I'll have new packages ready with libburn & libisofs in two days
[04:59] <siretart> first google hit. what would have been the correct one?
[05:00] <pygi> siretart, he correct one?
[05:00] <pygi> ergh
[05:00] <pygi> sec
[05:00] <pygi> siretart, http://www.gnome.org/projects/brasero/
[05:00] <pygi> please allow me to package those, I think I'll need to include a couple of patches
[05:00] <pygi> + it's my job to do those anyway :P
[05:01] <pygi> well, not job, but heh
[05:01] <pygi> siretart, 0.5.90 supports newest libburn and libisofs
[05:06] <Enola_Gay> hi all
[05:07] <Enola_Gay> Is there any replacement for the xserver-xorg-core-dbg in Feisty?
[05:07] <Enola_Gay> Xserver seems to have no dbg packages anymore at least I find no one.
[05:09] <tkamppeter> pitti, ping
[05:10] <Enola_Gay> tkamppeter: Do you know if there is a replacement for xserver-xorg-core-dbg in Feisty? I ask because you seem to be the one of the modesetting bug report.
[05:11] <Enola_Gay> I would like to create a crash dump of X but the Debian Wiki entry doesn't work for Ubuntu.
[05:20] <siretart> pygi: superb!
[05:21] <siretart> pygi: do you manage these packages in bzr? if so, please push them to your team's branches
[05:21] <siretart> s/your/our/
[05:21] <pygi> siretart, I don't, but I could ^_^
[05:22] <pygi> I guess if that'll help us test bzr builddeb stuff, I could play around a bit with it
[05:25] <Enola_Gay> cu all
[05:26] <mrmonday> Hi there, Are there any developers who would be interested in doing an article on how ubuntu is developed for fullcirclemagazine?
[05:28] <siretart> pygi: ok, just ping me again if you have some working packages
[05:29] <pygi> siretart, ofcourse :)
[05:34] <mrmonday> no takers?
[05:37] <codingmaster> Hello Ubuntu Developers!
[05:37] <codingmaster> I am participating this year in the Summer of Code for Ubuntu.
[05:37] <codingmaster> I am working on the Ubuntu Firewall Configuration.
[05:37] <codingmaster> I hope you can help me by adding suggestions for a good project name, using this wiki:
[05:37] <codingmaster> https://wiki.ubuntu.com/UbuntuFirewallConfiguration/Name
[05:37] <codingmaster> Thanks in advance to all of you!!!
[05:38] <pygi> codingmaster, Indpap ^_^
[05:38] <pygi> codingmaster, and it's you again :)
[05:38] <codingmaster> hey :)
[05:39] <codingmaster> would be great to see some suggestions from you all in the wiki :)
[05:39] <tkamppeter> Enola_Gay: I don't know, I have reported the i810-modesetting bug. The problem was that the standard i810 driver needs a high effort of manual configuration to work with not so common resolutions, and the proposed solution was to use i810-modesetting (which works for me), but there was nothing in my problem which has to do with xserver-xorg-core-dbg. Later on people talked about crashes of i810-modesetting, but I have nothing to do wit
[05:39] <tkamppeter> h that.
[05:39] <Solarion> *sigh*  how does Network-Manager do authentication?
[05:39] <mjg59> With wpa_supplicant
[05:39] <pygi> Solarion, wpa_supplicant
[05:39] <Solarion> It seems to totally forget that the AP requires Dynamic WEP inbetween bouts
[05:39] <pygi> codingmaster, I just told you an idea :P
[05:39] <Solarion> which is a problem if there's low signal
[05:40] <Solarion> heya mjg
[05:40] <codingmaster> @pygi: I know
[05:40] <Solarion> who is in charge of determining what method to use then?
[05:41] <Solarion> does N-M tell wpa_supplicant to auth using method foo, credentials bar, or does wpa_supplicant remember these things and is failing to remember correctly?
[05:41] <mjg59> N-M tells it things
[05:41] <Solarion> between the two of 'em, someone is forgetting
[05:41] <mjg59> To the best of my knowledge, anyway. The interaction is complicated.
[05:41] <Solarion> (from googling, it sounds like the APs are misconfigured.  It's shocking, I know, but it's the way it is)
[05:41] <Solarion> where should I go to push this further?
[05:42] <Solarion> 'cause this annoys the heck outta me
[05:44] <pygi> submit a bug, but n-m is a bit ...
[05:44] <pygi> :-/
[05:44] <Solarion> there's already a bug, which needs some love
[05:44] <pygi> codingmaster, how's the coding going?
[05:44] <pygi> Solarion, sadly I don't wanna play with n-m bugs anymore ... I did it for dapper too much
[05:45] <pygi> hi jdong 
[05:45] <Solarion> pygi: who else is doing it?
[05:46] <pygi> Solarion, dunno (I do actually, just not sure it's the right time for bugging right now ^_^)
[05:46] <Solarion> pygi: "right time for bugging" means what?
[05:46] <codingmaster> @pygi: hacking on python :) with gtk :)
[05:47] <pygi> Solarion, means vacation :p
[05:48] <Solarion> ah.  Well, queue it up then or something.  If I find a solution, I'll post a patch
[05:48] <Solarion> pygi: where would I look in the source for the decision-making portion of things?
[05:48] <pygi> Solarion, out of hand, no idea, sorry 
[05:48] <pygi> it's a bit more complicated then that I'm afraid
[05:49] <Solarion> hervorragend
[05:49] <Solarion> is there a n-m channel?
[05:51] <pygi> Solarion, nop
[05:51] <Solarion> well, that sucks
[05:52] <pygi> there is mailing list for n-m tho
[05:52] <Solarion> I've got enough mailing lists in my life.  :(
[05:54] <Solarion> If I have to enter all of my craptastic auth information one more time, I'm gonna scream.
[05:54] <Solarion> I think it's now 10 or 15 times in half an hour
[05:56] <Solarion> is odd, because sometimes it seems to re-auth; sometimes it doens't.
[05:56] <pygi> well, I use personally created shell script
[05:56] <Solarion> 11/16
[05:56] <pygi> that seems to do the trick :P
[05:58] <Solarion> 12/17.  shell script that does what?
[06:00] <Solarion> 13/18.  shell script that does what?
[06:03] <sn0> mrmonday im not a developer but just incase you haven't got a reponse, this might not be the best place to ask , maybe post on the mailing list(s) to get it seen
[06:07] <mrmonday> sn0, I have had a response thanks
[06:07] <sn0> mrmonday no prob, would be nice to see an article :)
[06:11] <Solarion> so, what are the chances of getting 2.6.21 (dynticks) in feisty?
[06:11] <Solarion> or do I have to DIM (Do It Myself)
[06:12] <mrmonday> sn0, keep your eye on the fullcirclemagazine site, 
[06:13] <sn0> already doo thx mrmonday :)
[06:21] <Solarion> I think it's 20/25.  :(
[06:22] <bddebian> Heya
[06:30] <keescook> pirast: 110066> thanks, I've approved the nominations (still working through a big back-log of stuff...)
[06:31] <jdong_> !omgjdong
[06:31] <pygi> :P
[06:31] <ubotu> jdong: You're going to hell.
[06:31] <jdong_> grr wrong channel
[07:32] <mquy> hello
[07:35] <mquy> can anyone tell me how to become an Ubuntu developer?
[07:35] <infinity> -> #ubuntu-motu
[07:35] <mquy> thanks
[07:36] <geser> infinity: any progress on the xmms2 build failure (bug #87077)?
[07:36] <ubotu> Launchpad bug 87077 in launchpad-buildd "The build of xmms2 fails because of HASH(0x82db558)="" in the environment" [Undecided,Unconfirmed]  https://launchpad.net/bugs/87077
[07:37] <infinity> geser: Haven't looked at it for a while, was far too concerned with releasing feisty and opening/bootstrapping gutsy, etc.
[07:58] <thomS> Are the yellow popup bubbles (e.g for NetworkManager applet) part of the GTK toolkit or something Ubuntu have added themselves?
[07:59] <geser> afaik it's done by libnotify1
[08:59] <mthaddon> Launchpad is going down in 15 mins for a code update. Estimated downtime is 10 mins or less.
[09:11] <pirast> keescook, great, thanks
[09:12] <jdong> hmm... why does ssh <command> cause remote command to hang when local ssh is killed?
[09:13] <jdong> I would expect / desire the remote command to be killed when connection is severed
[09:18] <shawarma> jdong: It'll probably die once it tries to write something to the client (SIGPIPE magic).
[09:18] <Kmos> bug 105859
[09:18] <ubotu> Launchpad bug 105859 in app-install-data-commercial "Opera 9.2 is out with many bug fixes" [Undecided,Confirmed]  https://launchpad.net/bugs/105859
[09:19] <jdong> shawarma: good idea!
[09:20] <shawarma> jdong: You could also pass '-t' to ssh. That makes it allocate a controlling terminal on the server in effect sending the ctrl-c (if that's how you kill it) down the line make it send SIGINT to the remote app rather than your local ssh client.
[09:21] <jdong> shawarma: yet another good idea :D
[09:22] <shawarma> jdong: Heh. It looks like it worked. :-)
[09:22] <jdong> lol don't get excited too fast :D
[09:23] <jdong> shawarma: the ssh -t flaw.. can't pipe from it...
[09:24] <jdong> but I think I have an idea why SIGPIPE isn't caught
[09:25] <jdong> AHAHAHA
[09:26] <jdong> yep... catching IOError too broadly is not a good idea
[09:51] <robertj_> are packages in commercial tracked in launchpad as well?
[09:51] <Kmos> robertj_: you need to set it to package: app-install-data-commercial
[09:56] <mario> anyone around willing to be bugged for a few secs?
[09:56] <robertj_> are vmware-server's deps messed up? it claims to depend on libssl .9.7 but .9.8 is what is in feisty
[09:57] <robertj_> also the kernel modules package doesn't seem to provide appropriately
[09:57] <mario> jdong, poke? :)
[09:58] <jdong> mario: sup?
[09:58] <mario> jdong, mind checking for me in brasero deps if it doesn't have wodim && genisofs or nautilus-cd-burner dependency?
[09:59] <jdong> which brasero?
[10:00] <mario> jdong, the one in feisty
[10:00] <jdong> libnautilus-burn4,
[10:00] <jdong> that's the only burning related dep I see
[10:01] <mario> jdong, oki, that means it's wrong :P
[10:01] <jdong> lol
[10:01] <mario> thanks, I thought I was hallucinating
[10:02] <agraveley> hi. so i'm getting the feeling something on my machine has a May1 backdoor programmed in ;-)
[10:03] <mario> agraveley, why? :)
[10:03] <mario> jdong, ^_^
[10:03] <agraveley> i'm getting "BUG: soft lockup detected on cpu#0!" on booting both latest 2.6.11 and older 2.6.10
[10:03] <mjg59> 2.6.11? Your life must suck.
[10:03] <mario> latest 2.6.11 o.O
[10:04] <mario> ergh, mjg59 beat me :P
[10:04] <agraveley> the only thing that's worked is disabling the wireless in the bios
[10:04] <mario> jdong, pm
[10:04] <mjg59> agraveley: ipw3945? Known bug, fixed in later versions of the driver.
[10:04] <agraveley> err, sorry!  2.6.17-11.  both this kernel and the older 2.6.17-10 worked fine until this morning
[10:05] <mario> hehe :)
[10:05] <mario> any updates this morning?
[10:05] <agraveley> nope
[10:05] <mjg59> agraveley: It's the temperature calibration routine in the driver
[10:05] <agraveley> wouldn't explain the older kernel not working too
[10:05] <mjg59> So, yeah, it's plausible that weather changes will affect it
[10:05] <mjg59> Computers are great
[10:05] <agraveley> omfg, you're kidding! :-)
[10:06] <Kmos> agraveley: update to feisty =)
[10:06] <Kmos> *upgrade
[10:07] <agraveley> is there an easy way to get newer kernels without upgrading just yet?  we're very close to a software freeze.
[10:07] <mjg59> agraveley: My recollection is that the hardware may block for some time before calibrating fully. Older versions of the driver would spin while this was happening, and the kernel detects this as a hang
[10:08] <mjg59> If you leave your machine for long enough, it /might/ carry on booting anyway, though I'm not sure of that
[10:08] <agraveley> mjg59: it's san francisco!  every day is the same! so that doesn't seem likely ;)
[10:08] <mjg59> agraveley: Dude, it rained on me there last week. Don't tell me it's /always/ the same.
[10:08] <agraveley> oh interesting.  maybe i've always just happened to leave it alone long enough?
[10:08] <mjg59> As I said, environmental factors may affect it
[10:09] <mjg59> You'll probably need the initramfs-tools as well, but if those dependencies are satisfied you ought to be good
[10:10] <ogra> probably udev too
[10:10] <ogra> no ?
[10:17] <agraveley> sweet! feisty has tomboy 0.6.3.
[10:17] <bhale> hi, agraveley 
[10:18] <agraveley> howdy :)
[11:11] <agraveley> hey.  okay, the kernel update fixed the boot halt problems, but wireless no longer works.  i'm seeing "Kill switch must be turned off for wireless networking to work.", but wireless is certainly turned ON in the bios (otherwise i didn't see the problem at all)
[11:12] <agraveley> this is on an IBM x60
[11:12] <agraveley> anyone have advice?
[11:13] <mjg59> agraveley: And the kill switch on the front of the laptop is switched on?
[11:13] <mjg59> agraveley: Oh!
[11:14] <agraveley> WHOA
[11:14] <mjg59> agraveley: Now that you mention that - the bug only manifests itself when the kill switch is on, as far as I remember
[11:14] <mjg59> agraveley: So what changed was probably that you flicked that switch accidently...
[11:14] <agraveley> wait wait wait
[11:14] <agraveley> WHO PUT A SWITCH THERE?!
[11:14] <mjg59> Alex loses
[11:15] <agraveley> hah.  this is comical.  rebooting again.
[11:26] <pochu> hey all! any archive admin can give back wxwidgets2.8? it failed to build because of that kernel issue.
[11:26] <pochu> https://beta.launchpad.net/ubuntu/+source/wxwidgets2.8/2.8.3.0-0ubuntu1
[11:32] <agraveley> moral of the story: know where all the poorly placed switches are on your laptop, bozo.
[11:33] <agraveley> thanks guys :-)
[11:55] <pygi> siretart, around?