[08:21] <Hobbsee> argh.
[08:21] <Hobbsee> where do i see what the email for a team is now, if i'm not an admin?  
[08:40] <carlos> morning
[08:40] <Hobbsee> morning carlos 
[08:41] <mpt> Hobbsee, there's no "E-mail addresses" box in the left column?
[08:41] <Hobbsee> mpt: no - but i'm suspecting that's correct if they have no valid team email.
[08:42] <Hobbsee> it's either that, or LP has removed it as a feature, like the packaging info :)
[08:42] <Hobbsee> s/feature/"feature"/
[08:59] <mpt> I don't know of any changes in that area
[09:01] <mpt> ok, that part of the person/team template hasn't been touched recently
[09:02] <mpt> Neither has the box that contains the addresses itself
[09:40] <ubotu> New bug: #147539 in launchpad "Answers reliability" [Undecided,New]  https://launchpad.net/bugs/147539
[10:00] <ubotu> New bug: #147544 in launchpad-answers "Default search is "by relevancy", which, empty, is identical to "newest first"" [Undecided,New]  https://launchpad.net/bugs/147544
[11:11] <ubotu> New bug: #147577 in launchpad "[edge]  Edit source does not work" [Undecided,New]  https://launchpad.net/bugs/147577
[11:50] <ubotu> New bug: #147598 in launchpad-bazaar "missing constraint to prevent user subscribing to a branch more than once" [Undecided,New]  https://launchpad.net/bugs/147598
[12:47] <egx0r> Whenever I try to "Browse code" I get a 404 not found complaining about the '/files' path was not found. This is only when I push my branch to a team project, not when it's my personal branch. 
[12:49] <egx0r> I pushed the branch yesterday, so maybe this is some kind of lag? 
[12:51] <ddaa> Interesting: https://answers.edge.launchpad.net/~workhorsy
[12:51] <ddaa> this user asked for his account to be deleted
[12:52] <ddaa> and apparently turned it back on later to use code hosting
[01:41] <ubotu> New bug: #147629 in launchpad ""Browse code" results in a 404 " [Undecided,New]  https://launchpad.net/bugs/147629
[01:54] <Hobbsee> how do i set a status of Fix Released, via the email interface?
[01:55] <Fujitsu> Hobbsee: status fixreleased
[01:55] <Hobbsee> Fujitsu: ahh.  no space.
[01:56] <Fujitsu> ie. `  status fixreleased' is the whole line.
[02:07] <variant> Hi, does anyone know how to report abuse/spammer/idiot using answers.launchpad.net ?
[02:07] <variant> gnomefreak: had a feeling this was just a developer channel..
[02:08] <variant> https://answers.launchpad.net/~elliony
[02:08] <gnomefreak> variant: it is but the people that can help would be here if they can do anything at all
[02:09] <variant> ok
[02:09] <gnomefreak> variant: what one is the bad one?
[02:09] <gnomefreak> i see 3 threads
[02:09] <variant> yeah, all junk
[02:10] <variant> it's hte user
[02:11] <variant> nothing too serious.. but it makes me wonder how to report that sort of thing in the future.. i imagine that abusive postings can be a lot worse than that and not being able to report them is not good
[02:11] <gnomefreak> 14321 doesnt look like anything but him asking for help
[02:13] <variant> true.. 
[02:14] <gnomefreak> Fujitsu: cprov what are the steps to get threads removed from answers?
[02:15] <variant> answers is a great service so it's annoying to see crap in there
[02:17] <Hobbsee> gnomefreak: waiting on a LP admin, i think.  i wonder if matsubara can do it
[02:18] <cprov> gnomefreak: or kiko 
[02:20] <variant> "alan pope" just set the status to "rejected"
[02:21] <variant> on one of them
[02:22] <matsubara> heya Hobbsee, how can I help?
[02:22] <Hobbsee> matsubara: abusive user on launchpad, needs the account removed :)
[02:23] <Hobbsee> https://answers.launchpad.net/~elliony
[02:23] <matsubara> Hobbsee: sorry, I don't have such permission.
[02:23] <Hobbsee> matsubara: that's kiko or SteveA, presumably?
[02:23] <Hobbsee> matsubara: i didnt think you did - i wasnt sure though :)
[02:24] <matsubara> Hobbsee: yes or mthaddon
[02:24] <Hobbsee> ahhh.  the other one that starts with m, and has a's and t's in it.
[02:26] <matsubara> :)
[04:17] <pochu> Hello everybody. Does anybody know whether the PPA i386 builder is down, and if so, whether the builds will be automatically queued when it's back?
[04:18] <kiko> pochu, cprov has been looking into it, but I'm not sure what the status on that is.
[04:20] <cprov> pochu: samarium was fixed one hour ago
[04:21] <stdin> just noticed that, it's building one of my packages now
[04:21] <cprov> pochu:  and it should have processed all the pending builds automatically.
[04:21] <pochu> cprov: great, thanks a lot.
[04:22] <Hobbsee> cprov: are there any plans to actually be able to fix things that break between the non-european/brazillian workday?
[04:22] <cprov> pochu: np
[04:22] <Hobbsee> on weekends, in particular?
[04:24] <cprov> Hobbsee: not yet, this particular issue depended on a infrastructure team action, not only me.
[04:24] <superm1> cprov, can you explain how the build score works? is it a sort of queue?
[04:27] <Hobbsee> cprov: true, i was mroe asking in relation to making the infrastructure fixing work better.
[04:27] <cprov> superm1: yes, it considers the source attributes, like  'how long it has been waiting in queue' (older job gets higher scores), target component (main gets higher score than multiverse) and missing build-deps (missing build-deps reduces the score).
[04:28] <cprov> superm1: obviously, highest score per architecture gets dispatched to the first idle builder. Does it make more sense now ?
[04:28] <superm1> yeah much more
[04:30] <superm1> that begs the question though, could one adjust how quickly they will be built by using an override and putting it in main (assuming it doesnt build depend on anything in universe/multiverse)
[04:30] <cprov> superm1: a better description should go to PPAQuickStart at some point (requested on the last PPA101 meeting).
[04:33] <cprov> superm1: yes, sources target to main will be built first and yes it can be considered a bug right now, because we don't have any strategy score against PPAs, for instance, give higher priority to more active PPAs or PPAs owned by people with more karma.
[04:34] <superm1> a step ahead of my recommendations :)
[04:34] <kiko> Hobbsee, what is the process when something, say, in loco team hosting breaks?
[04:35] <Hobbsee> kiko: i'm aware that it's more of a general question.  if it's during hte week, someone in #canonical-sysadmin can probably fix it, if it's on a weekend, tough luck.
[04:35] <Hobbsee> kiko: btw, i think you can deal with this?  https://answers.launchpad.net/~elliony is an abusive account
[04:35] <kiko> Hobbsee, right. 
[04:36] <Hobbsee> kiko: i guess i'm wondering if there's a more effective way of handling weekend breakage
[04:36] <Hobbsee> (although i know it's not specific to LP, per se, and that the answer may well be 'no')
[04:36] <kiko> Hobbsee, I thought we had weekend IS coverage
[04:36] <kiko> for Launchpad we don't have weekend coverage over what IS gives us
[04:36] <Hobbsee> kiko: well, they didnt fix the buildds
[04:36] <Hobbsee> (unsure whether they knew or not, though)
[04:37] <kiko> Hobbsee, was it brought to their attention? and is this clear?
[04:37] <Hobbsee> kiko: unsure, tbh
[04:37] <kiko> cprov, is it documented somewhere that IS should be notified if something goes wrong with a buildd?
[04:38] <cprov> kiko: not formally.
[04:38] <kiko> mrevell, where could we document this, given our existing PPA docs?
[04:39] <mrevell> kiko: I'd say in the PPA FAQ, along with a note in the step by step guide.
[04:41] <Hobbsee> mrevell: that'll probably make IS start getting support requests because people dont konw how to use PPA's properly
[04:42] <Hobbsee> mrevell: $averageuser probably doesnt know the difference between "help, the buildd is broken, so my package wont build" vs "my package has an error, and wont build"
[04:42] <Hobbsee> mrevell: and somehow i doubt they'd appreciate hearing that
[04:43] <mrevell> Hobbsee: Hmm, okay. Then we need to find a way to help people distinguish the difference. Would you say that's achievable?
[04:45] <Hobbsee> mrevell: if they're still having trouble with version numbers, and components in particular, i'd suspect "not at this point"
[04:46] <mrevell> Hobbsee: Okay. So, how would you explain to me how to tell the difference? Or is it just not that simple?
[04:47] <stdin> could it be possible that if a certain number of builds fail with a "CHROOTWAIT" in a certain amount of time, someone get notified?
[04:47] <Kopfgeldjaeger> mrevell: hi! could you check my team participation @ launchpad-beta-testers? of you have got time atm... my name is nicolai spohrer! :)
[04:47] <Hobbsee> mrevell: like stdin says, i would have thought there'd be a way to monitor anything that says CHROOT PROBLEM or whatever.
[04:48] <mrevell> Kopfgeldjaeger: I'll take a look now
[04:48] <Kopfgeldjaeger> thanks
[04:48] <mrevell> cprov: Does that sound possible?
[04:50] <Hobbsee> mrevell: i'd be very surprised if htey're not monitoring the buildds currently.
[04:50] <cprov> mrevell: yes, but usually major problem result in builder deactivation, this event could generate the notification.
[04:52] <Hobbsee> cprov: presumably deactivation, ie, going to the NOT OK status?
[04:52] <cprov> Hobbsee: we do monitor the master side (slave-scanner & queue-builder)
[04:52] <cprov> Hobbsee: exactly
[04:52] <Hobbsee> cprov: master side of?
[04:53] <cprov> the buildfarm
[04:53] <Hobbsee> oh right, yes.
[04:56] <cprov> anyway, there are clearly two actions to be taking, better instrumenting & monitoring buildfarm components and establishing a reliable communication path with IS for failure/disaster coverage.
[04:57] <elmo> cprov: my mobile is in the wiki ...
[04:57] <mrevell> Kopfgeldjaeger: Done!
[04:57] <cprov> what happened during the weekend was:  notifications warns were there, but nobody (including myself) felt responsible for fixing. 
[04:57] <Hobbsee> elmo: which works, for canonical related people, i expect.
[04:58] <Kopfgeldjaeger> mrevell: thanks a bunch!
[04:58] <mrevell> Kopfgeldjaeger: np :)
[04:58] <Hobbsee> elmo: i'm assuming w.c.c, not w.u.c?
[04:58] <elmo> Hobbsee: well, AFAICS, from back scroll, Canonical people were aware of this over the weekend
[04:58] <Hobbsee> elmo: hm, true.
[04:58] <cprov> elmo: yes, i should have called, my fault
[04:59] <elmo> Hobbsee: (yes)
[05:01] <Hobbsee> elmo: i'm thinking that this is wider than ppa - it's also the ubuntu archives, too.  but i dont know of the solution
[05:02] <elmo> Hobbsee: the ubuntu archives are covered by nagios, at least in terms of machine outages etc.
[05:02] <Hobbsee> elmo: right
[05:03] <elmo> something more subtle like corruption or porn in the archives or something is harder.  the escalation process atm for , isn't great, and it will be addressed at some stage
[05:03] <elmo> ah, well, that's less my area
[05:03] <Hobbsee> wasnt thinking of that, particularly.
[05:03] <Daviey> Are we not allowed pron in our ppa's?!
[05:04] <Hobbsee> elmo: yeah, i suspected so.  i was more thinking of the general issues.  although ti would be ncie if we could do givebacks on the ubuntu archives
[05:04] <Hobbsee> which can fix things quicker :)
[05:04] <elmo> the second p is for package
[05:04] <elmo> ;-P
[05:04] <Daviey> :)
[05:05] <Hobbsee> oh damn.  i want a link here, but i'd have to google to find it - and i sure as hell dont want to do that, based on the search content :P
[05:05] <Hobbsee> elmo: ah yes, but package of what?  you didnt say it couldnt be a package of porn.
[05:05] <Daviey> Hobbsee: ssh -X firefox  :)
[05:05] <laga> hi
[05:05] <Daviey> laga: I believe you are unwelcome here
[05:06] <laga> i just created a personal bzr branch in launchpad. the URL it's given me is: bzr+ssh://laga@bazaar.launchpad.net/~laga/+junk/epgdata-grabber - so, what's that "+junk" doing in there?
[05:06] <laga> Daviey: get lost :)
[05:07] <gnomefreak> jamesh__: you made it why did you name the branch +junk (normally that is a way to abandon branches)
[05:08] <jamesh__> laga: because you didn't associate the branch with any project
[05:09] <jamesh> gnomefreak: given the question, I'd assume he created the branch through the web UI
[05:09] <gnomefreak> ah
[05:09] <laga> yes, i registered it in the web ui. 
[05:18] <Kopfgeldjaeger> i get a mail with "rejected, Could not find person '', signer has no upload rights to this ppa" after uploading a package to PPA. does it take time for the ppa manager to include my key?
[05:19] <laga> Kopfgeldjaeger: are you sure you upload to your PPA and not to the main archive?
[05:19] <Kopfgeldjaeger> dput myppa *.changes
[05:19] <Kopfgeldjaeger> and this is ftp on ppa.launchpad.net
[05:20] <laga> hum, should be correct - if the myppa entry points to your ppa in dput.cf ;)
[05:20] <Kopfgeldjaeger> fqdn  = ppa.launchpad.net; method = ftp; incoming = ~/ppa/ubuntu; login = anonymous
[05:20] <Kopfgeldjaeger> and i see dput uploading to ppa
[05:20] <gnomefreak> Kopfgeldjaeger: make sure it was source.changes not binary changes
[05:20] <Kopfgeldjaeger> its source.changes
[05:21] <Hobbsee> gnomefreak: different error message
[05:21] <laga> incoming = ~laga/ubuntu/
[05:21] <gnomefreak> Hobbsee: i thought it was the one i got
[05:21] <laga> ^ you need to specify your username AFAIK
[05:21] <Hobbsee> username is needed, i think, yeah
[05:21] <Kopfgeldjaeger> oh, ok. ill try it later, i must go... bye!
[05:21] <gnomefreak> laga: no his dput.cf is right
[05:21] <gnomefreak> mines not unless its personal
[05:22] <gnomefreak> than his Lp name would need to be in ~/ppa/userid
[05:22] <gnomefreak> not right either
[05:22] <gnomefreak> Kopfgeldjaeger: incoming = ~gnomefreak/ubuntu/
[05:22] <gnomefreak> something like that
[05:23] <gnomefreak> for personal change user name for team name if for a team
[05:40] <ubotu> New bug: #147698 in malone "A failed build in PPA isn't flagged as superseded if a new revision has been uploaded" [Undecided,New]  https://launchpad.net/bugs/147698
[05:50] <ubotu> New bug: #147711 in rosetta "RosettaApplicationView.ubuntu_languages has no 'languages' member" [Undecided,New]  https://launchpad.net/bugs/147711
[06:14] <cr3> is there a way to rename a project, not the display name but the actual project?
[06:16] <salgado> cr3, apparently only launchpad admins can do that. (hint: mthaddon is one of them ;)
[06:17] <cr3> salgado: cheers, I need to talk to him for something else at the same time
[06:17] <mthaddon> cr3, just let me know what you need renamed
[07:31] <ubotu> New bug: #147749 in launchpad "When a oops occurs inside the search popup there's no way to close the popup" [Undecided,New]  https://launchpad.net/bugs/147749
[07:45] <ubotu> New bug: #147754 in malone "searching including duplicates uses wrong status" [Undecided,New]  https://launchpad.net/bugs/147754
[07:50] <Kmos> kiko: bug 109716
[07:50] <ubotu> Launchpad bug 109716 in launchpad "Cannot join open team if there's an existing membership pending approval" [Medium,Confirmed]  https://launchpad.net/bugs/109716
[07:50] <Kmos> kiko: how about to set an milstone for it?
[07:50] <Kmos> *milsetone
[07:50] <Kmos> err.. milestone
[08:02] <lamont> cprov: any word?
[08:05] <Kopfgeldjaeger> hi
[08:07] <cprov> lamont: it is still in `pending-review` :(
[08:08] <lamont> cprov: does that mean there's someone else I should poke to get it past that point?
[08:09] <cprov> lamont: no, it's more like 'I have to poke someone'.
[08:09] <lamont> cprov: I'm happy to help expedite... :-)
[08:10] <cprov> lamont: well, you can talk to kiko anytime and enforce the *urgent* flag
[08:11] <Kopfgeldjaeger> by the way, my dput.cf was weong. i had to specify my name in "incoming"
[08:12] <lamont> kiko: do I need to get a stick? :-)
[08:56] <andrea-bs> hello
[08:58] <Kopfgeldjaeger> h andrea-bs 
[08:58] <andrea-bs> hi Kopfgeldjaeger 
[08:59] <lamont> cprov: any chance of getting 146384 some activity?
[08:59] <lamont> or any other soyuz hacker...
[08:59] <cprov> bug 146384
[08:59] <ubotu> Launchpad bug 146384 in soyuz "germinate for hppa" [Undecided,New]  https://launchpad.net/bugs/146384
[09:17] <andrea-bs> bye all
[09:30] <mdke> how often are updates pushed to edge? for example, if I see "fixed in rf 4945" does that mean I can count on seeing it in edge soon?
[09:34] <matsubara> mdke: yes, usually edge updates once a day. when someone comments "fixed in rf XXX", the next day the fix should be available
[09:34] <mdke> matsubara: great news, thanks
[09:38] <matsubara> mdke: yw
[09:38] <mdke> matsubara: I don't suppose you happen to know what time of day, do you?
[09:39] <matsubara> mdke: around 500UTC
[09:39] <mdke> magic
[09:39] <mdke> thanks again
[09:39] <kiko> lamont, cprov: what are we talking about?
[09:40] <lamont> kiko: the fix for the bug where lp doesn't populate build records for stuff sometimes
[09:40] <cprov> kiko: bug 65712
[09:40] <ubotu> Bug 65712 on http://launchpad.net/bugs/65712 is private
[09:40] <lamont> without that fix, I get to either talk the release managers into letting me upload about 200 packages in main to work around the bug, or forget hppa/gutsy
[09:41] <lamont> if we include universe, the total passes 5000ish
[09:41] <cprov> kiko: eer, SPR.getBuildByArch() problem.
[09:41] <cprov> kiko: I've produced a slightly less complicated fix for it in https://devpad.canonical.com/~jamesh/pending-reviews/cprov/launchpad/bug-65712-revenge/full-diff
[09:41] <kiko> cprov, lamont: AFAICT that's in queue for flacoste to review. has cprov spoken with him?
[09:41] <Kopfgeldjaeger> i guess it takes some time to build packages in ppa, right?
[09:42] <cprov> kiko: it doesn't require changing the entire sampledata.
[09:42] <lamont> kiko: I just poke sticks... :-)  dunno if cprov and flacoste have talked...
[09:42] <lamont> OTOH, if I'm going to make gutsy release, I need the fix in real soon now
[09:43] <kiko> cprov, huh?!
[09:43] <flacoste> kiko, lamont, cprov: i will review bug-65712-revenge today
[09:43] <lamont> flacoste: thank you
[09:43] <cprov> flacoste: great, thanks.
[09:43] <cprov> kiko: what part is 'huh ?
[09:44] <kiko> cprov, your comment makes absolutely no sense in the conversation we were happening.
[09:44] <kiko> we were having.
[09:45] <cprov> kiko: maybe you are remembering exactly what was the problem with SPR.getBuildsByArch() ?
[09:47] <cprov> kiko: where the code fix was trivial , just dealing with distroseries inheritance instead of guessing the target location based on the architecture-dependency flag, but it would require stripping out half of our broken Build sampledata.
[09:48] <kiko> cprov, ah, I think we're getting somewhere now.
[09:49] <kiko> cprov, okay so far. 
[09:50] <cprov> kiko: right, the current branch allow us to have the code fix working in both, production and our sampledata (relying on the right ordering)
[10:47] <Kopfgeldjaeger> gn8
[10:50] <ubotu> New bug: #147828 in soyuz "Sends accepted mail for feisty-backports but package is in unapproved queue" [Undecided,New]  https://launchpad.net/bugs/147828
[11:01] <mpt> Gooooooooooooooooooooooooood morning Launchpadders!
[11:01] <allee> cprov: hi, siretart asked me to ask you ;)  Any chance to confirm/reject the launchpad-beta team users?  I've applied last week and need/would like to upload fixed fai pkgs to the fai team ppa
[11:02] <allee> s/user/pending joins/
[11:03] <cprov> allee:  mrevell or SteveA are driving lp-beta-testers.
[11:04] <allee> cprov: k, thx
[11:07] <allee> SteveA: ^^^ any chance you have a look at the 'recently applied' queue in the near future?
[11:08] <kiko> allee, mrevell processes that queue daily.
[11:08] <kiko> allee, how long has it been that you have asked?
[11:09] <allee> kiko: mhmm,  last Saturday
[11:20] <kiko> allee, that's odd
[11:28] <allee> kiko: looks like there's no way to see the complete 'pending' queue.  But when I try to join (again) I see: Your membership is awaiting approval from one of this team's administrators.
[11:29] <allee> kiko: not really critical.  In this case others have to build upload bzr out of the bzr repo
[11:30] <kiko> allee, it's odd that he hasn't processed it yet. let me just get off the phone and I'll sort you out.
[11:31] <lamont> cprov: once the fix is deployed, will the build records just show up, or will you need to kick it?
[11:37] <cprov> lamont: they will magically 'show up'.
[11:38] <lamont> rock
[11:40] <ubotu> New bug: #147857 in soyuz "Add link to source page for each release on the new +source page" [Undecided,New]  https://launchpad.net/bugs/147857