[01:02] <bac> lifeless: meeting ping
[01:03] <bac> StevenK: ^^
[01:03] <poolie> hi bac
[01:03] <bac> wallyworld: ^^
[01:03] <bac> morning poolie
[01:03] <wallyworld> ack
[01:03] <bac> wallyworld: you,of course don't have to come, but you're welcome
[07:02] <tgm4883> Is there some setting that will make it so only members of our bug team can change the status on bugs?
[07:08] <wgrant> tgm4883: Certain statuses are restricted (Won't Fix, Triaged and Opinion are the current ones, IIRC), but it's not configurable at the moment.
[07:09] <tgm4883> hmm
[07:09] <tgm4883> thats no deal
[07:09] <tgm4883> I'm not a fan of users changing status of a bug all willy nilly
[07:10] <wgrant> It's rare that a user does.
[07:12] <tgm4883> yea it is
[07:13] <tgm4883> mostly I see it when a user takes it from incomplete back to new
[07:13] <tgm4883> which is not what we want. It isn't new anymore if a dev is working on it
[07:13] <wgrant> Why would it be Incomplete if a dev is on it?
[07:14] <wgrant> Incomplete means it's waiting on info from the user.
[07:14] <tgm4883> in a lot of smaller projects. Bug team and dev team overlap
[07:14] <tgm4883> in either case, it isn't new
[07:15] <tgm4883> and the bug team (or dev in some cases) should be the one to decide if it isn't Incomplete anymore, not the user
[07:16] <tgm4883> I've also seen it go from "Fix released" to new/confirmed before
[07:16] <tgm4883> from a user
[07:17] <tgm4883> which again, IMO is bad
[07:18] <wgrant> There is a discussion going on about preventing users from unfixing bugs.
[07:18] <wgrant> But I find it's more effective to just chastise users when they do that. They only do it once!
[07:19] <tgm4883> well I wouldn't say it's more effective
[07:19] <tgm4883> it may be effective, but it's still annoying.
[07:19] <tgm4883> but if thats the only way, then I guess we will make it work
[07:19] <tgm4883> thanks for the info wgrant
[07:19] <wgrant> It's also annoying when users are prevented from performing legitimate actions.
[07:19] <wgrant> It's a bit of an imperfect balancing act.
[07:20] <tgm4883> perhaps
[07:20] <tgm4883> ideally it would be configurable at the project level
[07:20] <tgm4883> but I don't think for most cases those would be considered legitimate actions for the user
[07:21] <tgm4883> if the user wants to set status and priority, it sounds like they are fixing the bug themselves and have commit access
[07:21] <wgrant> One can fix bugs without commit access.
[07:22] <tgm4883> wgrant, true, but they can't commit it :)
[07:22] <tgm4883> who is to say the project would A) accept the patch, or B) decide the bug was worth fixing
[07:23] <spiv> I think many projects are comfortable with "wiki-like" access to those fields: so long as bad changes are easy to revert, there's little harm in allowing broad access.
[07:23] <spiv> And some benefit.
[07:23] <tgm4883> spiv, I agree. Which is why I asked if it was configurable
[07:24] <spiv> *nod*
[07:25] <tgm4883> anyway, we will do what we can with the way it is. Thanks for the info. Night
[07:25] <spiv> G'night.
[07:42] <bac> spiv i'll be happy to land your branch
[07:43] <spiv> bac: thanks!
[07:43] <bac> np
[08:30] <fta> danilos, hi, please let me know when i can update my translations
[09:14] <noodles775> mrevell: ^^ that's correct right?
[09:15] <mrevell> noodles775: I've just checked and it appears LP is offline, rather than read-only, atm. It's due to be back online around now. mthaddon are you too busy doing it to confirm?
[09:15] <mthaddon> mrevell: should be back now?
[09:15] <mrevell> Yep, thanks mthaddon.
[09:16] <mrevell> Thanks noodles775
[09:16] <noodles775> mrevell, mthaddon : I still can't push to codehosting.
[09:16] <mthaddon> yeah, working on it
[09:16] <mthaddon> hmm, service check says it's up
[09:18] <mthaddon> noodles775: still can't push?
[09:18] <noodles775> mthaddon: nope, bzr: ERROR: Connection closed: Unexpected end of message. Please check connectivity and permissions, and report a bug if problems persist.
[09:25] <savvas0> is launchpad code down? OOPS-ID OOPS-1741CB386
[09:26] <savvas0> neither bzr pull nor http://bazaar.launchpad.net/~surl/surl/trunk/files work
[09:26] <noodles775> savvas0: yes, the admins are working te get codehosting back up now (see topic)
[09:26] <savvas0> oh, oops :)
[09:26] <savvas0> thank you
[09:34] <eLBati> ciao
[09:40] <mthaddon> noodles775: can you confirm codehosting is now back?
[09:41] <noodles775> mthaddon: indeed, pushing happily now. Thanks!
[09:41] <mthaddon> sorry for the delay
[09:44] <eLBati> ant problem with bzr?
[09:44] <eLBati> *any
[09:45] <noodles775> eLBati: there was up until a few minutes ago, but codehosting should be back now?
[09:50] <eLBati> noodles775, uhm http://pastebin.com/Ww3VSjVk
[09:53] <noodles775> mthaddon: ^^ (also, I got the following trying to test a branch on ec2 https://pastebin.canonical.com/38292/ )
[09:53] <spiv> eLBati: works for me
[09:54] <mthaddon> noodles775: that looks like problem with your ec2 instance
[09:54] <spiv> eLBati: I notice you didn't specify a username on that command line
[09:55] <spiv> eLBati: have you set your .ssh/config to use your Launchpad nick when connecting to bazaar.launchpad.net?  Or does you local username match your Launchpad nick?
[09:56] <eLBati> spiv, my local username matches lp-login
[09:56] <eLBati> my public key worked till one hour ago
[09:57] <spiv> eLBati: what's your lp username?
[09:57] <eLBati> elbati
[09:59] <spiv> Hmm, your debug log's does mention the same key you have on your account...
[09:59] <spiv> But it also has this line:
[09:59] <spiv> #
[09:59] <spiv> Agent admitted failure to sign using the key.
[09:59] <spiv> Which I don't see when I connect; perhaps there's an issue with your local ssh-agent?
[10:00] <spiv> Otherwise I'm out of ideas, given that your username and key apparently match.
[10:00] <spiv> (And that the service is working fine for me)
[10:02] <eLBati> spiv,  I guess more probably an issue with  bzr service since it did not work little time ago
[10:03] <eLBati> did lp change something?
[10:03] <spiv> eLBati: I agree that's suspicious
[10:03] <spiv> But it was pretty mundane DB maintenance AFAIK
[10:03] <spiv> I'd certainly be surprised if it changed how codehosting auth worked.
[10:04] <spiv> (Which DB-wise is very simple: there's a SSHKey table, basically)
[10:04] <maxb_> In my experience "Agent admitted failure to sign using the key." either means 'gnome-keyring-daemon sucks, you should use ssh-agent instead' or 'Your agent was set up to require interactive confirmation of key usage, and that didn't/couldn't happen'
[10:05] <spiv> And the codehosting service just queries that, and clearly it still can because I can still auth to it, and noodles775 said a short while ago that it's working for him too.
[10:05] <eLBati> maxb_, you could be right
[10:05] <spiv> And the error about the agent is highly suggestive of a local issue.
[10:05] <spiv> Also, there aren't hordes of people in here complaining that codehosting is still down :)
[10:06] <eLBati> spiv, you re right too :-)
[10:17] <eLBati> somehow, my gnome-keyring-daemon slept
[10:17] <eLBati> after first fail due to lp issue
[10:18] <eLBati> thanks spiv maxb
[10:18] <eLBati> now it works
[10:18] <spiv> eLBati: you're welcome
[10:39] <fta> danilos, (re) hi, please let me know when/if i can update my chromium translations
[10:41] <danilos> fta, right, you can do that now: just doing "one time import" from the sync settings page should be sufficient now
[10:41] <danilos> anyway, brb
[11:36] <fta> danilos, i wonder if i should split my notes in two. i put various info in there, but only one part is useful to the translators, the other part is mostly useful for me to convert back to the original xml format
[11:40] <fta> seems the lp auth is somehow broken with chromium. it keeps saying i must login to edit a bug, i do, accept the form and back in the bug, i'm still signed-off, if it retry, it works, but only for a while
[12:14] <fta> uh?? where's the post comment button??? http://people.ubuntu.com/~fta/lp-no-post-comment-button.png
[12:20] <wgrant> fta: Hm, all the icons seem to be missing too.
[12:21] <fta> wgrant, chromium daily
[12:23] <fta> hm, a restart worked. weird
[15:58] <bsaibes> I am looking at whether Launchpad provides any resource load-balancing, estimating, etc... I am trying to figure out how  to check whether a particular developer is assigned too much work to handle, can Launchpad help in that area (I am thinking Blueprint mostly)
[16:29] <salgado> bsaibes, I don't think so, but you could check the list of bugs/blueprints that are inprogress for any given user through the "All assigned blueprints" and "All bugs in progress" links on their profile page
[16:31] <bsaibes> Ok - that is a start, I can check there - would I have access to check others' profile?
[16:31] <salgado> yeah, definitely!
[16:31] <salgado> bsaibes, https://edge.launchpad.net/~james-w for instance
[16:32] <bsaibes> now related question - does blue print allow me to assign sizing to a Work Item?
[16:33] <salgado> bsaibes, that's not really a Launchpad question as it has no idea about work items -- we just abuse the blueprints' whiteboard to list the work items which are them parsed by an external tool
[16:34] <salgado> bsaibes, that was just to say that if we extend that external tool, we can then include the sizing info along with the work items
[16:35] <salgado> but that's a question for Jamie Bennett. :)
[16:35] <bsaibes> yes that need to be looked at then see whether we  can abuse  the Whiteboard further
[16:35] <james_w> bsaibes, https://blueprints.edge.launchpad.net/~linaro-toolchain-wg/+specworkload
[16:36] <bsaibes> James_w, thx this link looks promising, let me check it out
[16:36] <james_w> that's a start, but the work item tracker is probably better for that, and it doesn't show bugs
[16:36] <salgado> james_w, wow, that's new to me.  quite interesting
[16:37] <james_w> (view any person team, go to blueprints and select "Workload" on the right)
[16:38] <bsaibes> james_w, I am working with Michael H. to address this issue, Michael has created this list for the Toolchain team now we need the sizing and check how to load balance the assignment
[16:40] <bsaibes> Salagado, so maybe we need to expand on the Work Item convention in the whiteboard to add a sizing to each Work Item, then creare a tool to check the load for each developer
[16:41] <james_w> I believe that's already in progress
[16:42] <bsaibes> James_w, who is handling this?
[16:42] <james_w> I don't know the status though, talk to JamieBennett
[16:43] <bsaibes> James_w, ok will do there a release meeting in few minutes, will ask there
[19:19] <tcole> therve: hi, so one question I have is where the appropriate place in an app lifecycle is to install a storm tracer
[19:19] <tcole> er, wrong window
[21:13] <michaelh1> mwhudson: syn...
[21:13] <mwhudson> michaelh1: hello
[21:14] <michaelh1> mwhudson: right, so he was ~rsandiford.
[21:14] <michaelh1> Hang on, this is too long to type.. Skype/Mumble?
[21:14] <mwhudson> michaelh1: in a few minutes?  i'm in a cafe, but won't be for much longer
[21:15] <michaelh1> mwhudson: there's no rush.  Any time today is fine.  Ping me when you're available
[21:15] <mwhudson> michaelh1: okidoke
[21:48] <mwhudson> uh
[21:48] <mwhudson> login.launchpad.net does not seem very happy?
[21:49] <mwhudson> oh, it was probably the login for prod, log in for edge problem
[22:21] <ilap> Hi, I deleted a package in my PPA because the build was not successful (some issue in the control file). After that I was trying to upload the modified package to PPA but it's always rejected /w the following err msg: "but uploaded version has different contents". So, why I can not upload a packeg to a PPA if that package is already deleted from that PPA? Is there any way to get it work or I need to create a new PPA and upload that 
[22:21] <mwhudson> ilap: yes, change the version
[22:22] <jonrafkind> something I dont get about that, if a package fails to build then its taking up space in launchpad, right? why doesnt the option exist to completely erase a version that didnt build at all?
[22:23] <ilap> Ta, I was thinking of this, but I did not want it as what if an other dependency issue appears?
[22:24] <ilap> So, there is no any way to completely erase a PPA and package.
[22:24] <mwhudson> that's just debian for you, really
[22:24] <ilap> and -> and/or
[22:24] <mwhudson> ilap: then you upload again
[22:24] <micahg> ilap: append a ~ppa1 to the end of the version string
[22:25] <mwhudson> ilap: in a package version in debian, in a version number like 1.2-4, the '4' is (at least by strong convention) an indication of the version of the packaging
[22:28] <ilap> Thx, but I did not want to change the version in my package due a Build-dependencies issue. So, that's why I thought (was I naive?:)) the delete it and reupload the modified one should be sufficient. Coz, I am not sure that all of the Build depencies are sorted in the control file.
[22:29] <mwhudson> well that's ok
[22:29] <mwhudson> it's not like you get bragging rights for having a particular version number
[22:41] <ilap> Ok, I see. Ta all.
[22:57] <ilap> As I am a really newbie here in launchpad therefore what do you recommend? Version nr is 0.0.1-0ubuntu1, so shall I modify to this? 0.0.1~1-0ubuntu1?
[22:59] <mwhudson> ilap: i go with  0.0.1-0ubuntu2~ppa1
[22:59] <ilap> ta
[23:00] <mwhudson> ilap: this will sort after  0.0.1-0ubuntu1, but before 0.0.1-0ubuntu2, and the latter is the smallest a new version that's uploaded to ubuntu would have
[23:01] <mwhudson> (i think, not really an expert on this)
[23:03] <ilap> mwhudson: not, no expert, I have no clue on this and also this is my 1st pkg in launchpad..:) Thx your help.
[23:08] <tgm4883> ilap, you want to ask in #ubuntu-packaging