[05:54] <sebi`> hi, how would I delete/remove a project registered by me?
[06:02] <thumper> sebi`: ask a question on Launchpad is the easiest trackable way
[06:03] <thumper> sebi`: which project?
[06:03] <sebi`> on launchpad? what do you mean?
[06:03] <thumper> sebi`: https://answers.edge.launchpad.net/launchpad/+addquestion
[06:03] <thumper> sebi`: but if you tell me which, I could help
[06:03] <sebi`> launchpad.net/frey is the project in question, I've discontinued it awhile ago (it's developed under a different name now and on a different site)
[06:04] <sebi`> I've set the owner to the launchpad internals (so I believe...), that means, I can't really access anything there anymore :/
[06:05] <sebi`> anyway, since the project site isn't needed anymore, I thought I could as well get rid of it
[06:06] <thumper> sebi`: done
[06:06] <sebi`> oh, thank you
[06:07] <sebi`> also, out of curiousity, is Launchpad ever planning to support Git?
[06:18] <sebi`> .. I guess not? :(
[06:19] <thumper> sebi`: sorry, was distracted
[06:20] <thumper> sebi`: at this stage there are no plans for native git support
[06:34] <sebi`> thumper: oh, but you say native? does that mean there is some sort of a bazar<->git bridge?
[06:34] <thumper> sebi`: yes there is
[06:34] <thumper> sebi`: you can have a foreign mirror of git branches in bzr format
[06:35] <sebi`> when I decided to abandon frey, I actually tried to maintain both the bazaar repository and the git repository, but that didn't work out so well (bzr kept appending .git* files, and other uncomfortable things)
[06:35] <sebi`> nice, do you have a link or something similar with additional information?
[06:36] <thumper> sebi`: https://help.launchpad.net/Code/Imports
[06:36] <sebi`> ah, thank you
[06:37] <thumper> although reading that I can see it isn't entirely up to date
[06:37] <sebi`> oh :(
[06:37] <thumper> but in a good way
[06:37] <thumper> ...
[06:37] <thumper> kinda
[06:39] <sebi`> okay
[06:39] <sebi`> I think I'll just play around with my local bazaar/git servers, and try to figure out how the bridging-stuff works
[06:40] <thumper> sebi`: well if you have a git branch hosted publicly
[06:40] <thumper> sebi`: you can request a git import easily on the lp project
[06:40] <thumper> sebi`: and just give the git location
[06:40] <thumper> sebi`: and LP does the rest
[06:40] <thumper> sebi`: it uses the bzr-git plugin
[06:41] <sebi`> ah
[06:41] <sebi`> neat, in that case I might consider registering the newly named project at launchpad then
[06:41] <sebi`> thank you, thumper
[06:41] <thumper> sebi`: np
[06:51] <sebi`> thumper: project registered and import requested. that was much easier than expected :D
[06:55] <sebi`> the importlog shows an error traceback, though
[07:53] <bebo_mz> can any one help me in this W: GPG error: http://ppa.launchpad.net lucid Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 449F83829320B41C
[07:59] <bilalakhtar> bebo_mz: run the command
[07:59] <bilalakhtar> just a minute
[07:59] <bebo_mz> ok
[08:00] <bilalakhtar> sudo apt-get update -o Acquire::http::No-Cache=True
[08:00] <bilalakhtar> run this command ^^
[08:00] <bebo_mz> what is my proplem
[08:01] <wgrant> That's not the issue.
[08:01] <wgrant> bebo_mz: How did you add the repository?
[08:02] <bebo_mz> add what
[08:02] <wgrant> The PPA.
[08:02] <bebo_mz> some times by .deb
[08:03] <bebo_mz>  bilalakhtar : that still the same
[08:04] <bebo_mz> W: GPG error: http://ppa.launchpad.net lucid Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 449F83829320B41C
[08:05] <bilalakhtar> bebo_mz: Make sure you have the key in the apt keyring
[08:05] <bilalakhtar> check
[08:06] <bebo_mz> how that
[08:06] <bilalakhtar> bebo_mz: open software source
[08:06] <bilalakhtar> s
[08:06] <bebo_mz> i open it now
[08:07] <bebo_mz> and check in authentication
[08:07] <bebo_mz> but i think there no pub key for lucid
[08:12] <bebo_mz> i had fix it
[08:13] <bebo_mz> http://ubuntuforums.org/showthread.php?t=1053126
[08:13] <bebo_mz> i hope all of you enjoy it
[08:13] <bebo_mz> and thanks for all
[08:13] <bebo_mz> i have to go now
[08:44] <sebi`> okay, apparently the import failed and I've received a Mail about this. How would I change the git location then?
[08:45] <sebi`> also, the log doesn't really imply that the location is wrong, but rather that bzr-git isn't able to parse it properly
[08:49] <maxb> sebi`: which import?
[08:49] <sebi`> import of a git repository into my project
[08:51] <thumper> sebi`: if you put the url into a browser, you can see it doesn't exist
[08:51] <thumper> sebi`: I can easily update it if you give me the right link
[08:51] <thumper> maxb: hi
[08:52] <sebi`> thumper: that#s because github is expecting a git client, not a webbrowser
[08:53] <sebi`> the refs url in the logs however works just fine
[08:53] <sebi`> and it's the URL from the readonly HTTP git acces, so it *should* work
[08:53] <sebi`> access, even
[08:54] <thumper> hmm...
[08:55] <sebi`> thumper: you're able to access the refs url, right?
[08:55] <thumper> http://github.com/nebukadnezzar/mars.git/info/refs
[08:55] <thumper> yes that works
[08:56] <sebi`> exactly
[08:56] <thumper> sebi`: jelmer should be along shortly, and he wrote bzr-git
[08:56] <sebi`> the readonly url is just the repository URL with ".git" appended
[08:56] <sebi`> okay
[08:56] <thumper> sebi`: so when you see him, ask away
[08:57] <sebi`> I will
[08:57] <maxb> There is a more practical solution - just import over the git protocol. Which should be faster anyway
[08:57] <sebi`> might be a try worth
[08:57]  * maxb edits url
[08:58] <sebi`> to git://github.com/nebukadnezzar/mars.git
[08:58] <sebi`> thanks in advance, hehe :P
[09:00] <maxb> Right, that works
[09:01] <maxb> Something rather odd is going on that http did not
[09:01] <sebi`> nice, yeah that worked
[09:01] <sebi`> indeed
[09:01]  * thumper remembers
[09:01] <thumper> there is a bug with our version of bzr-git right now
[09:01] <thumper> jelmer has landed a fix
[09:01] <sebi`> the trunkpage still thinks that there is no repository for mars, though... :(
[09:01] <thumper> to be rolled out at the next release
[09:03] <sebi`> ooh nevermind, I forgot to link the branch
[09:05] <sebi`> I presume bzr-git will automatically mirror all changes?
[09:08] <maxb> everything on the HEAD branch
[09:15] <sebi`> okay
[09:48] <thopiekar> thank you for setting up more i386 builders!
[11:32] <alkisg> Tuxpaint and tuxtype were demoted from main to universe in the Lucid cycle. As a result, the translations are missing, because they were stripped, supposedly to go to langpacks.
[11:32] <alkisg> I think LP should somehow force a reupload of the packages being demoted, to prevent that problem. Should I file a bug against LP for this? Or just try to apply for an SRU for the affected packages?
[11:35] <alkisg> (Bugs #572994 and #512285)
[11:37] <alkisg> Or at least the developers should be notified that each demotion should be accompanied by a dummy version bump?
[11:58] <wgrant> alkisg: What do you mean by 'a reupload'?
[11:59] <wgrant> It requires a full rebuild.
[11:59] <alkisg> wgrant: my terminology might need improving, I mean that no source code needs to be changed, just a version bump + rebuild
[12:01] <alkisg> I filed bug #612909 for soyuz, I hope that was the right thing to do.
[12:03] <dpm> alkisg, in the meantime, do you think you could file a bug for each of the affected packages in Ubuntu, so that this could be fixed in a Stable Release Upload (SRU)? Here's an example of the same bug for ekiga -> bug 577067
[12:04] <alkisg> dpm, is a separate bug required? (a bug already exist for each of those packages). If so, sure, I'd be glad to.
[12:04] <alkisg> (see above for the bug links)
[12:04] <dpm> alkisg, no separate bug needed if there already is one for each of the packages
[12:04] <alkisg> Nice. So I should just subscribe ubuntu-sru team?
[12:04]  * alkisg reads https://wiki.ubuntu.com/StableReleaseUpdates ...
[12:06] <dpm> alkisg, yes, but I'd also reword the bug description to be more in line with the guidelines on that wiki page
[12:06] <alkisg> Thank you, will do that now.
[12:07] <dpm> thank you!
[12:37] <alkisg> https://wiki.ubuntu.com/StableReleaseUpdates mentions that I should upload the fixed package to lucid-proposed. Should I really go ahead and do that? (it's pretty safe as no source code is changed, just a version bump). Is it OK that my name will be there in the changelog (unless I somehow upload it unsigned?)
[12:37] <shadeslayer> alkisg: not really the place to ask imo
[12:38] <wgrant> alkisg: How else will the package get into the archive?
[12:38] <alkisg> (it's a little out of topic now, but since it's just a yes/no question and I already have all the "history" above...)
[12:38] <alkisg> shadeslayer: heh I was just writing that
[12:38] <wgrant> But yes, #ubuntu-devel or #ubuntu-motu is more appropriate.
[12:38] <shadeslayer> ^ was about to say that :P
[12:38] <wgrant> Someone has to upload it to lucid-proposed. It might as well be used.
[12:38] <wgrant> Er.
[12:38] <wgrant> Be *you*.
[12:38] <alkisg> wgrant: it's the first time I'm doing this, sorry for asking simple questions :)
[12:38] <alkisg> OK, thanks, /me reads about uploading to -proposed...
[12:47] <geser> does somebody know if those 290 i386 jobs in the "official" build queue will get build eventually? As I see sometimes all 3 i386 buildds idling while there are still jobs in the queue and new uploads seem to get a higher build priority
[12:48] <bigjools> geser: the page has a bug
[12:48] <bigjools> they're translations jobs that should be in the PPA queue
[12:48] <bigjools> https://bugs.edge.launchpad.net/soyuz/+bug/609904
[12:52] <fta> OOPS-1676ED2269
[14:22] <ams_cs> hi all, I'm trying to work out why I'm not getting email notification from Launchpad. Does anybody know how to tell if email is being sent to a group address?
[14:27] <ams_cs> I want https://launchpad.net/~codesourcery-linaro-list to recieve merge notifications from https://code.launchpad.net/gcc-linaro and send them to the CS mailing list, but it's not working. Any ideas?
[14:29] <cody-somerville> ams_cs, You probably need to modify the team's subscription
[14:29] <cody-somerville> ams_cs, its probably set up not to send any mail at all right now
[14:29] <cody-somerville> ams_cs, or the mails are getting held up in moderation
[14:30] <ams_cs> I can't check, because I don't own the group, but I believe lool set it up to do that
[14:31] <cody-somerville> ams_cs, all e-mail sent to that group will be sent to gnu-linaro-tools@codesourcery.com
[14:32] <ams_cs> cody-somerville: right, but I'm not seeing it, so either it's being swallowed elsewhere, or never sent in the first place
[14:33] <cody-somerville> oh right, you're not a member of the team so you can't see the how the subscription is configured
[14:33] <cody-somerville> you'll have to ping lool
[14:33] <ams_cs> cody-somerville: yeah, I did that, but he's travelling, and suggested that somebody here would be able to determine the problem
[14:40] <MTecknology> Any chance I can get a review of this? https://code.edge.launchpad.net/~jailkit/jailkit/debian
[14:44] <MTecknology> hrm..
[14:45] <MTecknology> This one is better :) https://code.edge.launchpad.net/~jailkit/jailkit/trunk
[14:51] <jelmer> MTecknology, done
[15:07] <micahg> lifeless: I have an editstatus oops if you want it
[15:29] <MTecknology> jelmer: thanks :D
[15:43] <mxpxpod> how do I get both backports and proposed as dependencies for my PPA?
[15:45] <micahg> mxpxpod: on the PPA home page there should be an edit dependencies for something like that
[15:45] <mxpxpod> micahg: right, but it looks like I can only select proposed or backports
[15:45] <mxpxpod> not both
[15:45] <bigjools> mxpxpod: you can't :(
[15:46] <bigjools> file a bug about it, it's not too hard to fix
[15:48] <mxpxpod> Does the "backports" option include all of the options above it?
[15:49] <lool> ams_cs, cody-somerville: I just checked, and the team is sub-ed to "Email about all changes" for "Code review Level", on both branches
[15:49] <lool> ams_cs: I really think you ought to check the mail server on the other side, I can provide you with approximate dates at which they reached my server
[15:50] <ams_cs> lool: sure, but I don't have access, and the guy who does is unlikely to be out of bed yet, and is overworked anyway
[15:51] <lool> ams_cs: Still, it's the likely the problem is on this side, since I get emails, and we confirmed the email address of the team
[15:51] <lool> I can certainly see Launchpad send emails out
[15:51] <ams_cs> lool: right, and have the same emails in my personal inbox
[15:52] <ams_cs> lool: it's just the list copy that's missing
[15:52] <lool> It certainly sounds like a mailing-list manager issue, not a Launchpad issue
[16:16] <MTecknology> Isn't estimated wait time for builds supposed to down instead of up? From 6hr to 22hr to 1day seems kinda backward. :P
[16:16] <MTecknology> It'd be coolk if we could donate resources for building. :)
[16:20] <micahg> MTecknology: builders disappeared again
[16:23] <MTecknology> micahg: oh, it's sad when that happens
[16:35] <da> hi
[16:37] <da> i not good english beei
[16:37] <da> man
[16:54] <micahg> lifeless: I have another distrotask timeout and I have the oops code, should I update my bug with the neew code?
[17:36] <fta> micahg, yep, saw that too, that's sad. i'm now building my stuff on my own hardware as the ppas are no longer reliable. i'll tell the complaining users there's nothing i can do for them anymore and that they should suffer endlessly with agonizing ppas
[18:11] <MTecknology> grr... I built a package in launchpad, it's published - but I can't install it
[18:18] <MTecknology> and now I see why..
[20:41] <ari-tczew> is launchpad got a bug in assigning?
[20:43] <deryck> ari-tczew, are you trying to assign a bug to someone other than yourself?
[20:43] <micahg> ari-tczew: no, only bug supervisors can assign to others, or one can assign to onesself
[20:44] <deryck> http://blog.launchpad.net/general/assigning-bugs-to-someone-else-or-not
[20:44] <ari-tczew> deryck, micahg: I want to assign someone else than me
[20:45] <micahg> ari-tczew: you can't do that
[20:45] <ari-tczew> once I could do it. now it doesn't work
[20:45] <micahg> ari-tczew: see the link that deryck posted
[20:45] <deryck> ari-tczew, is this your project on Launchpad?
[20:45] <ari-tczew> deryck: no
[20:45] <deryck> hi micahg.  :-)
[20:46] <ari-tczew> hmmm, maybe it's good idea.
[20:46] <deryck> ari-tczew, yeah, so you no longer can do this.  See the blog post
[20:46] <micahg> hi deryck :)
[20:46] <ari-tczew> it's prevent bug from newbies
[20:47] <deryck> ari-tczew, plus, you really shouldn't assign a bug to someone to get their attention.  You're committing them to work on a bug that they may not be able to work on.
[20:47] <deryck> this is open to abuse
[20:47] <ari-tczew> I myself once did mistakes like assign to latest uploader for merge. I've been didn't familiar with procedures :P
[20:47] <micahg> which is why you fixed it deryck :)
[20:47] <deryck> exactly :-)
[20:48] <micahg> ari-tczew: you shouldn't be assigning to uploaders
[20:48] <micahg> you can subscribe someone if you think they have an interest in the bug
[20:48] <ari-tczew> micahg: it's history!~
[21:47] <lifeless> micahg: yes please
[21:48] <micahg> lifeless: I trusted my gut and filed it :)
[21:49] <micahg> lifeless: BTW, I updated my old bug, and now distrotask seems to be unusable in stable bug 609012
[22:12] <ari-tczew> last time +related-software gives timeout
[22:14] <micahg> lifeless: ^^
[22:15] <ari-tczew> micahg: hmm?
[22:15] <micahg> ari-tczew: he's on a performance kick at the moment
[22:16] <ari-tczew> micahg: who?
[22:16] <micahg> ari-tczew: lifeless.
[22:17] <lifeless> micahg: hi, sorry, morning email blitz
[22:17] <micahg> lifeless: ari-tczew is having a timeout issue with +related-software
[22:17]  * micahg doesn't know where that belongs
[22:18] <ari-tczew> micahg: ah! you mean about user. I thought that you're commenting situation
[22:18] <lifeless> ari-tczew: when you get a timeout
[22:18] <lifeless> ari-tczew: please file a bug on https://bugs.launchpad.net/launchpad/+filebug and include the OOPS code
[22:19] <ari-tczew> lifeless: when I'm on a user's profil and click on Related software and packages
[22:19] <ari-tczew> what's the OOPS?
[22:19] <lifeless> ari-tczew: theres a long story behind this, but doing that gives our process a real thing to hook into and fix
[22:19] <lifeless> ari-tczew: it should be in the text of the error page
[22:20] <micahg> lifeless: BTW, I updated my old bug, and now distrotask seems to be unusable in stable bug 609012 <--- from above as well
[22:20] <lifeless> micahg: for your distrotask thing - you can see stuarts comment, the page needs to be tuned
[22:20] <micahg> lifeless: I know, but I'm adding urgency since stable is currently unusable :)
[22:20] <lifeless> micahg: what do you mean by stable ?
[22:21] <micahg> lifeless: lp.net, not edge
[22:21] <lifeless> ah
[22:21] <lifeless> so, lp.net has a higher timeout limit. And *more timeouts*
[22:21] <lifeless> so, if edge doesn't work, its very unlikely lp.net will
[22:21] <micahg> lifeless: well, most things I get working if I disable edge, didn't help for +distrotask
[22:22] <lifeless> micahg: I've got graphs for this ;)
[22:22] <lifeless> production has about 10 times the timeouts edge does
[22:22] <micahg> lifeless: I believe you, I'm just telling you my experience with using edge primarily
[22:22] <lifeless> its also slower - compare https://bugs.edge.launchpad.net/ubuntu/+filebug vs https://bugs.launchpad.net/ubuntu/+filebug :)
[22:23] <lifeless> micahg: sure, I appreciate that.
[22:23] <lifeless> ari-tczew: could you take a screen shot of the error page you get ?
[22:23] <ari-tczew> lifeless: no problem, give me 5 minutes
[22:23] <lifeless> ari-tczew: I know LP is slow, sorry! :P
[22:24] <micahg> lifeless: any performance improvents with next week's rollout?
[22:24] <ari-tczew> lifeless: haha, I mean that I need to finish something :P
[22:24] <lifeless> micahg: yeah
[22:24] <micahg> that's good
[22:24] <lifeless> micahg: in particular filebug
[22:24] <micahg> yeah, that's a nasty one for people because back doesn't work as opposed to +distrotask
[22:24] <lifeless> micahg: which has been my pet project, but I've seen other timeout fixes go through
[22:25] <micahg> I was trying to keep an eye on fixes for a while, but I don't have time anymore, I just scan the titles for stuff that affects me now
[22:29] <lifeless> heh, yeah - and I hope we'll make it harder still (by doing more stuff :))
[22:39] <josh_k> who do I hassle to get private branches on my fancy $$PAID$$ LP Project?
[22:39] <lifeless> I think any losa can do that, though I'm not totally sure.
[22:40] <lifeless> bac: I know you've handed this off - but can you confirm process : once the project has a voucher, losas can do the rest ?
[22:40] <josh_k> any way I can easily tell who;s a losa?
[22:41] <bac> lifeless: that should be the case.  it's really better to ask mrevell or me, instead of a losa
[22:41] <bac> josh_k: what project ?
[22:41] <josh_k> bac: thanks! https://edge.launchpad.net/project-0823
[22:45] <ari-tczew> lifeless: where you would see uploaded screenshot?
[22:45] <wgrant> lamont: Around?
[22:47] <lifeless> ari-tczew: anywhere you like
[22:47] <lifeless> ari-tczew: e.g. http://imagebin.org/
[22:49] <ari-tczew> lifeless: what do you want to see in image? only web browser?
[22:49] <ari-tczew> full desktop items
[22:49] <lifeless> just the error page you get
[22:52] <ari-tczew> lifeless: http://imagebin.org/108004
[22:52] <lifeless> ari-tczew: see where it says Error ID:
[22:52] <lifeless> ari-tczew: after that is the OOPS code
[22:53] <ari-tczew> lifeless: it's black magic for me
[22:53] <lifeless> in your case it is OOPS-1676D1946
[22:55] <lifeless> ari-tczew: https://edge.launchpad.net/~bhavi/+related-software may work better, the page has been improved in the next release
[22:59] <ari-tczew> lifeless: when will be next release?
[23:00] <lifeless> 12th august
[23:01] <lifeless> http://identi.ca/launchpadstatus
[23:08] <ari-tczew> lifeless: so do you propose use edge version?
[23:08] <lifeless> ari-tczew: it may work better for you
[23:10] <ari-tczew> lifeless: are you sure that this issue will be fixed in next release?
[23:13] <josh_k> bac: btw, looks like I'm all private now
[23:13] <josh_k> thanks! :)
[23:14] <lifeless> ari-tczew: no I'm not
[23:14] <lifeless> ari-tczew: if you try the edge page and it works then that is a good sign that it may be fixed.
[23:14] <ari-tczew> ok
[23:32] <mwhudson> ooo my recipe build might actually build today!
[23:34] <wgrant> mwhudson: Have you applied the 2-3x buildd-manager inefficiency factor?
[23:34] <mwhudson> wgrant: not so specifically
[23:34] <mwhudson> wgrant: but it said 17 hours 24 hours ago and says 3 hours now
[23:35] <wgrant> True.