[01:54] <michaelh1> Afternoon.  How can I get the messages attached to a bug using launchpadlib?
[01:54] <michaelh1> I have a bug.messages_collection_link, but trying a luanchpad.load() on that gives an error
[01:55] <doctormo> Hey michaelh1
[01:55] <doctormo> Try for message in bug.messages_collection:
[01:56] <wgrant> Not messages_collection. Just messages.
[01:58] <michaelh1> Yip, that does it.  I didn't see that in the 1.0 API doc.  What's the best way of finding such things?
[01:58] <wgrant> michaelh1: launchpadlib is magic, and +apidoc doesn't know about the magic.
[01:58] <wgrant> *_link and *_collection_link are just URLs.
[01:58] <wgrant> launchpadlib works this out, and turns them into more normal attributes that retrieve the contents automatically.
[02:00] <michaelh1> Ah, so where I was using load(task.bug_link), I should use just task.bug
[02:02] <wgrant> michaelh1: Exactly.
[02:11] <michaelh1> Is there a way to speed things up by assuming the cache is good?
[02:11] <michaelh1> or other ways of speeding things up when you're writing a new script?
[02:32] <lifeless> michaelh1: there is a post about tuning lp api scripts on the launchpad blog
[02:32] <lifeless> michaelh1: beyond that, its largely in the lp devs hands to make things faster - which we are doing
[02:38] <michaelh1> lifeless: it's more that I'm running the same script over and over while developing, so could re-use the same data without fetching
[02:39] <lifeless> lplib has a cache in it
[02:41] <lifeless> so you should already be avoiding some redudant transfer
[02:45] <michaelh1> lifeless: yip, but my data set is read only and (for now) I don't care about upstream changes
[02:45] <michaelh1> It's all good.
[02:46] <wgrant> LP rejected a PPA upload because I used a bad team name.
[02:46] <wgrant> It has ignored two subsequent uploads to the right name, giving me no response.
[02:46] <wgrant> It is correctly signed -- the changes file is identical to the rejected one.
[02:51] <tgm4883> Not sure where I should file this bug against (lauchpad.net or w3m). I filed a bug via the command line which opened up launchpad.net via w3m. I tried to login, multiple links are present on the login page (including cancel), but I have no way to continue. The text where I would expect continue to be a link to submit my credentials appears to just be text, not a link
[02:51] <wgrant> spm: Is germanium's process-upload.py somehow unhappy?
[02:51] <wgrant> Or its poppy-sftp?
[02:52] <lifeless> wgrant: how would I tell ?
[02:52] <lifeless> wgrant: spm is awl
[02:52] <lifeless> tgm4883: well, both arguably have a problem - I'start with a bug on launchpad-foundations
[02:53] <wgrant> lifeless: No idea.
[02:53] <wgrant> I guess I'll try cocoplum instead.
[02:53] <tgm4883> lifeless, ok, i'll file one there. Thats where I was leaning anyway since the rest of the links appear to be working. Thanks
[03:46] <Dies> Anyone else having problems with "pear"?
[03:49] <lifeless> ?
[03:51] <magcius> oi
[03:51] <magcius> Launchpad is running like hell on my Firefox
[03:52] <magcius> https://launchpad.net/ubuntu/+source/xorg is updating very slowly when scrolling
[03:52] <micahg> magcius: nvidia chipset?
[03:52] <magcius> micahg: indeed
[03:52] <magcius> I'm running a Firefox nightly and I have a few patches for the xserver
[03:53] <lifeless> png provoked driver bug IIRC
[03:53] <magcius> lifeless: hm?
[03:53] <magcius> ok, what the hell?
[03:53] <micahg> magcius: known issue, I need to upstream it
[03:53] <magcius> https://dev.launchpad.net/ <-- the header background is a solid color png
[03:54] <magcius> and it's 1px wide, which is going to cause hell on the browser rendering
[03:54] <magcius> any reason you can't use background-color?
[03:54] <magcius> lifeless: do you know the cause?
[03:55] <magcius> lifeless: I can report it to the team, if you want.
[03:55] <wgrant> It won't cause hell -- it's a very normal technique.
[03:55] <wgrant> But yes, it should be a background colour.
[03:55] <magcius> wgrant: 1px wide is still stupid.
[03:56] <lifeless> well, we still support ie6
[03:56] <magcius> ok
[03:56] <lifeless> anyhow, I don't know the cause, I just remember a thread somewhere about linux driver bugs causing this behaviour
[03:56] <lifeless> micahg: do you have a bug # for magcius ?
[03:56] <magcius> I don't run Ubuntu.
[03:57] <lifeless> magcius: And ? Its not Ubuntu specific (in fact, I suspect we've fixed it in Ubuntu)
[03:57] <magcius> lifeless: hm, how did you fix it? xorg patch?
[03:57] <micahg> bug 223238
[03:57] <magcius> Thanks
[03:58] <magcius> oh what the hell
[03:58] <magcius> can I have a txt dump of that page, comments, attachments?
[03:58] <lifeless> https://launchpad.net/bugs/223238/+text
[03:59] <magcius> Thanks
[03:59] <magcius> This is why I love LP./
[03:59] <magcius> Except for code hosting.
[04:00] <magcius> ok, there's no patches
[04:00] <magcius> http://launchpadlibrarian.net/14027687/unnamed <-- oh, thanks
[06:51] <micahg> is there anyone around why can score up the chromium and mozilla daily builds?
[06:51] <StevenK> Yes, I can.
[06:51] <micahg> StevenK: awesome, do you know where they are?
[06:52] <StevenK> Nope, I am blissfully unaware
[06:52] <StevenK> I'm guessing ubuntu-mozilla-daily somewhere
[06:52] <micahg> https://edge.launchpad.net/~chromium-daily/+archive/ppa
[06:53] <micahg> https://edge.launchpad.net/~ubuntu-mozilla-daily/+archive/ppa/+packages
[06:53] <micahg> StevenK: don't bother w/chromium-codecs-ffmpeg as it's broke
[06:53] <micahg> StevenK: thanks :)
[06:53] <StevenK> You want all of the chromium builds bumped?
[06:54] <StevenK> Doesn't it take hours to build?
[06:54] <micahg> StevenK: looks like just i386 needs bumping
[06:55] <micahg> and for the daily, I think it's an hour
[06:55] <micahg> oh, maybe not
[06:55] <StevenK> micahg: i386 for hardy, jaunty, karmic, lucid and maverick is where I'm going ...
[06:55] <micahg> yeah, between 1-2 hrs depending on which builder I think
[06:56] <micahg> maverick build in 1 hr, jaunty in 2
[06:56] <micahg> on amd64
[06:58] <micahg> maybe it's just the small number of builders...not the python stuff
[06:58] <micahg> python stuff is still 2400
[06:58] <micahg> StevenK: any idea how long until the PPA bulders come back, i386 is showing 8/1 for build date
[06:59] <StevenK> Nope, but they're not usually gone all that long
[06:59] <micahg> StevenK: well, if we have to be picky about which builds to rescore, I'd say lucid and maverick
[06:59] <StevenK> But yes, you're right, there's 7 amd64 builders and 3 i386
[07:00] <StevenK> micahg: Given there's 3 builders, I'm a little bit retiscent to score up a bunch of stuff that could keep one builder fully occupied for over 24 hours, that's all.
[07:00] <micahg> that should only be about 8 hrs of build time
[07:01] <micahg> StevenK: no, just lucid and maverick i386 for mozilla daily and chromium daily
[07:01] <micahg> that should be around 8 hrs
[07:01] <StevenK> That's still 8 hours just for chromium :-)
[07:01] <micahg> no, should be 2-4
[07:02] <micahg> StevenK: just the daily PPA I think
[07:02] <wgrant> Um.
[07:02] <wgrant> There are 3 i386 builders.
[07:02] <wgrant> Dailies are surely the last things that should be scored up.
[07:02]  * StevenK waves his hands
[07:03] <StevenK> I'm doing it because I was asked to, and would rather avoid an argument about the best use of buildd CPU time
[07:03] <wgrant> Well.
[07:03] <wgrant> I don't think dailies are the best use.
[07:03] <micahg> these are the most popular dailies
[07:03] <wgrant> Given that they happen... daily.
[07:03] <wgrant> And take a damn long time to build.
[07:04]  * micahg will reduce the request even further to just xulrunner-2.0 and firefox 4.0 i386 for lucid and maverick for the mozilla stuff which'll take all of 2 hrs to build
[07:05] <StevenK> micahg: That's all of the chromium stuff bumped
[07:06] <micahg> StevenK: I hope just 2 builds, right?
[07:07] <StevenK> micahg: 4 builds
[07:07] <StevenK> But I've bumped stuff by mistake that can be fixed
[07:07] <StevenK> micahg: And xulrunner-2.0 firefox-4.0 i386 {lucid,maverick} bumped
[07:08] <micahg> StevenK: awesome, thank you :)
[07:12] <magcius> micahg: why aren't you just using the nightlies provided by Mozilla?
[07:12] <micahg> magcius: we use some system libs and our builds come as .debs
[07:12] <magcius> micahg: ok.
[07:12] <magcius> micahg: are there any changes to the source besides the configuration?
[07:13] <magcius> micahg: also, are you using PGO?
[07:13] <micahg> magcius: yes, we remove the binary parts
[07:13] <micahg> magcius: no, not yet since upstream is not doing it yet
[07:13] <magcius> micahg: binary parts? Also, isn't this a violation of the trademark guidelines?
[07:13] <micahg> magcius: we should go to #ubuntu-mozillateam to continue this
[07:13] <magcius> micahg: ok
[07:14] <magcius> micahg: I don't use Ubuntu, though
[07:14] <micahg> magcius: k, but this discussion is OT for this channel :)
[07:15] <magcius> micahg: I agree.
[07:16] <magcius> micahg: does Launchpad have a "Send Upstream" button yet? :P
[07:16] <micahg> magcius: no, but it's in progress I think
[07:19] <magcius> is http://packages.ubuntu.com/ obsolete now with http://launchpad.net/ubuntu/+source having the same data and more? Will it be phased out?
[07:22] <logari81> hi, what happened with the i386 ppa builders?
[07:22] <logari81> i386  	3  	 679 jobs (three days)
[07:29] <magcius> logari81: the builders are overloaded terribly right now
[07:30] <logari81> magcius: but why only i386?
[07:30] <magcius> logari81: because that's the majority of where build jobs go
[07:30] <logari81> ok
[07:33] <logari81> magcius: is there any way to cancel some jobs? I don't want to contribute to this jam
[07:33] <magcius> logari81: don't worry about it
[07:33] <magcius> logari81: someone here could probably do it though
[08:40] <rioch> I have a bunch of new translation files that have been sitting in my import queue with the status "Needs review" for some time now.
[08:40] <rioch> How can I get these imported?
[09:41] <tseliot> any launchpadders around? I'm having a problem with a private PPA
[09:43] <tseliot> I'm seeing the following error: https://pastebin.canonical.com/35210/
[09:43] <tseliot> after I try to upload to that private PPA. Another user is having the same problem
[09:51] <tseliot> allenap: ^^
[09:57] <allenap> tseliot: I don't know about PPPAs but I'll see if I can find someone who does.
[09:57] <tseliot> allenap: thanks
[09:58] <allenap> Perhaps if I mention soyuz here I'll cause some IRC clients to go ping :)
[09:59] <bigjools> hello
[09:59] <bigjools> was OTP
[10:00] <bigjools> tseliot: it's a bug
[10:00] <bigjools> private team?
[10:01] <bigjools> we've got private teams using private PPAs elsewhere though, so this is odd
[10:04] <tseliot> bigjools: yes, it's a private team
[10:05] <bigjools> tseliot: please file a bug on launchpad-registry, their code has a bug
[10:05] <bigjools> paste that rejection message
[10:06] <tseliot> ok, thanks
[10:12] <tseliot> I've filed bug #611617
[10:12] <bigjools> tseliot: was it a private PPA as well?
[10:12] <soren> I have an e-mail in a mailing list's moderation queue which was sent by a subscriber.. How can I tell why it's being held for moderation?
[10:12] <tseliot> bigjools: yep
[10:12] <bigjools> tseliot: ok thanks
[10:14] <soren> It even correctly identifies the sender and sets the Author URL to point to his lp page.
[10:14] <soren> so it's not because he's using an e-mail address unknown to LP, which was my only guess. :-/
[10:15] <soren> He also says he doesn't actually receive any e-mails from the list.
[10:15] <tseliot> bigjools: if you need further information, just let me know :-)
[10:15] <tseliot> and thanks for your help
[10:15] <bigjools> tseliot: I need to wait for curtis to comment
[10:15] <bigjools> np
[10:16] <tseliot> ok
[10:16] <wgrant> Sounds like it's because the private team's email addres is the maintainer.
[10:16] <soren> There's a private team?
[10:17] <wgrant> soren: I refer to tseliot's issue.
[10:17] <soren> Oh.
[10:17] <soren> Heh :)
[10:17] <tseliot> ah, let me check the other packages
[10:20] <czajkowski> soren: content in the email ?
[10:20] <czajkowski> soren: or subject
[10:21] <tseliot> wgrant: I've just looked at another package (that was successfully uploaded) and the maintainer's address is not the team's address
[10:21] <soren> czajkowski: Well, he does says "Wow!" in there, but being excited should be allowed :)
[10:21] <wgrant> tseliot: What about the package that failed to upload?
[10:21] <czajkowski> soren: I'm not gonna argue, just seen it sometimes if a subject is odd or there is unusal content.
[10:22] <tseliot> wgrant: it was using the team's address
[10:22] <wgrant> tseliot: That would probably be it, then.
[10:22] <tseliot> yep, let me try here
[10:22] <soren> czajkowski: Yeah.. I don't /think/ that's it. It doesn't look spammy to my eye at all.
[10:22] <wgrant> Someone should probably add that to the bug.
[10:24] <tseliot> wgrant: I'll try to upload again and add a note in the bug report
[10:24] <soren> czajkowski: Uh... And now the one in the queue just got accepted (without my doing anything) and another one he sent shot straight through. /me suspects a man behind the curtain laughing at me right now
[10:25] <czajkowski> soren: tis early in the morning, go make yourself a cuppa tea ;)
[10:31]  * soren does so
[10:34] <tseliot> wgrant: that did it
[10:34] <wgrant> tseliot: Excellent. I've already commented on the bug.
[10:36] <tseliot> wgrant, bigjools: thanks for your help
[10:37] <bigjools> tseliot: coolio, glad it works now
[10:38] <bigjools> so it DTRT, just the error message was kinda funky
[10:38] <tseliot> yes
[10:39] <wgrant> Is it the right thing?
[10:39] <wgrant> I guess it does end up in indices...
[10:46] <X3> can anyone look at this https://code.launchpad.net/~x3lectric/xbmc/svn-trunk
[10:46] <X3> it fails most of the times
[10:48] <wgrant> X3: It's that same issue as before...
[10:48] <wgrant> LOSA ping: pear's bzr-svn config is corrupt again.
[10:48] <mthaddon> ugh
[10:48] <X3> wgrant if the issue is that it keeps failing then ya
[10:48] <jelmer> mthaddon: I'll be landing a fix for that issue tonight.
[10:49] <X3> morning btw
[10:49] <jelmer> hi William, Tom, X3
[10:49] <X3> hi jelmer
[10:49] <wgrant> Morning jelmer.
[10:50] <mthaddon> wgrant, jelmer: ok, I think that should be better now
[10:50] <X3> whos buying breakfast?
[10:50]  * jelmer hands X3 a cup of coffee
[10:50]  * X3 takes it and has a sip
[10:51] <wgrant> mthaddon: Thanks.
[10:51] <mthaddon> np
[10:51]  * X3 passes bacon sandwiches around
[10:56] <X3> also besides that trunk failing to import, i wanted to ask about ntfs-3g is there a actuall ntfs-3g-2010.5.22 all I see is older versions
[10:57] <X3> some bugs I have been fixed in that new version
[10:57] <wgrant> X3: 2010.3.6 is the latest version in Ubuntu.
[10:57] <X3> current in linux even backport dont work
[10:58] <X3> ya that version is still bummed
[10:58] <wgrant> X3: The import is going again.
[10:58] <wgrant> On one of the slow machines, sadly.
[10:58] <X3> thx
[10:58] <X3> lol
[10:58] <X3> they all slow
[10:59] <wgrant> But some are slower than others.
[10:59] <X3> 20 hours to compile sabnzbdplus backport
[10:59] <wgrant> Oh, they're different machines.
[10:59] <X3> its a bit congested it seems
[10:59] <wgrant> The build farm is a little busy at the moment.
[10:59] <wgrant> Yes.
[11:00] <X3> is there an easy way to import the new ntfs-3g and have it buid
[11:01] <X3> im quite new at packaging and all my attempts fail
[11:30] <X3> how do I request a code import if the ntfs-3g project doesnt exist
[11:30] <X3> im at the request page and only 3 related projects are up
[11:35] <X3> do I have to register the project myself or how can I link it otherwise
[12:01] <vish> hi , I'm not able to assign a bug to the docs team [I'm part of the papercuts team,the bug supervisor for papercuts project] , is that also not possible now?
[12:02] <vish> Error ID: OOPS-1672N688
[12:02] <vish> and Error ID: OOPS-1672N673
[12:03] <vish> tried several times and it keeps giving Timeout Error..
[12:19] <vish> bah , same problem with edge too :(  Error ID: OOPS-1672EB2311
[12:56] <pmatulis> can someone confirm that launchpadlib does not have proxy support?
[12:57] <pmatulis> add-apt-repository uses it (i think) and fails in proxy environment
[12:59] <jpds> pmatulis: It doesn't (but I think it's more a Python issue).
[12:59] <pmatulis> jpds: alright, thx
[13:03] <vish> hmm ,i kept trying and lp kept giving me timeout errors! but seems to have worked!
[13:03] <vish> now I have a double comment :/
[14:31] <diwic> Three days until my package builds? *moaning*
[14:33] <X3> i been waiting for way more then 3
[14:44] <bigjools> where are you getting three days from?
[14:45] <shadeslayer> we owns the buildd with KDE ... muwhahaha :P
[14:46] <shadeslayer> jk
[14:46] <diwic> bigjools, https://launchpad.net/~diwic/+archive/ppa/+build/1897162
[14:46] <bigjools> hmmm
[14:46] <bigjools> ok thanks
[14:46] <bigjools> we might get some builders back today I hope
[14:47] <diwic> bigjools, are they busy building other things?
[14:47] <diwic> bigjools, doing archive rebuilds as a result of the new toolchain?
[14:48] <shadeslayer> bigjools: same goes for https://code.edge.launchpad.net/~team-iquik/+recipe/lmsensors-trunk
[14:48] <bigjools> no, the rebuilds were scored to the bottom
[14:49] <shadeslayer> btw can you delete the first 2 builds from that
[14:49] <shadeslayer> since we want the package to go in experimenting
[14:49] <bigjools> we've got a backlog because the available build machines has been reduced for 2 days
[14:49] <bigjools> you can delete your own builds if theyre not necessary
[14:49] <diwic> okay
[14:49] <shadeslayer> bigjools: ok
[14:49] <bigjools> just delete the source and the build will be ignored
[14:50] <shadeslayer> err
[14:50] <shadeslayer> bigjools: its a daily build ^_^
[14:51] <bigjools> recipe?
[14:51] <shadeslayer> bigjools: delete the recipie? :o
[14:52] <bigjools> I was asking if it's a recipe build
[14:52] <shadeslayer> yes
[14:52] <bigjools> ok
[14:52] <bigjools> abentley: is it possible to have more than one outstanding recipe build for the same package/person/ppa ?
[14:53] <abentley> bigjools, yes, if the distroseries are different.
[14:54] <bigjools> abentley: what if they're not?
[14:54] <abentley> bigjools, then you should get an error when you request it.
[14:54] <bigjools> ok
[14:55] <bigjools> shadeslayer: you can directly cancel the build request for a recipe
[14:56] <abentley> bigjools, I believe only admins can do that.
[14:57] <bigjools> abentley: oh really?  why the restriction?
[14:57] <abentley> bigjools, because it's not a proper cancel.
[14:57] <shadeslayer> brr everything is frozen
[14:58] <bigjools> oh, the slash and burn approach cancel
[14:58] <abentley> bigjools, it's just that horrible DB query, except as python.
[14:58] <shadeslayer> oh finally
[14:58] <bigjools> abentley: right
[15:04] <czajkowski> sinzui: any luck regarding yesterdays request?
[15:04] <sinzui> czajkowski, none yet. I am going to send  spam to all launchpad engineers to see if anyone knows if the information exists and how to read it
[15:05] <czajkowski> thanks
[15:05] <czajkowski> much appreciated
[15:39] <shadeslayer> jelmer: any news on the kdelibs import? :)
[15:49] <jelmer> shadeslayer: Not yet, still work in progress. I might have some more time for it tonight or some evening next week.
[16:20] <Cepheus> Hmm, milestones on my project are a bit bugged. Tried to delete the bugged milestone, got OOPS-1672C952
[16:52] <shadeslayer> jelmer: ok .. just wanted to know the status
[16:52] <jelmer> shadeslayer: I'll make sure to keep the relevant bug up to date - do you have the bug #?
[16:52] <shadeslayer> er.. i forgot :P
[16:52] <shadeslayer> ill look it up
[16:57] <shadeslayer> jelmer: bug 579491
[16:57] <shadeslayer> ive subscribed my self now
[17:50] <cody-somerville> Could I losa please rename the live-helper project to live-build?
[17:50] <mthaddon> cody-somerville: is that a blocked name? if not you should be able to rename yourself
[17:52] <cody-somerville> mthaddon, how? there isn't a field in change details
[17:52] <mthaddon> are you not the maintainer?
[17:52] <cody-somerville> mthaddon, I am, yes.
[17:53] <mthaddon> hmm, I thought maintainers could - in any case, renaming for you
[17:53] <mthaddon> cody-somerville: done
[17:54] <cody-somerville> mthaddon, thanks. Can you set up an alias too?
[17:54] <cody-somerville> mthaddon, live-helper -> live-build
[17:54] <mthaddon> ok, done
[17:54] <cody-somerville> Thank you! :)
[17:58] <mthaddon> np
[18:50] <bsaibes_> How can I find what is my ID URL
[18:54] <bsaibes_> I think I got it, it should be https://launchpad.net/~my-nickname, now I have to remember whether I have provided a nick name or where to add it
[22:34] <plars> any possible way to re-enable a ppa that has been disabled?
[22:34] <james_w> plars: yes, ask a losa I think
[22:35] <plars> james_w: ok, thanks
[22:37] <wgrant> plars: If a PPA has been disabled, you can reenable it yourself.
[22:37] <wgrant> If it's been deleted, it's not really recoverable at the moment.
[22:38] <plars> wgrant: yeah, in my case I think I deleted it, but if I try to upload to it, I think it said it was disabled... it's deleted, but still there it seems (confusing)
[22:38] <wgrant> plars: At the moment, deleting it just removes the archive from disk. It doesn't yet remove it from the database, although it probably will soon.