[00:16] <wgrant> timrc: With a bit of luck it will be deployed in a day or two.
[00:39] <timrc> wgrant: excellent, thanks again for the quick turnaround
[01:32] <mtaylor> is there a way to have a member of a team not receive PPA build emails?
[01:33] <wgrant> mtaylor: No :/
[01:33] <lifeless> mtaylor: there is a bug about the amount of mail
[01:33] <lifeless> mtaylor: you could fix that
[01:33] <mtaylor> lifeless: :)
[01:34] <mtaylor> lifeless: so I take it the answer for now is "figure out how to filter ppa message MUA-side"
[01:34] <lifeless> mtaylor: well, its a clear problem
[01:34] <lifeless> we should perhaps just add an option
[01:34] <lifeless> measure its use
[01:35] <lifeless> and if it gets past 60 or 70% just stop sending mail
[02:43] <PabloM> hi, I'm learning to use launchpad but I can't find the docs for what I want to do
[02:44] <PabloM> I requested a merge, the reviewer asked me to fix some things, I fixed them, commited the changes and pushed to my branch, how do I update the merge request with the new stuff?
[02:45] <wgrant> PabloM: It should automatically update within a couple of minutes.
[02:46] <PabloM> ohhh you are right, thx (note to self: press F5!)
[02:46] <wgrant> Heh.
[05:02] <poolie> spiv: hydrazine should be ok with maverick lplib now
[05:26] <spiv> poolie: thanks!
[07:02] <fta2> hi
[07:03] <fta2> using getPublishedBinaries(), is it possible to filter by date and/or by binary pkg name? (to limit the number of iterations)
[07:05] <wgrant> fta2: archive.getPublishedBinaries(binary_name='foo')
[07:06] <fta2> and by date?
[07:07] <fta2> it's for my ppa stats tool. i'd like to make the polling incremental
[07:07] <fta2> as 4h is way too long to use more than a few times a month
[07:08] <wgrant> fta2: It should order by date.
[07:08] <fta2> no, it's by pkg 1st
[07:08] <wgrant> Argh, true.
[07:08] <wgrant> (name, id)
[07:09] <fta2> which is too bad
[07:09] <wgrant> So.
[07:09] <wgrant> If you're already filtering by name, you get newest-first.
[07:09] <wgrant> So could you just filter by name then read until you see one that you've already seen?
[07:09] <fta2> i'm not filtering at all atm
[07:14] <fta2> how can i get all the published binary_names beforehand then?
[07:15] <fta2> (if i want to emulate incremental polling for all pkgs in a ppa)
[07:15] <wgrant> fta2: I was hoping you'd have a list :(
[07:17] <fta2> sadly, i don't.
[07:20] <fta2> wgrant, btw, did you have a chance to investigate the stats issue yet?
[07:21] <wgrant> fta2: We were LOSAless for most of today, unfortunately.
[08:22] <desrt> hello.  is there a launchpad admin that i can speak privately to?
[08:23] <wgrant> desrt: Hi. I'm the help contact for today, you can PM me if you want.
[09:36] <cdbs> 54 minutes to go...
[10:20] <philip_stoev> http://bazaar.launchpad.net/~maria-captains/maria/5.3 URLs do not work for "bzr checkout" . I assume it is connected to the current maintenance.
[10:20] <philip_stoev> bzr reports "bzr: ERROR: Not a branch:" , because the launchpad homepage is served instead
[10:20] <wgrant> philip_stoev: Right, we're not completely back up yet.
[10:20] <philip_stoev> ok thanks np
[10:20] <wgrant> philip_stoev: Nearly there, though.
[10:21] <wgrant> The webapp comes up early, codehosting takes a few minutes longer.
[10:23] <wgrant> philip_stoev: It's back now.
[10:23] <philip_stoev> wgrant: thanks
[10:29] <zyga> hi, is there a way to construct an URL to source viewer for particular launchpad project, branch name and _TAG_ (not revision)
[10:29] <cdbs> Yay!
[11:13] <spiv> zyga: I don't think so unfortunately
[11:13] <zyga> spiv, thanks
[11:13] <spiv> zyga: it probably wouldn't be hard to add
[11:13] <spiv> zyga: file a bug
[11:14] <zyga> spiv, I found two issues with current URLS - they require the (volatile) knowledge of branch owner
[11:14] <spiv> (I'm imagining something like http://bazaar.launchpad.net/~bzr-pqm/bzr/bzr.dev/changes/tag:bzr-2.4b1)
[11:14] <zyga> spiv, and there is no way to link directly to a tag instead of a revision
[11:14] <spiv> zyga: for official branches they don't
[11:14] <wgrant> You can use /+branch/project/changes
[11:14] <spiv> e.g. http://bazaar.launchpad.net/+branch/bzr
[11:15] <zyga> hmm
[11:15] <zyga> right
[11:15] <spiv> (Basically every lp:… branch can be viewed at the corresponding http://bazaar.launchpad.net/+branch/…)
[11:15] <zyga> in my use case I keep track of gcc-linaro/4.5 so it's not going to help that much, right?
[11:16] <wgrant> /+branch/gcc-linaro/4.5
[11:16] <zyga> oh, right it works
[11:16] <zyga> I though only trunk will work like that
[11:16] <zyga> cool
[11:16] <spiv> zyga: http://bazaar.launchpad.net/+branch/gcc-linaro/4.5 ?
[11:16] <wgrant> /+branch/WHATEVER works where WHATEVER is any branch name or alias that LP recognises.
[11:17] <spiv> Oh, I'm too slow :)
[11:17] <wgrant> (except for private branches, which only work on HTTPS)
[13:11] <Chr|s> hey guys
[13:12] <Chr|s> what happens if I am unable to access my account? I don't have access to the email tied to that account unfortunally
[13:24] <Chr|s> I have filed a support ticket regarding this
[16:21] <xnox> I've emailed merge@code.launchpad.net with a merge bundle generated by $bzr send but nothing seemed to happen =( Did I miss something? Does the email needs to be GPG signed?
[16:24] <maxb> xnox: Yes, it does
[16:24] <xnox> aha =) let me try again.
[17:11] <xnox> OOPS-1922CMP2 what happened?
[17:11] <xnox> did launchpad not figure out that i wanted to propose merge not for the development focus but a leave branch?
[17:11] <xnox> s/leave/leaf
[17:17] <fta> OOPS-1922F1441
[17:19] <maxb> jcsackett: Hello, would you be able to provide me with xnox's OOPS info? I have stared at CMP ones before and can probably figure it out
[17:19] <maxb> quite quickly
[17:20]  * jcsackett looks
[17:21] <jcsackett> maxb: probably, but first i have to go find it; it's not showing up in our Oops-tools.
[17:21] <maxb> jcsackett: crowberry
[17:21] <jcsackett> maxb: i know, i just have to dig it up. :-)
[17:22] <maxb> Ah. Last time this happened, we had people playing hunt-the-machine :-)
[17:22] <jcsackett> i think i know the time; i watched the hunt. :-)
[17:22] <jcsackett> hunt-the-machine. worst game ever.
[17:35] <maxb> xnox: The problem is bug 718723 - in short, mailed bundles for 2a format branches are broken
[17:36] <xnox> maxb: just great. I need to do a merge proposal for a non-dev-focus branch which is 500GB in size.
[17:36] <xnox> sorry =)
[17:36] <xnox> typo
[17:36] <xnox> 50MB
[17:36] <xnox> and when I push it, it takes ages from my connection
[17:36] <xnox> when I do $ bzr push lp:~/project/new --stacked-on=lp:~/project/old-target
[17:37] <xnox> it does it quickly, but the resultant branch is broken on launchad.
[17:37] <xnox> what is the correct naming scheme for me to reconfigure the branch on launchpad after the push?
[17:38] <xnox> but that's the old bugs with stacking on launchpad. I might right a plugin to do those things if at all it is possible.
[19:43] <sin8h_> http://bazaar.launchpad.net/~launchpad-pqm/launchpad/db-devel/annotate/head:/database/schema/trusted.sql isn't working
[19:47] <jcsackett> sin8h_: it's opening for me, have you tried reloading? loggerhead ocassionally errors the first time you try to access something.
[19:48] <sin8h_> jcsackett: yeah its working for me now. thanks :)
[19:48] <jcsackett> you're welcome. :-)
[20:15] <maco> i have a question for an LP Admin, but it's a bit sensitive, so i'd like to ask it in a PM...
[20:15] <maco> i just dont know who the LP Admins are
[20:16] <jcsackett> maco: i'm on help contact duty for lp right now, feel free to PM me.
[20:42] <Chr|s> how do I center the top table with my picture and info? https://wiki.ubuntu.com/ChrisMcCormick
[21:04] <benji> Chr|s: I /think/ this will help: http://moinmo.in/HelpOnTables
[21:11] <Chr|s> benji: thanks, can't seem to figure out how to center the table
[21:16] <benji> Chr|s: try margin:auto
[21:17] <Chr|s> how do I center the top table with my picture and info? https://wiki.ubuntu.com/ChrisMcCormickok
[21:17] <Chr|s> err
[21:17] <Chr|s> up arrow fml
[21:17] <Chr|s> ok will try
[21:18] <benji> heh
[21:18] <Chr|s> ahh that worked perfectly
[21:18] <benji> this appears to work in my sandbox: http://pastebin.ubuntu.com/590438/
[21:18] <Chr|s> thanks benji
[21:19] <benji> cool
[22:03] <nessita> hi there, any ideas why a launchpad build is failing with: dpkg-deb: error: control directory has bad permissions 700 (must be >=0755 and <=0775)?
[22:03] <nessita> (from https://launchpadlibrarian.net/68485456/buildlog.txt.gz)
[22:05] <sinzui> nessita: I do not know, but wgrant will be available soon and he may have insight into the matter
[22:06] <nessita> sinzui: thanks!
[22:06] <sinzui> nessita: I am aware that a change was made recently were builds were wrongly reported to be sucessful...they were in fact failing.
[22:06] <sinzui> nessita: have you built and installed this package from the ppa before?
[22:07] <nessita> sinzui: hum, I see. But I don't think that's our case, since we not only got 'build success' but also we got a new package available
[22:07] <nessita> sinzui: yes, everyday after every commit :-) (we have a bot)
[22:07] <bigjools> it doesn't like the permissions on your debian/control dir
[22:08] <nessita> bigjools: control is a file not a dir, so the error puzzles me
[22:08] <bigjools> sorry thinko, I meant file
[22:08] <nessita> bigjools: and we're using the exact same branch to build maverick and lucid, and that builds properly
[22:09] <nessita> bigjools: also, the control file has perms 644, not 700 like the error is reporting
[22:10] <bigjools> does this help? http://ubuntuforums.org/showthread.php?p=6471986
[22:10]  * nessita looks
[22:11] <nessita> bigjools: not really. I requested the build of this recipe: https://code.launchpad.net/~ubuntuone-hackers/+recipe/client-dailies, and it built fine for maverick and lucid, and failed for natty
[22:11] <bigjools> it mght be a dpkg bug
[22:11] <nessita> no NTFS file system around here
[22:11] <bigjools> I would google the error and see what you can find
[22:12] <bigjools> I see quite a few hits
[22:15] <nessita> bigjools: but... would that make fail only one build? :-/
[22:15] <bigjools> no idea :/
[22:15] <nessita> yesterday that same recipe built fine on the 3 versions
[22:15] <bigjools> something changed somewhere then
[22:16] <lifeless> there's an amd64 buildd issue at the moment
[22:16] <lifeless> lamont was talking about it in u-d
[22:17] <nessita> lifeless: thanks! that makes more sense
[22:19] <bigjools> that was an i386 build though?
[22:19] <nessita> checking
[22:19] <bigjools> well it's getting i386 Packages files :)
[22:19] <nessita> bigjools: you're right :-/
[22:20] <lamont> bigjools: speaking of which, land https://code.launchpad.net/~lamont/launchpad/lp-buildd-77/+merge/56652 pls
[22:20] <lamont> nessita: what builder?
[22:20] <bigjools> lamont: it's 22:20 here, but I am sure wgrant will do it for you when he starts
[22:20] <lamont> bigjools: i386 machines installed during march are likely to be affected
[22:20] <lamont> cool
[22:20] <nessita> lifeless: any idea why i'm getting this build failure https://launchpadlibrarian.net/68485456/buildlog.txt.gz for the ubuntuone-client dailies?
[22:21] <bigjools> lamont: aaaaa umask ....
[22:21] <lamont> nessita: what builder?
[22:21] <lamont> as in what's the build url
[22:21] <lamont> buildlogs are useless
[22:21] <bigjools> nessita: it's *always* best to post the build URL, not the log URL
[22:21] <lamont> bigjools: speaking of which... could we get the builder URL into the build log?
[22:21] <bigjools> lamont: file a bug on launchpad-buildd and send wgrant cookies :)
[22:22] <lamont> heh
[22:22] <lamont> nessita: and in the meanwhile, retrying the build will fix it.
[22:22] <bigjools> actually we could put a dirty hack in the b-m to send it in the build start message
[22:22] <lamont> the ones that retrying won't fix are the builds that "succeeded" because they silently failed
[22:23] <lamont> bigjools: couldn't sbuild-package do it?
[22:23] <nessita> lamont: natty for ubuntuone-client dailies recipe
[22:23] <lamont> URL??\
[22:23] <nessita> lamont: build log https://launchpadlibrarian.net/68485456/buildlog.txt.gz
[22:23] <nessita> lamont: I'm sorry, but I'm not sure what you're asking. is this the build url you want? https://code.launchpad.net/~ubuntuone-hackers/+recipe/client-dailies
[22:23] <nessita> lamont: I retried twice, let's see if the third time is a charm
[22:23] <bigjools> lamont: probably not
[22:23] <nessita> lamont: what URL are you asking me? :-)
[22:23] <lamont> of the build record
[22:24] <lamont> the place where you clicked on the link that gave you the 'buildlog'
[22:24] <lamont> and that retry, was it less than 50 minutes ago?
[22:26] <lamont> nessita: basically, from the buildlog, we can get no where.  from the build URL, we can get everywhere
[22:26] <lamont> and I have to run, willread scrollback later
[22:28] <nessita> lamont: https://code.launchpad.net/~ubuntuone-hackers/+recipe/client-dailies
[22:28] <nessita> (I linked that before, but seems like that is what you want?)
[22:30] <lamont> bigjools: sigh.  I'm going to bet that the recipe builder doesn't deal with umask either.
[22:30] <bigjools> lamont: why is it suddenly a problem?
[22:30] <bigjools> did the natty toolchain change?
[22:31] <lamont> https://code.launchpad.net/~ubuntuone/+archive/nightlies/+buildjob/2431983 <-- that's the actual URL I was after, yours got me there well enough though)
[22:31] <lamont> bigjools: underlying sudo on the builder guest got upgraded to 1.7.2
[22:31] <bigjools> ah I have recollections of some sudo thing
[22:31] <lamont> bigjools: I'll finish stabbing the sudoers version of the fix into things tonight
[22:31] <cody-somerville> When I search for a user in the 'Subscribe someone else' modal dialogue, how do I open the lp page for one of the results to verify the result is who I think it is?
[22:32] <lamont> but must flee now.  afk for a while
[22:32] <bigjools> sinzui: did you get all that? :)
[22:33] <cody-somerville> Also, how do I search for a user by e-mail address?
[22:33] <sinzui> no, I am still trying to stuff the info into my head
[22:36] <nessita> lamont: third build request failed with the same error
[22:38] <sinzui> cody-somerville: search user in pickers and /people always searches email address
[22:39] <cody-somerville> sinzui, search from homepage doesn't
[22:39] <cody-somerville> and no link to /people from homepage either
[22:39] <sinzui> cody-somerville: I did not say that did. that is google
[22:40] <sinzui> cody-somerville: browser people and teams got removed I see
[22:47] <fta> wgrant, \o/ multi-PPA stats: http://people.ubuntu.com/~fta/chromium/stats/stats.html
[22:48] <fta> still polling...
[23:27] <micahg> sinzui: karma has been expired for several hours, is this a known issue?
[23:28] <sinzui>  micahg: I cannot  say.
[23:29] <micahg> sinzui: should I file a support request?
[23:29] <sinzui> I am down about 10,000 karma points over the last 2 months. I believe that is because worked with blueprints last year about this time
[23:29] <sinzui> micahg: Can you verify you have maintained the same activity you had last year, doing the same comparable things?
[23:29] <sinzui> There are not reports of karma not running
[23:30] <sinzui> what activities do you do?
[23:30] <micahg> sinzui: huh?  I'm just noting that it shows as expired on everyone's page, not quibbling about the value
[23:30] <sinzui> everyones?
[23:30] <sinzui> intersting
[23:30] <sinzui> ha
[23:30] <sinzui> that is stupid
[23:30] <micahg> sinzui: yours, mine, pitti's
[23:31] <sinzui> it is not a support issue
[23:31] <sinzui> it is a defect in the templates
[23:34] <sinzui> micahg: This is bug 415346. The rules for PersonKarmaView.has_expired_karma look wrong
[23:36] <micahg> sinzui: well, something broke it in the last couple days
[23:37] <sinzui> I do not think so. We stopped working on karma a couple years ago because we think we should remove it
[23:37] <sinzui> I am annotating the code now
[23:38] <micahg> sinzui: it has been working and only showing that notice once a day on average when recalculating
[23:39] <sinzui> micahg: yes. understood. that time though is actually several hours
[23:39] <sinzui> So nothing has changed, though a script may be taking longer to run
[23:40] <sinzui> there are no karma script wanings in my inbox at the moment
[23:44] <maxb> Any reason not to simply remove that conditional message entirely, for a net better display of info?
[23:47] <sinzui> maxb. I was just thinking that. The message doesn't seem to work in any case
[23:47] <sinzui> I think the change was made about the time we decided karma was dead horse
[23:51] <wgrant> micahg, sinzui: The karma script would have been killed half-way through last night for the rollout.
[23:51] <wgrant> It's a bit of a silly script, so it will leave things in a terribly inconsistent state until it runs again in 8 hours.
[23:52] <micahg> ah, so it probably started and never finished
[23:53]  * maxb wonders when the losa assigned questions will next get processed :-/
[23:53] <wgrant> maxb: We have a new LOSA this week, so things may start happening soonish maybe :)
[23:53] <maxb> that would be nice
[23:54] <maxb> It's a bit suboptimal that trivial jobs for one who has access get left pending for days at a time :-/
[23:54] <Chex> maxb: that would be me this week, sorry, been pretty busy, will tackle those tomorrow
[23:54] <maxb> thanks :-)
[23:54] <Chex> maxb: do you have one specifically you need done now?
[23:54] <mbarnett> this iis very true.
[23:55] <maxb> Tomorrow will be fine
[23:55] <Chex> maxb: ok, thanks
[23:55] <lifeless> maxb: we've new losas coming on board soon
[23:55] <maxb> there are only two queued anyway :-)
[23:55] <mbarnett> maxb: we might have to look at how we manage that task to avoid letting easy tasks slip for days.
[23:55]  * mbarnett already has a couple ideas. 
[23:56] <lifeless> mbarnett: drive to zero, keep there ;)
[23:56] <maxb> That sounds like a great idea :-)
[23:56] <mbarnett> lifeless: too easy!  i want something far more complicated with algorithms and processes!
[23:56] <mbarnett> everything filed in triplicate
[23:57] <mbarnett> using actual carbon paper
[23:57] <maxb> Is there enough capacity that someone could have a rotation each day for doing stuff that is trivial, and leaving a "This is complex, we'll get to it later" comment on things that are not?
[23:57] <lifeless> monofilament carbon weave?
[23:57] <lifeless> maxb: in a month or so, maybe
[23:58] <mbarnett> maxb: that is how it is supposed to work right now, but once we have a few more heads actually trained up, we should be able to come up with a more failproof system to ensure that at least the easy stuff doesn't hang around.
[23:58] <spm> surely not atm. trivial is kinda a misnomer as well. anything trivial or not, is a mental switch from whatever you're doing. given that for most of my day I'm typically doing 2-3 things in parallel, all day long. "trivial" isn't.
[23:59]  * mbarnett says confidently speaking for everyone, which he has no authority to do. 
[23:59] <spm> :-)
[23:59] <mbarnett> spm: 2 or 3 NOTHINGS!
[23:59] <spm> sush. lets not spoil the illusion I have cunningly woven here