[08:04] <ricotz> hello, is it possible that someone restarts https://launchpad.net/~ricotz/+archive/ppa/+build/3302242 ?
[08:18] <wgrant> ricotz: It's not possible to retry a cancelled build.
[08:22] <ricotz> wgrant, ok, thanks
[08:23] <ricotz> wgrant, btw can you give me a list of ppa builders which have 24gb+ space?
[08:23] <ricotz> amd64 builders
[09:32] <dpm> hey all, could someone help me setting up translations exports for a project? I'm simply trying to set the field at https://translations.launchpad.net/ubuntu-online-tour/extended-tour/+link-translations-branch to the branch at https://code.launchpad.net/~ya-bo-ng/ubuntu-online-tour/extended-tour and it's simply not taking it
[09:35] <czajkowski> hmmm
[09:36] <czajkowski> dpm: are you getting an oops
[09:37] <dpm> czajkowski, I did get a timeout at some point, but I think I've figured out it's because I don't have permissions
[09:37] <czajkowski> dpm: should it be a bzr url also ?
[09:37] <dpm> oddly enough, I can set the imports settings, but not the export settings
[09:37] <czajkowski> bzr branch lp:ubuntu-online-tour/extended-tour ?
[09:38] <dpm> I think it rather expects something like '~ya-bo-ng/ubuntu-online-tour/extended-tour'
[09:38] <dpm> but it only lets me enter '~dpm/ubuntu-online-tour/extended-tour'
[09:38] <dpm> so I guess it only shows me my own branches because I don't have permissions on the other branch
[12:04] <pmatulis> i've had 2 people tell me that merge proposal requests are not working properly (neverending spinning dial).  known issue?
[12:06] <czajkowski> pmatulis: let me gind out
[12:06] <czajkowski> pmatulis: do you have any examples?
[12:07] <pmatulis> czajkowski: i will forward you 2 emails i received
[12:07] <czajkowski> pmatulis: ok thanks
[12:11] <wgrant> pmatulis: Which browsers? Is this just happening today?
[12:11] <pmatulis> wgrant: i got 2 complaints yesterday.  one person tried multiple browsers
[12:13] <wgrant> pmatulis: Which people, which branches?
[12:21] <czajkowski> pmatulis: well?
[12:28] <pmatulis> czajkowski: i sent you an electronic mail message
[12:30] <czajkowski> pmatulis: ok will pastebin it to wgrant
[12:31] <pmatulis> czajkowski: t/y
[12:32] <czajkowski> np
[12:39] <wgrant> pmatulis: In the ubuntu-core-doc case the user needs to manually specify a target branch, since that package isn't in Ubuntu yet.
[12:39] <wgrant> pmatulis: The spinner stays forever due to a Launchpad bug, but it can be worked around by manually selecting a target.
[12:43] <pmatulis> wgrant: what package?
[12:44] <wgrant> pmatulis: ubuntu-core-doc
[12:44] <wgrant> It's not in Ubuntu yet, so there's no default branch.
[12:44] <wgrant> So the merge proposal target must be specified explicitly.
[12:45] <wgrant> Bug #961126
[12:47] <pmatulis> wgrant: well, he said it didn't work from the interface.  there, is there any other way other clicking 'Propose for merging' ?
[12:48] <pmatulis> wgrant: k, i see in this specific case there is a form to fill
[12:50] <pmatulis> btw, if someone has already proposed a merge but it results in 'needs fixing', after editing does he simply 'Request another review' or 'Resubmit proposal'?
[12:50] <wgrant> pmatulis: Generally don't do either.
[12:50] <wgrant> People tend to comment on the MP or poke on IRC and wait for the reviewer to change their vote.
[12:52] <pmatulis> wgrant: hmm, ok.  but to me, re-request is reasonable.  why is it there?
[12:53] <wgrant> pmatulis: "Request another review" is for asking for an additional review from someone else.
[12:54] <pmatulis> wgrant: ah
[12:54] <wgrant> "Resubmit proposal"... I don't think anybody is really sure why it's there. It's most often used if the MP was mistargeted, or occasionally if it's changed so radically that it should basically be reviewed from scratch.
[15:28] <joohoo340> Can someone help me with a problem I have, I am trying to find an easy way to send a link to another person who can
[15:29] <joohoo340> 't  install any software, so they can download the source for a generic project hosted on launch pad
[15:29] <joohoo340> a project that I am not hosting
[15:32] <tsimpson> if it's using the Launchpad code hosting, then they just need bzr and can run "bzr branch lp:<project>" (replacing <project>)
[15:33] <joohoo340> Is there another way in which the user doesn't have to install anything?
[15:35] <tsimpson> if the project chooses to publish a download file, that's one way
[15:35] <tsimpson> but they'd still need some way to build the project
[15:35] <tsimpson> or you could download the bzr branch, tar it up, and put it somewhere they can access
[15:36] <joohoo340> right now its not really for building the project just a little way to show that this is where I got my packages from
[15:36] <joohoo340> and here is the source
[15:36] <joohoo340> im thinking thats what i am going ot have to do now
[15:36] <joohoo340> get the source myself then tar it up that is
[15:37] <thelinuxer> czajkowski: here I am :)
[15:37] <czajkowski> thelinuxer: so to answer your question no  ther isn't
[15:37] <czajkowski> and if its been deleted there really isnt anything to look into now is there
[15:37] <thelinuxer> czajkowski: ok thanks
[15:38] <thelinuxer> but it would gr8 to have such information for accountability purposes
[15:39] <czajkowski> thelinuxer: locoteams usually are only trying to help their members tbh
[15:39] <joohoo340> tsimpson: thanks I thought I would have to do it but i had to see if there was a faster option.
[15:40] <thelinuxer> czajkowski: yes of course, and that's what is expected. It's when something wrong happens you want to know who did it. Anyways thanks a lot for your help
[15:41] <tsimpson> maybe it would be useful for LP to have a "download as .tar.gz" option on bazaar. or maybe code.
[18:21] <tedious> Hi, searched online a bit, but couldn't find an answer. - Am I able to see messages I sent to people through launchpad? (the +contactuser thing)
[18:23] <czajkowski> tedious: no afraid not
[18:24] <czajkowski> there is a bug on that though
[18:24] <tedious> Ah, thank you for the prompt reply.
[19:55] <dpb_> Hi there -- I created a small branch and do not have the "add source recipe" link on the branch page.  Is there something I need to do to enable it?
[19:57] <jonrafkind> it seems that old binary packages have a state of 'superseded' in the status column. can I delete packages programmatically and/or have them automatically deleted when they are in the superseded state?
[20:03] <maxb> jonrafkind: Why, just to economize on space?
[20:04] <jonrafkind> yes
[20:04] <maxb> dpb_: Is it a /+junk/ branch?
[20:04] <jonrafkind> it looks from some bug report I read that superseded packages are in fact deleted, they just show up in the history of the ppa
[20:06] <maxb> Well, not quite
[20:06] <maxb> "Deleted" == a human decided this needed to not be here
[20:07] <maxb> "Superseded" == a newer version caused this to no longer matter as a side-effect
[20:07] <jonrafkind> i just mean the binary packages cease to exist so they don't take up space
[20:07] <maxb> Superseded packages get removed from disk eventually, but not as quickly as actually Deleted ones
[20:07] <jonrafkind> what is it based on?
[20:08] <maxb> I think there are rules based on how many superseded packages for a source, and how long ago they were superseded
[20:08] <jonrafkind> i upload nightly packages and each set of packages takes up 400m, so ill run out of space in about 4 or 5 days
[20:09] <jonrafkind> do you think launchpad might remove superseded packages if it needs more space?
[20:10] <maxb> So based on https://code.launchpad.net/~bzr/+archive/daily/+packages?field.name_filter=&field.status_filter=&field.series_filter=precise it seems to be keeping superseded packages for a day or two
[20:11] <maxb> I don't think it is smart enough to aggressively remove superseded packages for space
[20:11] <maxb> The simplest option is probably to just request more space
[20:11] <jonrafkind> ok if they are kept for a day or two I am probably in the clear
[20:11] <jonrafkind> ok, how do I request more space, through a bug report?
[20:11] <maxb> https://answers.launchpad.net/launchpad/+addquestion
[20:15] <jonrafkind> is getting more space mostly a trivial thing?
[20:34] <dpb_> maxb: sorry, missed that.  No, it's on a private project though.
[20:34] <maxb> hmm
[20:35] <dpb_> other branches on the project do have the "add source recipe" link.  But I just created this branch, so I was wondering if I did something wrong in the process
[20:35] <maxb> What happens if you go to your branch page in a browser, then append /+new-recipe to the URL?
[20:36] <dpb_> trying
[20:37] <dpb_> maxb: I get the expected page, let me try to create it
[20:45] <dpb_> maxb: ok, so, um, you can't create recipes on private branches.  duh.  not sure why I didn't remember that.
[20:46] <maxb> huh
[20:46] <maxb> I wonder why
[20:46] <dpb_> maxb: that I don't know.  way it's always been (really wish that we could). :)
[20:46] <maxb> Oh, probably the builder machines don't have privileged access to read the private branches
[20:47] <dobey> maxb: the builder can't pull them
[20:47]  * dobey has been down this road plenty :)
[20:48]  * maxb retreats to the nice fluffy world of open source where everything is publically readable :-)
[20:48] <dobey> haha, nice joke :)
[20:49] <dpb_> thx maxb. :)
[21:44] <lifeless> kirkland: are you using firefox or chromium ?
[21:45] <kirkland> lifeless: chromium, where I'm getting the No Such Resource problem
[21:45] <lifeless> use firefox
[21:45] <lifeless> its not broken
[21:45] <kirkland> lifeless: but I have firefox open here too
[21:56] <lifeless> kirkland: did that work ?
[21:57] <kirkland> lifeless: ack
[21:57] <lifeless> kirkland: cool
[21:57] <lifeless> kirkland: it is technically a chromium bug, though we can safely avoid tickling it
[22:04] <kirkland> lifeless: cool -- is there a bug in Launchpad linking the two?  chromium/lp/soyuz?
[22:05] <poolie> o/ kirkland
[22:06] <kirkland> poolie: hiya!
[22:10] <lifeless> kirkland: https://launchpad.net/bugs/677270
[22:25] <kirkland> lifeless: thanks, subscribed
[22:26] <kirkland> lifeless: should that bug have a chromium task?
[22:30] <lifeless> kirkland: not really
[22:30] <lifeless> kirkland: there is, I think, a link to the chromium issue in the bug already
[22:30] <lifeless> kirkland: tasks make sense for different workitems related to one defect; there are two defects here
[22:31] <kirkland> lifeless: alrighty
[22:31] <lifeless> a) that we generate non-normal urls
[22:31] <lifeless> b) and that chromium normalises urls when it really shouldn't
[22:32] <lifeless> thus there should be two bugs
[22:34] <kirkland> lifeless: alrighty, thanks
[22:34] <kirkland> lifeless: I'll use firefox for this, then
[22:49] <kirkland> poolie: fyi, poked my buddy over at Google, your Sydney Opera House maps issue has been reported "upstream" :-)
[22:50] <poolie> yes, i reported it too
[22:50] <poolie> i'm not offended, just amused