[00:01] <cprov> fta: fixed.
[00:02] <fta> cprov, excellent! thanks
[00:03] <cprov> fta: np, sorry for that. Buidd-manager was going boing, but I think I've just fixed it.
[00:21] <seb128> hi
[00:22] <seb128> do you guys record oops and look at those? it's not possible to add upstream tasks to some ubuntu bugs on edge at the moment
[00:22] <seb128> just trying to make sure that this will not be rolled in the stable update in some days
[00:23] <seb128> ie OOPS-1185EB1223
[00:24] <mwhudson> seb128: people do yes
[00:32] <sbeattie> hrm, any idea why launchpad.distributions['ubuntu'].main_archive.getPublishedSources(distro_series=launchpad.distributions['ubuntu'].getSeries(name_or_version="jaunty"), pocket="Release", source_name="linux", exact_match=True) returns a 500/ISE result?
[00:32] <sbeattie> Other source_name queries do not.
[00:34] <jml> sbeattie: not off the top of my head.
[00:34] <jml> sbeattie: is there an OOPS code?
[00:36]  * sbeattie tries to see if he can dig one out of the returned HTTPError exception
[00:45] <sbeattie> jml: I dunno why I can't catch the HTTPError exception (I'm not much of a python hacker), but if there's an oops, you ought to be seeing it every 15 min.
[00:50] <james_w> sbeattie: probably because linux tends to have more publications than other packages
[00:51] <james_w> though a single source package in a single series shouldn't be enough to trigger a timeout I would hope
[00:52] <james_w> sbeattie: you can run in a python shell after "import httplib2; httplib.debug_level = 1" and you should be able to see the OOPS number in the response headers
[00:52] <james_w> "httplib2.debuglevel = " sorry
[00:55] <lifeless> sbeattie:
[00:55] <lifeless> try:
[00:55] <lifeless>    <foo>
[00:55] <lifeless> except Exception, e:
[00:55] <lifeless>     print type(e)
[00:55] <lifeless>     raise
[00:55] <lifeless> then once you have a good type for e, change the except line to
[00:55] <lifeless> except <that type>, e:
[00:55] <lifeless>     <print e.args or whatever to get the oops out>
[00:55] <lifeless>     raise
[00:58] <sbeattie> james_w: I also get it for the wpasupplicant package in jaunty
[01:00] <sbeattie> lifeless: thanks, nearly there, I was being fooled by it being launchpadlib.errors.HTTPError not urllib2.HTTPError
[01:00] <sbeattie> jml: oops OOPS-1185EC1270
[01:00] <lifeless> bah, I hate things wrapping errors unnecessarily :)
[01:02] <jml> sbeattie: it's a unicode decode error.
[01:02] <jml> not sure what the root cause is, but it's a bug in Launchpad for sure.
[01:04] <sbeattie> jml: okay. Need me to file a bug? If so, against malone?
[01:06] <jml> sbeattie: against soyuz please
[01:15] <wgrant> cprov: OK, I return.
[01:15] <wgrant> cprov: I suppose that if you ever support customising PPA upload rights, you do need separate keys, so you really have to do it now.
[01:16] <wgrant> So the key UID format has to be argued...
[01:21]  * jml finally starts writing a thing that uses launchpadlib
[01:22] <wgrant> jml: Prepare for slow, slow pain :(
[01:23] <lifeless> jml: what are you righting?
[01:24] <jml> lifeless: a thing :)
[01:25] <jml> lifeless: some stuff to test the new package branch linking things :)
[02:22] <cpscotti> Hey, I need a help updating (the first version went ok) a package on my PPA. When I do <<debuild -S>>, all my files (.changes, .dsc and .diff.gz)  change (hence their checksums too) and my .orig.tar.gz continues the same (returns the same sha1sum reported on the original .chages file which I can see at lunchpad) although launchpad rejects my upload saying that I already uploaded that version. I see that I MUST NOT re-uplo
[02:22] <wgrant> cpscotti: You got cut off after 'I MUST NOT re-uplo'
[02:23] <cpscotti> re-upload my .orig.tar.gz with dput but I dunno how to do that..
[02:23] <cpscotti> If I move the .orig.tar.gz to another folder dput will miss him and won't do anything... if I leave it there dput uploads him (even though it warns me I should not do that)
[02:23] <wgrant> You can upload the same .orig.tar.gz twice, as long as it has the same checksum.
[02:24] <cpscotti> do I need to change the package version in some place?
[02:24] <wgrant> But you cannot upload the same version of the .diff.gz/.dsc (as specified in debian/changelog) twice.
[02:24] <cpscotti> so I need to change the changelog?
[02:24] <wgrant> Yes - use 'dch -i' to increment the version and create a new entry.
[02:27] <cpscotti> hmm
[02:27] <cpscotti> dch -i seems to be nice =]
[02:28] <wgrant> It is.
[02:29] <cpscotti> well.. it seems it really did the magic
[02:29] <cpscotti> (the version incremented everywhere =] )
[02:30] <wgrant> There's only one place (except for the stuff generated from the changlog by debuild) to change it - debian/changelog.
[02:31] <cpscotti> man!
[02:31] <cpscotti> thanks!
[02:31] <cpscotti> hehe
[02:31] <cpscotti> it worked
[02:32] <wgrant> Excellent.
[02:32] <cpscotti> thing is.. all this stuff really forces u to do the right thing
[02:32] <cpscotti> thanks a lot
[02:32] <wgrant> That tends to be a good thing.
[02:32] <wgrant> np
[03:05] <jml> so, what do you do with a foo_link attribute?
[03:06] <lifeless> the new google spec?
[03:06] <jml> hmmm. I see there's more than meets the eye here.
[03:07] <jml> getattr(lpobject, 'foo') goes to the link and loads the object...
[03:08] <wgrant> jml: Yes, launchpadlib is magical.
[03:08] <wgrant> Normally you have to launchpad.load() the link or something like that.
[03:08] <jml> I really need to twistify this.
[03:08] <wgrant> But launchpadlib is sufficiently awesome that it works that out.
[03:08] <jml> wgrant: thanks.
[03:13] <jamesh> jml: all the cool kids are doing synchronous programming these days
[03:13] <jml> really?
[03:14] <jml> synchronous is so passé
[03:15] <jamesh> if you're running on a hyperthreaded 8 core processor, why bother with async code? :)
[03:16] <lifeless> because threads are for people that can't program state machines?
[03:17] <jamesh> threads are for people who can program lots of state machines
[03:19] <jml> awww yeah.
[03:23] <jml> so launchpad APIs on staging could be a little snappier.
[03:30] <Legendario> does rosetta accept ts file imports?
[03:31] <Legendario> or only pot?
[04:13] <Ursinha> Legendario, only pot, afaik
[04:21] <Andre_Gondim-afk> when I upload translations to rosetta, these translations stay as suggestions or become the official translations?
[04:44] <jamesh> Andre_Gondim-afk: it depends on the policy set for the project you're translating, iirc.
[04:46] <wgrant> Probably more likely your permissions over the project, which depends on the policy.
[04:46] <Andre_Gondim-afk> jamesh, GNOME, KDE...
[04:48] <jamesh> Andre_Gondim-afk: see https://help.launchpad.net/Translations/YourProject#Choosing%20a%20permissions%20policy
[04:48] <jamesh> Andre_Gondim: if you go to https://translations.launchpad.net/$project it will tell you what the project's policy is
[04:49] <jamesh> [this is assuming that the project in question is using Launchpad for translations, of course]
[04:50] <Andre_Gondim> jacob, in the case of gnome in ubuntu? there is a gnome upstream project, and I imported to rosetta
[04:51] <jacob> Andre_Gondim: wrong tab-complete ;)
[04:51] <Andre_Gondim> sorry
[04:51] <Andre_Gondim> jamesh, , in the case of gnome in ubuntu? there is a gnome upstream project, and I imported to rosetta
[04:53] <jamesh> Andre_Gondim: upstream Gnome doesn't use Launchpad for translations, so there is no automatic way for translations done in Launchpad to make it into the upstream releases unfortunately
[04:53] <jamesh> people are working on that.
[04:53] <jamesh> you can translate the Gnome packages in Ubuntu, and those translations will make it into Ubuntu releases
[04:54] <jamesh> but again, those translations don't get fed upstream yet :(
[04:55] <Andre_Gondim> jamesh, I have upstream access project. and I can import to rosetta, my question is, if is already translation in rosetta witch will be the final translation?
[04:55] <jamesh> Andre_Gondim: which project in particular are you talking about?
[04:58] <Andre_Gondim> jamesh, look, I translate the ubuntu to portuguese Brazil and there is a br.gnome.org project, they translated the gnome, and I get the po file and get pot ubuntu file and then importe to rosetta, my question is, if is there some translation in the package witch will be, the imported or that was there?
[04:59] <cody-somerville> Any translation people around?
[04:59] <cody-somerville> er...
[05:00] <cody-somerville> My real question is, generally the .pot and .po files are generated right? So I wouldn't want to keep them in revision control with my xml files. right?
[05:01] <jamesh> Andre_Gondim: so, the process for Ubuntu translations is that PO templates and upstream translations are extracted during the package build process and imported into Launchpad.  Translations done in Launchpad take precedence.
[05:01] <jamesh> as Ubuntu is using the structured translation policy, translations need to be approved by the appropriate translation group before they'll be used too.
[05:02] <Andre_Gondim> jamesh, ok, so that translation made by po into in rosetto like suggestion, is it?
[05:02] <jamesh> anyone can request an export of the Ubuntu translations and commit them upstream, but you'd want to use msgmerge in case there has been some drift (e.g. because of upstream changes, or ubuntu patches)
[05:04] <jamesh> if an upstream project wanted to use Launchpad for translations, all the work done for Ubuntu would be available as suggestions where the message IDs matched
[05:04] <jamesh> cody-somerville: you wouldn't be able to use Launchpad to generate historic PO files for old releases
[05:05] <jamesh> so if you want to be able to reproduce a release from version control, you'd want the PO files in there.
[05:05] <cody-somerville> jamesh, but they'd be in the actual package though
[05:06] <jamesh> cody-somerville: one of the original goals for Rosetta was integration with version control.  The idea was that Rosetta would manage a branch of your project and commit up to date translations to it.
[05:06] <jamesh> for developers, the export process would become a simple "bzr merge"
[05:06] <wgrant> It does imports from bzr as of 2.2.3, doesn't it?
[05:08] <jamesh> wgrant: it might.  I haven't been following recent development.
[05:08] <jamesh> the idea was to also do exports in the same way
[05:15] <stub> thumper, jml:  I can do that call now if you guys would prefer
[05:15] <jml> stub: I have to head out in < 15 minutes. :(
[05:18] <tjs> G'day
[05:19] <tjs> I'm just trying to get someone commit access to lp:pomke. I've created a team, added the person to the team, associated the team with the project, set the branch as the mainline for the project..
[05:21] <tjs> still no go. The process for 'give person X write access to branch Y' seems particularly convoluted o.O
[05:21] <wgrant> What isn't working?
[05:21] <tjs> spats_: what's not working?
[05:21] <wgrant> Oh, you need to associate the team with the *branch*, not the project.
[05:21] <tjs> ahh
[05:22] <wgrant> tjs: At the moment you own it.
[05:22] <wgrant> You need to change the owner to the team.
[05:22] <tjs> https://launchpad.net/pomke/trunk says the registrant is the team and the team is also the driver
[05:22] <wgrant> tjs: That's a project series, not a branch of code.
[05:23] <wgrant> The two can be associated, but are not the same thing.
[05:23] <tjs> ok
[05:24] <wgrant> sinzui: Nice work on the team page.
[05:24] <tjs> spats_: try again :)
[05:24] <wgrant> But just as you destroyed the empty Mailing Lists section, a new Personal Package Archives one sprung up :(
[05:27] <lifeless> tjs: you've done a lot of unrelated things
[05:27] <lifeless> tjs: go to the branch, and change the owner to the team
[05:30] <tjs> lifeless: I did that (https://code.launchpad.net/~pomke/pomke/pj)
[05:32] <lifeless> tjs: ah then  its done; just add people to the pomke team and you're away laughing
[05:32] <tjs> I notice that has changed the url for the branch from ~tjstebbing to ~pomke
[05:32] <tjs> will that have updated the lp:pomke alias?
[05:32] <wgrant> tjs: Yes.
[05:33] <tjs> neat :)
[09:34] <dominiks> hello.. can somebody check remote watch for bug 98626 please? Bug was closed in Debian 4 days ago, but still no change in LP... how is remote watch supposed to work? any ideas please?
[09:50] <bigjools> gmb, can you help ^
[09:52] <gmb> dominiks, I'll look into it, bear with me...
[09:52] <dominiks> gmb: thanks
[09:55] <geser> is there a way to more infomation about an error when using launchpadlib? I get a "launchpadlib.errors.HTTPError: HTTP Error 500: Internal Server Error"
[09:56] <gmb> dominiks: Hmm. It looks like it's not been checked for a few days. It *should* get checked shortly, but there are a lot of watches so sometimes the recently checked ones (this was last checked on the 23rd) fall to the back of the queue. Unfortunately the bug watch checker is a bit dumb about age and treats all watches equally unless they've never been checked before.
[09:57] <gmb> dominiks: I'll keep an eye on it. If necessary I'll get an admin to kick off a full update of the debbugs bugtracker; that should sync it.
[10:10] <wgrant> geser: Catch the exception. The message attribute will occasionally give useful information, particularly if you're in ~launchpad (ie. they don't give you useful information unless you can look at the code instead).
[10:18] <geser> at least I could get a OOPS-ID this way
[10:27] <dominiks> gmb: thanks for all info.. don't worry about that bug, that's low level priority anyway.. we can wait :)
[10:28] <gmb> dominiks: no worries. But if I don't find out why it's out of date it'll bug me :)
[12:25] <jblount> Sometimes, when someone closes a bug that has been frustrating me, I wish LP had a way to thank them. Like maybe on the closed bug page, there could be a way to give the person who closed / fixed the bug a bit of Karma, or something similar.
[12:26] <firefly2442> I'm looking for an online gettext translation system.  The Launchpad Rosetta project looks great but isn't Launchpad still closed source?  Are there any plans to spin Rosetta off into a separate standalone application?  Thanks.
[12:27] <henninge> firefly2442: https://dev.launchpad.net/OpenSourcing
[12:28] <firefly2442> ahh thank you
[12:31] <BUGabundo> good morning
[12:31] <BUGabundo> trying to edit a description
[12:31] <BUGabundo> and I'm getting "No operation name given."
[12:31] <BUGabundo> on edge
[12:31] <BUGabundo> with the new ajax title name
[12:33] <BUGabundo> no LP contact online??
[12:35] <BUGabundo> after page refresh it worked
[12:35] <BUGabundo> timeout?
[13:24] <cody-somerville> kiko, Can you take care of  question #65972 when you have a free moment?
[13:27] <lamothe> When bugs for a package are raised against Ubuntu, am I supposed to mark this as fixed when/if I fix it in upstream.  Or, is the bug only fixed when the version of the application is updated/patched in Ubuntu?
[13:27] <lamothe> For example, https://bugs.edge.launchpad.net/ubuntu/+source/me-tv/+bug/350779
[13:29] <lamothe> Is there a special name for these types of bug reports?
[13:30] <wgrant> lamothe: If it also affects upstream, you should click 'Also affects project', to add a separate row of the table against me-tv upstream.
[13:30] <wgrant> You can then set the Fix Committed or Fix Released status there.
[13:31] <wgrant> What you do upstream doesn't affect the Ubuntu version.
[13:31] <wgrant> (until we merge from you)
[13:32] <lamothe> wgrant: Thanks for that.
[13:32] <wgrant> gmb: Do you know what's going on with https://bugs.edge.launchpad.net/ubuntu/+source/me-tv/+bug/350779? The activity alternately indicates 'me-tv' and 'me-tv (Ubuntu)'... is that because one of the users is using edge?
[13:33]  * gmb looks
[13:35] <lamothe> I'm on edge.
[13:35] <gmb> wgrant: That's frickin' weird.
[13:36] <gmb> wgrant: Actually, no it's not weird. You're right, I'm on crack.
[13:36] <wgrant> gmb: Right, I didn't think it was weird.
[13:36] <wgrant> Just a code change.
[13:36] <gmb> Yeah.
[13:36] <wgrant> And I think edge is wrong.
[13:36] <wgrant> Oh.
[13:36] <wgrant> No.
[13:36] <wgrant> edge is right.
[13:36] <gmb> wgrant: Right :)
[13:36] <wgrant> But why isn't the task target recorded in a proper field?
[13:36] <wgrant> So it can be linkified and all?
[13:36] <wgrant> And not have horribly inconsistent data.
[13:38] <gmb> wgrant: Because we haven't actually changed the underlying data structure for the activity log, on the basis that whichever way you try and store it you'll end up with horribly incosistent data (i.e. going from text -> proper relationships in the DB will not handle renaming, etc., any better than going from text-> text).
[13:39] <gmb> wgrant: We may alter it in future, though, I don't know. There's no plan for that atm though (there was originally but it seems to have been discarded along the way).
[13:39] <lamothe> wgrant: So, I should never really touch "me-tv (Ubuntu)" unless I can close a bug due to it being inappropriately filed?
[13:39] <wgrant> gmb: That's unfortunate...
[13:39] <wgrant> lamothe: Yes.
[13:39] <wgrant> lamothe: But you could confirm it or similar if you know it's really a bug in the code.
[13:39] <wgrant> But you can never set it past Triaged.
[13:39] <wgrant> (by 'can' I do not mean technically)
[13:40] <lamothe> wgrant: Yep, thanks again.
[13:40] <wgrant> 350779's +activity just got mighty confusing.
[13:40] <wgrant> lamothe: np
[13:41] <gmb> wgrant: Well, it's sort of unfortunate. I agree that tracking actual bug tasks would be useful, but the problem then is how to record historical data properly. If you track the task and then the task is retargeted you end up with an incorrect history.
[13:41] <wgrant> gmb: I don't think that retargetting tasks makes sense in the first place.
[13:42] <gmb> wgrant: It makes sense if the task is mistargeted, surely?
[13:43] <lamothe> Here's the interesting thing, I have turned off "bugs" for the Me TV project.  This feature seems to able to circumvent that setting.
[13:43] <wgrant> gmb: I'm not sure. I think the way to do that should be to create a new task and delete (ie. hide) the old one.
[13:43] <wgrant> But it is hard to say.
[13:44] <gmb> wgrant: Hmm. Interesting point. I think this might be one of those things where it's hard to DTRT because TRT is a bit fuzzy.
[13:44] <wgrant> gmb: I don't think retargetting after any attribute has been changed makes sense.
[13:44] <wgrant> Before any other triage, perhaps.
[13:45] <gmb> Yeah, I can see your point there.
[13:49] <cody-somerville> I broke launchpad.
[13:49] <wgrant> That's getting harder to do these days.
[13:50] <cody-somerville> Well shucks wgrant :) I bet the launchpad guys are glowing right now.
[13:51] <wgrant> cody-somerville: Glowing with the light from the fire in which they are forging their weapons?
[13:52] <cody-somerville> https://edge.launchpad.net/xubuntu-docs <-- you'll notice that I've manage to violate unique restraint packaging_uniqueness :(
[13:52] <wgrant> Impressive.
[13:53] <AnMaster> bzr: ERROR: Target directory lp:~anmaster/cfunge/speedup already exists, but does not have a valid .bzr directory. Supply --use-existing-dir to push there anyway.
[13:53] <AnMaster> what do I do?
[13:53] <AnMaster> I just registered the branch on the web page as hosted
[13:53] <AnMaster> and now I wish to initially push it
[13:53] <AnMaster> should I do --use-existing-dir
[13:53] <AnMaster> ?
[13:53] <andrea-bs> AnMaster: bzr push --use-existing-dir
[13:53] <AnMaster> ah
[13:53] <andrea-bs> :)
[13:53] <AnMaster> so that is safe then
[13:53] <wgrant> AnMaster: Supply --use-existing-dir - you don't actually need to register on the web UI first.
[13:53] <wgrant> You can just push to a new URL.
[13:53] <AnMaster> wgrant, what about marking as experimental and such?
[13:53] <AnMaster> then
[13:53] <wgrant> AnMaster: You can do that later on.
[13:53] <AnMaster> ah
[13:53] <AnMaster> hm
[13:54] <AnMaster> btw did they add a option to clean out revisions removed with bzr uncommit yet?
[13:54] <AnMaster> it would be a pain to branch around with a new shared repo for that on my setup
[13:55] <andrea-bs> AnMaster: if you want to remove commits from a hosted branch you just need to "bzr uncommit" and then "bzr push --overwrite"
[13:55] <andrea-bs> AnMaster: is it what you were trying to do?
[13:55] <AnMaster> andrea-bs, not hosted, I mean local
[13:56] <AnMaster> as in I commited then noticed a major typo in the commit message and did bzr uncommit
[13:56] <AnMaster> but it seems the actual revision is around still in the repo
[13:56] <AnMaster> considering count reported by bzr check
[13:56] <wgrant> It is. Is that a problem?
[13:56] <AnMaster> wgrant, it's wasting space isn't it?
[13:57] <wgrant> Barely.
[13:57] <wgrant> It won't be transferred when you push, AFAIK.
[13:57] <AnMaster> wgrant, depends on how much you commited, any png or such and you can have a lot of wasted space locally
[13:57] <AnMaster> but true
[13:57] <AnMaster> it won't be sent when you push
[14:00] <gmb> cody-somerville: How the fuck did you dod that?
[14:00] <cody-somerville> gmb, :(
[14:00] <gmb> *do
[14:01] <cody-somerville> gmb, $project/$series/+ubuntupkg lets you
[14:01] <gmb> cody-somerville: Eww. Please to file a bug; I'll let the registry guys know.
[14:01] <wgrant> One of the three views to let you make such links...
[14:01]  * cody-somerville nods.
[14:01] <cody-somerville> wgrant, hehe
[14:02] <gmb> wgrant: I'm going to have that comment stuffed and mounted over the  mantlepiece at Millbank.
[14:02] <gmb> Well, over the dishwasher, anyway.
[14:02] <wgrant> gmb: ... huh?
[14:02] <gmb> wgrant: "That's getting harder to do..." etc.
[14:03] <wgrant> Ah.
[14:06] <wgrant> I like it when it gets hard to break Launchpad, as it means I'm less likely to have angry blog posts about me.
[14:10] <wgrant> I wonder if closed bugs should prominently display a warning that it's probably not the right place to be.
[14:45] <cody-somerville> Are there any translation folks around?
[14:46] <henninge> cody-somerville: no, we are not ;-)
[14:46] <cody-somerville> henninge, How do I delete a template that doesn't exist anymore?
[14:46] <cody-somerville> and how do I create new ones?
[14:47] <henninge> cody-somerville: deletion (deactivation, really) is done by asking us through a request on answers.
[14:47] <henninge> cody-somerville: creation is done by uploading a template file.
[14:47] <henninge> cody-somerville: and us approving it.
[14:47] <cody-somerville> henninge, I don't see an option for doing that - just to uploading a template for an already accept one
[14:48] <henninge> cody-somerville: what's the project?
[14:48] <cody-somerville> xubuntu-docs
[14:48] <jtv> cody-somerville: what do you mean by "doesn't exist anymore"—it doesn't exist anymore upstream?
[14:49] <cody-somerville> jtv, right
[14:50] <jtv> cody-somerville: that's a matter of disabling it.  Any admin—such as henninge and I, bow before us—can do that.
[14:50] <cody-somerville> okay
[14:51] <cody-somerville> I've filed it a question for it
[14:52] <henninge> cody-somerville, jtv: got it (moving it to roestta ;)
[14:52] <cody-somerville> so where do I go to upload a brand new template?
[14:54] <henninge> cody-somerville: how does this https://edge.launchpad.net/xubuntu-docs relate to the package in Ubuntu?
[14:54] <henninge> cody-somerville: is that the upstream?
[14:54] <cody-somerville> It relates directly, yes.
[14:56] <ivangarcia> hi guys, I'm having error when pushing my code in bzr
[14:56] <ivangarcia> bzr launchpad-login chaos.proton
[14:56] <ivangarcia> bzr: ERROR: Connection error: curl connection error (SSL certificate problem, verify that the CA cert is OK. Details:
[14:56] <ivangarcia> error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed)
[14:56] <ivangarcia> on https://launchpad.net/%7Echaos.proton/%2Bsshkeys
[14:56] <ivangarcia> any help?
[14:58]  * jtv is about to leave
[14:58] <henninge> jtv: stop
[14:58] <henninge> jtv: please confirm the following to cody-somerville
[14:59] <henninge> cody-somerville: AFAIK uploads to Ubuntu packages all happen from soyuz.
[14:59] <henninge> cody-somerville: so once you have the xubuntu-docs package build in soyuz it will be uploaded to rosetta
[14:59] <cody-somerville> That only occurs for packages in main
[14:59] <henninge> jtv: right?
[15:00] <jtv> …and of course at that point my otherwise now very stable IRC connection had to break.
[15:00] <jtv> It is possible for translation team members to upload to individual Ubuntu translations as well, i.e. for specific languages.\
[15:00] <jtv> *Most* uploads are by Soyuz, however.
[15:01] <henninge> jtv: yes, but cody-somerville wants to upload a *template*
[15:01] <jtv> henninge: that's still possible, though I don't know off the top of my head who has the privileges.
[15:01] <henninge> cody-somerville: at least I don't see an upload option, either.
[15:02] <jtv> henninge: if you clicked straight through from the Product page, remember to go from there to a distroseries package, not to a distro package.
[15:02] <jtv> (bastardizing internal nomenclature a bit here)
[15:03] <jtv> henninge: ah, and from there you also need to click through to the actual template.
[15:03]  * jtv had stupidly forgotten that
[15:04] <henninge> jtv: the upload option there is only for updating a template, though.
[15:04] <henninge> jtv: this is about a new template.
[15:04] <cody-somerville> Maybe this is why rosetta hasn't quite caught on? No one can use it? :P
[15:04] <jtv> cody-somerville: this is only for Ubuntu, and Ubuntu was already using it.  :)
[15:05] <henninge> cody-somerville: no, it is much simpler for products (projects).
[15:05] <jtv> henninge: in that case, yes, the only way is through Soyuz.
[15:05] <henninge> jtv: what I thought.
[15:06] <henninge> cody-somerville: Only main packages end up in the language packs but I know there are more templates coming in from soyuz.
[15:06] <henninge> cody-somerville: You will have to talk to Arne or Martin Pitt about the details.
[15:17] <jtv> danilos, henninge: I'm off, see you tomorrow!
[15:17] <henninge> jtv: Ciao!
[15:17] <danilos> jtv: did you have a chance to land the export fix?
[15:18] <jtv> danilos: alllllmost, one last-minute mistake.  :(
[15:19] <danilos> jtv: it'd be nice to be able to QA that on staging tomorrow so we can get an RC as well
[15:20] <jtv> danilos: ok, ok, I'm looking at it
[15:20] <danilos> jtv: thanks
[15:35] <menesis> hello. I got an error trying to upload to ppa, but got a "Failed to upload".
[15:36] <menesis> 2009-03-30 19:53:48 ERROR   Exception while accepting:
[15:36] <menesis>  duplicate key value violates unique constraint "binarypackagerelease_binarypackagename_key"
[15:36] <menesis>  -> http://launchpadlibrarian.net/24545170/cb1TWHeZAb1ZYclOUas44ivnbEl.txt
[15:36] <jtv> cody-somerville: could that be related?
[15:36] <cody-somerville> jtv, no, thats another bug
[15:36] <Ursinha> hi menesis
[15:36] <Ursinha> bug 347194
[15:37] <Ursinha> menesis, we're working on it :)
[15:37] <menesis> Ursinha: yes it's the same, thanks
[15:38] <Ursinha> menesis, np
[15:38] <menesis> can I retry or make a new package to help it build?
[15:39] <Ursinha> menesis, hm, I don't know
[15:39] <Ursinha> as per cprov comment, it seems a race condition of some kind
[15:40] <cprov> menesis: what's the build URL ?
[15:41] <menesis> cprov: https://launchpad.net/~schooltool-owners/+archive/ppa/+build/923947
[15:42] <cprov> menesis: build record fixed, ignore the error
[15:42] <cprov> menesis: it won't happen again :)
[15:43] <menesis> cprov: thank you, that was quick fix :)
[15:46] <cprov> menesis: np, you are welcome.
[19:19] <cody-somerville> Why isn't this import working? https://code.edge.launchpad.net/~vcs-imports/sion/trunk
[19:19] <mwhudson> cody-somerville: probably because svn sucks
[19:21] <mwhudson> cody-somerville: did the url change at some point?
[19:21] <cody-somerville> Yes
[19:21] <mwhudson> cody-somerville: who made the change for you?
[19:21] <cody-somerville> I made the change
[19:21] <mwhudson> oh
[19:21] <mwhudson> well: don't do that
[19:21] <cody-somerville> doh
[19:21] <mwhudson> cody-somerville: can you tell me what the old url is?
[19:22] <cody-somerville> s/gigolo/sion/
[19:22] <cody-somerville> so, (NEW) http://svn.xfce.org/svn/goodies/gigolo/trunk  -> (OLD) http://svn.xfce.org/svn/goodies/sion/trunk.
[19:24] <mwhudson> cody-somerville: i think it's fixed now
[19:25] <cody-somerville> what magic did you cast?
[19:25] <mwhudson> cody-somerville: it involves ssh and nasty shell scripts
[19:26] <mwhudson> cody-somerville: except it didn't work :(
[19:27] <cody-somerville> All I want is my gigolo! :(
[19:28] <mwhudson> cody-somerville: would requesting a new import work for you?
[19:28] <cody-somerville> can you rename the sion project to gigolo for me?
[19:29] <mwhudson> cody-somerville: it wouldn't merge with any branch you've made of the current import
[19:29] <mwhudson> cody-somerville: i cannot
[19:29] <mwhudson> cody-somerville: mthaddon or herb can though
[19:29] <cody-somerville> mthaddon, herb: Could you rename sion to gigolo for me please?
[19:30] <cody-somerville> mwhudson, you're welcome to delete our broken import if you'd like
[19:30] <cody-somerville> (although somehow I get the impression that it isn't just that easy :P)
[19:30] <mwhudson> cody-somerville: you need to unhook the branch from sion trunk
[19:30] <mthaddon> cody-somerville: can you file a question for it if you haven't already so we can track the request? https://edge.launchpad.net/launchpad/+addquestion
[19:30] <cody-somerville> mthaddon, I have already
[19:31] <cody-somerville> mwhudson, okay
[19:31] <mthaddon> cody-somerville: you have the link?
[19:32] <cody-somerville> mthaddon, https://answers.edge.launchpad.net/launchpad/+question/65728
[19:32] <cody-somerville> mwhudson, done
[19:33] <mwhudson> cody-somerville: the import is deleted, time to request a new one :)
[19:33] <mthaddon> cody-somerville: you want sion kept as an alias
[19:33] <mthaddon> s/alias/alias?/
[19:33] <cody-somerville> mthaddon, sure thing
[21:31] <AnMaster> someone said you didn't need to create branch on launchpad first
[21:31] <AnMaster> when pushing
[21:31] <AnMaster> right?
[21:31] <wgrant> AnMaster: That was me.
[21:32] <AnMaster> so why doesn't bzr push lp:~anmaster/efunge/supervisor-tree work? pushing branches I created on website first works
[21:32] <AnMaster> but that command gives me
[21:32] <wgrant> Yes, you can just push to a valid but non-existent URL.
[21:32] <AnMaster> bzr: ERROR: Cannot lock LockDir(lp-46121872:///~anmaster/efunge/supervisor-tree/.bzr/branchlock): Transport operation not possible: readonly transport
[21:32] <AnMaster> wgrant, the branch name is supervisor-tree
[21:32] <wgrant> Make sure you've run bzr launchpad-login
[21:32] <AnMaster> is it invalid?
[21:32] <AnMaster> wgrant, it uses ssh keys right?
[21:32] <AnMaster> iirc
[21:32] <wgrant> That's fine, assuming that your Launchpad username is 'anmaster' and the 'efunge' project exists.
[21:33] <wgrant> It will try to use HTTP unless you tell it your username with 'bzr launchpad-login <username>'
[21:33] <AnMaster> wgrant, and yes efunge exists and I'm the lone developer of it
[21:33] <AnMaster> and I'm called anmaster on there
[21:33] <AnMaster> $ bzr launchpad-login
[21:33] <AnMaster> anmasterkB @    0kB/s
[21:33] <AnMaster> huh
[21:33] <AnMaster> that looks strange
[21:33] <wgrant> It does.
[21:33] <wgrant> I presume it's just a progress indicator gone wrong...
[21:34] <AnMaster> ah yes
[21:34] <AnMaster> wgrant, bzr 1.13.1
[21:34] <AnMaster> I follow ~arch bzr on gentoo here
[21:34] <AnMaster> as in testing version
[21:34] <AnMaster> still bzr: ERROR: Cannot lock LockDir(lp-46121872:///~anmaster/efunge/supervisor-tree/.bzr/branchlock): Transport operation not possible: readonly transport
[21:34] <AnMaster> any idea about that?
[21:35] <AnMaster> I'll assume pushing without creating is broken and just create it manually sigh
[21:35] <wgrant> What is the command that you are using?
[21:35] <AnMaster> bzr push lp:~anmaster/efunge/supervisor-tree
[21:35] <wgrant> I did that just a couple of days ago, though.
[21:35] <AnMaster> as I said
[21:35] <wgrant> Ah, so you did.
[21:35] <wgrant> Oh.
[21:35] <wgrant> I see.
[21:35] <wgrant> That branch already exists!
[21:35] <AnMaster> oh
[21:36] <wgrant> And it's a mirrored branch, so it's read-only except by Launchpad itself.
[21:36] <AnMaster> how do I convert mirrored branch to hosted one
[21:36] <AnMaster> since server is gone
[21:36] <AnMaster> so I'll need to convert it
[21:36] <AnMaster> wgrant, hosting company went bankrupt
[21:36] <wgrant> You can delete it, or probably change the type on the edit page.
[21:36] <wgrant> Ouch.
[21:37] <AnMaster> well then I'll wait
[21:37] <AnMaster> I can't change on edit page
[21:37] <AnMaster> too much work to remove and re-create atm
[21:37] <wgrant> Unfortunately it looks that way.
[21:38] <wgrant> mwhudson: Is it possible to change a branch type?
[21:38] <mwhudson> wgrant: not really
[21:38] <wgrant> AnMaster: Can't you just delete and repush, taking all of a couple of minutes?
[21:38] <mwhudson> wgrant: we'd like to change this
[21:38] <mwhudson> AnMaster: i can delete and repush from a machine in the dc if you like
[21:38] <mwhudson> that will be pretty fast
[21:39] <mwhudson> well
[21:39] <mwhudson> pull, push, delete, reassign i guess, for sanity
[21:39] <AnMaster> wgrant, had to re-add details and such
[21:39] <AnMaster> meh
[21:40] <AnMaster> mwhudson, feature request though is being able to switch between hosted and mirrored with edit branch
[21:40] <mwhudson> AnMaster: yes i know
[21:40] <AnMaster> possibly both ways. switching to mirrored would need validating it is valid
[21:40] <mwhudson> AnMaster: that's not possible right now
[21:41] <mwhudson> AnMaster: i'm trying to suggest a workaround
[21:41] <AnMaster> yeah
[21:41] <AnMaster> I'll do it tomorrow
[21:55] <wgrant> Why do I get a 403 at https://code.edge.launchpad.net/~launchpad-pqm/lazr-js/toolchain? I can see the branch in listings and Loggerhead fine.
[21:56] <mwhudson> i bet it's something terrible involving a private team
[21:58] <wgrant> mwhudson: Shall I file a bug?
[21:59] <mwhudson> wgrant: please
[21:59] <mwhudson> he says, pretty confident that it's not going to be him that fixes it
[23:11] <maxb> ooi, what time of day does Launchpad production get deployed?
[23:16]  * maxb finds the blog