[00:13] <c_korn> hello, can some opera user confirm bug 396081?
[00:18] <jkimball4> Can I get my account deleted, please?
[00:18] <jkimball4> I no longer use it.  Would like to get it closed.
[00:19] <Ursinha> jkimball4, you can disable it in your profile
[00:19] <jkimball4> Okay, i'll take a look.  I read that I had to get an admin to delete it.
[00:20] <mwhudson> if you can still access it, you can disable it yourself
[00:21] <jkimball4> Done and Done.  Thanks chaps
[00:27] <wgrant> Ampelbein: Security uploads don't show up because they are actually uploaded to the ~ubuntu-security P3A, which you can't see. They're then copied into Ubuntu, which doesn't generate an upload record yet.
[01:23] <thumper> mwhudson: the wine import...
[01:23] <thumper> mwhudson: was it started before our re-roll?
[01:24] <thumper> mwhudson: the start time of 47 hours ago seems too far back
[01:24] <thumper> finished 13 hours ago taking 34 hours
[01:27] <mwhudson> oh maybe
[01:28] <mwhudson> i think i approved it just after tom told us the rollout was complete
[01:28] <mwhudson> but maybe it was before indeed
[01:29] <mwhudson> i can check, i guess
[01:31] <mwhudson> thumper: yeah, no saved db for that import
[01:32] <mwhudson> thumper: i deleted the so far imported branch
[01:40] <wgrant> Is a branch disk size indicator going to be showing up at some point soon?
[01:41] <lifeless> Is there a bug open?
[01:41] <wgrant> I think so.
[01:41] <wgrant> I remember it being active recently.
[01:41] <wgrant> I'll see if I can track it down...
[01:42] <wgrant> Ah, yes, bug #350031
[01:42] <wgrant> Apparently mwhudson was working on it last month.
[01:46] <mwhudson> probably not super soon
[01:46] <mwhudson> although it's probably not that much work...
[02:50] <GatoLoko> hi
[02:53] <GatoLoko> launchpad is giving me an error message that seems like i'm a launchpad beta testes, but i'm not, is this something known?
[02:53] <micahg> GatoLoko: what is the error message?
[02:54] <GatoLoko> Our edge server has a lower timeout threshold than launchpad.net, so we can catch those before they hit a wider audience. As a member of the Launchpad Beta Testers team, you're more likely to experience them. If this is blocking your work, you can disable redirection.
[02:54] <micahg> ah
[02:54] <micahg> did you go to edge.launchapd.net?
[02:54] <micahg> *launchpad
[02:54] <GatoLoko> nop, i was trying to load https://launchpad.net/~locoteams
[02:54] <micahg> hmm
[02:55] <GatoLoko> opened a new tab on firefox, copypasted the url and there was a timeout error with that message
[02:55] <micahg> hmmm
[02:55] <micahg> I didn't get that timeout error but another one
[02:56] <GatoLoko> i even checked that i'm not a beta tester team member
[02:56] <GatoLoko> i though maybe there was an error and something/somebody added me to the team
[02:56] <GatoLoko> but i don't appear on the team member list
[02:58] <GatoLoko> reloading the same url works now, but it was weird
[02:58] <GatoLoko> xD
[02:58] <micahg> I don't know
[02:58] <micahg> anyone else have any ideas?
[03:26] <poolie> GatoLoko: what's your launchpad id? GatoLoko?
[03:26] <poolie> it does seem kind of slow at the moment
[03:27] <GatoLoko> https://launchpad.net/~gatoloko  <-- i'm this ugly guy
[03:27] <GatoLoko> xD
[03:28] <poolie> do you still have that tab with the erorr open?
[03:28] <poolie> if so, filea  bug with the screenshot
[03:29] <GatoLoko> i reloaded it a while ago and it worked
[03:29] <GatoLoko> if it happens again a will report it
[06:43] <cellofellow> is there an IDE with comprehensive LaunchPad integration? The bzr, the bugs, the blueprints, the branches, the whole nine yards?
[10:00] <nfilus> hello
[10:01] <nfilus> how can I speedup the review of uploaded messages.pot?
[10:24] <wi_nk> i haven't received my ubuntu cd. why? how can i know what happened to it
[10:47] <lamalex> Is there a way to be notified of all changes to blueprints like I am with bugmail?
[10:55] <intellectronica> lamalex: sort of. you can get changes for a specific blueprint, but you can't do that for all the blueprints in a project, like you can with bugs
[10:55] <lamalex> that's whack
[10:55]  * lamalex opens bug
[10:55] <lamalex> but searches first..
[10:55] <intellectronica> lamalex: patches welcome .... well, patches will be welcome shortly :)
[10:56] <lamalex> yah :)
[10:56] <lamalex> can't wait
[10:56] <lamalex> word on the street is some people at GNOME are thinking of moving from bugzilla
[10:56] <lamalex> some people have been talking to them about how awesome LP is at GCDS and a bunch of people are really hyped on it
[10:57] <mwhudson> cool :)
[10:57] <lamalex> I KNOW
[10:57] <mwhudson> still unlikely though
[10:57] <mwhudson> i'd say
[10:57] <lamalex> hey
[10:57] <lamalex> dont rain on my parade
[10:57] <mwhudson> :)
[10:57] <lamalex> let me dream
[10:57] <mwhudson> though if people get enthusiastic and fix blueprints for us, that would be awesome :)
[10:58]  * mwhudson wanders off
[10:58] <lamalex> whats the release date? late july?
[10:58] <mwhudson> yep
[10:59] <mwhudson> (barring technical glitches)
[11:00] <lamalex> radical
[11:00] <lamalex> although I'm /really/ bummed that codehosting will not be part of it
[11:01] <lamalex> that integration is one of the most excellent parts of the service, so I understand canonicals desire to protect it..
[12:22] <lamalex> Hi, I'm trying to upgrade our LP bzr repo's format to 1.6.1-rich-root
[12:22] <lamalex> I did the converstion locally and am trying to do bzr push --overwrite
[12:22] <lamalex> but it fails
[12:23] <lamalex> do I /need/ to do this over the network?
[13:00] <spiv> lamalex: yes, or at least remove the .bzr directory over sftp (the lftp client is good for that) and push --use-existing-dir
[13:01] <spiv> lamalex: --overwrite won't overwrite formats, it's purely about overwriting one history with another.
[13:41] <lamalex> spiv: ahh, wish I had known before I ran bzr check over the network
[13:48] <lamalex> spiv: how do i connect via sftp?
[13:48] <c_korn> hello, can some opera user confirm bug 396081?
[13:50] <persia> I'm encountering another Debian Developer complaining about bug #204980 for one of their maintained packages.  Does anyone know if this is scheduled to get work in the next few months?
[13:50] <barry> c_korn: i'm pulling down an updated opera now.  i'll give it a shot
[13:57] <barry> persia: i don't know for sure, but it may not be scheduled until after launchpad 3.0 is released
[13:58] <persia> barry, I guess my question is more: "Is it on the list of stuff to be scheduled?", rather than a specific timeframe.
[13:58] <persia> To put it differently, should I be advising complainants that they should just unsubscribe from the packages, or that they should try submitting a patch once the code is available.
[13:59] <barry> persia: it's definitely on our radar to give users more control over exactly what email they receive from launchpad
[13:59] <persia> OK.  I'll pass that along.  Thanks.
[14:00] <barry> np.  short term (i.e. next couple of months) it's best to unsubscribe
[14:00] <lamalex> anyone know how i can connect to bazaar.launchpad.net with sftp?
[14:01] <barry> abentley: ^^
[14:02] <barry> lamalex: i don't, but abentley might though he may not be actually online yet
[14:03] <persia> I've never done it, but I thought it was just sftp://bazaar.launchpad.net/foo
[14:06] <vila> Hi guys, I just created a PPA: https://edge.launchpad.net/~vila/+archive/ppa, uploaded a package, but when I try to install it, I get:
[14:06] <vila> WARNING: The following packages cannot be authenticated!
[14:06] <vila>   mydevtools
[14:06] <c_korn> barry: thanks for confirming
[14:06] <noodles775> vila: have you added your PPA's signing key for authentication?
[14:06] <barry> c_korn: np
[14:06] <vila> looking at http://ppa.launchpad.net/vila/ppa/ubuntu/dists/jaunty/ I see a Release file but no Release.gpg file, any hint ?
[14:07] <vila> PPA's key added and checked with sudo apt-key list
[14:07] <vila> sudo apt-get update ran too
[14:07] <barry> vila: take a look at this page: https://help.launchpad.net/Packaging/PPA
[14:08] <barry> vila: scroll down to the sections on adding the ppa keys
[14:08] <noodles775> Hmm... that's strange... (barry, afaiu vila has already done that?)
[14:08] <vila> scolling up the already opened page :)
[14:08] <james_w> yeah, he has added the key
[14:08] <barry> vila, noodles775 ah
[14:08] <james_w> (I've just been trying to debug it with him elsewhere)
[14:09] <barry> james_w: gotcha
[14:09] <noodles775> Hmm... so perhaps there's a delay publishing the signing key to the archive?
[14:09] <noodles775> cprov ^^^^
[14:09] <noodles775> (calling in the big-guns ;) )
[14:09] <vila> 5703355D is the key fwiw
[14:09] <barry> noodles775: :)
[14:09]  * cprov checks
[14:09] <vila> barry is not ? One more dream down the drain :-)
[14:10]  * vila hugs barry :)
[14:10]  * barry hugs vila and thanks him for boosting his ego :)
[14:12] <vila> Just for my own curiosity, should there be a Release.gpg at http://ppa.launchpad.net/vila/ppa/ubuntu/dists/jaunty/ or am I climbing the wrong tree ?
[14:12] <cprov> vila: the key generation took a little longer that it should -> https://edge.launchpad.net/~vila/+archive/ppa
[14:12] <cprov> vila: you have to modify your PPA to trigger the repository re-publication.
[14:13] <vila> what kind of modification ? Uploading a new package ?
[14:13] <cprov> vila: yes, the Release.gpg should be there.
[14:13] <noodles775> ah, so the packages were published *before* the key had been generated? That makes sense...
[14:13] <cprov> vila: deletion, copies, new upload
[14:13] <vila> cprov: ok
[14:19] <abentley> lamalex: Well, you launch and sftp client, and provide bazaar.launchpad.net as the hostname.
[14:19] <abentley> lamalex: hitchhiker, lftp and the commandline sftp client all seem to work.
[14:19] <lamalex> abentley: i can do tha tmuch, but how to i get to my projects directory?
[14:20] <abentley> lamalex: cd /~lamalex/project/branch
[14:20] <lamalex> it ust sits at [Connecting...]
[14:21] <abentley> lamalex: lftp?
[14:21] <cprov> vila: you've just won your signed PPA.
[14:21] <lamalex> abentley: yah
[14:21] <vila> cprov: seen that, was waiting for a successful install before reporting :)
[14:22] <vila> wow, the package has the ubuntu icon in front of it under synaptic ???
[14:22] <abentley> lamalex: Try starting it in the project directory: "lftp sftp://bazaar.launchpad.net/~lamalex/project/branch"
[14:23] <vila> cprov, james_w , barry , noodles775 : install successful, mission accomplished, thanks all, you resume you usual schedule
[14:23] <noodles775> yay... good to hear vila :)
[14:23] <cprov> vila: ehe, nice one!
[14:23] <barry> vila: i am the help contact today, so i am totally laser focused on your wishes and desires :)
[14:24] <abentley> lamalex: lftp does not default to sftp, so you must specify sftp:// when connecting.
[14:24] <lamalex> abentley: [Delaying before reconnect: 25]
[14:25] <abentley> lamalex: Does bzr work for you?
[14:25] <lamalex> abentley: yah
[14:26] <abentley> lamalex: That's output from "lftp sftp://bazaar.launchpad.net/~lamalex/project/branch" ?
[14:26] <vila> barry: hehe, ok, a quick question then: now that my immensely mature package has reached 2.0.0, can I just delete it in the PPA and start again with a modest 0.0.1 or is it too late ? (Half serious question, if you don't know, just ignore me :)
[14:26] <lamalex> abentley: yah
[14:27] <barry> vila: i'd never ignore you, but i don't actually know ;)
[14:27] <abentley> lamalex: Can I suggest trying hitchhiker instead?  I don't know why lftp wouldn't work for you, but hitchhiker will work anywhere bzr does.
[14:27] <lamalex> abentley: lftp sftp://bazaar.launchpad.net/~do-plugins/do-plugins/trunk
[14:28] <lamalex> abentley: can you give me a link to hitchhiker?
[14:28] <lamalex> doesn't appear to be in the repo
[14:28] <vila> barry: ok, great. Have a nice help day !
[14:28] <abentley> lamalex: lp:hitchhiker
[14:28] <persia> vila, You can't.  versions must always increase, even after deletion.
[14:28] <lamalex> abentley: heh, too easy..
[14:28] <barry> vila: you too!
[14:28] <vila> persia: Thanks !
[14:29] <abentley> lamalex: btw, why do you want sftp access?
[14:29] <lamalex> abentley: i need to mv our .bzr directory
[14:30] <lamalex> So I can push one with an upgraded format
[14:30] <lamalex> /would/ have been faster than upgrading via the network
[14:30] <lamalex> but I spent so much time trying tofigure out how that idk if it was faster
[14:30] <abentley> lamalex: Upgrading via the network is done on the server side.
[14:31] <lamalex> so you think that would just be better?
[14:31] <abentley> lamalex: There are only a few permitted filenames: ".bzr" "backup.bzr" and ".bzr.backup", so you'll need to mv to one of those.
[14:32] <abentley> lamalex: Depending on the kind of upgrade, probably not.
[14:32] <lamalex> we're going to 1.6.1-rich-root
[14:34] <abentley> lamalex: from rich-root-pack, it might be faster to upgrade directly.  From pack-0.92, it definitely won't be.
[14:34] <lamalex> abentley: yah, i'ts an old format
[14:35] <lamalex> I think pushing from a locally upgraded repo would be faster
[14:40] <fta> could someone please tell me what's wrong with https://edge.launchpad.net/~ubuntu-mozilla-daily/+archive/ppa/+build/1109028 ?
[14:41] <bigjools> fta: looks like it built twice and the second one failed to upload
[14:41] <barry> bigjools, fta from the log file: duplicate key value violates unique constraint "binarypackagerelease_binarypackagename_key
[14:41] <bigjools> yes
[14:42] <bigjools> now, to work out why
[14:42] <abentley> mthaddon: I need some help running down this bug: https://bugs.edge.launchpad.net/launchpad-code/+bug/384217
[14:42] <fta> barry, bigjools: how did that happen?
[14:43] <abentley> mthaddon: Do you know how to determine the branch id from its name?
[14:44] <bigjools> fta: it's probably a bug in the buildd manager and it got dispatched twice
[14:44] <bigjools> cprov can you confirm?
[14:47] <cprov> fta: let me check.
[14:50] <cprov> fta: the binaries seems to be correctly published, so it's probably a hiccup on the buildd-manager or in the script which takes builders in/out of the farm.
[14:50] <fta> nothing i should worry about then?
[14:51] <bigjools> no, it's built and published
[14:53] <fta> ok, thanks
[15:05] <lamalex> .. abentley  now im getting a crash when i push
[15:05] <abentley> lamalex: Please pastebin the crash.
[15:06] <lamalex> trace fills my entire buffer and then some
[15:06] <abentley> lamalex: Even part of a traceback will be helpful.
[15:07] <jpds> .26
[15:07] <jpds> Whoops, sorry.
[15:07] <lamalex> abentley: http://paste2.org/p/312578
[15:09] <abentley> lamalex: I suspect this is bzr trying to stack your branch on itself, because it's trunk.
[15:09] <lamalex> can i tell it not to stack?
[15:11] <abentley> lamalex: You can try doing "bzr init nosmart+bzr+ssh://bazaar.launchpad.net/~do-plugins/do-plugins/trunk".  If that doesn't try to stack, then you would be able to push.
[15:12] <lamalex> abentley: still use --use-existing-dir?
[15:12] <abentley> lamalex: No, you shouldn't need that.
[15:12] <lamalex> ok
[15:17] <lamalex> abentley: shouldthis be a fast operation?
[15:17] <abentley> lamalex: depends on the amount of data to be transferred.
[15:17] <abentley> lamalex: You're pushing from scratch, right?
[15:17] <lamalex> i mean the init
[15:18] <abentley> lamalex: yes, it should take a few seconds at most.
[15:18] <lamalex> init just crashed..
[15:18] <lamalex> same thing
[15:18] <lamalex> it's trying to stack
[15:19] <abentley> lamalex: So the most likely fix is to make this branch not the "development focus", push, and set it back.
[15:21] <lamalex> run init again?
[15:21] <nhandler> persia: Remember that LP Map issue? It is more interesting than I thought. Even some direct team members don't show up on the map. However, if you goto the /+map page, *all* members, direct and indirect, show up
[15:21] <nhandler> I'm creating the bug now
[15:22] <abentley> lamalex: no
[15:22] <abentley> lamalex: After you've make the branch not the developement focus, just push.
[15:23] <persia> nhandler, That's the optimisation I mentioned before.  It's intentional behaviour.  Check the old bugs, because I think it was previously discussed.
[15:23] <lamalex> abentley: still crashes
[15:24] <abentley> lamalex: does it say it's stacking when you push?
[15:24] <lamalex> it doesnt say anything, no
[15:24] <lamalex> but i ge the same "maximum recursion depth" error
[15:25] <nhandler> persia: I'm not seeing a bug about that filed against LP. Would it be filed against something else?
[15:26] <persia> nhandler, It could well be against launchpad-registry
[15:26] <persia> And it could be closed.
[15:26] <nhandler> I was looking at all bugs ever reported. I'll check -registry
[15:28] <abentley> lamalex: Did you delete the .bzr directory before pushing?
[15:28] <lamalex> abentley: in my tree?
[15:29] <lamalex> or on bazaar.launchpad.net
[15:29] <abentley> lamalex: on Launchpad.
[15:29] <lamalex> i moved it to bzr.backup
[15:29] <lamalex> it's not possible to rm a dir with hitchhiker apparently
[15:29] <abentley> lamalex: It's possible to rmtree a dir.
[15:29] <lamalex> ah, didnt see that command
[15:30] <nhandler> persia: Bug 314238, I guess I won't file a bug
[15:30] <abentley> lamalex: You need to delete the .bzr directory every time an attemp fails, or the half-built .bzr will frustrate further attemtps.
[15:31] <lamalex> abentley: k
[15:31] <lamalex> ughh its trying to stack against the development focus
[15:32] <abentley> lamalex: That's why you need to not have a development focus.
[15:35] <lamalex> abentley: how do i not set one?
[15:35] <lamalex> there's no blank option
[15:37] <abentley> lamalex: Go to the series which is your development focus, and set the branch name to blank.
[15:40] <lamalex> do /what/?
[15:40] <lamalex> ok, found it
[15:40] <lamalex> complicated
[15:44]  * lamalex hopes
[15:46] <lamalex> win!
[15:50] <lamalex> abentley: thanks a lot for your help
[15:50] <lamalex> seems to be working now
[15:50] <abentley> lamalex: I'm glad.  You're welcome.
[16:05] <mthaddon> abentley: did you still need help finding the branch id of a branch?
[16:06] <abentley> mthaddon: No, I was able to figure it out, thanks.
[16:06] <mthaddon> cool
[16:18] <fta> PPA exceeded its size limit (41398.00 of 40600.00 MiB).
[17:54] <mxpxpod> has launchpad resumed scanning release url patterns?
[18:20] <james_w> is the soyuz import from Debian running ok?
[18:21] <james_w> hmm, maybe it's a problem with Debian actually
[18:23] <james_w> the package is in the archive since the 7th, but LP is out of date
[18:23] <james_w> https://edge.launchpad.net/debian/+source/nagios-plugins
[18:24] <barry> bigjools: ^^
[19:57] <mtaylor> hey all... there's a "(community)" next to a reviewer's name on merge request review... what does it designate? It doesn't seem to be relevant to our project - or at least I don't know how any of us could be non-community
[20:01] <barry> mtaylor: do you have a link?
[20:01] <mtaylor> barry: https://code.edge.launchpad.net/~dshrews/drizzle/my_dir_removal/+merge/8426
[20:01] <mtaylor> barry: you'll notice both reviewers are marked as community
[20:04] <barry> mtaylor: that's pretty interesting!  i've never seen that before.  when the antipodeans wake up we can ask them.  in the meantime, let me check the code.
[20:05] <mtaylor> barry: silly people in other timezones...
[20:06] <barry> mtaylor: yeah!
[20:06] <mtaylor> barry: I'm glad that it hasn't been there for years and I'm just now noticing it at least. :)
[20:06] <barry> mtaylor: or as homer might say: stupid rotating earth!
[20:06] <mtaylor> doh
[20:06] <Ursinha> lol
[20:09] <barry> mtaylor: source to the rescue!  that tag means that the person reviewing it is not a member of the default branch reviewer team
[20:10] <barry> mtaylor: i.e. not a drizzle-developer
[20:10] <barry> mtaylor: indeed brian aker does not appear to be a member of that team
[20:11] <barry> afaict
[20:11] <barry> mtaylor: basically it means it's an "unofficial" review
[20:27] <mtaylor> barry: hrm. that's interesting. because both brian and jay are members of ~drizzle-developers (brian is the owner of the team, in fact)
[20:28] <mtaylor> barry: bug perhaps?
[20:29] <barry> mtaylor: i think so.  i could be reading the code wrong, but it might be a bug.  jml, mwhudson, thumper are any of you awake yet?
[20:29] <mtaylor> barry: makes sense if it's a team member/non-team-member thing
[20:31] <barry> mtaylor: yep, i think that's the basic intent.  i could be reading the team membership check wrong though.  those guys will be up and active in a few hours so we can ask them then
[20:34] <mtaylor> barry: awesome. thanks!
[20:45] <Kangarooo> drupal doesn't want to be translated? https://translations.launchpad.net/drupal
[20:47] <barry> Kangarooo: apparently not in launchpad at least
[20:48] <barry> Kangarooo: http://drupal.org/project/Translations
[20:48] <Kangarooo> ubuntu is working with it also..
[20:57] <MrKanister1> hi. I got a question regarding the python launchpad API
[20:58] <MrKanister1> oh...it's two questions :)
[20:58] <MrKanister1> 1. I heard about "launchpadlib" and "launchpadbugs" which should work quite different
[20:59] <MrKanister1> which of them can you recommend?
[20:59] <dpm> barry: can you give me a hand purging the mailing list for https://launchpad.net/~launchpad-translators-leaders? It's about what I was asking you last week regarding renaming the team
[21:00] <barry> dpm: done!
[21:00] <dpm> barry: awesome, thanks (I might ask you for another one in a few minutes)
[21:01] <barry> dpm: np
[21:01] <barry> MrKanister1: i'm not familiar with launchpadbugs
[21:02] <barry> MrKanister1: launchpadlib is the python binding we're supporting
[21:02] <MrKanister1> barry: I think launchpadbugs was created by Markus Korn and it integreates functions of it (found this: http://www.linux-archive.org/launchpad-user/140985-launchpad-api-testing.html)
[21:02] <jpds> MrKanister1: launchpadlib.
[21:03] <jpds> MrKanister1: I'm not sure what thekorn  is doing with it in the light of the API.
[21:04] <MrKanister1> barry, jpds: ok..thanks. Now, although digging through some pages of documentation, I don't know how to get for example the importance of a bug
[21:05] <dpm> hm, I'm trying to rename a team from 'launchpad-translators-leaders' to 'launchpad-translations-coordinators', but I get a "The name 'launchpad-translations-coordinators' has been blocked by the Launchpad administrators." error. Could anyone give me a hand on that?
[21:05] <MrKanister1> I make it to the point where I can do "bug = launchpad.bugs[1]" and can read out the title, etc, but I don't know how to get further
[21:05] <barry> dpm: you'll have to ask a losa or kiko-fud for that i think
[21:06] <barry> mthaddon, herb ^^
[21:06] <mthaddon> dpm: I can take care of that for you
[21:06] <dpm> thanks barry, thanks mthaddon
[21:06] <jpds> MrKanister1: http://bazaar.launchpad.net/~ubuntu-dev/ubuntu-dev-tools/trunk/annotate/head%3A/requestsync#L364
[21:07] <mthaddon> dpm: can you file a quick question on LP with the request just so we can track it? https://answers.launchpad.net/launchpad/+addquestion
[21:08] <barry> MrKanister1: it may be that bug importance isn't exported yet
[21:08] <jpds> barry: 'tis.
[21:09] <barry> jpds: cool
[21:09] <MrKanister1> jpds: Thank you VERY much. I could not find any clue how to get information out of collections
[21:09] <dpm> mthaddon: done -> https://answers.edge.launchpad.net/launchpad/+question/76523
[21:09] <barry> jpds: oops, indeed.  i was looking at the wrong interface
[21:12] <jpds> MrKanister1: No problem. We make good use of the API in ubuntu-dev-tools :)
[21:12] <mthaddon> dpm: ok, that's done
[21:14] <MrKanister1> jpds: hm...maybe I should have looked in that package first...I had a look at the package "bughelpers", but it is entirely using "launchpadbugs" :/
[21:15] <jpds> MrKanister1: Yeah, we ported everything from that and screen-scrapping to the API a while back.
[21:15] <jpds> Does the trick and all.
[21:17] <MrKanister1> jpds: ok. I should investigate more time in that ... Python is great :). Thanks again for pointing me to right approach
[21:19] <dpm> mthaddon: thanks a lot!, I'd like to migrate the archive from the old list, could you help me with that? -> https://answers.edge.launchpad.net/launchpad/+question/76523
[21:19] <DanielSouza> I'm having problems importing code from a git repository
[21:19] <DanielSouza> https://code.launchpad.net/~vcs-imports/nationbuilder/trunk
[21:20] <DanielSouza> I think it is a bug of the importer script
[21:20] <mthaddon> dpm: I thought I'd checked that and there was no mailing list configured?
[21:21] <dpm> mthaddon: I had to deactivate the old one in order to rename the team. I've just applied for the new one.
[21:22] <mthaddon> barry: any ideas? I don't see any folder on forster's lists directory
[21:22] <mthaddon> barry: does the mailing list get purged when we rename?
[21:23] <barry> mthaddon: we had to purge it before we renamed it, but the old archive should still exist
[21:23] <barry> mthaddon: look in archives/listname.mbox
[21:23] <barry> er
[21:23] <barry> archives/private/listname.mbox
[21:24] <mthaddon> barry: ok, I see it - just rename it to the new team name?
[21:24] <barry> mthaddon: there should be a listname.mbox file in that directory (yep, it's repeated).  that will serve as the input to the mhonarc command you need to run to re-import
[21:24] <mthaddon> ok
[21:24] <barry> mthaddon: hang on, there's a wiki page about this
[21:24] <mthaddon> yeah, finding it now
[21:24] <DanielSouza> I'm having problems importing code from a git repository
[21:24] <DanielSouza> https://code.launchpad.net/~vcs-imports/nationbuilder/trunk
[21:24] <DanielSouza> I think it is a bug of the importer script
[21:25] <barry> DanielSouza: let me take a look
[21:25] <barry> mthaddon: ping me if you can't find it
[21:31] <mthaddon> dpm: ok, archives migrated - if you configure the mailing list now it should all just DTRT
[21:32] <mthaddon> dpm: let me know if you have any issues, as typically we import the archives after the list is created whereas here we've done it before
[21:32] <mthaddon> (can just redo if we need to)
[21:32] <DanielSouza> Also I my having problems with the translation been waiting review for days to be imported https://translations.launchpad.net/nationbuilder/+imports
[21:33]  * henninge looks at that
[21:33] <henninge> DanielSouza: are those files templates?
[21:34] <DanielSouza> what is the differnece?
[21:34] <dpm> mthaddon: awesome, thanks. Actually, the mailing list is pending approval. Is this an automatic process or does it have to be manually activated by someone?
[21:34] <DanielSouza> all files are separated branches of the translation
[21:35] <mthaddon> dpm: just approved
[21:35] <pace_t_zulu> hey guys... i'm trying to setup a launchpad project for packaging a project hosted elsewhere
[21:35] <dpm> mthaddon: thanks!
[21:35] <pace_t_zulu> the example i'm following is chromium-browser
[21:35] <mthaddon> dpm: hmm, looks like I'll need to reimport the archives - one sec
[21:36] <dpm> np
[21:36] <henninge> DanielSouza: you mean different translation domains, therefore different templates.
[21:36] <pace_t_zulu> i see that the trunk can be pulled from "lp:chromium-browser"
[21:36] <pace_t_zulu> i see that the trunk can be pulled from "lp:chromium-browser" ... how can that be achieved for another project?
[21:36] <henninge> DanielSouza: they should be named *.pot
[21:36] <DanielSouza> understood
[21:38] <henninge> DanielSouza: please read the relevant help pages
[21:38] <henninge> https://help.launchpad.net/Translations/YourProject
[21:38] <henninge> https://help.launchpad.net/Translations/ImportPolicy
[21:39] <mthaddon> dpm: ok, seems to be better now - https://lists.launchpad.net/launchpad-translations-coordinators/
[21:39] <henninge> https://help.launchpad.net/Translations/ImportingFromBazaarBranches
[21:39] <henninge> DanielSouza: ^ if that applies
[21:40] <henninge> DanielSouza: main problem I see with your templates is that they are all in the same directory
[21:40] <DanielSouza> i have only one source code branch, but i have 4 po files, what I do?
[21:40] <mthaddon> pace_t_zulu: assign the relevant branch as a development focus for the project
[21:40] <henninge> DanielSouza: that must be because you used 4 different translation domains in your source code.
[21:41] <pace_t_zulu> mthaddon: will it automatically get that new location... ie: "lp:myproject"
[21:41] <DanielSouza> translation domains = languages?
[21:41] <henninge> DanielSouza: it is easier to maintain if you only have one domain
[21:41] <henninge> no
[21:41] <mthaddon> pace_t_zulu: if you do that, yes
[21:41] <henninge> DanielSouza: you should familiarize yourself with gettext
[21:41] <DanielSouza> Im newbie on that, im not a developer, i converted those files from yaml files
[21:41] <pace_t_zulu> mthaddon: thank you
[21:42] <henninge> DanielSouza: RTFM still applies
[21:42] <mthaddon> pace_t_zulu: you can still reference it at the full location, lp:myproject is just a convenience shortcut for whatever is assigned development focus
[21:42] <pace_t_zulu> mthaddon: what about a vcs-import ... is it ill advised to used that as the "development focus" ?
[21:42] <henninge> DanielSouza: in short: you can group your translatable strings using translation domains.
[21:42] <pace_t_zulu> mthaddon: the codebase is managed by git at sourceforge right now
[21:43] <mthaddon> pace_t_zulu: er, not sure to be honest...
[21:43] <henninge> DanielSouza: but usually you use one translation domain per proejct/program
[21:43] <pace_t_zulu> mthaddon: i'll stick to having a launchpad based packaging right now... that's why i was looking at chromium-browser as my example
[21:43] <henninge> DanielSouza: that is easier to maintain, especially with Launchpad uploads.
[21:43] <dpm> mthaddon: it looks good! Now if I can still steal some more of your time, I'd like to do the same for another list (purge ML, rename team, migrate archive). Here's the initial purge request -> https://answers.edge.launchpad.net/launchpad/+question/76527
[21:44] <henninge> DanielSouza: You should talk to the developers then why they choose to use multiple translation domains.
[21:45] <mthaddon> dpm: you should be able to purge it as an admin of the team - let me know when you've done that and I'll do the rename for you
[21:45] <dpm> mthaddon: I thought it was the other way round - I can't do the purge, but I can do the rename
[21:46] <dpm> the last time barry had to do the purge for me
[21:46] <DanielSouza> henninge, i will try talk to then, but as everybody on the project are newbies with po files we dont to complicate it a lot
[21:46] <mthaddon> ah, okay
[21:47] <mthaddon> dpm: ok, purged - let me know if you can't rename
[21:47] <henninge> DanielSouza: then they need to use only one translation domain in their source code.
[21:47] <DanielSouza> we dont use po on the translation but yaml files
[21:48] <DanielSouza> and convert then with yml2po.sh and po2yml.sh
[21:49] <henninge> DanielSouza: ok, then check were those scripts get the 4 translation domains from. I don't know anything about yaml.
[21:49] <pace_t_zulu> mthaddon: thanks for your help
[21:50] <mthaddon> sure
[21:50] <DanielSouza> henninge, yaml is "YAML isnt Another Markup Language" its a markup language
[21:50] <Kangarooo> https://launchpad.net/~locoteams this is not loading.. 4 or 6 days ago first time I noticed that..
[21:51] <DanielSouza> henninge, this is the yaml files tree
[21:51] <DanielSouza> daniel@opensuse-n1:~/Desktop/nationbuilder/config> ls -r locales/
[21:51] <DanielSouza> notifications  menu  general  activities
[21:51] <DanielSouza> henninge, i tried to use the convertor to create a single pot file, but it failed
[21:52] <dpm> mthaddon: yes, I could rename. could you now please approve the new ML and migrate the archive? -> https://answers.edge.launchpad.net/launchpad/+question/76527
[21:54] <mthaddon> dpm: ok, should be all done now
[21:58] <dpm> mthaddon: brilliant, thanks a lot, Tom!
[21:58] <mthaddon> sure
[22:10] <henninge> DanielSouza: I have to go now. You will have to find somebody with experience in yml2po and acquaint yourself more with the matter to find out how to produce a single template. Upload that as a .pot file to have it approved.
[22:15] <DanielSouza> henninge thanks for all!
[22:16] <thumper> Ursinha: pig
[22:26] <barry> thumper: hey
[22:27] <thumper> barry: hey man
[22:27] <thumper> barry: what's up?
[22:27] <barry> thumper: mtaylor had a question a few hours ago about the (community) tag next to a person's name in a merge proposal
[22:28] <thumper> barry: heh
[22:28] <barry> thumper: what exactly does that mean?
[22:28] <thumper> barry: bug
[22:28] <barry> mtaylor: ^^ :)
[22:28] <thumper> barry: the idea is that if the review was done by a non-reviewer, it should show (community)
[22:28] <thumper> we have brought back the "anyone can review"
[22:28] <thumper> but wanted to somehow indicate reviews by people who are not on the review team
[22:28] <thumper> nor had been requested to review
[22:28] <barry> thumper: that's what i thought from looking at the code, but it looks like a person who is on the review team got that tag
[22:28] <Lumiere> how do you 'bzr upgrade' a branch on launchpad?
[22:29] <thumper> barry: that bit is the bug
[22:29] <thumper> barry: I believe abentley has landed the fix
[22:29] <thumper> but it hasn't rolled out yet
[22:29] <thumper> edge FTW
[22:29] <barry> thumper: super.  thanks for the confirmation!
[22:29] <thumper> np
[22:30] <barry> Lumiere: have you tried just doing it?  you might have to use an sftp url, but thumper or abentley would know for sure
[22:31] <Lumiere> got it
[22:31] <Lumiere> thank you
[22:32] <Lumiere> hopefully it won't fail
[22:41] <Ursinha> thumper, pig was funny :P
[22:42] <thumper> Ursinha: oops, sorry, ment ping
[22:42] <Ursinha> thumper, I know :)
[22:42] <Ursinha> thumper, what's up
[22:42] <thumper> Ursinha: the critical bug isn't really critical
[22:42] <thumper> just high
[22:42] <thumper> should be fixed with 1.17 release of bzr
[22:43] <Ursinha> thumper, hmm, I see
[22:43]  * Ursinha chases the bug no.
[22:47] <Ursinha> thumper, I'll change the status then
[22:47] <thumper> ta
[22:49] <Ursinha> bug 390563
[22:49] <Ursinha> meh
[22:51] <barry> okay folks.  i done my duty so i'll see y'all tomorrow
[22:51] <barry> happy launchpadding
[23:05] <kb9vqf> anyone here willing/able to increase PPA space?
[23:06] <kb9vqf> https://answers.launchpad.net/soyuz/+question/76526
[23:06] <kb9vqf> :)
[23:09] <mwhudson> willing, yes
[23:09] <mwhudson> able, no
[23:12] <BUGabundo> gmb: ping do you have a minute?
[23:18]  * kb9vqf kicks his PPA
[23:20] <maxb> kb9vqf: A temporary option for you might be to delete some superseded versions
[23:21] <maxb> until you can find an admin
[23:22] <kb9vqf> Yeah, In know...but that takes many hours as well
[23:23] <wgrant> I thought 'many' == 1 for deletions.
[23:25] <BUGabundo> one thing I never understood: if APT is able to store several versions of a package, why won't PPAs allow it too? tech prob?
[23:25] <wgrant> BUGabundo: Why would you want to?
[23:26] <wgrant> apt will always try to upgrade to the latest.
[23:26] <BUGabundo> I know
[23:26] <wgrant> So it doesn't really make sense to have anything but the latest, unless you keep reinstalling old ones by specifying a particular version.
[23:26] <BUGabundo> but one may want to downgrade
[23:26] <BUGabundo> and since PPAs superseed, one can't access via apt the older version
[23:27] <BUGabundo> while they still are lodge on LP
[23:27] <wgrant> Keeping old versions around automatically would eat lots of disk space.
[23:28] <wgrant> Allowing copying of old versions back in would be confusing.
[23:28] <BUGabundo> wgrant: never wanted to downgrade?
[23:28] <BUGabundo> I have. lots of times
[23:28] <wgrant> No. I just fix the bug.
[23:28] <BUGabundo> try to get NM packages by hand
[23:28] <BUGabundo> eheheheeheheheheheh
[23:28] <BUGabundo> wgrant: AAHHAHAHAHAAHAH
[23:29] <BUGabundo> not all bugs are fixed by newer versions
[23:29] <BUGabundo> at least not in a short time period
[23:35] <Lumiere> anyone who has access to bzr on lp?
[23:35] <Lumiere> cause I think that my bzr upgrade on lp:gasp-lessons crashed mid-stream
[23:38] <mtaylor> barry, thumper: cool. thanks
[23:38] <mtaylor> thumper: do you mean that I should see the fix in edge? or I should see the bug in edge?
[23:39] <thumper> mtaylor: you should see the fix in edge soon
[23:39] <thumper> mtaylor: the bug won't show on production right now
[23:39] <mtaylor> thumper: sweet. thanks
[23:40] <thumper> Lumiere: the LOSAs do
[23:41] <mthaddon> Lumiere: what do you need?
[23:44] <Lumiere> mthaddon: I had a bzr upgrade on lp:gasp-lessons fail midstream
[23:44] <Lumiere> and I can't run it again
[23:44] <mthaddon> Lumiere: what errror are you getting?
[23:45] <Lumiere> t
[23:45] <Lumiere> err /t
[23:46] <mthaddon> I'm not sure I'm following - can you paste the full output?
[23:46] <Lumiere> sec
[23:47] <Lumiere> http://paste.lisp.org/+1SAL
[23:47] <thumper> mthaddon: bzr moves the .bzr dir out of the way to backup.bzr
[23:47] <thumper> mthaddon: probably just needs backup.bzr moved to .bzr
[23:48] <Lumiere> and then if you could run the bzr upgrade it would be wonderful
[23:48] <mthaddon> thumper: yeah, that's what I thought, just wanted to check
[23:48] <Lumiere> I have been having issues with my network crapping out in the middle of that cast
[23:48] <thumper> Lumiere: it is normally easier to run upgrade on your local copy
[23:48] <Lumiere> thumper: the problem is getting the lp one upgraded too
[23:48] <mthaddon> thumper: http://paste.lisp.org/display/83325 - looks like a different error to me?
[23:48] <thumper> Lumiere: have you heard of hitchhiker?
[23:48] <Lumiere> no
[23:49] <Lumiere> I have a couple remote branches that are branch version 6,
[23:49] <Lumiere> but it didn't seem to upgrade that one
[23:49] <thumper> mthaddon: I'm guessing the the existing .bzr dir might not be complete
[23:50] <thumper> mthaddon: to be save move .bzr -> .bzr.old and backup.bzr -> .bzr
[23:50] <thumper> s/save/safe/
[23:50] <thumper> Lumiere: it is a bzr plugin that abentley wrote
[23:50] <Lumiere> thank you for the help, I am going to grab some food
[23:50] <thumper> allows extra hacking :)
[23:50] <Lumiere> ic
[23:51] <thumper> mthaddon: actually
[23:51] <thumper> mthaddon: you could just not move the backup.bzr back
[23:51] <thumper> which would leave a non-existant .bzr
[23:51] <mthaddon> thumper: just let me know - I see the folder here - so what should I do?
[23:51] <thumper> so a fresh push would mean Lumiere would not need to upgrade
[23:51] <thumper> mthaddon: move .bzr to .bzr.old
[23:52] <thumper> mthaddon: there shouldn't be a .bzr dir there now
[23:52] <mthaddon> thumper: isn't that going to flood subscribers?
[23:52] <thumper> mthaddon: shouldn't
[23:52] <thumper> mthaddon: as the database thinks it has a certain revision there already
[23:53] <mthaddon> thumper: seems like Lumiere has stepped away to grab some food so I don't think he can push if I do this
[23:53] <thumper> Lumiere: do a `bzr push --use-existing lp:gasp-lessons`
[23:53] <thumper> mthaddon: ok, wait till he is back
[23:54] <thumper> Lumiere: what version have you upgraded to locally?
[23:54] <mthaddon> thumper: bzr info seems okay on the branch - should I just try moving the old back and running bzr upgrade?
[23:55] <thumper> mthaddon: are you in the mirrored or hosted area?
[23:55] <mthaddon> push-branches
[23:55] <thumper> ok
[23:55] <thumper> that's right
[23:55] <thumper> mthaddon: we should make sure the versions are the same
[23:56] <thumper> going from knits -> packs can take a while, but he only has 74 revisions, so likely to be fast no matter what
[23:56] <mthaddon> maybe just remove backup.bzr and leave it to him?
[23:56] <thumper> there seems to be a concurrency issue