=== hexmode` is now known as hexmode [00:55] is there a place to ask questions concerning the ubuntu building process, possibly here? [00:55] more precisely, questions regarding package building as done in Ubuntu. [00:55] cosmodad: You could try here. Depending on the question, it may be the right place. [00:56] persia: ok let me shoot. [00:56] I'm trying to add a patch to the thunderbird packages but already trouble with CDBS and quilt. [00:56] I suspect for that, you want #ubuntu-mozillateam [00:57] persia: likely, but I suspect my question to be more of a general nature. [00:57] OK. Try again then :) [00:57] heh ok [00:57] I apt-get source'd the thunderbird source package which comes with a tarball'ed copy of the upstream source... [00:58] in order to see how quilt works, I unpacked the tarball and tried to push the first patch using `quilt push'. [00:58] when I try so, however, I get a "can't find file to patch at input line X" error. [00:59] Ah. Packages with built-in upstreaam tarballs can be tricky. [00:59] persia: is there something wrong with my approach? [00:59] I don't think there is a quilt-edit-patch script (but I could be wrong). [01:00] even if not, shouldn't a plain quilt push work anyway? [01:00] You'll need the unpacked, and patched source somehow, to create your patch. I'm not sure of the standard way of generating that for thunderbird. You likely do want a hint from #ubuntu-mozillateam, but your basic approach is correct. [01:00] ok. [01:01] persia: thanks for the starter, I'll try the mozilla branch of Ubuntu next. [01:03] cosmodad: In general, you want to have the patched source (just apply all the patches in quilt), a quilt add, a quily push, a quilt refesh, unpatch everything with quilt, and try a build. The only tricky part is making sure you prepare the patched source the same way it is usually prepared. [01:04] persia: the "just apply all the patches in quilt" is what bugs me. I can't even tell quilt to apply the very first patch. [01:05] seems to me like some more preparation work needs to be done before quilt push can work, but I can't find anything. [01:06] Hmm. Let's try automation... [01:06] !patch [01:06] Patches are files describing the changes in code to achieve some results. There are a number of ways these can be produced, but https://wiki.ubuntu.com/Bugs/HowToFix and https://wiki.ubuntu.com/PackagingGuide/PatchSystems may provide some useful guidelines. [01:06] Yep. See the second link ubotu provided. Should be some hints on using quilt. [01:07] cool, I'll take a look. [01:29] persia: ok I'm doing some progress. However, I couldn't resolve the following quilt question yet, maybe you can help me out: how'd I tell quilt that file foo.diff includes a patch file already? [01:30] persia: seems to me that quilt's purpose is to filter out diffs by difference between an edited version and the original only. [01:30] cosmodad: You'd be better asking generally. I have to leave now. I believe you just reuse the current patch as the patch name, but I don't remember precisely. [01:30] persia: ok, thanks for helping. [01:36] cosmodad: you certainly can tell quilt to apply the very first one. [01:37] crimsun: what I want is have quilt take the .diff file I have and create a new patch from it. [01:38] cosmodad: put the patch into debian/patches (or wherever $QUILT_PATCHES is set to), and modify $QUILT_PATCHES/series as appropriate [01:39] crimsun: that's it? [01:39] cosmodad: well, you'll need to test that it applies and builds afterward, but yes. [01:40] it's that straightforward. [01:40] great. [01:42] cosmodad: I think you'll find the `push' definition in quilt(1) helpful [01:54] crimsun: seems to have worked. [01:56] crimsun: I'm off, thanks for the assistance. [01:57] yw [03:04] Heya gang [03:04] Aloha bddebian. [03:05] Howdy RAOF [03:05] Hey bddebian [03:06] Heya protonchris [03:07] hi bddebian [03:08] Heya LaserJock! [03:47] anybody familiar with bootcharts around? [03:47] Not me, sorry [03:47] I'm trying to diagnose why my wife's laptop is having issues [03:47] booting takes roughly 2.5-3 min [03:49] it spends about 80s in readahead === beuno is now known as beuno_ === beuno_ is now known as beuno [04:10] LaserJock: have you tried doing a profile boot [04:10] just did one [04:10] did that help at all? [04:11] LaserJock: where's the chart? [04:11] mb2: didn't do anything as far as I can tell [04:11] interesting... had the system ever been profiled before? [04:12] nope [04:12] it's a fairly fresh install [04:12] you rebooted again after the profile boot right? [04:13] yeah [04:13] http://laserjock.us/files/gutsy-20080403-2.png [04:15] I wonder if perhaps the hard drive is dying but I'm not sure why it would neccesarily make everything slow [04:20] LaserJock: holy mother of jeebus [04:20] jdong: what? [04:20] LaserJock: usplash is slurping on your silicon soul! [04:20] LaserJock: it would appear like splash is CPU spinning throughout bootup [04:21] have you tried booting nosplash? [04:21] nope [04:21] yeah try removing splash for a bootup and see if that gets any better [04:21] I've seen this bug several release cycles back with AMD64 nvidia [04:22] this is i386 ATI, but ... [04:23] ok, that's so totally better [04:24] I guess the more interesting question now is, why on earth is usplash misbehaving? :) [04:24] haha [04:24] it's 40s now [04:24] * ajmitch wishes his laptop booted in 40s [04:24] that trimed off 145s [04:24] Does removing splash from the options, or adding nosplash fix it? [04:24] removing splash from options [04:24] nosplash I just made up [04:25] lol [04:25] I did nosplah [04:25] nosplash [04:25] they're semantically identical [04:25] what does usplash look for? [04:26] http://laserjock.us/files/gutsy-20080403-4.png [04:26] that's the new bootchart [04:27] this is so weird, I mean all I did was a fresh install of gutsy and the thing is like roasted [04:28] now at least it boots fast [04:29] may I retire please? [04:29] * LaserJock fires nixternal [04:29] sweet jesus, that's just as good!!! [04:30] our class tonight, we bid for projects for points...so me being the dumb ass I am, bidded on all of the high point projects and got all 10 of them [04:30] what a dumb ass I am [04:32] :'<,'>s/(>=[^)]*)//g [04:32] * jdong whistles.... [04:32] brownies for whoever identifies what evil that does :D [04:33] It's a ed line for vi, firstly [04:33] It removes the version components in lines containing a ',' [04:33] lol guilty as charged :) [04:34] hmm, that's pretty good [04:34] StevenK's the man [04:36] impressive indeed [04:37] nixternal: which means that you have a large amount of work to do? [04:37] :'<,'s/(>[>=]?[^)]*//g [04:37] Is probably better, though [04:39] yo yo [04:39] ajmitch: a large amount is an understatement [04:40] sucker [04:45] tell me about it [04:45] that's what I get for being greedy for that 4.0 GPA [04:45] extra shots of espresso tonight! [04:46] no way, I gotta go to bed..gotta wake up in a few hours and get to the free software conference in the city === dhaval_away is now known as dhaval [04:47] why bother with sleep? [04:47] funny, jcastro and I were just talking about not sleeping for Penguicon in a couple of weeks :) [04:49] but jcastro is mad [04:49] true [04:59] !visternal [04:59] Oh no! The pointy-clicky Vista lover has arrived! He's rumoured to be giving out free money, too! [05:00] if I install a -dbg pkg, where do I need to put the source so that gdb will find it? === n3xu|laptop is now known as nexu [05:56] ScottK2: with regards to the FF3 backport, are you sure you looked at the debdiffs/dscs from post https://bugs.edge.launchpad.net/gutsy-backports/+bug/191796/comments/25? [05:56] Launchpad bug 191796 in gutsy-backports "Please backport firefox-3.0 3.0~b4 final" [Undecided,Incomplete] [05:56] err how did I bold that? [05:57] I think I looked at the last one. [05:58] * jdong looks again [05:58] ok, time to do a sanity check on myself [05:59] "Have I written a unreadable regexp in the last twenty minutes?" 'Check. I'm sane.' [06:01] ScottK2: both patches apply for me against hardy... make sure you used firefox-3.0 and xulrunner-1.9 source packages? [06:01] * jdong wonders how much his suggestions sound like "is it plugged in?" [06:02] I thought I did. [06:03] gdb question, how do I persuade it to read the symbol table of a particular .so when info share says the symbol table is there but not read? [06:03] I got a grand total of one hour of sleep on Monday night, so I'm a little fuzzy this week. [06:03] it's been a pretty rough week for me too === neversfelde_ is now known as neversfelde === asac_ is now known as asac [07:07] StevenK: are promotions done via bug report these days? [07:10] They are. === dhaval is now known as dhaval_away === dhaval_away is now known as dhaval [08:17] good morning [08:23] good morning dholbach [08:24] hi geser [08:26] <\sh> moins [08:58] protonchris: Hi. Do you think we might get one more glom version in? [09:14] Good morning === doko_ is now known as doko [09:29] morning [10:10] LucidFox: hi, bug 184084 has an RFS, are you looking into it? [10:10] Launchpad bug 184084 in checky "Extension description mentions Iceweasel/Icedove/Iceape" [Undecided,Confirmed] https://launchpad.net/bugs/184084 [10:19] pochu> sure, I'll look into it [10:23] thank you === jono_ is now known as jono [11:24] jono. just mailed you [11:27] thanks rod :) [11:34] Heya. I have ge-packaged the thunderbird package and added another patch. To reflect this in TB's version, I changed "2.0.0.12+nobinonly-0ubuntu0.7.10.0" to "2.0.0.12+nobinonly-0ubuntu0.7.10.0~mypatch1". Nevertheless, aptitude upgrade wants to revert back to the non-patched package. [11:35] how'd I need to version the new package in order for it to be more recent than the old one? [11:40] cosmodad: The entire point of ~ is that it is less than even nothing. [11:40] Perhaps +mypatch1 [11:41] Fujitsu: at the very end? [11:41] Yes - just change the ~ to a + [11:41] Fujitsu: or next to the first +? [11:42] cosmodad: no, at the end [11:43] james_w: looks kind of inconsistent to me, having the +nobinonly part followed by the ubuntu-specific version, and then by another +part. [11:44] cosmodad: it doesn't matter [11:45] Putting it after the nobinonly is completely wrong. [11:45] ok. [11:48] I used to know a bit of (single-lined) shell code which you could use to compare two debian versions, such that you get to know which of them is the higher one. [11:48] Anyone remember that? [11:48] dpkg --compare-versions [11:49] Lamego: ah, thanks a lot. [11:55] is there a way to change the version and produce new binary packages without going through the hassle of recompilation using cdbs? [11:56] I don't think so [11:56] Is dpkg-buildpackage really too hard to run? [11:57] cosmodad, debuild -nc [11:57] assuming you did a previous build [11:58] I did [12:00] -nc stands for no clean [12:12] Lamego: I'm using pdebuild and used --debbuildopts -nc to provide the switch, but now I get "dpkg-genchanges: cannot combine -b or -B and -S" [12:12] the build process used dpkg-genchanges -b -S [12:14] Maybe it is not the right channel but, I am looking for a good bug tracking system for bazaar. Is there any other solution as using Launchpad? [12:14] zoli2k: there is a plugin for trac [12:14] zoli2k: #bzr would be a more appropriate channel [12:16] james_w: I checked the trac_bzr, but I am not sure it is stable enough for a production production environment. [12:16] I will check the #bzr channel, thx. === ZrZ is now known as RzR [12:23] Hey [13:02] nxvl: hi, I've unsubscribed u-u-s from bug 196778. Should you fix it, I'll sponsor you... so feel free to ping me for it once you're done [13:02] Launchpad bug 196778 in likewise-open "Provide likewise-open-gui and likewise-open binaries rather than domainjoin-gui and domainjoin-cli" [Low,Incomplete] https://launchpad.net/bugs/196778 [13:06] murrayc_: It is definite worth a try. I'll have time to package it this weekend. [13:21] protonchris: Great. I'll do yet another tarball release today. [13:22] murrayc_ and protonchris: At this point it's probably easier to package a new revision with a patch for a bugfix than upload a new upstream version if that's feasible. [13:23] ScottK2: You can have the diff between versions if you like, but there are about 10 bugs that are fixed. It's easier just to take the tarball. [13:25] murrayc_: Makes sense. [13:26] I missed the earlier part of the conversation. For single fixes a patch is simpler/faster right now, but for that, I agree a new tarball is better. === chuck_ is now known as zul [13:41] ScottK2: thanks for the info. If you are arround this weekend, I might ask you to sponsor an upload :) [13:41] hi [13:42] After I get an FFe of course. [13:42] protonchris: I should be around off and on. No FFe needed if it's just bug fixes. [13:42] jdong: Thoughts on Bug #211605? [13:42] Launchpad bug 211605 in ktorrent-kde4 "new upstream release ktorrent-kde4" [Undecided,Confirmed] https://launchpad.net/bugs/211605 [13:42] ScottK2: Great. Thanks. [13:43] ScottK2: I think it's a good Hardy candidate [13:44] jdong: Thanks. [13:53] i just went on that bug : https://bugs.edge.launchpad.net/ubuntu/+source/svn-load/+bug/210754 [13:53] Launchpad bug 210754 in svn-load "apt-get install svn-load fails because of conflicting files" [Undecided,Confirmed] [13:54] what can I do to solve it ? adding a conflict in the control file ? [13:54] is it the right way ? [13:58] huats: no, it looks like svn-load is now a part of subversion-helper-scripts [13:59] huats: ah no, I'm wrong [14:00] :) [14:00] (that was my first feeling too) [14:02] huats: subversion-helper-scripts should be removed from Ubuntu [14:02] james_w: any reason ? any url where can I found that ? (i am cuious) [14:03] huats: rmadison -u debian subversion-helper-scripts is a good place to start [14:05] james_w: if I understand clearly, the result of your command shows me that it is no longer available in debian ? [14:05] huats: compare with "rmadison -u ubuntu subversion-helper-scripts" [14:06] I already did :) [14:06] but yes, sorry for being obtuse, it was removed from Debian a while ago, although I am having trouble finding any evidence it was ever there. [14:06] ok [14:06] so is there any thing I can do to ask for removal ? [14:06] (never did that) [14:07] huats: I don't know exactly, I've never done it myself. [14:07] ok [14:07] I think we need a little more information before we do ask for removal. [14:07] i think so [14:08] I'll try to investigate :) [14:08] or may be someone else has an idea ? [14:08] https://edge.launchpad.net/ubuntu/+source/subversion-helper-scripts [14:08] that says it's been around in Ubuntu for ever [14:08] https://bugs.edge.launchpad.net/ubuntu/+source/subversion-helper-scripts/+bug/149677 [14:08] Launchpad bug 149677 in svn-load "svn package conflict [hardy, gutsy]" [Undecided,Confirmed] [14:09] you should mark your bug as a duplicate of that. [14:09] I did already [14:12] great [14:15] <\sh> anyone using lighttpd there? [14:15] huats: I can't find the record of it being removed from Debian [14:16] hum, weird [14:18] yep [14:18] maybe it wasn't synced from Debian, but the changelog says "unstable" [14:18] yep [14:21] ok, can anyone tell us how to request a package removal? [14:22] james_w: whcih package? [14:23] slytherin: subversion-helper-scripts [14:24] james_w: ideally you should file a bug. But why do you want it removed? [14:25] slytherin: it's gone from Debian, it conflicts with svn-load-dirs, has only had one update [14:25] and it appears to just be thin wrappers around svn and svnadmin [14:25] james_w: gone when and why? [14:25] james_w: add that info to bug report. :-) [14:26] slytherin: that's the problem, I can't find it in removals.txt and google seems to know nothing about it ever being in Debian. [14:26] you missed all the discussion unfortunately. [14:27] james_w: may be we can just put a conflict between the 2 packages... [14:27] Is there a record of where a package was synced from? [14:28] james_w: don't seem to find one... [14:35] For a package that old, it's unlikely you'll find it. [14:37] <\sh> ScottK, we should have references...even when it was coming from this apt-get.org website... [14:37] \sh: I agree, but where would it be. Launchpad didn't even exist yet at that point, did it? [14:38] <\sh> nope... [14:38] <\sh> ScottK, but some archive-admin could have some old lists ;) [14:38] <\sh> asking pitti :) [14:38] Maybe. OTOH, if it hasn't been touched in years the odds of killing it hurting anything are small. [14:39] * ScottK would say ask via the removal bug. [14:39] <\sh> well, the fun part: [14:39] <\sh> * Removed from disk on 2006-05-04. [14:39] <\sh> * Removal requested on 2006-05-04. [14:39] <\sh> * Superseded on 2006-02-04 by subversion-helper-scripts - 0.5-2 [14:39] <\sh> * Published on 2005-12-21 [14:40] on the other side like I say since the beginning : since it is conflicting file with another package, why not simply add a conflict between the 2 packages ? since they are both providing the same functionality.... [14:41] huats: no, I don't think they are [14:41] <\sh> what about this: http://www1.apt-get.org/search.php?query=subversion-helper-scripts&submit=Submit+Query&arch[]=i386&arch[]=all [14:41] <\sh> output is here: http://paste.ubuntu.com/6466/ [14:42] Then it should definitely die. [14:42] <\sh> bah...I'm old... [14:42] subversion-helper-scripts' svn-load is just a wrapper around "svnadmin load". svn-load-dirs is a replacement for some non-free script that was in subversion package for a while IIRC. [14:42] \sh: thanks [14:42] james_w: ok... my mistake [14:43] <\sh> james_w, np :) [14:43] thanks \sh and ScottK too... [14:44] so shall I submit a removal request for sponsorship? [14:44] My vote is yes. [14:44] <\sh> james_w, file it... [14:44] But I'm generally a fan of removals. [14:44] I can convert an existing bug? [14:45] Do I need to follow a format for the title like ftp.d.o ones? [14:45] Yes. [14:45] No. Just provide the needed information. [14:45] great, thanks. [14:45] <\sh> guys...even when I'm not a fan of trance music :) but you should listen to Acid Reflux from Jamendo.com (CC music) [14:45] Heya gang [14:45] anyone knows a reason other than hardware problem, why my realtek network card would not show up under lspci at all, althgouh it did show up yesterday [14:46] but then it had the problem that it timed out after 10 min [14:46] <\sh> white, I'm guessing: "Sudden Death" ,-> [14:46] <\sh> hey bddebian [14:46] <\sh> it happens sometimes to realtek nics [14:46] \sh: hi :) [14:46] \sh: well that was not quite the answer i wanted to hear :) [14:47] james_w: https://wiki.ubuntu.com/MOTU/Removal is where the needed information used to live. Unfortunately it's been moved to I don't know where. [14:47] <\sh> white, how old? [14:47] 1-2 years [14:47] \sh: if another device would steal the memory space, the card would still show up under lspci, right? [14:47] <\sh> white, ok...two possibilities: 1. your card died or 2. your mainboard has problems with at least one pci slot [14:48] <\sh> white, yes... [14:48] <\sh> white, the latter one happened to me in the past...but that was my agp port on a gigabyte board [14:48] I'd start by looking through dmesg logs. [14:49] dholbach: https://wiki.ubuntu.com/MOTU/Removal was made into a redirect to https://wiki.ubuntu.com/UbuntuDevelopment#Removals which no longer exists as part of your wiki reoganization. Would you please undeprecate the page or repoint the forward to where the information now is. [14:49] the story is quite interesting, my laptop was broken and i send it in to acer under warranty. They replaced and most likely changed some hardware in there and when i start up the laptop, i get told that there is a conflict on a pci slot [14:49] i mean they should have seen that when they repaired it [14:49] Hi \sh [14:49] <\sh> oh ...laptop [14:50] https://wiki.ubuntu.com/UbuntuDevelopment/PackageArchive#head-6a4a4d2ad0cc004c6199f465539e3bbc2239291e [14:50] <\sh> -ENEVERBUYACER ,-) [14:50] ScottK, dholbach: ^ [14:50] acer travelmate 5514wlmi [14:50] \sh: ACK [14:50] james_w: thanks [14:51] <\sh> white, I have a desktop from them...cheapware from saturn ... I'll never buy such a thing again..I'll pay more the next time [14:52] \sh: well i do not have thre equipment here in my room to open it now and i either suspect that they screwed the slots up or the card is just dead [14:52] ScottK: done [14:52] either way, i have to wait for my thinkpad to arrive next week, i guess [14:52] wasn't sure, if there was anything else i could have tried on the software side, but neither lspci nor iomem shows the code of the device at all [14:54] does the bios enumerate it? [14:57] nope [14:58] the bios does not give anything, as far as i can see :/ [15:08] https://bugs.edge.launchpad.net/ubuntu/+source/link-monitor-applet/+bug/185318 is on the hardy milestone list and is in universe, does anyone fancy fixing it? [15:08] Launchpad bug 185318 in link-monitor-applet "link-monitor-applet dependency problems" [Medium,Confirmed] [15:11] <\sh> james_w, there should eb a new package in debian [15:12] <\sh> regarding the comments [15:12] \sh: I'm aware of that, I was just suggesting it would be a suitable task for someone. [15:13] <\sh> preparing a FFe :) [15:13] <\sh> and then following up for sync eventually [15:14] yeah, hopefully it will be quite straightforward. [15:14] <\sh> I'm subscribed now for that bug...if I find the time this evening I'll think I can deal with it [15:14] * \sh has still some other bugs to take care of [15:15] <\sh> anywys...weekend time now :) cu later from home [15:15] I can take it later if no-one else gets to it, I was just hoping that mentioning it would have someone jump at the chance. [15:15] bye \sh. === thekorn_ is now known as thekorn === hexmode` is now known as hexmode [15:56] ScottK: How will you handle the SPE fixes? [15:56] stani: he already uploaded it [15:56] spe (0.8.4.e-1ubuntu1) hardy; urgency=low [15:56] . [15:56] * Add 01pycheck-list.dpatch from spe svn to fix crash (LP: #201069) [15:56] if that's what you are referring to ;) [15:57] stani: https://launchpad.net/ubuntu/hardy/+source/spe/0.8.4.e-1ubuntu1 [15:57] ok, I've been fixing some more bugs on the upstream bug tracker [15:58] stani: Please attach patches to the bugs. Unified diff is better (diff -ruN) [15:58] but I don't know if it is possible they still get uploaded as well (maybe as SPE 0.8.4.f) [15:58] Possible. [15:58] ScottK: but the bugs are on berlios, not on launchpad [15:58] I see [15:59] stani: How many bugs? [15:59] 5 bugs or so [15:59] At this point I think we should limit changes to significant bugs. [16:00] I'd say if you've got patches for bugs that aren't in LP, file a bug that essentially says please add the following patches to fix .... [16:00] pochu or I will take it from there. [16:01] or release 0.8.4.f and make our lives easier :) [16:01] and my life too [16:01] (if it's strictly bug-fix only, of course) [16:01] yes only bug fixing [16:01] pochu: If we go that route, I want to upload direct to Ubuntu right now. I want to leave dpatch in the package so we'll have it for SRUs if we need it. [16:02] That'll work too. [16:02] hi pochu [16:02] hey jcastro [16:02] ScottK: fine for me [16:02] pochu: can you pick a time/date for your python packaging on the wiki so I can write an announcement up? [16:02] ok [16:03] pochu: feel free to contact me about it for brainstorming or whatever help you need [16:03] pochu: I mean about open week [16:03] jcastro: Thu 31st Apr at 18 or 19 UTC... if I knew whether I'm UTC+1 or +2... :) [16:03] stani: thanks :) [16:03] stani: what are we right now, +1 or +2? [16:04] DST confuses me :) [16:04] Someone who cares about Tex might want to look into Bug 131239 [16:04] Launchpad bug 131239 in tex4ht "sync request" [Wishlist,Incomplete] https://launchpad.net/bugs/131239 [16:04] jcastro: looks like I'm +2... so 18:00 UTC on Thursday WFM [16:05] pochu: I am in amsterdam (so I think +1) [16:05] stani: is it 17:05 there? [16:05] yep [16:05] then +2 :) [16:05] pochu: where are you? [16:05] ScottK: What do you need more to grant FFe? [16:06] mok0: The usual stuff. [16:06] stani: Spain [16:06] ScottK: I'll give it a look, during the weekend [16:08] is there any possible way we can get a "this absolutely needs to be done before release" list? [16:08] LaserJock: In theory it's the list of milestoned stuff. [16:08] LaserJock: milestone it for ubuntu-8.04 :) [16:09] aScottK: If you unsubscribe release-team, I'll resubscribe when I'm done with it [16:09] ScottK: ^ [16:09] Will do. [16:09] ScottK: are we actually using the milestone? [16:09] LaserJock: I know the RM is looking at it. [16:09] as in, maybe we need to announce and properly use the milestone [16:09] Dunno how complete it is. [16:11] https://launchpad.net/ubuntu/+milestone/ubuntu-8.04 [16:11] I'm feeling overwhelmed by lots of trivial stuff while it seems at times important things are falling through the cracks [16:11] ScottK: yes, I'm aware of where the milestones are ;-) [16:12] but I am unaware of MOTU actually ever using it in a cohesive or coordinated way [16:12] I find Launchpad confusing enough that I never assume people know how to find stuff. [16:12] good point [16:12] pochu: do you think an hour is enough for your session? [16:12] Personally I do use it for stuff that I think really needs to get done. [16:12] pochu: I figured if we're going to try to get upstream participation that it would suck if we ran out of time [16:13] I agree that we don't use it cohesively. [16:14] jcastro: hmm, I haven't thought about that... do you think we should do a two hours session? [16:14] I could probably run one in one hour, making it simple enough [16:15] pochu: I was just thinking about that. [16:15] jcastro: hmm, perhaps we can put it at 21UTC and in case we need more time, we take it :) [16:16] that sounds good [16:16] or we can move people to an #ubuntu-python after your hour too [16:17] jcastro: 21 works for me too, so I think that would be better [16:17] ok [16:17] thanks [16:17] give me 45 minutes for the wiki to update. :D [16:18] I didn't know there was an ubuntu-python room. [16:19] I don't think there is one :) [16:20] I think for the logging it would be better to do it at the end 21UTC [16:20] stani: yeah I was just recommending that if people wanted to continue to ask questions we could just lump them in a temporary channel while the rest of the classroom sessions went on [16:20] but 2100+ is fine too [16:21] jcastro: ok, so let's put it on 2100+ === sdh_ is now known as sdh [17:11] mok0: I can't remember if I asked you this before, but I was wondering if you'd take a look at Bug 66862 [17:11] Launchpad bug 66862 in python-numpy "scipy not built with atlas support ?" [Undecided,Confirmed] https://launchpad.net/bugs/66862 [17:12] ScottK: thanks for accepting my membership in ~pythonistas [17:13] proppy: You're welcome. I just recently got that ability. [17:15] leaving ubuntu-gnomemm === LjL-Temp is now known as LjL [17:46] ScottK: What is pythonistas? [17:46] It's a Launchpad team for looking after Python packages in Universe. [17:47] Mostly it just gets you bugmail. [17:47] Would it be interesting for me to be a member as well? [17:50] If you're interested in trying to triage/fix bugs in packages that are written in Python, then yes. [17:50] stani: ^^ [17:51] stani: I just received bugmail from you [17:51] stani: I thought you were already a member :) [17:51] proppy: You'll get a lot more now that you're in the team. [17:51] proppy: yes, I am trying to fix now all bugs on launchpad of spe [17:52] stani: If you interest is limited to spe, then it shouldn't be necessary to join. If you are interested in getting more broadly involved in Ubuntu and fixing/packaging Python stuff, then I'd be glad to add you. [17:54] ScottK: Ok, maybe I don't need to be a member now. Feel free to bother me if you some wxpython applications have bugs. That I know quite well. [17:54] stani: As a rule, we'd like to limit asking people to install stuff from outside the packaging system. Maybe you could upload svn snapshots for testing to a PPA instead of asking people to directly pull from your SVN. [17:54] stani: Will do. [17:55] stani: We could help you with getting the versioning right so that your svn snapshot would then automatically get replaced by the official package once it's uploaded. [17:56] I am not an expert on packaging (that's why I'd like to see that python-packaging session). I've never setup a PPA before. [18:00] stani: I have a PPA, I could explain how to use it if you are interested and/or upload a snapshot of spe to mine [18:01] pochu: That would be great, but we have to do it another time as I have to leave soon for dinner. [18:05] Scottk & pochu: I think I fixed all linux related bugs on berlios and launchpad in subversion. So I plan to do a .8.4.f release tomorrow. (There are still some Windows bugs left, which I can't reproduce, but I feel to lazy to start Windows.) [18:06] stani: Great. [18:07]