[01:12] <twb> Where is the wiki article explaining what a new Ubuntu/Launchpad blueprint should look like?  I want to steal your good ideas.
[01:12] <twb> I had a look on wiki.ubuntu.com, but couldn't find anything relevant.
[01:13] <twb> What I'm looking for will remind/explain to the blueprint author stuff like user stories.
[01:14] <thumper> twb: I don't think so
[01:14] <thumper> feel free to write something on dev.launchpad.net
[01:14] <twb> thumper: OK, thanks.
[01:14] <spm> yo thumper, how's pycon-nz?
[01:15] <thumper> spm: pretty good actually
[01:15] <thumper> more people there than I originally expected
[01:15] <thumper> had some good talks
[01:15] <thumper> gave a few :)
[01:15] <thumper> didn't get any rotten fruit or eggs thrown
[01:16]  * spm makes note to self. purchase rotten eggs/fruit for attending future thumper talks
[02:18] <murcherson> hi folks
[03:31] <RenatoSilva> when you use LP translations, you must include the BSD license text in your package, right? It is the text itself that stands this
[04:13] <RenatoSilva> something seems wrong here: https://help.launchpad.net/TermsofUse. See Translations copyright. It says that the work done in Launchpad is available under BSD for other users, rather than under the license of the underlying project using those translations, which would be perfectly possible, so that when you do a translaton in LP, you are automatically giving others the right of using your translations under BSD-compatible licenses. It's a license cha
[04:15] <RenatoSilva> I mean, according to the terms of use and the BSD text, all projects using translations from LP *should* include the BSD text in their packages regardless of the project license. However when e.g you download a .po file, it stands that its license is the same as the project, rather than explictly specifying it as the BSD one, which should be done according to the above terms
[04:16] <RenatoSilva> I just wonder why not stand something different in the terms of use: "when you translate something in LP, you're automatically licensing your work under any BSD-compatible license, for any LP user that wishes to reuse that work."
[04:19] <RenatoSilva> Therefore it would not require adding the BSD text, which I wonder if anyone currently does
[06:05] <RenatoSilva> https://bugs.launchpad.net/launchpad/+bug/478902
[06:45] <davidstrauss> Are download statistics broken?
[06:47] <spm> hmm. could be. looking....
[06:47] <RenatoSilva> they are and there's a bug about it
[06:47] <davidstrauss> RenatoSilva: Thanks.
[06:48] <RenatoSilva> bug 458835
[07:27] <glen> could somebody explain why the items are so long in needs review state? https://translations.launchpad.net/eventum/+imports
[07:27] <glen> and what should i do with ones that are in state "failed"
[07:33] <spm> glen: ahhh. that could *partially* be due to a broken script post the rollout last week. I fixed this morning, and the backlog is processing atm. danilo_ may also be able to comment later. stress the 'may'.
[07:42] <glen> ok. i'll recheck tomorrow then
[07:44] <RenatoSilva> Launchpad needs a wiki nature
[10:36] <dpm> hey launchpadders, good morning to you all! I've got a question on blueprints: how can I unmark a blueprint for a sprint? I'm looking at https://blueprints.edge.launchpad.net/ubuntu/+spec/community-lucid-kubuntu-translations-feedback-and-improvements , which I've marked as superseded, but it's still targeted for uds-l and I cannot change it
[10:46] <geser> bigjools: Hi, can you explain me what went wrong in http://launchpadlibrarian.net/35202722/upload_1321811_log.txt? (build: https://edge.launchpad.net/ubuntu/+source/dimp1/1.1.3-1/+build/1321811)
[10:47] <bigjools> geser: what happened?
[10:48] <wgrant> Intriguing.
[10:48] <geser> bigjools: don't know, just that this build in lucid is marked "Failed to upload"
[10:48] <bigjools> hmmm odd
[10:48] <wgrant> Nothing went wrong :(
[10:50] <bigjools> geser: retry it (or I can if you can't) and let's see if it happens again
[10:50] <bigjools> it might be because of the rollout
[10:51] <geser> retried
[10:53] <geser> when was the rollout exactly?
[10:54] <bigjools> thursday, but we had a few problems with scripts that were not fixed until late Friday
[11:00] <geser> bigjools: while waiting on the retry, I've looked at some recent "Failed to upload" and it still happens: http://launchpadlibrarian.net/35396661/upload_1330916_log.txt (from today, 7h ago)
[11:00] <bigjools> oh dear
[11:01] <wgrant> Huh.
[11:02] <wgrant> buildd-manager isn't doing something utterly stupid like looking at a slav,e, is it?
[11:04] <bigjools> wgrant: what do you mean?
[11:05] <wgrant> bigjools: It will mark the build as Failed to Upload if process-upload.py doesn't set it to Successfully Built, or if it has no binaries.
[11:05] <bigjools> correct
[11:05] <wgrant> But we can clearly see that process-upload.py commits.
[11:06] <bigjools> ah slave store you mean
[11:06] <bigjools> yeah that would make a lot of sense
[11:06] <wgrant> Oh, right, sorry.
[11:06] <wgrant> Did those auth master changes end up landing?
[11:06] <bigjools> we cowboyed a change
[11:07] <bigjools> only this morning
[11:07] <wgrant> Ah. So that's not it.
[11:07] <bigjools> as in 1 hour ago
[11:07] <bigjools> it might be it actually - the auth store stuff was totally buggered for scripts
[11:08] <wgrant> But I would have expected it to always use the main master when it should have been using the auth master.
[11:08] <wgrant> Not the other way around, which is the only way this could happen.
[11:08] <wgrant> But it must have been using the main master, since the object it gets is writable.
[11:09] <bigjools> hmmm
[11:09] <wgrant> Oh.
[11:09] <wgrant> No it doesn't.
[11:09] <wgrant> It gets the build *again*.
[11:09] <wgrant> Checks the status and binaries.
[11:09] <wgrant> And then throws it away,.
[11:09] <wgrant> And it uses the SQLObject compatibility layer, so I have no idea what it's doing.
[11:10] <wgrant> So it could well be using the wrong store for the status check.
[11:10] <bigjools> time to cowboy the buildd-manager ...
[11:10] <wgrant> Which is the branch?
[11:11] <pgquiles> what software do the soyuz autobuilders run to build packages? buildbot?
[11:12] <wgrant> pgquiles: A modified version of sbuild.
[11:12] <pgquiles> wgrant: thanks
[11:12] <wgrant> With a custom Twisted-based manager controlling everything.
[11:12] <wgrant> And breaking, in this case :(
[11:13] <pgquiles> is that modified version available somewhere? I'm interested in setting up a similar environment at work to build packages for our software
[11:13] <geser> bigjools, wgrant: http://launchpadlibrarian.net/35411063/upload_1321811_log.txt from the dimp1 retry (finished 1 min ago)
[11:14] <bigjools> geser: ok I am pushing a change out, one moment
[11:14] <bigjools> geser: ok retry again! sorry ...
[11:17] <pgquiles> wgrant: why sbuild and not pbuilder? :-?
[11:19] <wgrant> pgquiles: sbuild is what real buildds have used forever.
[11:19] <wgrant> And diverging from Debian on that seems ill-advised at best.
[11:19] <pgquiles> wgrant: indeed :-)
[11:19] <wgrant> (plus sbuild predates pbuilder by some years)
[11:20] <wgrant> And is more useful for buildds
[11:59] <geser> bigjools: did the pushout went well? as https://edge.launchpad.net/builders/ shows one i386 build idle and 7 jobs in the queue (similar for armel)
[12:00] <bigjools> geser: no, we're having problems, trying to resolve it now, but basically no builds are being processed at this time
[12:00] <geser> ok
[13:20] <menesis> I get an error after a successful PPA build: "Could not find upload log file"
[13:20] <bigjools> menesis: yes known problem, I am fixing it
[13:20] <menesis> will i have to restart the build later?
[13:20] <bigjools> you can retry the build and it will catch up when I've fixed everything
[13:20] <bigjools> sorry for the hassle
[13:21] <menesis> ok good luck fixing it :)
[13:22] <bigjools> thanks
[13:46] <esr> gmb: ping
[14:22] <ScottK> al-maisan or bigjools: I gather from recent upload successes that today's Soyux problem is fixed.  Are you going to do a mass retry or does someone need to go through the buildd histories and do it by hand?
[14:27] <al-maisan> ScottK: I am sorry but I wouldn't know that, bigjools should get back to you shortly.
[14:27] <ScottK> al-maisan: Thanks.
[14:45] <bigjools> ScottK: I wasn't planning on doing a mass retry but I can if there's a *lot*
[14:46] <ScottK> bigjools: It's not a large number, but someone will have to hunt through the build histories.  I can do it, I guess.
[14:48] <bigjools> asac, cjwatson: the failed-to-upload problem was fixed about 1h15m ago
[14:48] <bigjools> crap ECHAN
[14:49] <bigjools> ScottK: cool - it's easy to write a script to do it via the API
[14:50] <geser> bigjools: wouldn't it be better to wait till the other bug causing "Failed to upload" is also fixed? (the one about slony)
[14:50] <bigjools> geser: that's fixed
[14:50] <bigjools> well, cowboyed pending a proper fix
[14:51] <geser> great
[14:51] <bigjools> this release sucked bad :/
[14:56] <geser> bigjools: I retried dimp1 once again (the package I asked at the beginning) and it worked now :)
[14:56] <bigjools> geser: great, thanks for letting me know
[15:12] <ScottK> All retried now.
[15:38] <kirkland> is anyone from Launchpad attending linux.conf.au?
[15:38] <kirkland> ie, any Launchpad developers
[15:39] <LarstiQ> kirkland: I'm pretty sure there are
[15:40] <kirkland> LarstiQ: who?
[15:41] <LarstiQ> kirkland: I don't know, but several of them live in the general area
[15:41] <kirkland> LarstiQ: right, i know that
[15:42] <kirkland> LarstiQ: i'm trying to find someone who is known to be attending
[15:44] <LarstiQ> kirkland: I'm just speculating as an outsider, but seeing as spiv's wife seems to be involved in the organisation, I'd guess the chance that he attends is pretty big
[15:44] <kirkland> LarstiQ: thanks
[15:55] <Ursinha> hi bac
[16:07] <bac> hi Ursinha
[16:11] <Ursinha> bac, I have one email from a user asking if he's qualified to use launchpad or if he needs a commercial subscription, he said he sent one email to feedback but I can't see any emails in that list
[16:11] <Ursinha> bac, may I forward it to you?
[16:11] <bac> Ursinha: sure
[16:11] <bac> Ursinha: are you CHR this week?
[16:11] <Ursinha> thanks bac
[16:11] <Ursinha> bac, yes
[16:11] <bac> Ursinha: you should modify the topic to say so.
[16:12] <Ursinha> bac, oh, I thought the "Help contact" was enough
[16:13] <bac> Ursinha:  nm -- i didn't see it was there.
[16:13] <Ursinha> bac, :)
[16:21] <Ursinha> bac, sent
[17:37] <Vorador>  Hi. Could someone help with PPA builds? The problem is that the build-bot installs the wrong version of software (I have the needed version in my ppa already built, but it installs ubuntu version instead) and package building fails because of that. Build log -> http://launchpadlibrarian.net/35424976/buildlog_ubuntu-karmic-lpia.audacious-plugins_1.5.1-2ubuntu3~ppa1_FAILEDTOBUILD.txt.gz Package list -> https://launchpad.net/~sandshrew/+a
[17:37] <Vorador> rchive/ppa/+packages
[17:39] <Vorador> ..Or maybe it's impossible to build lower version than the one in default ubuntu repos?
[17:42] <bigjools> Vorador: correct, you need a higher version
[17:47] <quentusrex> Can someone help with the seahorse-agent mailling list spam????
[18:00] <Ursinha> quentusrex, what's happening?
[18:00] <quentusrex> I'm getting 50+ e-mails a day
[18:00] <quentusrex> because I reported an empathy crash
[18:01] <quentusrex> and many others are e-mailing the list of us who are getting it, complaining that to unsubscribe times out....
[18:01] <quentusrex> Any time someone reports a duplicate of: https://bugs.launchpad.net/bugs/429322
[18:03] <Ursinha> quentusrex, let me see here
[18:03] <Ursinha> quentusrex, hm, it
[18:04] <Ursinha> quentusrex, hm, it's timing out for me as well
[18:05] <Ursinha> quentusrex, are you using edge or launchpad.net only?
[18:05] <quentusrex> but I don't want to know when someone else reports a duplicate of that bug...
[18:05] <quentusrex> I want to know anything other than duplicates of that bug...
[18:06] <Ursinha> quentusrex, so you want to keep subscribed but don't receive duplicates notifications?
[18:06] <esr> gmb: ping?
[18:08] <dreamcat4> hi. There appear to be issues with the file release pattern glob.
[18:08] <dreamcat4> can anyone help?
[18:10] <quentusrex> Ursinha, that's right
[18:10] <Ursinha> quentusrex, I don't know if it's possible..
[18:10] <gmb> esr: Hi.
[18:11] <Ursinha> gmb, is it?
[18:12] <gmb> Ursinha, quentusrex: No, that's not possible. However, you could filter email based on a header if you have the ability to do that
[18:13] <esr> Hello.  Nudging you again about joining forgeplucker and the forgeplucker-dev - things are moving quickly and listeing to what's going on will help prepare you for doing the Launchpad handler.  Project development is actually running *ahead* of my most optimistc estimates, if you can imagine that.
[18:14] <quentusrex> gmb, I've unsubscribed.
[18:14] <esr> I'm a little bemused by it - I don't think I've seen that happen before.
[18:14] <quentusrex> and I'm considering not reporting all the crashes I get...
[18:15] <quentusrex> if my e-mail will get flooded.....
[18:15] <gmb> esr: I'm already subscribed to the list; I'm going to be taking a look at doing the Launchpad integration tonight. Our API should make it pretty straightforward.
[18:15] <esr> OK.
[18:15] <gmb> esr: I'll drop into the IRC channel later tonight.
[18:15] <quentusrex> If I report a crash, and it is a duplicate of another bug
[18:15] <esr> Excellent.
[18:15] <quentusrex> I don't want to know when someone else reports a duplicate of that bug mine was a duplicate of...
[18:17] <Ursinha> gmb, quentusrex, I think this is bug 418659
[18:17] <Ursinha> gmb, could you triage that, please?
[18:18] <gmb> Ursinha: I'll take a look at it when I get back; about to step out.
[18:18] <Ursinha> sure, thanks gmb
[18:21] <quentusrex> Yeah, that's the bug...
[18:21] <quentusrex> I can confirm that is what is killing my inbox...
[18:29] <Ursinha> quentusrex, I'll talk to malone people about that bug
[18:45] <Ursinha> I have a doubt: if I set a branch as development focus of a project, when I do a bzr branch lp:project, is that the branch I'll get?
[19:23] <grahal> i'm trying bzr launchpad-login gustavo-grahal but I get "The user name gustavo-rahal is not registered on Launchpad"... I also tried my email address
[19:24] <grahal> oh god
[19:24] <grahal> forget it
[19:24] <grahal> I was actually trying gustavo-rahal not gustavo-Grahal
[19:24] <idnar> Ursinha-afk: you reintroduced the typo in the topic with your latest change :P
[19:32] <fagan> Found a small bug with launchpad https://launchpad.net/~ubuntu-allstars
[19:32] <fagan> It was a moderated team when I applied and then it was changed to open
[19:32] <fagan> Im stuck in the proposed members thing
[19:32] <fagan> is this a known issue?
[19:55] <thumper> fagan: easiest thing to do is to file a bug
[19:55] <thumper> fagan: if it gets marked as a dupe, it is known, if not, you've found a new one :)
[19:56] <bigjools> hello thumper
[19:56] <thumper> bigjools: hey
[19:57] <fagan> thumper: cool
[20:52] <bialix> hi guys, I need to make garyvdm the admin of qbzr-dev team on LP. But I don't see a knob for this. Any help/guidance?
[20:59] <bialix> ok, so only owner can give other people admin rights? right?
[21:09] <hggdh> is there a way to stop email notifications on a specific bug? c.f. bug 429322
[21:16] <hggdh> which, BTW, I cannot open anymore -- I get a timeout from LP
[21:20] <jgoppert_> why does my git repository fail to import into launchpad?
[21:22] <jgoppert_> ls
[21:23] <cody-somerville> jgoppert_, link?
[21:24] <jgoppert_> https://code.launchpad.net/~jgoppert/+subscribedbranches
[21:24] <jgoppert_> tried it twice, first i think was due to the white space after the url, but i fixed it for the second, still a no go
[21:25] <jgoppert_> git://uvsim.git.sourceforge.net/gitroot/uvsim/uvsim
[21:35] <cody-somerville> which is the first attempt?
[21:36] <cody-somerville> jgoppert_, I think you're right for the first one and the second one looks like a bug in bzr-git
[21:37] <jgoppert_> thanks, that's too bad
[21:37] <jgoppert_> are they going to get git on launchpad anytime soon?
[21:38] <cody-somerville> jgoppert_, Lots of git branches get imported successfully
[21:38] <cody-somerville> Can you file a bug against launchpad-code?
[21:40] <jgoppert_> ok i'll do that
[21:41] <jgoppert_> what do i file it under bzr-git?
[21:43] <cody-somerville> launchpad.net/launchpad is a safe place
[21:48] <jgoppert_> thanks
[21:50] <Ursinha> idnar, now I see :)
[21:51] <idnar> :)
[22:43] <tgm4883> In the branch naming convention ~userid/project-name/branch-name, is there a way to change the project-name in a current branch?
[22:50] <Ursinha> tgm4883, hmm, I don't think so, but have to confirm
[22:51] <maxb> No... though I seem to remember someone saying there used to be, but the UI got removed because no-one fixed it to work with package branches
[22:51] <Ursinha> losas, is it possible to rename a project changing all that's related to it?
[22:51] <Ursinha> hi maxb :)
[22:52] <Ursinha> do you know if it's possible to copy one package from one PPA to another? (I was pretty sure the answer is yes)
[22:52] <maxb> yes, it is
/+copy-packages
[22:53] <wgrant> tgm4883: You can change it using the API. There is no UI at the moment because, as maxb said, it needs to be rather more complex to work with package branches.
[22:53] <tgm4883> wgrant, I see
[22:53] <Ursinha> maxb, I want to answer https://answers.edge.launchpad.net/launchpad/+question/89097
[22:53] <wgrant> Ursinha: It is possible to rename a project, yes.
[22:53] <tgm4883> sounds like I should just repush and delete
[22:53] <Ursinha> wgrant, rename a project and all that's related to it?
[22:53] <Ursinha> branches and yada yada
[22:53] <wgrant> tgm4883: If there are no merge proposals or the like associated, that's probably easier.
[22:54] <wgrant> Ursinha: Right.
[22:54] <wgrant> Ursinha: It's just one field in the DB.
[22:54] <tgm4883> wgrant, will do, thanks
[22:54] <Ursinha> wgrant, I thought so, but wanted to confirm with the losas
[22:54] <Ursinha> they do the sql magic for such requests
[22:55] <maxb> Ursinha: On-request copying is possible - automatic copying of all future uploads is not.
[22:55] <Ursinha> maxb, that was my understanding. Thanks
[22:55] <wgrant> Automatic copying of all future uploads sounds like they want a PPA dependency.
[22:55] <maxb> (For good reason: what if a future upload requires a new dependency which isn't on the destination's copy-list?)
[22:56] <maxb> No, this is more like wanting to cherrypick a subset of someone else's PPA to expose to clients
[22:58] <maxb> Ursinha: Shall I answer that question?
[22:59] <Ursinha> maxb, well, I'm answering now, but your input is appreciated if you want to
[23:00] <maxb> Ok - if you include the rationale on why auto-copying would be a mistake, I don't have anything additional to say.
[23:04] <Ursinha> maxb, I've answered there, you can add anything else you find appropriated to
[23:26]  * jml concurs w/ maxb & wgrant
[23:39] <RenatoSilva> the fix for download counters has been released. So will it start counting again now, or was it just that the count was being stored but not displayed anymore?
[23:55]  * maxb wonders what jml is concurring with
[23:56] <wgrant> The branch reassignment UI thing, perhaps.