| ahasenack | hi, any idea why this bug won't expire? https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/1188475 | 18:00 |
|---|---|---|
| ubot5 | Ubuntu bug 1188475 in cyrus-sasl2 (Ubuntu) "ldap group doesn't work" [Medium,Incomplete] | 18:00 |
| ahasenack | other "incomplete" bugs have a small banner saying they will expire in X days | 18:00 |
| roadmr | ahasenack: expiration is configured on a per-project basis | 18:32 |
| ahasenack | isn't it the ubuntu project in this case? | 18:33 |
| roadmr | ahasenack: ah, right | 18:38 |
| roadmr | ahasenack: but no - it's cyrus-sasl2 https://launchpad.net/ubuntu/+source/cyrus-sasl2 | 18:38 |
| roadmr | ahasenack: on a project on which I'm an admin, I can configure the bug tracker to " Expire "Incomplete" bug reports when they become inactive". Someone would have to do this for cyrus-sasl2 I guess | 18:39 |
| ahasenack | it's still an ubuntu package, I didn't know or realise each package is its own project | 18:40 |
| teward | that's not always the case | 18:41 |
| teward | Ubuntu I believe that's set, but you may want to ask #launchpad if there's issues with those settings | 18:41 |
| teward | or bdmurray who probably has godly access as the bug god. | 18:42 |
| roadmr | the scorpion king | 18:44 |
| ahasenack | I'll just mark it as invalid on my own | 18:48 |
| ahasenack | 2 months and I got no answer from the OP | 18:48 |
| bdmurray | https://help.launchpad.net/BugExpiry | 18:49 |
| ahasenack | bdmurray: https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2 does not conform to https://bugs.launchpad.net/<yourproject>/+expirable-bugs | 18:51 |
| ahasenack | what is the project, ubuntu? | 18:51 |
| bdmurray | yes, ubuntu is the project | 18:51 |
| bdmurray | there's also bug.isExpirable() in the API which you might check | 18:51 |
| bdmurray | although teward flipping it to New might have screwed things up | 18:52 |
| bdmurray | The only thing that I can see that might block it is the "Remote bug watch". | 18:52 |
| ahasenack | how can I see the ubuntu project policy on bug expiration? | 18:52 |
| ahasenack | well, I closed it now, I'll move on | 18:53 |
| ahasenack | thx | 18:53 |
| bdmurray | The expiry period is 60 days | 18:53 |
| bdmurray | In [1]: bug = lp.bugs[1188475] | 18:54 |
| bdmurray | In [2]: bug.isExpirable() | 18:54 |
| bdmurray | Out[2]: False | 18:54 |
| bdmurray | https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1664426 | 18:55 |
| ubot5 | Ubuntu bug 1664426 in gstreamer1.0 (Ubuntu) "Can no longer play wma files with Ubuntu 16.04" [Undecided,Incomplete] | 18:55 |
| bdmurray | Notice the banner "This bug report was marked for expiration 1 days ago." | 18:55 |
| bdmurray | ahasenack, teward: ^^ | 18:56 |
| ahasenack | yes, that was my original remark | 18:56 |
| ahasenack | that this cyrus-sasl2 bug didn't have that banner | 18:56 |
| ahasenack | even though it was marked as incomplete over 60 days ago | 18:56 |
| ahasenack | and had no updates | 18:56 |
| bdmurray | ahasenack: Right and I said might block it is the "remote bug watch". | 18:56 |
| bdmurray | See the "bugs that affect several projects" section of BugExpirty | 18:57 |
| ahasenack | which isn't like a task, right | 18:57 |
| ahasenack | it's something autodetected in a bug comment | 18:57 |
| bdmurray | That's correct re the remote bug watch its just a guess as to what blocked it. | 18:58 |
| ahasenack | ok, that has an interesting activity | 18:58 |
| ahasenack | https://bugs.launchpad.net/bugs/1188475/+watch/124017 | 18:58 |
| ubot5 | Ubuntu bug 1188475 in cyrus-sasl2 (Ubuntu) "ldap group doesn't work" [Medium,Invalid] | 18:58 |
| ahasenack | it updates everyday | 18:59 |
| bdmurray | In [6]: [t for t in bug.bug_watches] | 18:59 |
| bdmurray | Out[6]: [<bug_watch at https://api.launchpad.net/devel/bugs/1188475/+watch/124017>] | 18:59 |
| ahasenack | would that count as the incomplete bug receiving updates, and thus resetting the 60 days timer everyday? | 18:59 |
| ahasenack | even though the upstream bug had no changes | 18:59 |
| bdmurray | Maybe - I'm not that familiar with the LP code anymore. | 19:00 |
| ahasenack | ok | 19:00 |
| bdmurray | You could delete the bug watch and set the bug to Incomplete to see what happens. | 19:01 |
| bdmurray | Maybe doing that on staging would be best. | 19:01 |
| teward | bdmurray: that was my phone being stupid. it never had an expiry date on my page either | 19:08 |
| teward | before that either. | 19:08 |
| * teward hates his phone's touch screen being stupid | 19:09 | |
| bdmurray | hunh, I wonder if that's how bug statuses get flipped with no comment. | 19:09 |
| teward | bdmurray: well then there's people who 'experiment' with things outside sandbox | 19:12 |
| teward | that usually causes that | 19:12 |
| teward | in MY case, it was an accident - phone lagged when trying to scroll, guess what was right under my finger. | 19:13 |
| * teward subsequently rebooted his phone and it works now. | 19:13 | |
| teward | bdmurray: but what's odd is it didn't show the expiry thing. and it should've expired. | 19:13 |
| teward | i can't rule out an LP bug but... | 19:13 |
| bdmurray | I'm willing to bet money its the remote bug watch and you could test on staging if you want, remove the bug watch and use the api to see if isExpirable() is true. | 19:15 |
| === meetingology` is now known as meetingology | ||
| === PaulW2U_ is now known as PaulW2U | ||
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!