[00:46] <bjf> lifeless, tgardner is having the exact same problem
[00:48] <wgrant> bjf: Is there a public bug that you know to have a similar issue?
[00:48] <bjf> wgrant, this was the best example, right now i don't have one that I can point to
[00:49] <wgrant> OK. Just makes it a bit harder to debug if we can't see it :/
[00:50] <wgrant> lifeless: Do we know that someone else in the team didn't mute it?
[00:50] <lifeless> no
[00:51] <lifeless> however the team is never the actor
[00:51] <bjf> wgrant, i can subscribe you if that would help
[00:51] <lifeless> wgrant: they don't have mute available yet
[00:51] <wgrant> bjf: That would probably be helpful.
[00:51] <wgrant> lifeless: You can mute team subscriptions if you're in ~malone-alpha.
[00:52] <lifeless> wgrant: https://launchpad.net/~malone-alpha/+members#active
[00:52] <wgrant> Hmm, OK.
[00:52] <lifeless> wgrant: if you're going to look into this, thats great, I'll switch to a different issue
[00:52] <lifeless> wgrant: [I would love it if you do that]
[00:52] <wgrant> lifeless: I plan to.
[00:53] <wgrant> And/or am.
[00:53] <bjf> wgrant, i think i subscribed you
[00:53] <lifeless> ok, handoff done.
[00:53] <bjf> wgrant, I subscribed some "wgrant"
[00:55] <bjf> wgrant, can you see the bug now ?
[00:55] <wgrant> bjf: Hmm, no.
[00:55] <wgrant> I am 'wgrant'
[00:56] <bjf> wgrant, yes, and I subscribed "wgrant"
[00:57] <wgrant> To bug #759176?
[00:57] <bjf> yes
[00:57] <wgrant> Really...
[00:57] <wgrant> I still cannot see it.
[01:00] <bjf> wgrant, when i choose "subscribe someone else" and put wgrant in the edit box and hit search i am presented with: "William Grant", "Bill" "grantcentral", and "wgrant <email address hidden>". I chose "wgrant <email address hidden>"
[01:01] <wgrant> Ah, that's billgrant-central.
[01:01] <wgrant> My username is wgrant, display name is 'William Grant'. billgrant-central looks like a ShipIt-only person.
[01:02] <wgrant> (this UI is absolutely awful)
[01:02] <bjf> well, that's kind of difficult to figure out
[01:02] <bjf> so I should subscribe "billgrant-central" ?
[01:02] <wgrant> No, you *did* subscribe billgrant-central.
[01:02] <wgrant> I am 'William Grant' in that list you gave.
[01:03] <wgrant> https://launchpad.net/~wgrant is me, but that is not the 'wgrant' in the list you gave.
[01:03] <wgrant> That 'wgrant' is https://launchpad.net/~billgrant-central
[01:03] <bjf> so that is "William Grant me@williamgrant.id.au" ?
[01:03] <wgrant> That's the one.
[01:04] <wgrant> My Canonical address is not primary because I have heaps of filters that I really don't want to port over to procmail.
[01:04] <bjf> subscribed, now we have to somehow remove "wgrant"
[01:05] <wgrant> spm may already be on that :)
[01:05] <wgrant> Hi spm.
[01:05] <spm> yo.
[01:12] <bjf> spm, we need to get "wgrant" unsubscribed from bug 759176
[01:15] <wgrant> bjf: What do you see at https://bugs.launchpad.net/dell/+bug/759176/+subscriptions?
[01:16] <spm> bjf: removed
[01:16] <wgrant> Possibly nothing.
[01:16] <wgrant> Thanks spm.
[01:17] <bjf> wgrant, correct, nothing
[01:18] <bjf> wgrant, however, i see the same thing for https://bugs.launchpad.net/apport/+bug/765178/+subscriptions which i _am_ subscribed to
[01:19] <wgrant> bjf: Yes. The page only works for alpha testers at the moment :(
[01:19] <bjf> wgrant, heh, ok
[01:20] <bjf> wgrant, if it would help in some way for me to be an alpha or other tester, just let me know
[01:56] <wgrant> bjf: I've tracked down the issue. canonical-kernel-team has an unvalidated email address but no validated ones, which breaks a corner case in code that was added the day of the last email.
[01:56] <wgrant> bjf: We should probably remove the unvalidated email address, since they don't do anything (... well, apart from breaking this)
[02:00] <bjf> wgrant, that's great that you found it
[03:07] <bjf> wgrant, did you remove the unvalidated email address or is that something I need to do ?
[03:09] <wgrant> bjf: I could probably convince a LOSA to do it, but probably better for a team admin to do it.
[03:10] <wgrant> Hmm.
[03:10] <wgrant> I hope there's UI to do that.
[03:10] <wgrant> https://launchpad.net/~canonical-kernel-team/+contactaddress might be helpful.
[03:16] <bjf> wgrant, i don't have permission to access that page
[03:20] <wgrant> bjf: Right, that page is only accessible by admins. But it seems we'll need SQL to remove the unvalidated address.
[03:20] <bjf> wgrant, you have someone in mind to perform that surgery ?
[03:24] <wgrant> bjf: I believe we have a candidate victim, yes.
[03:24] <bjf> wgrant, cool :-)
[03:35] <lifeless> bjf: we're going to not mangle the db; the code fix will be ready to go live in ~ 7 hours, so within 24 is a solid bet for having it fixed.
[03:50] <bjf> lifeless, hmmm, i guess i have no choice but to wait, it _is_ good to know that you know what the problem is and have a fix, hopefully i will have an inbox full of bug mail when I get up tomorrow
[03:59] <lifeless> bjf: theres risk everytime we do manual SQL on the db
[04:00] <lifeless> bjf: we reserve it for zomg style issues, which I don't think this is (because its affecting a limited group of folk, and we'll have a fix shortly.)
[04:00] <bjf> lifeless, i can understand that, and the want to be conservative
[04:01] <bjf> lifeless, however, it does feel like this is something that should be "fixed" for this team, but if it's safer to leave it for now, then that's probably the right answer
[04:03] <lifeless> bjf: we have caused entire site-wide outages doing 'safe' sql in the past.
[04:03] <lifeless> bjf: its a Big Deal to do sql.
[04:04] <bjf> lifeless, like i said, safe is probably best
[04:04] <lifeless> bjf: by analogy, if I had a fix to my wifi driver dropping off on N networks a lot, you'd still go through your normal QA process etc before shipping the deb in the archive ;)
[04:08] <lifeless> bjf: its a shame that theres no ability for you to run a custom variant till we have the main code deployed, but web services are like that :(
[05:24] <bjf> lifeless, you assume we have a qa process :-)
[05:26] <lifeless> I'm sure you do ;)
[05:26] <wgrant> Yes, it makes our PPA queues huge :)
[05:27] <bjf> you'd be surprised, if you are going to uds, i'll buy you a beer and tell you about it, have a good day, i'm going to get some shut eye
[05:27] <wgrant> Night. Thanks for letting us know about the bugmail issue. It may well be fixed by tomorrow.
[05:35] <marvin2> Hi, could someone tell me how to create a private branch on launchpad? We've paid for it and applied the code to a project, but can't restrict the visibility of any branches we create.
[05:36] <lifeless> that needs a policy setup for you, which our sysadmins can do
[05:36] <lifeless> spm: yo
[05:36] <spm> yo
[05:36] <spm> ahh I see
[05:36] <marvin2> lifeless: Do we need to mail someone to get that done?
[05:36] <spm> marvin2: if you could PM me the project name?
[05:37] <marvin2> spm, just one second.
[05:38] <marvin2> spm, it's willow-code.
[05:38] <spm> ta. gimme a sec....
[05:40] <spm> marvin2: I've set it so that members of https://launchpad.net/~willowit-team have access, see how that goes?
[05:40] <marvin2> spm: Perfect!
[05:42] <spm> marvin2: I'd advise to a trial push of a dummy branch first. make sure that goes up and is private, so you don't have any accidental leaks.
[05:42] <marvin2> spm: Yeah, gonna try that now.
[05:42] <spm> paranoid is, as paranoid does. ;-)
[05:44] <marvin2> spm: :)
[07:10] <marvin2> spm: Thanks for that, it worked. I pushed a branch under that project, but Launchpad says I'm the only one that can upload files to it. How can I authorise other people to push their changes to the branch hosted on Launchpad?
[07:10] <spm> marvin2: hrm. let me have a look...
[07:11] <wgrant> marvin2: How did you push it?
[07:11] <wgrant> marvin2: The owner of the branch can write to it.
[07:11] <wgrant> So bzr push lp:~TEAM/PROJECT/SOMENAME will let anyone in ~TEAM push to it.
[07:14] <marvin2> wgrant: OK. I'd like to just take the version already on launchpad at lp:~USER/.... and move it to lp:~TEAM/...
[07:15] <marvin2> Is it possible?
[07:15] <wgrant> marvin2: Sure. Click on 'Change details' on the branch page.
[07:15] <wgrant> marvin2: You'll see a team selector up te top.
[07:15] <marvin2> wgrant: Cool, I'll try that.
[07:48] <marvin2> wgrant: Thanks, that worked.
[07:49] <wgrant> marvin2: Great.
[10:37] <poolie> jam i really like your +inprogress idea
[10:37] <poolie> i wish those views were a bit more opinionated about how you probably want to use them, in choosing their defaults-
[10:38] <poolie> historically bugs like that have not had a high chance of being fixed
[10:39] <lifeless> still don't :)
[10:39] <lifeless> I nearly duped it on 'make columns configurable'
[10:40] <poolie> it would be neat if lp's dupefinder was extended to predict the chance the bug will ever be fixed
[10:40] <poolie> a smart enough keyword matcher could probably say "don't even bother" before you finish typing
[10:40] <poolie> :)
[11:23] <tsimpson> general question, is there a timeline for when the +text bug interface is going away?
[11:26] <fta> wgrant, hi, did you have time to investigate the ppa-stats issue since last time we discussed it?
[13:33] <web_knows> rai
[14:31] <hrw> hi
[14:32] <hrw> is it 'normal' that each bug query which uses tags == OOPS?
[14:32] <hrw> https://bugs.launchpad.net/ubuntu/+bugs?field.tag=ftbfs+natty+multiarch&field.tags_combinator=ALL (Error ID: OOPS-1936CC361)
[14:34] <bigjools> adeuring: ^
[14:34] <bigjools> his analysis is wrong but still ...
[14:34] <henninge> adeuring: do you know anthing about the +text bug interface?
[14:35] <adeuring> henninge: no
[14:35] <hrw> in previous days it was oopsing too but gave answers usually on 2-3rd reload
[14:35] <adeuring> hrw: seems that our new timeout settings is too strict...
[14:36] <henninge> tsimpson: sorry for missing your questions earlier.
[14:36] <hrw> adeuring: https://bugs.launchpad.net/ubuntu/+bugs?field.searchtext=&orderby=-datecreated&search=Search&field.status%3Alist=NEW&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.status%3Alist=FIXCOMMITTED&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_supervisor=&field.bug_commenter=&field.subscriber=&field.comp
[14:36] <henninge> tsimpson: why do you think it is going away?
[14:36] <tsimpson> henninge: because I know the LP devs hate it :)
[14:37] <henninge> tsimpson: ;)
[14:37] <henninge> tsimpson: I only found out about it just now. Can you be more specific about a hater? ;)
[14:37] <hrw> adeuring: does LP do 'lets do DB query and if it not give results in <XYZ ms then raise timeout'?
[14:37] <henninge> tsimpson: IOW I don't know anything about such plans.
[14:38] <tsimpson> henninge: well we use it in ubottu and the like, and we have internally deprecated support for +text in the bug tracker plugin, but we don't have any time-line for removing the code
[14:39] <tsimpson> so I was mostly just curious if the devs had any concrete plans or not
[14:39] <henninge> tsimpson: I guess you switched to the rest api?
[14:39] <tsimpson> yeah, we just use launchpadlib and fallback to +text if it's not installed
[14:44] <henninge> tsimpson: Are you on the launchpad-dev mailing list?
[14:45] <tsimpson> henninge: not currently
[14:45] <abentley> adeuring: with deryck away, I guess I'll take his help contact rotation.
[14:45] <tsimpson> but I can subscribe easily enough
[14:46] <henninge> tsimpson: yeah, I think it would be a good place to kick of a discussion about defining a time line for this.
[14:46] <henninge> tsimpson: please do that ;)
[14:46] <tsimpson> ok :)
[14:48] <hrw> adeuring: is there a bug for LP timeout issue where I can leave some complains and example queries?
[14:51] <adeuring> hrw: yes
[14:51] <adeuring> hrw: yorry, the yes was for your previous question; let me check if we already have a bug about this specific timout
[14:54] <hrw> adeuring: would be useful to add "if query.contains(tag) then timeout=10*timeout" kind of change
[14:55] <adeuring> yeah...
[14:55] <hrw> as I understand timeout change for simple queries like 'show me bugs in package X' but more complex ones takes more time by default
[14:57] <adeuring> hrw: right, but we don't have anything like that in place right now. Anyway, did you try a search on https://bugs.launchpad.net/ubuntu/natty
[14:58] <adeuring> (that would make the tag "natty" obsolete
[14:58] <adeuring> ...in theory
[14:59] <adeuring> hrw: bzg 757426
[14:59] <adeuring> ...bug 757426
[15:01] <hrw> thx
[15:09] <davidgiluk> I'm getting repeated timeout/oops's on a tag search I commonly use    https://bugs.launchpad.net/ubuntu/+bugs?field.tag=arm-porting-queue  giving OOPS-1936EC403
[15:21] <davidgiluk> any LP engineers around to give it a bit of a kick?
[15:46] <bjf> is there a guestimate when the fix for bug 766561 will go live (it's being QA'd now) ?
[15:46] <bjf> this is really impacting the kernel team
[15:49] <jcsackett> bjf: i'm checking our deployment queue now.
[15:49] <jcsackett> it's been qa'ed okay, so if there's nothing ahead of it in the queue that is broken, it should go out on the next deploy.
[15:49] <bjf> jcsackett, and that would be when ?
[15:50] <jcsackett> bjf: that, i'm not entirely sure of.
[15:50] <jcsackett> bjf: two things ahead of it, one is being qa'ed now. i'm looking into the other one.
[16:01] <fta> bug 767258
[16:02] <bjf> jcsackett, is there anyone that could tell me when it will deploy ?
[16:56] <jcsackett> bjf: it's dependent on when things get qa'ed. there's one thing still in the queue, and as i understand it, it's complicated.
[16:56] <jcsackett> historically though, we seem to do at least one deployment a day.
[17:03] <benji> cool, thanks
[17:03] <benji> oops
[18:12] <joshuahoover> adeuring: ping
[18:12] <adeuring> joshuahoover: yes?
[18:13] <joshuahoover> adeuring: do you know how i can get "answers" removed from a project site? i tried configuring to "not applicable" but the link still shows: https://launchpad.net/ubuntuone-servers
[18:14] <joshuahoover> adeuring: i set the "Configure support tracker" to not applicable, but somehow we still got a question
[18:14] <joshuahoover> adeuring: https://answers.launchpad.net/ubuntuone-servers/+question/153458
[18:15] <joshuahoover> adeuring: i was surprised to see a question still got through even though the project is not setup for answers :)
[18:15] <adeuring> joshuahoover: yeah, I undrstand, but let me check a bit...
[18:15] <joshuahoover> adeuring: k, thanks!
[18:18] <adeuring> joshuahoover: You can simply append "/+addquestion" to the main answers URL  (https://answers.launchpad.net/ubuntuone-servers) and then you can submit your question...
[18:18] <adeuring> Looks like a bug
[18:18] <joshuahoover> adeuring: ah, ok
[18:21] <adeuring> abentley-lunch: can you take the role of the help contact?
[18:35] <ovnicraft> hello i am in bugs page
[18:35] <ovnicraft> i reported one
[18:35] <ovnicraft> and want to report another one
[18:36] <ovnicraft> so i need back
[18:36] <ovnicraft>  to bugs
[18:36] <ovnicraft> click on report a bug
[18:36] <ovnicraft> how can i from reported bug page report another bug ?
[19:22] <charlie-tca> ovnicraft: if it is a bug in the same package, scroll down to the bottom of the page:  Report another bug in ???
[20:39] <spinny> Hello folks. Is there a way for users to query changes/updates in PPAs automatically such a via RSS?
[20:46] <DNS__> hi guys :)
[20:47] <DNS__> am i able to compile/make deb packages for debian squeeze too at lp?
[20:47] <DNS__> if so, idk how
[20:50] <joey> abentley: help :-)
[20:51] <abentley> joey: What can I do for you?
[20:51] <joey> hi abentley
[20:51] <joey> I'm on https://blueprints.launchpad.net/sprints/uds-o/+addspec
[20:51] <joey> and under "For:" where you add in the project/product name,  if I select the chooser it doesn't put back in my chosen result
[20:51] <joey> so.. search for "linaro-project", click on the result, and nothing
[20:52] <abentley> joey: It's as if you didn't invoke the chooser at all?
[20:52] <joey> abentley: correct
[20:52] <joey> blank field
[20:52] <abentley> joey: I saw that a few minutes ago with a Person picker.
[20:53] <joey> yeah same base code as I recall...although it's been a few years :-)
[20:53] <DNS__> so, i guess im not able to compile packages for squeeze or?
[20:53] <abentley> joey: So I think this may be a launchpad-wide issue.
[20:53] <DNS__> (on launchapd)
[20:54] <joey> abentley: yeah and it's affecting Linaro and others I'm sure
[20:54] <joey> abentley: the good news is ubuntu should be unaffected
[20:54] <joey> abentley: they use "ubuntu" in that field
[20:54] <abentley> DNS__: Not deliberately ignoring you, but since you didn't use my handle, it didn't attract my attentionl.
[20:54] <DNS__> np :)
[20:55] <abentley> DNS__: But you're right, we only support creating packages for Ubuntu distributions via our packaging system and build farm.
[20:56] <abentley> joey: you can work around this by putting in the actual project name manually, right?
[20:56] <DNS__> ok i was just wondering because i found debian debian/squeeze and debian/lenny on launchpad, and i thought maybe...
[20:56] <DNS__> :D
[20:56] <DNS__> thx for info
[20:56] <joey> abentley: assume so. doing it now.
[20:57] <joey> abentley: yes I can. https://blueprints.launchpad.net/linaro-project-management/+spec/linaro-other-project-management-enhancements
[20:58] <joey> oops wrong naming
[20:58] <abentley> joey: I'm going to try to assess the scope of the problem.
[20:58] <joey> https://blueprints.launchpad.net/linaro-project-management/+spec/linaro-other-o-project-management-enhancements
[20:59] <joey> abentley: thanks. I have track leads in Linaro trying to do this and it impacts them
[21:02] <abentley> joey: Okay, it's not site-wide.  For example, assigning a person to a bug and assigning a branch to a productseries are working.
[21:16] <ovnicraft> charlie-tca, LP help with UI
[22:41] <jaypipes> are any LP admins around?
[22:44] <lifeless> jaypipes: whats up ?
[22:45] <jaypipes> lifeless: hi Robert, thx. was hoping someone could change a project name... https://launchpad.net/openstack-dbaas to https://launchpad.net/reddwarf. I was setting it up for another team and goofed the project name they wanted.
[22:46] <jaypipes> lifeless: I changed everything except the project identifier..
[22:46] <lifeless> you can do that yourself can't you ?
[22:46] <lifeless> anyhow, done.
[22:47] <jaypipes> lifeless: no, only the display name...
[22:47] <jaypipes> lifeless: tyvm sir!
[22:47] <lifeless> de nada
[22:49] <doko> lifeless: you did send some traces for the search of <tag1> AND <tag2> reports
[22:49] <doko> is there some work ongoing?
[22:49] <lifeless> doko: its in the pile of criticals
[22:49] <doko> ok, thanks!
[22:49] <lifeless> the search is triggering a very slow query path
[22:49] <lifeless> I'm not sure quite what we need to do
[22:50] <lifeless> we may need to use arrays or whatnot
[22:50] <doko> any workaround I could use in the mean time?
[22:50] <lifeless> if we need a schema change, this will have to wait to be fixed for the downtime deploy in may
[22:50] <lifeless> doko: I'll have a look at adding a timeout exception for the page
[22:51] <lifeless> there are some risks doing that
[22:51] <lifeless> doko: it may work if you refresh a few times, part of the slowness is hitting the 500K row bugtag table which can be out of cache
[22:51] <doko> thanks, if it's worth filing reports with a "combined" tag, I'll do that too
[22:53] <lifeless> so the interesting thing about your query is that the tags you are searching on a reasonably common (some of them)
[22:53] <lifeless> but the intersection is empty
[22:54] <lifeless> so no bugs should be found
[22:54] <lifeless> empty/near empty
[22:55] <doko> hmm, but nor for things like ftbfs+natty or ftbfs+oneiric
[22:55] <lifeless> those I would expect to have matches, yes.
[22:55] <lifeless> btw
[22:55] <lifeless> why are they tagged natty
[22:55] <lifeless> rather than being on the natty series ?
[22:56] <doko> the bug filing tool lacked support filing reports for a series ;-P
[22:56] <lifeless> our search schema can handle many more bugs on a series than bugs with a tag
[22:56] <doko> so if you want to target these to a series, please do
[22:59] <lifeless> probably best to do that with an api script
[23:00] <lifeless> anyhowm I'll see if I can get something going for you today
[23:00] <lifeless> we're just dealing with a small crisis right now
[23:00] <lifeless> so it will be later today
[23:01] <doko> thanks
[23:12] <bjf> lifeless, the bug email is starting to roll in, many thanks
[23:13] <lifeless> excellent