[00:06] <bdmurray> lifeless: If I were to work on this how could I actually test it?
[00:16] <lifeless> bdmurray: well, at the outermost level the existing tests should be enough
[00:17] <lifeless> for the performance side, I would check the queries generated - probably by hand - for a few interesting combinations
[00:17] <lifeless> e.g. structsub + tags
[00:36] <SpamapS> I want to get from the distro_seris_link returned from a source_package_publishing_history entry, to a distro_series entry ..
[00:36] <SpamapS> its entirely unclear to me how to do that from the reference :(
[00:36] <SpamapS> sorry this is in launchpadlib
[00:36] <bdmurray> I think you need to run another query for that
[00:37] <SpamapS> Thats fine I just don't know how
[00:37] <wgrant> SpamapS: Just use spph.distro_series.
[00:37] <bdmurray> getPublishedSouces
[00:37] <wgrant> SpamapS: launchpadlib resolved *_link to *.
[00:38] <wgrant> s/resolved/resolves/
[00:38] <SpamapS> thats deep magic..
[00:38] <SpamapS> https://launchpad.net/+apidoc/1.0.html#source_package_publishing_history
[00:38] <SpamapS> I've been using this
[00:38] <SpamapS> is it just, totally outdated?
[00:38] <wgrant> That's the raw API docs.
[00:39] <wgrant> launchpadlib implements magic on top of it.
[00:39] <wgrant> https://help.launchpad.net/API/launchpadlib
[00:39] <wgrant> (not very well documented magic, but there is some stuff)
[00:40] <SpamapS> I've been able to do quite a bit w/ the raw API docs.. nice to see there's more. :)
[00:55] <niemeyer> Hey there
[00:55] <niemeyer> Anyone able to provide some support for daily builds?
[05:21] <poolie> what stability guarantee, if any, is made for the devel api?
[05:22] <wgrant> None.
[05:22] <poolie> great
[05:24] <poolie> (that's not sarcasm, I think that's fine.)
[05:24] <wgrant> Ah!
[05:24] <poolie> i think most clients are going to be ok with just dealing with launchpad as it exists on the day they call it
[06:51] <palhmbs> hey guys - I want to file a bug against one of your help pages
[06:55] <palhmbs> https://help.launchpad.net/BlueprintRoadmaps << - invalid link to • Ubuntu Roadmap
[07:10] <poolie> hi palhmbs
[07:11] <poolie> do you know where it should point?
[07:11] <wgrant> I think that feature may have been removed.
[07:12] <poolie> was this the Dot diagram thing?
[07:14] <wgrant> Not quite, I don't think. That still exists, but on each blueprint page.
[07:16] <poolie> palhmbs: anyhow, thanks for reporting it
[07:16] <poolie> filing a bug against launchpad itself in pad.lv/fb/launchpad is probably best
[07:16] <palhmbs> right - ok
[07:16] <palhmbs> I thought it must of dissappeared
[07:17] <wgrant> revno: 6867 [merge]
[07:17] <wgrant> timestamp: Sat 2008-08-16 15:08:17 +0100
[07:17] <wgrant> message:
[07:17] <wgrant>   [r=gmb] Fix bug #174480 by removing the specificationtarget roadmap
[07:17] <wgrant>         page
[07:17] <palhmbs> probably another projects Roadmap could be moved.
[07:21] <poolie> should we just delete that page then?
[07:21] <wgrant> Yes.
[07:21] <wgrant> I think so.
[07:22] <palhmbs> :(
[07:22] <poolie> ok, i'll do that
[07:22] <palhmbs> I wanted to create a blueprint that wasn't currently linked to a project
[07:22] <poolie> palhmbs: did you want to use it?
[07:23] <palhmbs> no, I'd just like to see an example of a awesome roadmap that's all
[07:23] <palhmbs> #openhatch needed a good example at this last weeks meeting....
[07:24] <poolie> wow interesting project
[07:24] <palhmbs> we did one, but it's pretty much just a /braindump -
[07:24] <palhmbs> poolie, thanks, I'm pretty proud of being involved in it myself
[07:24] <palhmbs> I started coding in python about 3 mnths ago
[07:25] <palhmbs> I've done a few patches against OpenHatch, I'm currently working on a Bash mission
[07:25] <palhmbs> you know, a mission to help teach people the power of the commandline
[07:25] <poolie> oh so you just want to know "what does Ubuntu's roadmap look like"?
[07:26] <palhmbs> yup
[07:26] <poolie> https://blueprints.launchpad.net/sprints/uds-o is a start
[07:26] <poolie> it's very fine-grained though
[07:26] <poolie> the kickoff mail is almost better
[07:26] <palhmbs> our missions are at http://openhatch.org/missions
[07:26] <palhmbs> kickoff mail?
[07:26] <palhmbs> never heard of it
[07:27] <poolie> like http://www.markshuttleworth.com/archives/646
[07:30] <palhmbs> poolie, I'm not sure either of those suggestions/links quite covers what I'd expect in a "great roadmap"
[07:31] <palhmbs> maybe https://help.launchpad.net/API/Roadmap
[07:31] <palhmbs> :D
[07:31] <poolie> haha
[07:31] <poolie> that's a bit out of date
[07:32] <palhmbs> here are some links to roadmaps that paulproteus found during last weeks meeting--- http://openhatch.org/wiki/Meetings/weekly/2011-06-04
[07:32] <poolie> you want this an example of how a project ought to be run?
[07:32] <palhmbs> that's the thing with a Roadmpa
[07:32] <palhmbs> s/Roadmpa/Roadmap/
[07:32] <palhmbs> it's always going outta date
[07:32] <fta2> who killed my builds???
[07:32] <fta2> and why?
[07:32] <wgrant> fta2: Your builds were killed?
[07:32] <palhmbs> so a good project would/should keep it up-to-date :P
[07:32] <fta2> wgrant, https://launchpad.net/~chromium-daily/+archive/ppa/+build/2551502
[07:33] <wgrant> fta2: OOM killer.
[07:33] <poolie> palhmbs: citation needed :)
[07:33] <palhmbs> citation?
[07:33] <palhmbs> is this the PC police?
[07:34] <fta2> wgrant, well, what now? it seems stuck in my keep-alive
[07:34] <wgrant> fta2: It got partially killed, but your build process seems to not have noticed.
[07:34] <wgrant> Let me kill it a bit harder.
[07:35] <wgrant> Done.
[07:35] <wgrant> Now started on thorium.
[07:35] <fta2> if ld-bfd is no longer usable, and as ld-gold is total crap in all our toolchains, i don't see what options are left :(
[07:35] <wgrant> Link smaller things :P
[08:07] <geser> fta2: does our linker perhaps have link time optimization enabled (-flto)? I read yesterday on the debian-devel ml a thread about it and someone mentioned that it needs much RAM and I remember also reading that some packages disabled -flto on oneiric-changes
[08:52] <fta2> geser, linking chromium with ld-bfd usually takes ~2GB of RAM, and ~1h
[08:52] <fta2> geser, with ld-gold, it's just a few minutes, even seconds if you have a fast box
[08:53] <fta2> but our ld-gold is crap, it's too old on all dists and it produces bad code, it even segfaults on some arches
[08:53] <fta2> the upstream version is fine though
[08:54] <StevenK> fta2: Then upload a good version of ld-gold to your PPA and Build-Depend on it?
[08:54] <lifeless> or to backports
[08:54] <lifeless> and make it available for everyone
[08:54] <fta2> yep, i can do that for the PPAs, but it's not possible for the official builds
[08:55] <fta2> i've been told that backports are not welcomed/wanted
[08:55] <micahg>  fta2 I thought it was just lucid with the back ld-gold
[08:56] <fta2> nope, all, to various degrees
[08:56] <micahg> StevenK: that won't help us in the distro when we have to build that version of chromium
[08:56] <lifeless> fta2: huhwhatnow ?
[08:56] <lifeless> backports are official man
[08:57] <micahg> lifeless: backports won't help for the -security pocket where we need to push new versions of chromium
[08:58] <micahg> fta2: it's in the works to get ld-gold updated for lucid, if the same changes are needed in the other releases, we might be able to do that as well, I have to see what happens with the lucid fix
[09:00] <fta2> micahg, doko told me last week it's not wanted
[09:01] <micahg> fta2: orly?  I'll look into it
[09:02] <micahg> lifeless: in any event, toolchain backports are generally frowned upon since it has the potential to affect so many things
[09:04] <fta2> bug 789223, bug 789231, bug 791283, etc.. i have more
[09:11] <micahg> fta: I'll see what I can find out
[09:16] <fta2> micahg, http://paste.ubuntu.com/613946/
[09:16] <fta2> that's why it's not usable
[09:17] <fta2> that's also bug 673893
[09:42] <micahg> fta2: k, thanks
[10:03] <henninge> Does a 404 on a bug report mean that it is private?
[10:04] <henninge> A bug I reported has been marked a duplicate of another bug but I cannot see that other bug.
[10:04] <henninge> https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/787431
[10:05] <mfraz74> Remember, this bug report is a duplicate of a private bug.
[10:07] <kamel> how can i mark a bug as "affects release natty"
[10:07] <kamel> ?
[10:08] <lifeless> thats done via nomination
[10:08] <kamel> ah, this link is not shown when loged in... wtf
[10:09] <kamel> lifeless: yes, but noticed that this link is removed when i log in
[10:09] <lifeless> bug nomination requires bug supervisor privilege
[10:10] <kamel> how can i get them?
[10:11] <micahg> kamel: you can ask in #ubuntu-bugs for a nomination (you have to be a member of bug control)
[10:12] <kamel> thanks
[11:15] <doude> Hi all, do you have some trouble to access launchpad ?
[11:17] <danilos> doude, not me
[11:18] <danilos> doude, what kind of problems are you seeing?
[11:23] <doko> spam at https://bugs.launchpad.net/ubuntu/+source/unity/+bug/591253
[11:24] <doude> danilos: I get error page 'Please try again' when I try to brows source code of project OpenStack Nova
[11:24] <dpm> hi could someone with registry permissions help with https://answers.launchpad.net/launchpad/+question/158960 ? It's currently blocking the approval of a translation team and driving away contributors. Thanks
[11:25] <danilos> doko, fixed, thanks
[11:25] <danilos> well, removed rather than fixed :)
[11:27] <danilos> dpm, I think you really need LOSAs to do that
[11:27]  * gmb -> grabbing an early lunch
[11:27] <danilos> doude, sounds like a logger head issue, let me check
[11:28] <dpm> thanks danilos, what's the best way to give losas a heads up?
[11:29] <gnuoy> dpm: Hi
[11:29] <gnuoy> I'll take a look
[11:29] <dpm> excellent, thanks gnuoy :)
[11:32] <danilos> doude, yeah, I can see it's down, I'll let someone know and hopefully they'll look into it
[11:37] <danilos> doude, it seems to be back, fwiw
[12:07] <maxb> danilos: Hello, re https://answers.launchpad.net/launchpad/+question/160366, project owners aren't allowed to use Project:+admin, you need to be at least a registry admin. Also, setting the project to inactive *will* remove it from the view of everyone who isn't a registry admin.
[12:09] <danilos> maxb, oh, ok :)
[12:09] <danilos> maxb, want to clarify that in the question?
[12:09] <maxb> OK, will do
[12:09] <danilos> maxb, thanks
[12:10] <danilos> and I thought we had an "inactive development" state for projects :/
[12:38] <doude> danilos: Ok, it's came back. Thanks.
[13:34] <soren> How often do code imports run? Is it configurable at all?
 How often do code imports run? Is it configurable at all?
