[04:34] <persia> Erm.  "There is no project in Launchpad named "Ubuntu". Please search for it as it may be registered with a different name." is a confusing message.  I know why it came, and acknowledge it as PEBKAC, but thought I'd point out it being confusing.
[04:36] <spiv> I think there may already be a bug about that.
[04:36] <spiv> (If not, there probably should be...)
[04:36] <mwhudson> it's not too hard to check for other pillars with a given name
[04:37] <persia> spiv: quite possibly.
[04:37] <persia> mwhudson: Nope.  Rather easy.  Just an offputting message from the viewpoint of an Ubuntu developer.
[04:37] <mwhudson> persia: in the code, i mean
[04:37] <mwhudson> as in, it sounds like a bug, and not a hard one to fix
[04:38] <persia> mwhudson: OOh: that would be cool, perhaps with some hook back to point to the right thing to add.
[04:48] <poolie> mwhudson: it's actually a bit hard to find the loggerhead link with the new sub-tabs
[04:48] <poolie> maybe i'm just not used to them
[04:49] <mwhudson> poolie: where?
[04:49] <poolie> perhaps we should add a more prominent "browse source code" back onto the branch or series home page?
[04:49] <poolie> or indeed the project homepage?
[04:49] <poolie> well, starting from for example launchpad.net/loggerhead
[04:49] <poolie> how many clicks and how much searching does it take to find the code?
[04:50] <persia> Browse source code is confusing from the branch overview, as it doesn't actually display the source code, instead showing the revision history.
[04:51] <spiv> Yeah, I wouldn't mind a prominent "Browse source code" button, in the style of the "Report a bug" button.
[04:51] <poolie> persia: where is that?
[04:51] <mwhudson> poolie: oh, you mean from the branch page?
[04:51] <poolie> what spiv said - on the branch page in particular, but also on the project and series pages
[04:51] <poolie> um
[04:52] <spiv> The sub-tabs aren't really somewhere my eyes are used to looking.  The greyness just makes my gaze instinctively glide past and on to the actual contents of the page below.
[04:53] <persia> poolie: e.g. https://code.launchpad.net/loggerhead "Browse the source code" link.
[04:53] <persia> I'd think it ought default to "Files"
[04:54] <poolie> spiv, me too
[04:54] <poolie> persia, i agree
[04:55] <poolie> mwhudson: do you know why code.../loggerhead looks so different to /mysql?
[04:55] <poolie> oh i guess it's because mysql is a project group
[04:55] <mwhudson> poolie: project group
[04:55] <poolie> it's a bit confusing though
[04:55] <mwhudson> right
[04:55] <poolie> you could say "this is a project group" and still show the stats
[04:58] <spiv> If I pay attention to how my gaze wanders on https://code.edge.launchpad.net/~bzr/bzr/trunk (without consciously directing it), it's first drawn to the pillar name and attached dark grey "This site is running pre-release code..." bar.  It's then pulled towards the largest and brightest text on the page, the "bzr mainline" heading.  It then starts reading the details below that before getting bored by the bland mass of text and goes to glance at t
[05:00] <spiv> Then it circles back up to the top-left.  So I think my gaze roughly moves counter-clockwise around the page -- and the sub-tabs are in the middle of that circling, but doesn't manage to get much attention.
[05:03]  * spiv considers studying typography, but decides that lunch is more important for now
[05:07] <poolie> it's like the eyes follow you around the room...
[05:27] <emgent> barry: ping
[08:52] <emgent> barry: whe you have time please set up ~ubuntu-cruft-busters ml
[08:52] <emgent> thanks.
[09:44] <Whoopie> Hi again, I still don't understand exactly why there're some old packages in my PPA even though I deleted the superseding packages, e.g. http://ppa.launchpad.net/whoopie79/ubuntu/pool/main/b/bluez-utils/
[09:45] <ace> hello
[09:45] <ace> I want to put my half opensource project in launchpad, how do to that?
[10:56] <bigjools> Whoopie: https://help.launchpad.net/PPA#Deleting%20packages
[13:38] <pfctdayelise> hi, I just set up a launchpad project and I added a branch (I think). I'm not hugely familiar with bzr and branches etc- I was wondering if anyone would mind looking to see if it's done correctly?
[13:57] <Adri2000> pfctdayelise: if you can see it at code.launchpad.net/yourproject, it should be ok
[13:57] <kiko> good morning
[14:12] <pfctdayelise> Adri2000: ok, thankyou
[14:15] <kiko> so, has anyone here used the APIs yet?
[14:19] <geser> kiko: the new LP API?
[14:20] <kiko> geser, yeah, exactly
[14:21] <geser> kiko: not myself, but IIRC thekorn uses it in python-lp-bugs already
[14:22] <kiko> geser, ah, that's cool to hear. I wonder what he's finding of it
[14:22] <kiko> thekorn, yo
[15:02] <thekorn> kiko, hi, yes I played with the API a bit,
[15:03] <thekorn> and tried to integrate it into existing scripts,
[15:03] <kiko> thekorn, cool. I want to get some idea of how it went
[15:03] <thekorn> I was a bit suprised
[15:03] <thekorn> it was not that fast than I expected
[15:04] <thekorn> but it might be because I was using staging mainly
[15:04] <kiko> might be. what was the request overhead? can you give me more detail?
[15:04] <thekorn> It is also very unfortunate that the API currently only covers a small part of launchpad
[15:05] <thekorn> especially the fact that you currently can not get bug lists by project/product etc.
[15:06] <kiko> thekorn, working on that -- I think intellectronica and allenap might be able to tell you more about where that is
[15:06] <intellectronica> thekorn: we're constantly working on exposing more stuff via the api. bug searching / listing will be available very soon
[15:06] <thekorn> good to heaer!
[15:06] <kiko> thekorn, tell me more about the slowness
[15:07] <thekorn> well I was comparing the speed of the API and the +text interface,
[15:07] <thekorn> I've no sientific results,
[15:07] <kiko> anecdotal helps, though scientific is best
[15:07] <thekorn> I will try to get more detailed results over the weekend
[15:08] <kiko> thekorn, okay, cool
[15:09] <thekorn> especially the fact that you get all the bug information by one read request in the +text interface,
[15:09] <thekorn> where the api needs multible one to get comments etc.
[15:09] <thekorn> but my overall feeling is, that its a very good start,
[15:09] <thekorn> but more has to be done ;)
[15:10] <kiko> cool
[15:10] <thekorn> thanks to all who worked on it
[15:10] <kiko> thekorn, were you able to use it fine from the docs, or did you get stuck somewhere?
[15:11] <allenap> thekorn: If you notice any specific things you'd like exposed in the API that are missing, bearing in mind that we're only exposing bugs and some common stuff for now, please file a bug against launchpad or malone and tag it 'api', or just ping one of us.
[15:11] <thekorn> I find the docs very helpfull
[15:11] <thekorn> ok cool
[15:12] <thekorn> small docs issue I recently found: https://help.launchpad.net/API/SigningRequests, step 3 : it is POST /+access-token and not POST /+access_token
[15:13] <kiko> thekorn, could you fix that in the docs?
[15:13] <thekorn> sure, let me try
[15:13] <intellectronica> thekorn: did you give launchpadlib a try? if you use python there's no reason why you should have to deal with the love-leve protocol, you just get a nice OO interface
[15:14] <thekorn> I'm using launchpadlib, but I tried to understand how this all works,
[15:14] <kiko> thekorn, you rock for trying it out, thanks for the feedback. I'm going to spend tomorrow looking at our appserver request performance
[15:15] <thekorn> and the docs were published earlier than the lib, so I tried to do things by hand
[15:26] <thekorn> allenap, intellectronica one last question, how can I find out when more parts were added to the API, will the docs or the reference documentation be updated,
[15:27] <thekorn> or is there any other more readable list
[15:27] <intellectronica> thekorn: we will always announce new features when we release them (just like any other LP features)
[15:27] <intellectronica> thekorn: i'm also happy to give you a shout when something becomes available
[15:27] <allenap> leonardr: wrt ^^^, is +apidoc rendered dynamically?
[15:28] <thekorn> intellectronica, yes please do so, I'm always happy to test new features
[15:28] <leonardr> allenap: i don't think so. i think that's on flacoste's todo list
[15:29] <intellectronica> thekorn: cool, and thanks!
[15:29] <allenap> leonardr: Do you know if I can I regenerate it before committing?
[15:30] <thekorn> btw, has the API + launchpadlib been announced yet?
[15:30] <thekorn> last entry on news.lp.net was :"We’ll announce full details of the API and Python library later this week; keep an eye on this blog!"
[15:32] <kiko> thekorn, yeah, leonard will be writing a news entry today
[15:32] <kiko> leonardr, ^^
[15:32] <thekorn> hehe, cool
[15:33] <leonardr> allenap: i'm looking at flacoste's emails before he went on vacation and i don't see information about how to update the documentation. sinzui, maybe you know something?
[15:33] <kiko> leonardr, I think I do. there's a tool in scripts/ which regenerates it
[15:42] <eMxyzptlk> Hey guys, anyonw knows why VCS Imports is exiting with an error ? https://code.launchpad.net/~vcs-imports/sabayonlinux/trunk
[15:42] <eMxyzptlk> That's the error http://launchpadlibrarian.net/16634825/sabayonlinux-trunk-log.txt
[15:43] <eMxyzptlk> Trying to import http://svn.sabayonlinux.org/overlay
[15:43] <kiko> emgent, LookupError: Cannot find svn repository root
[15:43] <kiko> that was for eMxyzptlk, sorry
[15:44] <eMxyzptlk> kiko, yea I know but I don't understand what it means
[15:44] <kiko> eMxyzptlk, you can't import a whole repository
[15:44] <kiko> eMxyzptlk, imports are for trunk branches only
[15:44] <eMxyzptlk> kiko, the repo has no trunk branches and tags folders...
[15:44] <kiko> so you can't really do what you are intending to do
[15:44] <eMxyzptlk> it's just trunk in root
[15:45] <eMxyzptlk> hmmm it's impossible to import it if it has no 'trunk, branches, tags' folders ?
[15:45] <kiko> eMxyzptlk, you can't import a tree with code from multiple projects. that's not the right way to do it.
[15:46] <eMxyzptlk> kiko, it's not multiple projects, the repo is the main overlay of Sabayon Linux, hence it's just ebuilds..
[15:47] <kiko> eMxyzptlk, hmmm
[15:47] <eMxyzptlk> example: http://svn.sabayonlinux.org/filedetails.php?repname=Sabayon+Linux+Overlay&path=%2Fsys-kernel%2Flinux-sabayon%2Flinux-sabayon-2.6.26.ebuild
[15:47] <kiko> eMxyzptlk, yeah, I see what you mean
[15:47] <kiko> hmmm
[15:48] <kiko> mrevell, hey there
[15:49] <kiko> mrevell, leonardr wants to write a news.l.n article -- can you help him get a draft started?
[15:50] <eMxyzptlk> kiko, should I perhaps fill a bug for it?
[15:54] <kiko> eMxyzptlk, I'm not entirely sure how to fit this repository into launchpad's model
[15:54] <kiko> eMxyzptlk, I mean, sure you can file a bug, but I think a question is better
[15:54] <kiko> since we need to discuss your problem a bit more
[15:55] <eMxyzptlk> kiko, ok I'm gonna fill a question for it, and give u the link, brbr
[15:55] <eMxyzptlk> brb *
[15:55] <kiko> eMxyzptlk, thanks
[16:03] <eMxyzptlk> kiko, I tried to clarify it as best as I could :)
[16:03] <eMxyzptlk> kiko, https://answers.launchpad.net/launchpad/+question/41621
[16:05] <kiko> eMxyzptlk, thanks
[16:05] <eMxyzptlk> kiko, np :)
[18:13] <emet> hey
[18:13] <emet> how do I add files to the downloads section of my project?
[18:53] <mrevell__> Hi emet
[18:53] <mrevell__> here's a guide:
[18:53] <mrevell__> emet: https://help.launchpad.net/Projects/FileDownloads
[19:30] <Guest94626> hi, i was looking at a lot of junk bugs submitted on launchpad that deal with config files in the home directory getting messed up, but the OPs dont realise that. Shouldnt launchpad give you a piece of text before you report a bug saying, "always try reproducing the bug on a new user account before submitting, and if it doesnt appear there we dont want it to be submitted", or automatically...
[19:30] <Guest94626> ...tag it as one of these bugs, and then probably ignore it (also provide them a link to how to fix broken user specific config files). Surely this would put a small dent in the amount of bugs reported
[20:06] <afflux> hi there. the gajim project seems to have trouble with imports: https://code.edge.launchpad.net/~vcs-imports/gajim/main
[20:37] <mpt> Guest94626, that's not really on-topic for #launchpad (more on-topic for whatever program or OS the bug is about), but IMO bugs that cause broken configs are still bugs
[20:37] <mpt> Unfortunately they're harder to reproduce because the reporter probably won't have a copy of the previous version of the config
[20:39] <mpt> Guest94626, as for response templates: that is on-topic, :-) it's bug 74741.
[21:09] <Guest94626> hi, i dont mean that a specific program has a bug about config files
[21:11] <Guest94626> i'm making a suggestion that launchpad should warn people in advance that bugs where config files have gone bad shoul deither not be reported or should have a special tag, as they are much more likely to be things that are fixed and just have old config files lying around, or just randon usage which isnt reproducable, so isnt useful
[21:17] <Guest94626> maybe a bit of text saying "if on a new user account, and you can recreate the bug then continue, otherwise tag it as "old config files gone awry"" which developers should generally ignore, unless it is highly reported in which case maybe lots of peoples config files are all going awry.. i was looking through this canned search http://people.ubuntu.com/~brian/reports/yesterday/ and if we...
[21:17] <Guest94626> ...just knew whether it was reproducible on a new user account (without having to ask with a canned response every time), then it would cut out a lot of the cruft. the cruft of things that it would be better in general to just ignore
[21:20] <Guest94626> the key is: bugs that cause broken configs ARE bugs, but simply having a broken config doesnt point to any bug even existing (anymore), unless you can reproduce it on a new user account. so we shouldnt waste time investigating, as a general launchpad rule
[22:08] <pbryan> Is there a way to "unlink a series" in LP?
[22:41] <sistpoty> hiho, I'm very much not amused about bug #159304 still being present
[22:41] <sistpoty> (and voiced so with my last comment)