[02:04] <RenatoSilva> Any ideas on how to use rosetta to translate a software that does not use LP officially for translations?
[02:05] <spm> RenatoSilva: the first stumbling block'd be ensuring the upstream knows to grab the appropriate po files from LP
[02:06] <RenatoSilva> spm: I'd do that
[02:06] <RenatoSilva> spm: I have a planned workflow
[02:07] <spm> :-) which is probably the biggest problem for my 2c worth; so sounds like you'd be fine
[02:07] <RenatoSilva> but LP's policy denies it
[02:07] <spm> oh?
[02:07] <RenatoSilva> the project must use LP for translation officially
[02:07] <RenatoSilva> I'd just use rosetta as a po web editor
[02:08] <spm> Ah. I wasn't aware of that wrinkle. apologies for misleading.
[02:08] <RenatoSilva> spm: you're not from staff?
[02:08] <spiv> spm: I assume it's known that the branch scanner doesn't seem to be working?
[02:08] <spm> sysadmin, not translation policies expert :-)
[02:08] <spm> spiv: aye. it's a bit twitchy atm.
[02:09] <spm> spiv: mwhudson did tell you about the s/~spiv.*// addition to the scanner??
[02:10] <mwhudson> spiv, spm: the scanner is fine, the puller is ill
[02:10] <spm> mwhudson: i did it *again*. s/scanner/puller/ gah gah gah gah.
[02:11] <mwhudson> spm: spiv started it
[02:11] <RenatoSilva> spm: I was thinking of a hack: introduce the po/pot in my related project
[02:11] <spm> to confirm - scanner is busy working fine right now.
[02:11] <spiv> mwhudson: well, the lack of scanning is the symptom I noticed :P
[02:11] <mwhudson> spiv: sure
[03:08] <spm> robert_ancell: can you confirm that branch of yours is now as expected?
[03:12] <robert_ancell> spm: looking now...
[03:13] <spm> ta
[03:16] <robert_ancell> spm, it looks like revision 113 got lost
[03:16] <spm> mwhudson: ^^ ???
[03:17] <robert_ancell> it's in the log but the changes are not in the head
[03:17] <mwhudson> robert_ancell: ??
[03:17] <mwhudson> robert_ancell: which is this branch?
[03:17] <robert_ancell> lp:~ubuntu-desktop/gdm/ubuntu
[03:19] <mwhudson> robert_ancell: what is is that's other than you expect?
[03:19] <mwhudson> s/is is/is it/
[03:19] <robert_ancell> so rev 118 added debian/patches/80_disable_busy_cursor.patch and modified debian/changelog but a clone of lp:~ubuntu-desktop/gdm/ubuntu doesn't show these changes
[03:21] <mwhudson> robert_ancell: you mean rev 113, right?
[03:21] <robert_ancell> sorry, yes
[03:21] <mwhudson> robert_ancell: it should be there now
[03:21] <mwhudson> robert_ancell: when did you make the clone that missed the rev?
[03:22] <robert_ancell> The clone was longstanding, I updated to 113 today, made some commits, then couldn't push which is why I asked here
[03:23] <robert_ancell> So bzr log -v shows 114 did remove the changes but that doesn't seem to make sense
[03:25] <mwhudson> robert_ancell: i guess you need to ask seb about that
[03:25] <mwhudson> robert_ancell: i very much doubt it's launchpad's fault
[03:26] <robert_ancell> I've emailed seb to check, I'll let you know if it wasn't intentional
[03:26] <mwhudson> ok
[03:26] <robert_ancell> spm, mwhudson, thanks
[04:22] <spiv> mwhudson: Ooh, OOPS-1368MPCJ1 (LP failed to send merge proposal notification, maybe because it wasn't pulled yet so no diff could be made?)
[04:22] <mwhudson> i thought the diff mailer was smarter than that
[04:23]  * spiv smiles sweetly
[04:23] <spiv> mwhudson: on the other hand, I got a very polite email from LP telling me about the problem :)
[04:29] <mwhudson> spiv: sounds like a dangerous regression, informing users what's going on rather than just silently doing nothing
[04:39] <spiv> mwhudson: dangerous and possibly subversive!  The rebellion must be quashed!
[04:48] <ScottK> At least it didn't actually let the user do anything about it.
[06:36] <al-maisan> Good morning!
[06:42] <mbt> Wondering if anyone would be around to help me with a server-side codehosting problem; need a lock broken:  http://pastebin.com/m73b09df5
[06:47] <spm> mwhudson: ^^ I assume this is something fairly trivial for me to do - any gotchas I need to be aware of? (breaking the lock)
[06:52] <lifeless> mbt: spm: users can break their own locks.
[06:53] <mbt> lifeless, Please see the pastebin.  It will not let me.
[06:53] <lifeless> mbt: 'bzr break-lock :push'
[06:53] <lifeless> mbt: thats because the URL it tells you to use is bong; there is a bug open about that
[06:53] <mbt> lifeless, So the command it gives in its help output is incorrect?
[06:53] <mbt> Ahh, alright.
[06:54] <mbt> lifeless, thanks!  I'm able to push again.
[08:26] <ripps> Is there going to be the possibility to delete ppa's in the future?
[08:28] <noodles775> ripps: afaiui, we'd always want to keep a history of the publishing (like any other publishing system). Why do you want to delete the history of an old PPA?
[08:30] <ripps> noodles775: I was considering creating a seperate ppa for testing new libmpdclient2 apps, but once they've hit fullsteam, I wanted to move the packages to their respected primary ppas
[08:30] <ripps> I suppose I should just use my personal staging ppa for that.
[08:31] <ripps> It seems unneccsary to have an empty ppa in my teams page
[08:31] <noodles775> ripps: yeah, either way that'd be fine, but I still don't see why you'd need or want to delete the history of publishing to that test ppa.
[08:31] <noodles775> ripps: right
[08:32] <noodles775> ripps: so perhaps we should investigate the ability to dis-associate a ppa with a team/person.
[08:32] <ripps> noodles775: actually, yes. That probably be better
[08:32] <noodles775> ripps: great. I'll see if there's already a bug, if not I'll file it.
[08:33] <ripps> noodles775: thanks :)
[08:37] <ripps> noodles775: Oh, I have an even better question, if I could indeed disassciate a ppa from my team, could I make the leftover address of that old ppa forward to a new one. It seems I might need to merge 2 ppas in the near future.
[08:41] <noodles775> ripps: I've updated bug 392887 with your thoughts. Feel free to add more details.
[08:41] <ripps> noodles775: awesome, thanks
[10:09] <dpm> jtv: henninge_, can any of you come by to #ubuntu-installer? We've got a problem with the debian-installer templates in Ubuntu and it would be great if you could give us a hand...
[10:10] <jtv> dpm: coming...
[10:10] <dpm> thanks!
[13:58] <mpt> "The following errors were encountered: OK"
[14:01] <beuno> mpt, leaving aside our stupid error message, launchpad seems to be very slow atm
[14:02] <mpt> ah, that's probably why
[14:02] <mpt> (why the error message didn't end up fully-formed, that is)
[14:02] <beuno> mpt, I think the API does funky things to errors
[14:03] <beuno> we have an error handling sprint in Nov
[14:03] <beuno> for lazr-js
[14:35] <ulysses__> LP and Ubuntu Wiki seems to be dead
[16:33] <mbt> Is it possible to simply upgrade a project's trunk to the 2a bzr format in-place, or does a new trunk branch really have to be created?
[16:40] <kirkland> what's the process for kick/banning a bad LP user?
[16:42] <kirkland> can an admin please kick/ban davidelizondo2006?
[16:42] <kirkland> this user is adding garbage to a number of my bug reports
[16:42] <kirkland> i see he's doing this to others too
[16:44] <ScottK> kirkland: I think you need to ask a question about malone on LP to get it done
[16:44] <kirkland> ScottK: cheers
[16:45] <ScottK> Also if it's garbage that's not obviously spam, I wish you luck.  I've yet to succeed.
[17:18] <RobOakes> Is this a good place to ask PPA and package signing questions?
[17:27] <lodder> hi RobOakes
[17:34] <maxb> RobOakes: This is a good place to ask about PPA issues insofar as they relate to using Launchpad-the-service. If the questions tend towards "How do I make an Ubuntu source package?", then they are more into #ubuntu-motu's territory
[17:36] <RobOakes> Thanks maxb.  I've got an unsigned package that I would like to change to a signed package and upload to my PPA.
[17:36] <maxb> debsign whatever_source.changes
[17:36] <RobOakes> My question is, what type of key do I need to sign it with.  Do I use an ssh key (like my pub_rsa), or do I need to create a PGP key?
[17:37] <RobOakes> (Sorry, I'm tremendously new to the encryption/signing thing and I've just started reading about these this morning.)
[17:37] <maxb> Package signing is exclusively to do with PGP keys
[17:37] <maxb> The only time you use a SSH key to interact with Launchpad is when you are pulling/pushing code using Bazaar
[17:38] <RobOakes> Okay, that makes sense.  I wasn't sure if I needed to use my existing launchpad SSH key (which wasn't something I was excited to do), for signing.
[17:38] <RobOakes> Which is to say, I'm not even sure if an ssh key can sign
[17:41] <RobOakes> Does the encryption type matter?  Is there any reason DSA Elgamal is better than RSA?
[17:42] <lodder> RobOakes: use the default
[17:43] <maxb> Although there's discussion on changing the default at the moment :-)
[17:43] <lodder> ah
[17:45] <maxb> I am in no way a crypto guru, but I'd probably create an RSA 4096 bit key if I was creating a new personal general purpose key at the moment
[17:49] <stani> how can I get all blueprints associated to a project series through the launchpad api?
[17:50] <beuno> stani, I think we don't have APIs for blueprints
[17:50] <mpt> How do I change a bug report from private to public?
[17:50] <mpt> (or from security-related to not)
[17:51] <stani> beuno: ah thanks, hmm... i wanted to batch assign blueprints to a milestone
[18:16] <addikt1ve> hi
[18:16] <addikt1ve> how do i delete a projet i just registered?
[18:19] <Ursinha> addikt1ve, you have to file a question asking for it to be removed, you can do it here: https://answers.launchpad.net/launchpad/+addquestion
[18:19] <addikt1ve> Ursinha: yeah I just discovered that page
[18:20] <addikt1ve> mmh actually it seems more reasonable to change ownership of the project
[18:20] <addikt1ve> I guess I did it right
[18:21] <addikt1ve> because its maintener bacame "wedesign Team" instead of addikt1ve :)
[18:21] <addikt1ve> but it's still telling me to use lp:~the-addikt1ve/wedesign/trunk as a bzr url
[18:23] <addikt1ve> and, wel
[18:23] <addikt1ve> l that sucks.
[18:24] <LarstiQ> that is easy to change
[18:25] <LarstiQ> addikt1ve: push up a branch under the team namespace, like lp:~webdesign-team/webdesign/trunk
[18:25] <LarstiQ> addikt1ve: then set the series focus to point at that branch instead of lp;~the-addikti1ve/wedesign/trunk
[18:27] <addikt1ve> LarstiQ: actually, I created a new branch which belongs to wedesign Team, and deleted the branch which I used to own
[18:27] <addikt1ve> there was no code in it, so, that's cool.
[18:27] <addikt1ve> thank you :)
[18:42] <mrooney|w> Oh no, a bug! Perhaps launchpad isn't properly html escaping when sending bugs upstream?
[18:43] <mrooney|w> I tried to send https://bugs.edge.launchpad.net/ubuntu/+source/compiz/+bug/438580 upstream to compiz by filing through launchpad and it sent me to http://bugs.opencompositing.org/2008%3AsvnDellInc.%3ApnXPSM1330%3Apvr%3ArvnDellInc.%3Arn0U8042%3Arvr%3AcvnDellInc.%3Act8%3Acvr%3A%0Admi.product.name%3A%20XPS%20M1330%0Admi.sys.vendor%3A%20Dell%20Inc.%0Asystem%3A%20distro%20%3D%20Ubuntu%2C%20architecture%20%3D%20x86_64%2C%20kernel%20%3D%202.6.31-11-generic wh
[18:43] <mrooney|w> I guess, I should file a bug. Anyone know the appropriate component?
[19:25] <jkakar> mbt: Thanks for your AutoPPA bug reports.
[19:29] <mbt> jkakar, no problem.  Do you see any workarounds that I can employ to use the tool?
[19:29] <jkakar> mbt: Yeah, you're missing a dash in your version string.
[19:30] <jkakar> mbt: I've posted a workaround on the bug report.
[19:30] <jkakar> mbt: As far as I understand it, AutoPPA is doing the right thing.  The version you tried to build didn't have a "package version" component, which is expected/assumed to be there, so kaboom. :)
[19:30] <jkakar> mbt: Of course, it could fail much more gracefully. :)
[19:31] <jkakar> mbt: I'm stepping away for lunch, but please let me know if that workaround solves the issue for you.
[19:32] <mbt> Ahh, alright.  I'll see if I can come up with a patch.
[19:33] <jkakar> mbt: Awesome!  You want to look at autoppa/target.py, specifically at BuildTarget._get_version.
[19:33] <mbt> jkakar, Cool.  Will do that in a few.  Seems to be working now, I didn't think about the extra hyphen.  Oops! :)
[19:34] <jkakar> mbt: Yeah, I've had that "WTF?!?!" moment several times because of a missing dash.
[19:51] <mbt> jkakar, I don't know if I can do that.  I appear to be getting another error about missing a "commandant" module.
[20:02] <Kmos> why this doesn't work on staging? https://bugs.staging.launchpad.net/ubuntu/+source/bash/+filebug/dogOgTHhDHOnyXMsARfHVijyDrx/+login?field.title=bash+crashed+with+SIGSEGV+in+__kernel_vsyscall%28%29
[20:13]  * RenatoSilva is trying to convince people to use LP :) http://img74.imageshack.us/img74/651/moinlp.png
[20:16] <jkakar> mbt: Yeah, the version of AutoPPA in trunk relies on commandant.  It's available at lp:commandant, or you can install the python-commandant package from https://edge.launchpad.net/~jkakar/+archive/commandant
[20:26] <jkakar> mbt: Interesting, I wasn't aware of "epochs" in version strings.  I'll try and check out the issue this week.
[20:28] <mbt> jkakar, yes, by default dpkg assumes a 0, so the full version number is for example 0:0.7.4dev-1ubuntu0 or (with a 1 epoch) 1:0.7.4dev-1ubuntu0.  The epoch serves to level uncomparable versions.
[20:28] <mbt> I did find the PPA, but now I get some commandant error about a missing import.
[20:28] <jkakar> mbt: I see.  So I guess the real problem is that the filenames AutoPPA writes are crap?
[20:28] <mbt> No, no.
[20:28] <jkakar> mbt: Oh?  I think it only relies on bzr.
[20:29] <mbt> Epochs don't go in the file names.
[20:29] <jkakar> Ah ha.  Okay that makes more sense.
[20:29] <mbt> Just in the version number.
[20:29] <jkakar> Thanks for clarifying.
[20:29] <mbt> At least I'm 90% certain of that, let me double check to be sure.
[20:29] <mbt> First let me find the fialing import error thing.
[20:30] <mbt> jkakar: ImportError: cannot import name DocstringHelpTopic
[20:31] <mbt> Supposedly supposed to be in commadant.help_topics
[20:31] <mbt> commandant.help_topics, even.
[20:32] <jkakar> mbt: Crap.  I guess that means you need to use lp:commandant.  Sorry for the confusion.
[20:33] <mbt> Alright, I'll try that in a few.  First to find out why my packages aren't building from AutoPPA.  :-P
[20:35] <mbt> Oh, hrm.
[20:35] <mbt> jkakar, is there a way to tell AutoPPA to run autogen.sh locally before rolling the package?  I don't store generated files in the project's branch.
[20:39] <jkakar> mbt: No, but that's a cool idea.  Can you file a bug please?
[20:39] <mbt> Sure thing.
[20:39] <mbt> In the interim, I think I can work around it by using a branch that is just used for the builds, and storing the files in there.
[20:39] <jkakar> mbt: Yeah.
[20:40] <ThomasWaldmann> moin :)
[20:40] <jkakar> mbt: It seems that that pattern, one branch for upstream code, another branch for packaging, is quite common and even recommended, to keep the upstream branch "pure".  I've recently using the pattern with some of my other projects and it's working well.
[20:41] <ThomasWaldmann> one of our translators is suggesting moving the moin translations from master wiki to lp
[20:41] <mbt> jkakar, I can see that;  for me, it's just extra hassle, but I can see where it would provide benefit.
[20:41] <ThomasWaldmann> is it correct that i need to use bzr for translation files pushing/pulling or can i use something else also?
[20:42] <LarstiQ> ThomasWaldmann: tarballs afaik, but I know very little about the translation part
[20:43]  * ThomasWaldmann uses mercurial (and has used gnu arch in the past) and is not very keen on using bzr because of that :)
[20:43] <LarstiQ> ThomasWaldmann: yeah, I know
[20:43] <LarstiQ> (didn't know about your arch usage though :)
[20:44] <jkakar> mbt: Yeah.
[20:44] <LarstiQ> ThomasWaldmann: mercurial wise, I don't think launchpad has any support for that, but you could try talking to jelmer
[20:45] <ThomasWaldmann> i could also live with http or xmlrpc :)
[20:45] <LarstiQ> ThomasWaldmann: then I'd look into the option of up/downloading .po tarballs
[20:46] <ThomasWaldmann> ok, thanks
[20:53] <RenatoSilva> ThomasWaldmann: you could upload/download the po(t) files manuallly, but I think you mean have a script doing that using some standard url
[20:53] <ThomasWaldmann> yes
[21:23] <stani> is it possible to remove a series target from a bug report?
[21:24] <stani> if I try "del bug.bug_tasks[1]" I get "TypeError: 'Collection' object doesn't support item deletion"
[21:28] <maxb> stani: I'm pretty sure you can't delete bugtasks
[21:29] <stani> maxb: is there than another way to remove a series which is wrongly assigned to a bug?
[21:29] <maxb> I think in such a case, the series nomination is usually just declined
[21:30] <maxb> but stays visible on the bug in declined status
[21:31] <stani> maxb: do you mean with declined the 'Invalid' status?
[21:34] <meden> Hello, I need help to copy official Ubuntu packages to my PPA, someone can help me?
[21:41] <bialix> creating new project @ lp; stuck with Name field, hint says: "The name of the project as it would appear in a paragraph." -- what it means "in a paragraph"?
[22:19] <RenatoSilva> ThomasWaldmann:
[22:28] <Kmos> stani: you should set that bug task as invalid, you can't remove it.
[22:28] <stani> Kmos: ok thanks