[07:54] <dholbach> good morning
[08:00] <dholbach> Laney, tumbleweed: if you still want to do the other session about "working in debian", could you please go and grab a slot soonish? https://wiki.ubuntu.com/UbuntuDeveloperWeek/Timetable - HUGS :)
[08:06] <bkerensa> dholbach: Would be cool if Ubuntu Developer Week was a physical event... I surely could benefit from a week of development sessions :D
[08:07] <dholbach> haha, yes, that'd be nice
[10:11] <Laney> dholbach: yeah, sure
[10:11] <Laney> sorry that it's harder work for you this time around :(
[10:13] <dholbach> Laney, it's fine - I just want the schedule to be sorted out RSN, so I can still get in touch with some other Linux sites, so we get more participants this time - that's why I urge everyone a bit more than usual :)
[10:13]  * Laney goes cross-eyed looking at wiki markup
[10:13] <dholbach> Laney, I can help you with that if you tell me title and time :)
[10:13] <Laney> got it
[10:13] <dholbach> ok great
[10:13] <dholbach> :)
[10:14]  * dholbach hugs Laney and tumbleweed
[10:14] <dholbach> thanks a bunch
[10:15] <bkerensa> =o
[10:47]  * tumbleweed supposes he should take on an extra session or two
[11:07] <tumbleweed> dholbach: what were you thinking about for the pbuilder / sbuild session? advanced usage & hooks
[11:08] <dholbach> maybe, yeah - maybe even some quick introduction about what the tools are, why they're useful, pros of each and how to generally use them
[11:08] <dholbach> I'd leave it up to you :)
[11:09] <tumbleweed> you do cover the basics in the intro, though?
[11:11] <dholbach> tumbleweed, I'm not quite sure how much time I'll have - I'll sure mention it and ask folks to setup a pbuilder in the getting set up session - in the past I almost never had the time for them to actually build a package
[11:11] <dholbach> but 2h in one sitting is probably as much as you can type non-stop :)
[11:11] <tumbleweed> and there I thought you were copying-and-pasting :P
[11:12] <dholbach> I did that the last time around and it helped a lot
[11:12] <tumbleweed> well, I asked around here, and people thought that was the most useful from your list of suggestions, so I'll snag a 30min slot for it
[11:12] <dholbach> but sometimes you can guess by the questions that you need to expand on a thought, etc
[11:12]  * dholbach hugs tumbleweed
[11:12] <dholbach> beers are on me next time we meet :)
[11:13] <dholbach> oh and my friend showed me pictures of his trip trip Cape town yesterday - it was beautiful
[11:13] <highvoltage> it still is :p
[11:13] <dholbach> a shame he didn't read my mail in time to come to your LUG meeting
[11:13] <tumbleweed> unfortunatly rather hot recently
[11:13] <dholbach> highvoltage, ok, I meant the pics were beautiful :-P
[11:14]  * highvoltage just wanted to chime in :)
[11:14] <dholbach> highvoltage, hey, you could chime in with a session you're giving! :-)
[11:15] <dholbach> highvoltage, how about a 30m demo of Edubuntu and what's cooking there? :)
[11:15] <highvoltage> dholbach: tumbleweed has already been putting some pressure on me to do that. I guess I might just do that!
[11:16] <tumbleweed> heh
[11:16] <highvoltage> (and just last night I decided to say 'no' to more things)
[11:17] <tumbleweed> dholbach: I can probably extend the pbuilder session to an hour if the schedule stays empty (going into sbuild if I run out of material)
[11:18] <dholbach> highvoltage, sorry, I didn't mean to browbeat you into something
[11:18] <dholbach> highvoltage, maybe some of your Edubuntu friends would be interested?
[11:19] <highvoltage> dholbach: nah, not at all. I fullheartedly want to
[11:19]  * dholbach hugs highvoltage
[11:19] <highvoltage> *hugs*
[11:19] <highvoltage> I just need to find ways to be more time-efficient (it's hard)
[11:20] <dholbach> THAT's a session we should have at UDW :)
[11:20] <dholbach> or two
[11:21] <tumbleweed> highvoltage: I need a session on how to actually get a thesis done when there is so much fun OSS stuff to do
[11:22] <highvoltage> yeah I bought a bunch of e-books on time management and how tobe more efficient when doing creative kind of work. but I haven't had the time to read them yet :)
[11:22] <tumbleweed> :)
[11:22] <highvoltage> tumbleweed: ah I thought you were very near to the end
[11:22] <tumbleweed> time wise, that doesn't mean progress-wise
[11:22] <Laney> th...e...sis?
[11:23] <tumbleweed> the.... ooh, look, bugs!
[12:44] <dholbach> Laney, nice work on LP!
[12:44] <Laney> :-)
[12:45] <Laney> was quite fun actually
[12:45] <Laney> and to think it was all to make nigelb proud!
[12:46] <dholbach> Laney, I guess there won't be a way to fix historic data, right?
[12:46] <Laney> sadly not, as it wasn't stored anywhere
[12:46] <dholbach> I thought so
[12:47] <dholbach> but at least it's fixed from now on :)
[12:47] <Laney> unless you want to trawl through bugs and do it manually :P
[12:47] <dholbach> or well, when it landed
[12:47] <dholbach> yeah, I great way to spend a lazy sunday afternoon
[12:47] <dholbach> or 1500 lazy sunday afternoons
[12:47] <Laney> heh
[12:47] <dholbach> :)
[12:48] <Laney> different definitions of 'great' possibly …
[12:48] <dholbach> I guess it depends on how great your other lazy sunday afternoons are :)
[12:48] <Laney> sunday afternoon is the afternoon for making soup
[13:20] <nigelb> Laney: lol
[13:35] <Laney> nigelb: do you know how often production is upgraded?
[13:36] <nigelb> Laney: No, but this will help figuring out http://lpqateam.canonical.com/qa-reports/deployment-stable.html
[13:36] <Laney> yeah I know that. It tells me what but not *when*
[13:36] <nigelb> right now, nothing's blocking deployment
[13:36] <nigelb> So, soon.
[13:37] <Laney> like I don't know if it's a once a month thing or whatever
[13:37] <Laney> dev.lp is hiding the goods somewhere, but I can't find out where
[13:37] <Laney> ah well /me carries on being impatient ...
[13:38] <nigelb> Laney: Its not once a month.
[13:38] <nigelb> its several times a week.
[13:38] <Laney> sweet
[13:40] <Laney> 14700 was friday
[13:41] <nigelb> When did everything get QA'd?
[13:42] <nigelb> (I'm guessing some time today)
[13:42] <Laney> dunno
[13:42] <Laney> I don't mind waiting, was just wondering how frequent it is
[13:47] <nigelb> Laney: except for db patches, which you have wait since there's only one window at a time, everything eelse is fairly fast after qa-ok.
[13:47] <nigelb> the only trouble is, all revisions in the stack before yours need to be qa-ok as well.
[13:47] <Laney> righto
[14:17] <l3on> hey guys
[14:17] <l3on> I have this unmetdep:
[14:17] <l3on> Package: live-config-sysvinit
[14:17] <l3on> Version: 3.0~a22-1ubuntu1
[14:17] <l3on> Missing: sysvinit (>= 2.86)
[14:17] <l3on> the problem is in ubuntu sysvinit does not exist, but we have:
[14:17] <l3on> Binary: sysvinit-utils, sysv-rc, initscripts
[14:17] <l3on> I'm going to change that, which package do you suggest ?
[14:18] <l3on> I think initscripts should be fine, 'cause depends on the others two
[14:19] <tumbleweed> seeing as Ubuntu uses upstart, why do we need that binary package?
[14:20] <l3on> maybe someone would use sysvinit ?
[14:20] <tumbleweed> if we don't have sysvinit, how could they? :)
[14:21] <l3on> but we have : sysvinit-utils, sysv-rc, initscripts
[14:21] <l3on> that come from sysvinit source
[14:21] <Laney> we don't have sysvinit itself
[14:22] <l3on> yes now I see
[14:22] <l3on> ok.. so, drop that package ?
[14:22] <l3on> I mean → Package: live-config-sysvinit
[14:22] <tumbleweed> or just leave it as uninstallable (but we are already patching it, so might as well dropit)
[14:24]  * l3on tries to drop it
[14:30] <tumbleweed> we could use a better document for referring people to when they ask "what can I do for Ubuntu" (/me tries to avoid writing it)
[14:30] <valterstr> :D
[14:30] <valterstr> about me?
[14:30] <tumbleweed> in general, but yes
[14:31] <valterstr> so... the question, what can I start with?
[14:31] <valterstr> bug tracker?
[14:32] <tumbleweed> my usual suggestion is to pick a relatively obscure and un-cared-for package that you use, and tidy it up
[14:32] <valterstr> will look into that...
[14:33] <tumbleweed> (by tidy it up, I mean look through the bugtracker, see if we have applied patches that haven't been forwarded upstream, etc)
[14:33] <valterstr> i understand
[14:33] <valterstr> so, in general, look for older bugs that have fixes that have not been merged?
[14:34] <valterstr> launchpad changed bug page interface recently?
[14:34] <tumbleweed> review operation cleansweep patches? https://wiki.ubuntu.com/OperationCleansweep
[14:34] <tumbleweed> yes
[14:34] <l3on> since I'm going to propose a merge for live-config, someone would take a look to this ? bug 913874
[14:35] <tumbleweed> valterstr: you can pretty much ask any questions in here and should get help (sometimes after several hours, if it's quiet)
[14:35] <valterstr> ok.
[14:35] <valterstr> thanks.
[14:35] <valterstr> I will start looking through the bug tracker then.
[14:36] <tumbleweed> harvest.ubuntu.com also aggregates things that should be looked at
[14:36] <valterstr> also, the "pushing upstream through sponsor" thing. could you please explain it in more detail?
[14:36] <tumbleweed> !sponsorship
[14:36] <tumbleweed> err, maybe not
[14:36] <tumbleweed> http://wiki.ubuntu.com/SponsorshipProcess
[14:37] <valterstr> https://wiki.ubuntu.com/DistributedDevelopment/Documentation/SeekingSponsorship
[14:37] <valterstr> but do I do it like that for the changes I do or is there another process I should do?
[14:40] <tumbleweed> valterstr: that process works
[14:40] <valterstr> ok
[14:40] <valterstr> tumbleweed: big thanks for the help
[14:52] <Laney> nigelb: oh, r14713 (Get the code!)
[14:52] <Laney> !!!
[14:52] <nigelb> \m/
[14:52] <nigelb> omgomgomg
[14:53] <Laney> ssssssssssssswwwwwwweeeeeeeeettttttttt
[14:53] <tumbleweed> hah
[14:54] <tumbleweed> Laney: will you sort out lp-udd.py ?
[14:54] <Laney> yus
[14:54] <Laney> sponsor something so i can test it :P
[14:54] <nigelb> Laney's all charged up today. He can do *anything* you ask him to do.
[14:54] <Laney> gotta submit this paper review
[14:54]  * tumbleweed looks for a nice gnarly lp bug
[14:54] <Laney> or ELSE
[15:00] <Laney> tumbleweed: nah, next fix should be ui for this
[15:01] <tumbleweed> yes, that'd be nice
[15:02] <Laney> and not too hard
[15:03] <Laney> want to do the python-markdown sync? could be ok but you'd know better
[15:03]  * tumbleweed looks
[15:04] <tumbleweed> probably safe, I'll do it
[15:04] <Laney> sweet
[15:06] <tumbleweed> can't be synced yte. importer is out of date
[15:07] <Laney> bah
[15:52] <l3on> hey guys... looking at bug 783568 mdeslaur suggests me to use a different notation for the version.. but I'm not clear a thing about oneiric ... also it need a ubuntu1.11.10.1 version ?
[15:52] <l3on> sorry, ubuntu0.11.10.1 ?
[15:57] <micahg> l3on: yes
[16:02] <l3on_> mmm...
[16:02] <l3on_> I mean, in oneiric should be ubuntu1 .. no ?
[16:02] <l3on_> considering precise has a new version of gdevilspie
[16:03] <micahg> l3on_: no
[16:04] <micahg> ubuntu1 should only be used in the devel release
[16:05] <l3on_> ah ok :) thanks micahg
[16:09] <l3on_> ok, branches updated... micahg could you take a look ? :)
[16:10] <micahg> l3on_: non-security stuff, sure, I'll take a look when I pilot a bit later if that's ok
[16:10] <l3on_> thanks
[17:25] <jtaylor> l3on: shogun was "fixed" can you update the merge? also check if the hdf5 stuff is ok
[17:25] <jtaylor> btw is there interest in getting the hdf5 transition done in precise too?
[17:26] <jtaylor> would be nice as it includes a couple new helper commands which would ease backporting, but the status does not look very good yet
[17:26] <jtaylor> also updating science stuff always takes ages :/
[17:29] <tumbleweed> science stuff tends to be big an dclunky
[17:29]  * tumbleweed needs to set up something like this for the bugs I file http://blog.gerv.net/2012/01/outstanding-requests-in-bugzilla/
[17:31] <Laney> hdf5 is having problems
[17:31] <tumbleweed> otoh, opencv seems to be going well
[17:32] <jtaylor> can I sync stuff that does not exist in ubuntu yet?
[17:32] <jtaylor> I want to have dh_linktree :)
[17:32] <tumbleweed> yes
[17:32] <jtaylor> now review necessary?
[17:32] <tumbleweed> it'll go to NEW, yes
[17:33] <jtaylor> automacially if I use syncpackage?
[17:33] <tumbleweed> yup
[17:33] <jtaylor> nice
[17:33] <bkerensa> https://bugs.launchpad.net/ubuntu/+source/snort/+bug/889721 <-- Upstream had a interesting response
[17:34] <tumbleweed> bkerensa: yeah, upstreams don't understand how we work
[17:34] <micahg> jtaylor: dh_linktree was already sync'd by cjwatson
[17:34] <jtaylor> oh good
[17:35] <bkerensa> tumbleweed: Yeah he also e-mailed me and thanked me but essentially also assigned blame to both Debian and Ubuntu for not keeping up with Upstream heh
[17:38] <cjwatson> well, dh_linktree still needs binary NEW - I'll do that now
[19:02] <Rhonda> interesting that someone files a sync request for wesnoth-1.9 when I am preparing wesnoth-1.10 :)
[19:02] <micahg> that's why I subscribed you :)
[19:02] <Rhonda> Ah, you subscribed me. I wonder why it appeared in my mailbox :)
[19:04] <micahg> launchpad should tell you why you got it
[19:04] <micahg> although I think that message is delayed a bit
[19:06] <Rhonda> You have been subscribed to a public bug:
[19:06] <jtaylor> anyone knowlegable about fonts?
[19:06] <Rhonda> micahg: but it doesn't tell by whom.
[19:06] <micahg> oh, it used to say by whom
[19:06] <Rhonda> You received this bug notification because you are subscribed to wesnoth in Ubuntu.
[19:07] <Rhonda> And that is in the footer.
[19:11] <Rhonda> micahg: marked it as wontfix, guess thats acceptable with the reasoning I wrote :)
[19:12]  * Rhonda . o O ( being able to do so on my own without having to ask someone else is the good thing about being a MOTU :) )
[19:13] <micahg> yep
[19:13] <micahg> well, it'll still need to be NEW processed, but as long as it's in Debian, that qualifies as the initial package review
[19:16] <Rhonda> Sure
[19:17] <Rhonda> One of the reason I keep 1.9 in my PPA is, the last 1.9.14 release is extremely close to the 1.10 release, thus I don't expect any FTBFS or similar issues with it. :)
[19:18] <Rhonda> There are just bug fixes and translation updates in between, but 1.9.14 was string frozen and feature frozen (I think feature freeze was upstream at 1.9.10 or such already)
[19:22] <jtaylor> the new launchpad is not working so great :(
[19:22] <jtaylor> constantly oops not found errors
[19:24] <l3on> hello there.. where I can find some statistic for precise ?
[19:24] <jtaylor> what kind of statistics?
[19:25] <l3on> packages, bugs closed, what else ?
[19:25] <l3on> merges, syncs,
[19:28] <tumbleweed> l3on: you can find some things here: http://qa.ubuntu.com/report-list/
[19:32] <jtaylor> interesting blcr-dkms is in the top 10 most duplicates
[19:32] <jtaylor> apparently many use it, but there is no patch for this issue since 3.0 kernels
[19:35] <l3on> thanks :)
[19:35] <tumbleweed> I also have graphs of ftbfs packages and upload counts, but that's about it
[20:08] <l3on> tumbleweed, can I see that ? :)
[20:09] <tumbleweed> http://people.ubuntuwire.org/~stefanor/
[20:10] <Laney> what a day for the debian package importer to be broken >:(
[20:10] <tumbleweed> :)
[20:18] <l3on> beautiful tumbleweed
[20:18] <l3on> .:D
[20:18] <l3on> maybe some numbers could help :)
[20:19] <tumbleweed> they're all there in the js :P
[20:19] <l3on> can I checkout the code? :)
[20:19] <tumbleweed> yes
[20:19] <tumbleweed> and if you have access to alioth, you can mine that kind of thing yourself
[20:37] <tumbleweed> l3on: do we know what's wrong with the importer?
[20:37] <tumbleweed> err Laney
[20:37] <l3on> tumbleweed, what do you think about some tooltip/popup ?
[20:37] <Laney> something fell over with ftp.uk.debain.org
[20:37] <Laney> ian
[20:38] <l3on> something like → http://jqueryfordesigners.com/coda-popup-bubbles/
[20:38] <Laney> which is where it pulls from
[20:38] <tumbleweed> l3on: for what?
[20:38] <l3on> for top 50 uploaders
[20:39] <l3on> just to know how many packages for instance
[20:39] <tumbleweed> one of the reports already has tooltips, it'd make sense to use the same library (unless it sucks)
[20:39] <l3on> which one ?
[20:39] <l3on> I mean, which one report ?
[20:40] <tumbleweed> I can't remember, and I can't see it :)
[20:41] <l3on> lol
[20:42] <Laney> 23/01 15:57:04 <Sledge> themill: looks like mirroring is broken somewhere upstream of free
[20:42] <Laney> 23/01 15:57:19 <Sledge> I'm getting that looked at now, and also doing a manual sync
[20:42] <Laney> free = box with mirror
[20:42] <Laney> 23/01 15:57:37 <Sledge> DNS will be updated shortly to point elsewhere in the meantime
[20:43] <tumbleweed> l3on: aah, ftbfs
[20:44] <l3on> :)
[20:45] <tumbleweed> anyway, patches welcome. Shout if you want me to move one of those +junk branches into a lp project, for easier merge requests
[20:46] <l3on> we'll see, I'm not sure that what I want is easly to do :)
[20:46] <l3on> *easy
[20:49] <tumbleweed> flot.js alreday has some hover support: http://people.iola.dk/olau/flot/examples/tracking.html
[21:52] <tumbleweed> Laney: we appear to have imports
[21:53] <Laney> good ones?
[21:53] <tumbleweed> they'd better not be bad :)
[21:54] <Laney> not sure i can see any syncs on precise-changes
[21:55]  * tumbleweed just did one
[21:55] <Laney> sponsored?
[21:55] <tumbleweed> no, coming up now
[21:55] <Laney> https://lists.ubuntu.com/archives/precise-changes/2012-January/007903.html ? seems all you
[21:55] <tumbleweed> yes
[21:57] <tumbleweed> barry: still intend to build pypy in a ppa that has arm, or should I just sync it?
[21:57] <Laney> not sponsored then?
[21:57] <Laney> sponsor it to someone if you do it :P
[21:58] <tumbleweed> Laney: syncing python-markdown, sponsored
[21:58] <Laney> oh, it woke up?
[21:58] <Laney> good stuff
[21:58] <barry> tumbleweed: ah, last week i was trying to build it on my arm box, but honestly, i probably won't get to it now.  sync it i guess ;)
[21:58] <tumbleweed> commit myself to making it work before release :)
[22:00] <Laney> In [2]: ubuntu_archive.getPublishedSources(source_name='python-markdown', distro_series=lp.distributions['ubuntu'].current_series, exact_match=True)[0].sponsor
[22:00] <Laney> Out[2]: <person at https://api.launchpad.net/1.0/~stefanor>
[22:00] <tumbleweed> oh, ScottK sorry, didn't seeyou assigned yourself to that
[22:05] <ScottK> tumbleweed: As long as it's done.  I was just waiting for it to appear.
[22:09] <Laney> tumbleweed: select source, version, changed_by, signed_by from ubuntu_upload_history where source = 'python-markdown' and version = '2.1.0-1';
[22:09] <Laney> :-)
[22:09] <tumbleweed> :)
[22:11] <Laney> it is nice going end-to-end like that