[14:19] <maxb> Every 5 hours, or you can click the "Import now" button for a given import
[14:27] <soren> maxb: Is that exposed in the API?
[14:27] <maxb> I don't think so
[14:27] <soren> Hahah! It is.
[14:28] <maxb> Really?
[14:28] <soren> requestImport on code_import objects.
[14:29] <soren> Great, that'll do.
[14:57] <abentley> gmb: could you please review https://code.launchpad.net/~abentley/launchpad/ppa-api/+merge/63601 ?
[14:57] <gmb> abentley: Sure. I'll take a look when I've finished with allenap's branch
[14:57] <abentley> gmb: thanks.
[15:05] <gmb> abentley: I see a 1100 line diff and a conflict. Can you check what's going on for me?
[15:06] <abentley> gmb: The conflict is trivial, and I've pushed up a new revision that should fix it momentarily.
[15:06] <gmb> OK
[15:07] <abentley> gmb: the diff is 1100 lines because it was already approved once at 800 lines, and then wgrant rolled it back and I had to redo it.  There's a link to the new changes in the summary.
[15:08] <gmb> abentley: OK, thanks.
[15:09] <abentley> I guess I could have made those extra changes in a prerequisite branch, but I didn't think of it.
[15:19] <gmb> abentley: r=me.
[15:19] <abentley> gmb, thanks.
[15:19] <gmb> np
[16:13] <abentley> gmb: could you please review https://code.launchpad.net/~abentley/launchpad/fix-update-cache/+merge/63717 ?
[16:14] <gmb> abentley: Sure; I'll take a look after I've finished with henninge's.
[16:14] <abentley> gmb: thanks.  This one's a bit shorter than the last one.
[16:18] <gmb> abentley: Approved.
[16:18] <abentley> gmb: thanks.
[17:47] <smoser> anyone able to help me see why a email interface is not working for me ?
[17:49] <smoser> i attempted 13 minutes ago (16:34 UTC) with "Subject: Please merge rsyslog 5.8.1-1 (main) from debian unstable"
[17:53] <cody-somerville> smoser, ah, you meant "the" and not "a", lol.
[17:54] <smoser> yes, i guess so.
[17:54] <smoser> :)
[18:07] <bdmurray> Using Launchpad how am I supposed to find the diff that fixed bug 730643?
[18:10] <Cube``> hmm
[18:10] <Cube``> shits been unconfirmed for ages
[18:10] <Cube``> idk what to do
[18:12] <geser> bdmurray: follow the link "lp:ubuntu/natty/software-properties" and then look below "Recent revisions" for that one that mentions your bug number (rev 63 in this case) [http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/natty/software-properties/natty/revision/63]
[18:13] <bdmurray> geser: what's all the merged into ... at revision 535 stuff about then?
[18:16] <geser> bdmurray: that's the upstream branch, but this merge looks a little strange for me as it looks "backwards": the upstream project branch (lp:software-properties) got merged into a branch of ~echidnaman
[18:18] <geser> bdmurray: the second one (lp:ubuntu/natty/software-properties) is the "Ubuntu packaging" branch (generated from the uploaded source packages)
[18:19] <bdmurray> geser: right I was really hoping / thinking there should be a one click way to load the right revision to find the diff.
[18:22] <geser> bdmurray: yes, those links would be more useful if they linked to the revision which contains the fix (the bug number) instead of the branch itself (which gets hard to find the right commit for older bugs and very active branches)
[18:22] <bdmurray> geser: yes exactly
[18:26] <fta> did lp stop sending emails for bzr commits??
[18:27] <fta> worked until ~2 days ago
[18:34] <fta> oh, this branch is stuck: https://code.launchpad.net/~chromium-team/chromium-browser/channels   last rev is 1047
[18:47] <RawChid> Is it possible to get a list of Ubuntu distro series from the LP API?
[18:53] <RawChid> Oh wait, I found the API doc :-)
[18:54] <RawChid> Hints are still welcome though
[19:31] <fta> could someone please unbreak https://code.launchpad.net/~chromium-team/chromium-browser/channels ? it's been scanning for days
[20:09] <smoser> yeah, the email interface seems not working for me at the moment.
[23:03] <micahg> lifeless: do you know if there's someone available to take a look at an LP issue?  a branch seems to be stuck
[23:04] <poolie> micahg: tell me more?
[23:04] <micahg> poolie: [13:31] <fta> could someone please unbreak https://code.launchpad.net/~chromium-team/chromium-browser/channels ? it's been scanning for days
[23:06] <poolie> could you please ask a question for it and then i'll escalate it?
[23:06] <micahg> fta: ^^
[23:12] <fta> poolie, https://answers.launchpad.net/launchpad/+question/160629
[23:13] <poolie> thanks
[23:13] <poolie> we're looking into it