[12:25] <shawn_work> Question: When is launchpad source code going to be released? will it be?
[12:27] <shawarma> Nothing's planned.
[12:27] <gnomefreak> shawn_work: best to ask in #launchpad (some of it is open)
[12:27] <shawarma> shawn_work: https://launchpad.net/faq <--- Search for "open source"
[12:27] <shawn_work> merci
[12:28] <shawarma> gnomefreak: Huh? Like what?
[12:28] <gnomefreak> shawarma: read the page you gave him ;)
[12:28] <gnomefreak> lol
[12:28] <gnomefreak> hold on ill find it
[12:28] <shawn_work> I See :(
[12:29] <gnomefreak>  Our goal is to release all of Launchpad as free software, though it will take some time (potentially, years) before that happens.
[12:29] <gnomefreak> We are doing so in a piecemeal approach. Parts of Launchpad have already been released as free software where they would be particularly useful to other projects. 
[12:29] <shawarma> gnomefreak: Yes, but which parts?
[12:29] <gnomefreak> shawarma: dont know never asked
[12:30] <illovae> hello
[12:30] <shawarma> gnomefreak: Ah, ok.
[12:30] <gnomefreak> hi
[12:31] <illovae> excuse me, LaserJock are you available please ?
[12:38] <LaserJock> illovae: yep, what's up?
[12:39] <illovae> LaserJock: hi, first sorry for my english but it is not my native language ^^'
[12:39] <illovae> well i'm Hari Seldon from https://bugs.launchpad.net/ubuntu/+source/labplot/+bug/98547
[12:39] <ubotu> Malone bug 98547 in labplot "incorrect category in 'Applications' menu" [Wishlist,In progress]  
[12:39] <LaserJock> oh hi
[12:39] <illovae> i've discuss of this bug with Adri2000 and mr_pouit and they told me there's nothing to fix...
[12:40] <illovae> i am an beginner in fixing so i don't know what can i do with this
[12:40] <illovae> i am interresting by you experience for closing it in the best way :)
[12:40] <illovae> your*
[12:40] <LaserJock> well, it's a bit of an unfortunate bug
[12:40] <illovae> ^^
[12:41] <LaserJock> technically, it should probably go in Education or Graphics
[12:42] <LaserJock> unfortunately early on I tried to tackle the "Science has no menu" problem
[12:42] <LaserJock> but it's really up to freedesktop.org
[12:42] <illovae> yes so for gnome there's no way for this bug
[12:42] <illovae> you have seen the .desktop for KDE are good
[12:43] <LaserJock> I infact did file a bug in Gnome about it
[12:43] <illovae> ah okay thanks, i didn't think to do it ^^'
[12:43] <illovae> so do i reject the bug ? if yes, how can i tell to close it ?
[12:44] <illovae> s/how/what
[12:44] <LaserJock> well, I guess we can reject it
[12:44] <illovae> "No fixing for ubuntu > bug reported upstream in GNOME ?"
[12:44] <LaserJock> I'm not happy about it
[12:44] <illovae> i understand, i'm not happy too
[12:44] <LaserJock> well, I think my Gnome bug was basically rejected too
[12:45] <illovae> arf
[12:45] <LaserJock> basically it seems to me that freedesktop.org has said that "Science" should be a submenu of "Education"
[12:45] <LaserJock> I should ask freedesktop about it I guess
[12:46] <LaserJock> anyway, for now, I think we should reject the bug
[12:46] <illovae> yes but you're agree it is not a good submenu "Education" for a science application :/
[12:46] <illovae> okay so
[12:46] <illovae> we don't make a .desktop for GNOME in the sources ?
[12:46] <illovae> or in the debian/ ?
[12:46] <LaserJock> not if it installs one already
[12:46] <illovae> a .desktop like > menu:Others ?
[12:46] <illovae> ah yes
[12:47] <LaserJock> no, in the .desktop we say something like Categories=Application;Science
[12:47] <LaserJock> it's just that basically Science = Other in the current menu
[12:47] <illovae> yes it's true
[12:47] <illovae> so it's a freedesktop.org problem i understand
[12:48] <LaserJock> to reject the bug you can click on the little arrow to the left of "labplot" under "Affects"
[12:48] <LaserJock> illovae: and I'm not sure it's one they see as a problem
[12:48] <illovae> arf :/
[12:49] <illovae> so i reject the bug and saying that : "Cannot fix this bug in Ubuntu - It's a bug/problem in the menu definition in freedesktop.org" ?
[12:51] <LaserJock> sure
[12:51] <LaserJock> illovae: check out http://standards.freedesktop.org/menu-spec/latest/apa.html
[12:52] <illovae> ah yes i saw it
[12:52] <LaserJock> notice that Science is a valid Category
[12:52] <illovae> yes
[12:52] <LaserJock> but it isn't in the "Main Menu" section
[12:53] <illovae> why there aren't a Education/Science category Education for main et Science for additional
[12:53] <illovae> ?
[12:53] <illovae> it would be the best ?
[12:54] <LaserJock> well, that's the part that is Gnome
[12:54] <LaserJock> Gnome doesn't do submenus
[12:54] <illovae> oups
[12:54] <illovae> yes :/
[12:54] <illovae> s/oups/ /
[12:55] <illovae> okay thank you for your help, just a little thing : can i quote your name in the bug reject ?
[12:55] <LaserJock> sure
[12:55] <illovae> okay thank you very much for your help, it was a real pleasure for me to discuss with you :)
[12:56] <LaserJock> no problem
[12:56] <LaserJock> anytime ;-)
[12:56] <illovae> :)
[01:48] <bdmurray> tepsipakki: ping
[02:46] <LeeJunFan> shouldn't the low-latency kernel have the hz timer set in /proc? by default the timer interrupts are turned off "0".
[02:50] <crimsun> the safe setting is preferred. You can always set it to 1.
[02:51] <crimsun> (does it really matter for idle, anyhow?)
[02:52] <LeeJunFan> crimsun: yeah, I just figure that most people expect the lowlatency kernel to give them low latency simply from installing it, but turning off interrupts is really turning of preempt isn't it?
[02:54] <ds> the tick rate is not related to kernel preemption
[02:58] <LeeJunFan> I don't think that corresponds to tick rate, it's just a 0/1 enable/disable. 0 is kernel interrupts are disabled.
[04:08] <derek_> is there any reason way a framebuffer isnt compiled into ubuntu kernel so we can have a bearable virtual terminal without recompiling the kernel..?
[04:09] <null__> derek_, i think it is compiled by default ?
[04:09] <null__> u should be able to just pass the vga= parameter to the kerenl opetion on bootup
[04:10] <derek_> what version of ubuntu
[04:10] <null__> i think all of the ones that have the ubuntu splash screen should support
[04:11] <derek_> vga=0F01
[04:11] <derek_> thats not with a frame buffer
[04:11] <null__> CONFIG_FRAMEBUFFER_CONSOLE=m
[04:11] <null__> that should be set in your kernel config
[04:11] <null__> check in /boot/config`uname -r`
[04:11] <mjg59> Because framebuffers mess up suspend/resume support
[04:12] <mjg59> If you pass a vga= argument to put the screen in a vesa mode, vesafb will be used
[04:12] <mjg59> But it's not going to be the default
[04:12] <null__> mjg59, really ?
[04:12] <null__> hmm i dont really have a proibme here 
[04:12] <null__> but i am running the 2.6.20-3 vanilla tho
[04:13] <mjg59> It works on some hardware
[04:13] <mjg59> But not all
[04:13] <derek_> when i switched from gentoo i could no longer use the virtual terminals because how bad they are
[04:13] <null__> oh oki
[04:13] <mjg59> If you want to have a framebuffer, pass the boot option.
[04:13] <mjg59> But, as I said, it's not going to be the default.
[04:14] <null__> ahkkk
[04:15] <null__> u need to have CONFIG_VGA_CONSOLE=y for the vesa buffer
[04:15] <derek_> they need to get out of usplash
[04:15] <mjg59> ?
[04:15] <null__> out of usplash ?
[04:15] <derek_> stop using it
[04:15] <null__> mjg59, i believe that is the present default for ubuntu
[04:15] <null__> for the vesa fb
[04:15] <mjg59> Ok. I will say this one more time, and then that is the end of the conversation.
[04:16] <mjg59> If you want a framebuffer, pass the vga= argument to the kernel. Then you will have vesafb, which is broadly equivalent to what gentoo uses by default. This will not be the default on a stock Ubuntu installation, as it tends to interfere with power management on a large number of systems.
[04:16] <null__> derek_, yeah i have disabled the usplash
[04:16] <mjg59> If you have a framebuffer, usplash will use the framebuffer.
[04:17] <mjg59> Otherwise it will make vesa calls directly.
[04:17] <null__> thats right
[04:18] <mjg59> null__: I wrote the software, I know it's right :)
[04:18] <_ion> :-)
[04:18] <mbiebl> mjg59: I always wondered, why usplash can use arbitrary resolutions.
[04:18] <null__> hehe 
[04:19] <mjg59> mbiebl: Because it uses code from svgalib to make direct vesa calls
[04:19] <mjg59> It can't actually do arbitrary resolutions, just ones that the vesa bios provides
[04:20] <mbiebl> mjg59: why is that safer (regarding suspend/resume) then using a fb directly? Just curious
[04:21] <mjg59> When you resume, you have no idea what state the video hardware is in
[04:22] <mjg59> The framebuffer that vesa gave you may no longer exist
[04:22] <mjg59> So writing to it isn't safe
[04:22] <mjg59> On the other hand, vga memory is basically specced to be there
[04:22] <mjg59> So it's not a problem to depend on it still existing
[04:22] <mjg59> The worst that can happen is that you get some garbage on the screen
[04:23] <mjg59> When usplash exits, it returns you to standard vga text mode (unless you're using a framebuffer, in which case it just exits)
[04:25] <mbiebl> Thanks for the clarification. So splashy, which relies on libdirectfb+a framebuffer is very likely to have more problems with suspend/resume.
[04:25] <mjg59> Yes
[04:25] <mjg59> That's why I wrote usplash
[04:26] <mjg59> libdirectfb simply doesn't provide the functionality we wanted
[04:26] <mjg59> And it was easier to start from scratch than to modify splashy to avoid the libdirectfb dependence
[04:27] <mbiebl> ok
[04:28] <mbiebl> Have you any plans to focuss more on uswsusp in the future?
[04:28] <mbiebl> So things like graphical suspend/resume work too.
[04:28] <mjg59> Yup
[04:28] <mjg59> The uswsusp package in our archive should Just Work
[04:28] <mjg59> Though I haven't had time to test it
[04:29] <mjg59> I'm trying to finish my PhD off at the moment, so I haven't had as much time as I'd have liked to work on this sort of thing lately...
[04:29] <mbiebl> ;-)
[04:30] <Hobbsee> morning all
[04:33] <bddebian> Heya Hobbsee
[04:34] <Hobbsee> hi bddebian :)
[04:34] <Mez> !seen keybuk
[04:34] <ubotu> Sorry, I don't know anything about seen keybuk - try searching on http://bots.ubuntulinux.nl/factoids.cgi
[04:35] <Hobbsee> [12:35]  [Notice]  -SeenServ- I last saw Keybuk (n=scott@yttrium.canonical.com) 10h 25m 53s ago, quiting: ""
[04:35] <Mez> I swear I saw keybuk tonight :D
[04:35] <Hobbsee> Mez: /msg seenserv seen keybuk
[04:35] <Mez> Hobbsee, already did that, ubotu used to do it for ou
[04:35] <Mez> I swear I saw Keybuk though :D hehe
[04:35] <Hobbsee> Mez: true.  hasnt done so for a long time
[04:36] <Mez> Hobbsee, and i haven;t used that functionality in a long time
[04:36] <Hobbsee> ahhh
[04:36] <Mez> I think I danced with keybuk tonight :D
[04:45] <Mez> I was at  gay bar
[04:45] <Mez> s/at  /at a /
[04:48] <Hobbsee> heh
[04:49] <StevenK> bddebian: Is that a pointy stick in your pocket or are you just really really pleased to see us?
[04:50] <bddebian> haha
[08:19] <janimo> cjwatson: hi, when you're around please let through xubuntu-meta, thunar and libxfce4mcs (the latter two are FTBFS related). thanks
[08:19] <janimo> crimsun: hi, libxfce4mcs alsoo needed .la removal
[08:21] <crimsun> janimo: ok
[08:21] <crimsun> that should be the last thing in the stack for xfdesktop4, then
[08:41] <janimo> crimsun: indeed. the last dev package using libstartup-notification-1.la seen by grepping /usr/lib/*a
[08:42] <janimo> crimsun: thunar does not use mcs so when I saw it had built I thoight it was only the gui4 lib
[10:30] <fabbione> Lathiat: ping?
[11:44] <ivoks> ok, debian will get zenoss packages
[11:44] <ivoks> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=361253
[11:44] <ubotu> Debian bug 361253 in wnpp "ITP: zenoss -- Zenoss is a powerful, integrated," [Wishlist,Open]  
[11:44] <ivoks> (ups.. wrong channel)
[11:45] <Robot101> it's a powerful integrated? I always wanted one of those :D
[11:46] <bhale> its a network management portal
[11:47] <bhale> it looks pretty good, but i spent the last 2 years writing my own
[11:47] <ivoks> :)
[11:48] <bhale> which takes some focus away from event dashboard onto automation
[11:49] <mdke> whoosh! the dvdcss script has been put back
[12:18] <alex__> can anyone help me with my sound card and wifi card? I'm usuing ubuntu feisty running on LG laptop
[12:18] <mdke> alex__: you can try #ubuntu or #ubuntu+1, or http://www.ubuntu.com/support
[12:19] <alex__> so what this channel is for?
[12:19] <pochu> alex__: development, not support
[12:19] <mdke> discussion of Ubuntu development
[12:20] <mdke> each irc channel has a topic you can read, at the top of your screen, which explains what the channel is about
[12:20] <alex__> what the disscusion is about? Ideas or help applying new things? requests?
[12:21] <mdke> discussion of specific problems that the developers have
[12:23] <alex__> so I still have two more questions if you don't mind
[12:23] <poningru> alex__: #ubuntu+1 is for you
[12:23] <poningru> dude...
[12:24] <alex__> it's not a suuport isue
[12:25] <alex__> ok, I get it. thanks anyway
[12:30] <Hobbsee> mdke: what do you mean?  (the dvdcss script)
[01:05] <Hobbsee> oh, found it.
[01:15] <Riddell> Mithrandir: new adept uploaded http://kubuntu.org/~jriddell/tmp/adept_2.1.2ubuntu25.debdiff
[01:19] <Lathiat> fabbione: pong?
[01:34] <Riddell> Lathiat: he's on holiday (as is almost everyone else)
[01:38] <StevenK> Mithrandir: New ipvsadm uploaded, debdiff is http://wedontsleep.org/~steven/ipvsadm.debdiff
[01:41] <Riddell> most inconvenient really
[01:42] <StevenK> Hopefully, cjwatson will notice.
[01:56] <cjwatson> StevenK: accepted
[01:56] <cjwatson> (I'm aware of everything else in the queue as of now, but haven't reviewed all of it yet due to aforementioned holiday)
[01:58] <StevenK> cjwatson: Thanks!
[02:00] <cjwatson> Riddell: accepted
[02:09] <Riddell> thanks
[02:10] <StevenK> Oh, you can tell when uploads are being held.
[02:10] <StevenK> The buildds just *pounce* on everything.
[02:46] <rouzic> Hi everybody
[02:47] <rouzic> https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/103413
[02:47] <ubotu> Malone bug 103413 in linux-source-2.6.20 "(Feisty) During boot, configuring network interface is very slow" [Undecided,Confirmed]  
[02:50] <robertj> can someone please look at https://wiki.ubuntu.com/SimpleSambaIntegrationSpec and tell me if that is a viable solution to the people who are filing bugs against samba "not working" when its just that they haven't created samba users
[03:22] <Lathiat> fabbione: ah wellhe pinged me a fewhours aho
[03:22] <Lathiat> err
[03:22] <Lathiat> Riddell: he pingedmea few hoursback
[03:22] <Lathiat> typing on these olpc keyboards is abit ofan art
[03:24] <shawarma> It must be if you mistype "Riddell" as "fabbione". 
[03:24] <shawarma> That's really... wow.
[03:27] <StevenK> Hah
[03:54] <mdke> :)
[03:59] <doko> cjwatson: please have a look at http://people.ubuntu.com/~doko/tmp/bash.debdiff
[04:00] <Tonio_> Mithrandir: I just uploaded dolphin for universe
[04:01] <Tonio_> Mithrandir: I put a patch so that it deals with kde ioslave, otherwise switching to it as default would break a lot of things on the desktop, including the kicker
[04:01] <Tonio_> Mithrandir: hope it is okay to be approved :)
[04:01] <Riddell> Tonio_: universe packages shouldn't need approved
[04:02] <Tonio_> Riddell: but they do....
[04:02] <Tonio_> This upload awaits approval by a distro manager
[04:02] <Riddell> oh, ok
[04:02] <Tonio_> I wouldn't ping here if that wasn't frozen too :)
[04:03] <StevenK> This is because selected components can't be subjected to the freeze. Otherwise main and restricted would freeze leaving universe and multiverse thawed.
[04:03] <geser> universe doesn't need approval like main but an archive admin must accepted them by hand
[04:04] <geser> after April 12th universe needs approval too (from motu-uvf?)
[04:07] <StevenK> geser: More than likely. What happened for Edgy was ubuntu-release picked a few universe people to say yay or nay
[04:22] <fabbione> Lathiat: re... sorry.. still around?
[04:54] <Lure_> Tonio_: universe is just on manual, not in approval-required yet
[04:55] <Tonio_> Lure_: hum okay
[04:55] <Tonio_> Lure_: so who will proceed ? :)
[04:56] <Lure_> Tonio_: archive-admins are doing them on regular basis (probably not as much today and over WE due to holidays)
[04:56] <Lure_> Tonio_: universe freeze is Apr 12, afair
[04:56] <Tonio_> Lure_: yup I noticed that concerning universe
[04:57] <Tonio_> Lure_: I'll just wait then :)
[05:05] <rmjb> hello, I'm looking for someone from the kernel team
[05:07] <Hobbsee> rmjb: it's a public holiday
[05:07] <kylem> not really...
[05:07] <kylem> rmjb, join #ubuntu-kernel
[05:07] <mjg59> Hobbsee: In parts of the world, yeah
[05:08] <Hobbsee> most of them, i thoguht
[05:08] <kylem> some of us don't care about non-secular holidays.
[05:09] <rmjb_> hi, sorry about that, my "reliable" isp just dropped my connection again, is there anyone from the kernel team here?
[05:09] <Hobbsee> kylem: well of course - but i would have thought the "any excuse for a holiday" applies
[05:10] <Hobbsee> kylem: no matter whether you agree in what it's for or not
[05:10] <mjg59> Hobbsee: You haven't seen a Canonical employment contract :p
[05:10] <Hobbsee> mjg59: true that.  it's about as bad as my work's, then?
[05:10] <mjg59> Well, Kyle's working, so we can make assumptions :)
[05:11] <sharms> Its not a holiday in the US thats for sure
[05:11] <Hobbsee> sharms: weird!  i thought it was.
[05:11] <kylem> Hobbsee, feh.
[05:11] <Hobbsee> hehe
[05:12] <sharms> ha
[05:13] <kylem> Hobbsee, no, almost everyone is off today.
[05:13] <Hobbsee> kylem: right.
[05:13] <Riddell> they're all skiving
[05:13] <Riddell> he's skiving :)
[05:15] <sharms> What holiday are we talking about? I am 90% sure there isnt once in US
[05:16] <Hobbsee> sharms: it's easter in a whole lot of countries.
[05:16] <sharms> ah that is sunday here?
[05:16] <Hobbsee> no idea
[05:17] <sharms> that is the day we lay easter eggs and go out in the yard and retrieve them
[05:17] <mjg59> It's Good Friday today
[05:17] <sharms> although for some reason since I stopped living at my parents, the easter bunny stopped coming
[05:17] <mjg59> More of a "Jesus being nailed to a cross" thing than an easter bunny one
[05:18] <sharms> I think that is discrediting the bunny
[05:18] <kylem> mjg59, is that the guy who founded your college? :)
[05:19] <mjg59> That lad, yeah
[05:22] <sharms> hey since we have a crowd today, does anyone know if gcc 4.2 is for sure going to be in feisty + 1?
[05:34] <Mirv> does anyone have an idea why the "Install" icon on the desktop does not show its translations? all the translations are there in the ubiquity-gtkui.desktop, so it might be possibly to fix this for feisty?
[05:35] <Mirv> hmm, it's translated under System/Administration menu, but if it's again added/copied to the desktop from there, it's shown as untranslated
[06:09] <Mirv> hmm hmm, it happens only on the live-cd, and for each item that is on the desktop. but it does not happen on an installed system. the translation are there in the menus. would someone have an idea in what part of the system the problem could be? I could try to find some relevant bug.
[06:10] <Mirv> there shouldn't be too many differences between a live system and an installed system, I gather
[06:16] <Mirv> well, I added the information to bug 45741 , and added nautilus to it (purely guessing)
[06:16] <ubotu> Malone bug 45741 in ubiquity "Ubiquity desktop icon "Install" is not translated" [High,Confirmed]  https://launchpad.net/bugs/45741
[06:36] <cjwatson> doko: I'm curious about why we're bothering to apply patches that claim not to even affect our system
[06:37] <doko> cjwatson: counts the patch counter up; I can leave it out, but then I have to modify the patch
[06:38] <cjwatson> doko: what's the release-critical bug you're trying to fix here? I've only skimmed the patch
[06:38] <cjwatson> doko: similarly for python 2.5.1rc1 - would like to know what release-critical bugs it's fixing
[06:38] <doko> cjwatson: bash? 
[06:39] <cjwatson> both
[06:39] <doko> cjwatson: ? yesterday you agreed to an UVF exception for python 2.5.1 ...
[06:39] <cjwatson> I did? it's been a busy couple of days ...
[06:40] <cjwatson> remind me what the reason you gave was
[06:40] <cjwatson> I think I may have been under the impression that you were updating from 2.5.1rc1 to 2.5.1, which would have been a different matter
[06:40] <cjwatson> (the more actual releases and the fewer release candidates, the better)
[06:44] <doko> wait, extracting the diffs for python2.5
[06:45] <doko> cjwatson: bash32-013 is one crash fix, that the same for readline5
[06:48] <doko> cjwatson: http://people.ubuntu.com/~doko/tmp/python2.5-changes , the locale.strxfrm fix already is in python2.4
[06:52] <sharms> Anyone want to help me get some action going on: https://wiki.ubuntu.com/Spec/EnhancedBash
[06:55] <cjwatson> doko: bash up to 013 is fine; 014 scares me as it changes parsing (possibly for the better, but I don't really want to risk it), and 015 doesn't apply to us as we have /dev/fd
[06:56] <cjwatson> doko: the python2.5 diff is huge; can we just have a targeted patch for the locale.strxfrm bug?
[06:56] <cjwatson> when I looked at the diff, it changed a lot more than what that release notes diff indicated
[06:57] <doko> wait, sending a diff of the two trees
 cjwatson: (sorry, wrong channel) would like to update python2.5 to the 2.5.1 release candidate 1 today; see bug 103302
 Malone bug 103302 in python2.5 "UVF exception for python 2.5.1" [Undecided,Unconfirmed]  https://launchpad.net/bugs/103302
[06:57] <doko> * illovae_ ist jetzt bekannt als illovae
 doko: ok, that's fine
[06:57] <ubotu> Malone bug 103302 in python2.5 "UVF exception for python 2.5.1" [Undecided,Confirmed]  https://launchpad.net/bugs/103302
[06:59] <cjwatson> doko: ok, sorry, I was obviously frazzled and misunderstood, plus the release notes diff you sent at that point was a lot less scary than the actual diff
[06:59] <cjwatson> score -1 for release notes
[06:59] <illovae> ?
[07:00] <cjwatson> illovae: ignore it, it's just a paste of an IRC log fragment
[07:01] <illovae> arf okay ^^ thanks
[07:08] <doko> cjwatson: http://people.ubuntu.com/~doko/tmp/python2.5.diff ; removed the PC build changes and the changes where just revision Ids are changed.
[07:10] <cjwatson> doko: I would prefer a fix for just the locale.strxfrm bug, if you don't mind
[07:10] <Lathiat> fabbione: am now
[07:10] <Lathiat> fabbione: 3 hours later again ;)
[07:11] <Lathiat> fabbione: feel free to just ask or email lathiat@bur.st
[07:11] <doko> cjwatson: I would really prefer the update to the rc1. mvo did have enough problems with pickling changes in 2.5
[07:12] <doko> s/changes/bugs/
[07:12] <cjwatson> are there bug numbers?
[07:13] <cjwatson> it would really help if you told me all the reasons at once :-)
[07:13] <cjwatson> rather than bringing up a new reason each time I have an objection
[07:13] <cjwatson> I don't have much time here
[07:13] <cjwatson> and I guarantee that mdz will be asking me why I accepted this
[07:17] <doko> cjwatson: the upstream bug numbers are mentioned in the NEWS file; the locale.strxfrm bug is debian #416931. we should know python upstream very well, that they don't introduce new stuff in point releases, plus in the past we always shipped with the current release or releae candidate
[07:17] <ubotu> Debian bug 416931 in python2.4 "python2.4: off-by-one bug in strxfrm() (causes information leak)" [Important,Closed]  http://bugs.debian.org/416931
[07:18] <cjwatson> doko: what's that timemodule change?
[07:18] <doko> 30% of the patch are documentation fixes
[07:18] <cjwatson> for the record, arguments that go "but upstream are really good" don't tend to go over very well with me :)
[07:19] <cjwatson> I knew about the locale.strxfrm bug. That's one line
[07:19] <cjwatson> ah, the timemodule change is Windows-only
[07:20] <doko> cjwatson: ifdef windows
[07:20] <doko> cjwatson: remove the IN.py diff; that's my mistake
[07:21] <cjwatson> see, the thing you uploaded is a 160929-line diff
[07:21] <cjwatson> the thing you're showing me now is 876 lines
[07:21] <cjwatson> which is it? :)
[07:22] <doko> Colin, ...
[07:22] <cjwatson> no, really, this is something I will be called on
[07:22] <cjwatson> you need to help me justify it
[07:22] <doko> cjwatson: the diff are the regenerated docs (debian/patches/docs.uue)
[07:23] <doko> - the removed debian/patches/svn-updates.diff
[07:23] <doko> I don't hide any diffs, the diff was meant to have a clear look at the changes
[07:24] <doko> there are about 200 diff lines doc changes
[07:26] <cjwatson> I'm not accusing you of anything, I'm just finding it hard to reconcile
[07:26] <cjwatson> copying the diff down now to try to get a better look locally
[07:28] <cjwatson> dinnertime, will continue to look later on
[08:06] <jabra> I have a debian package I would like to get updated in feisty if possible
[08:07] <jabra> the recent update is in debian unstable
[08:07] <robertj> ajmitch: can you look at https://wiki.ubuntu.com/SimpleSambaIntegrationSpec for 60 seconds and give me an initial good-idea bad-idea impression?
[08:29] <Adri2000> jabra: which component ? main, universe? is it a new upstream release or just an update of the package?
[08:30] <jabra> update to fix a bug
[08:30] <jabra> it is in universe
[08:30] <jabra> package is called pbnj
[08:30] <Adri2000> jabra: ok, then it's possible to request a sync
[08:30] <jabra> k
[08:31] <jabra> so should I just submit a bug for the request to sync
[08:31] <Adri2000> jabra: yes: https://wiki.ubuntu.com/SyncRequestProcess
[08:31] <jabra> cool thanks
[08:32] <jabra> will it be able to get into feisty ?
[08:33] <Adri2000> yes, if you do it now and if you get a developer to ack your sync request quickly
[08:33] <Adri2000> this is done by subscribing ubuntu-universe-sponsors to the bug, and/or asking in #ubuntu-motu
[08:34] <jabra> k
[08:45] <gnomefreak> bdmurray: good luck in -bugs. she will never leave you alone now :(
[08:46] <bdmurray> gnomefreak: thanks for the warning
[08:47] <gnomefreak> yw
[08:47] <bdmurray> maybe if I just don't respond now
[08:47] <cjwatson> doko: ok, I think I have resolved some of my confusion by realising that many of the changes were already present in debian/patches/svn-updates.diff
[08:47] <cjwatson> doko: it would REALLY have helped if you had just said that up-front, instead of making me try to guess
[08:47] <gnomefreak> good luck
[08:48] <cjwatson> doko: everyone on the release team is under a lot of pressure to make exactly the right decision at the moment
[09:05] <doko> cjwatson: I don't deny that; anyway, I'll have to leave now, trying to get internet access tomorrow or on Sunday. the readline5 patch is the same as the bash32-013 patch; is that one approved as well?
[09:06] <doko> I updated the python2.5 package on chinstrap:~doko/for-feisty
[09:26] <mdke> cjwatson: around?
[09:28] <mdke> or elmo, mako, sabdfl?
[10:56] <unfo> hi all, how do i forward a bug to an upstream devel mailing list so that list members can click "Reply to All" and replies will get into launchpad?
[10:57] <LaserJock> hmm, like for a specific bug?
[10:57] <unfo> LaserJock: yes, a bug in emacs-snapshot
[10:58] <LaserJock> I'm not exactly sure if that's possible
[10:58] <LaserJock> I think you can use <bug number>@bugs.launchpad.net
[10:58] <LaserJock> but I'm not sure if that's suitable for that kind of thing
[10:59] <unfo> if I email the bug report text to the list and CC <bug number>@bugs.launchpad.net, then when people Reply to All, will it get into lp?
[10:59] <unfo> or will that fail because they're not registered lp users?
[11:01] <LaserJock> I'm really not sure
[11:02] <LaserJock> you might have to ask the Launchpad people
[11:02] <unfo> ok, i'll ask on channel #launchpad.
[11:33] <Burgwork> unfo: it will fail, because LP only accepts signed mail
[11:33] <Burgwork> LaserJock: ^
[11:34] <unfo> Burgwork: oh. :(
[11:34] <Burgwork> and it needs the users key already, so they need an LP account
[11:34] <LaserJock> Burgwork: darn, figures
[11:34] <unfo> Burgwork: it seems from my experimentation that it silently ignores unsigned mail from both registered and not-registered users?
[11:34] <unfo> Burgwork: is that true?
[11:34] <Burgwork> likely
[11:35] <unfo> Burgwork: :( i should file a bug.  It sucks for it to silently drop mail.  It should always provide *some* response.  I wish Launchpad was fully open-source.
[11:35] <Burgwork> unfo: yes, yes, and yes
[11:36] <Burgwork> :)
[11:37] <unfo> Will all of launchpad really eventually be open-sourced, so I could, say, run a private copy of launchpad on my personal web server including malone, answers, and everything?
[11:37] <mdke> unfo: it used to send responses when mail was dropped, so you should file a bug
[11:38] <unfo> I've read the FAQ but I still don't understand if it will.
[11:38] <mdke> #launchpad is the better channel for launchpad discussion, though
[11:39] <mdke> I suspect the answer to your last question is that we don't know. Certainly it isn't ready to be run on various people's private servers at the moment
[11:39] <mdke> the intention, as you saw from the faq, is to make it open source
[11:40] <unfo> mdke: ah.
[11:40] <unfo> mdke: Burgwork: it seems it accepts unsigned comments by email from registered LP users, but it silently drops comment and new-bug emails from others.  I'll file a bug.
[11:40] <Burgwork> mdke: intention to make open source != actual timeline
[11:41] <mdke> Burgwork: I hope that I didn't suggest there was an actual timeline. it would surprise me if the devs have any idea about how to make it happen at the moment. Maybe they do though
[11:42] <Burgwork> mdke: I hope they do
[11:42] <mdke> I suspect they have been focused on 1.0 for a while now
[11:43] <mdke> without worrying about how to scale the concept to make it open-sourceable
[11:43] <mdke> but I think we should move channels
[11:46] <unfo> mdke: ok, moving to #launchpad.