[17:07] <Rosco2> Bug 364238 Bug 568239 Bug 778208 Bug 812279 Bug 830831
[17:07] <ubot5> bug 364238 in Ubuntu "If initially turned off, blueman-applet doesn't turn back on properly and doesn't connect to Headset service after X restart." [Undecided,New] https://launchpad.net/bugs/364238
[17:07] <ubot5> bug 568239 in Furius ISO Mount "Table 'Mounted images' is not scrollable: problems when path is long" [Undecided,Confirmed] https://launchpad.net/bugs/568239
[17:07] <ubot5> bug 778208 in Ubuntu "Fetch news from Readers Digest" [Undecided,New] https://launchpad.net/bugs/778208
[17:07] <ubot5> bug 812279 in Ubuntu "twistd scripts don't work when installed" [Undecided,New] https://launchpad.net/bugs/812279
[17:07] <ubot5> bug 830831 in SchoolTool "Asian characters don't render in PDF reports" [High,Triaged] https://launchpad.net/bugs/830831
[17:07] <Rosco2> These all have Ubuntu tasks that could be deleted
[17:10] <teward> Rosco2: justification?
[17:10] <Rosco2> They all have other tasks that have a resolution
[17:11] <Rosco2> I think a relevant project was added
[17:11] <Rosco2> instead of changing Ubuntu to the other project
[17:12] <Rosco2> They come up in list of bugs with unassigned packages
[17:13] <Rosco2> https://bugs.launchpad.net/ubuntu/+bugs?field.status%3Alist=NEW&field.importance%3Alist=UNDECIDED&assignee_option=none&field.has_no_package=on
[17:13] <teward> okay, well, i have a question then - if this bug i'm linking were assigned to just Ubuntu and no package, but then was assigned to just the NGINX project, what would you do?  https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1403283
[17:13] <ubot5> Launchpad bug 1403283 in Nginx "[Security] BREACH vulnerability is not mitigated in default configuration" [Medium,Confirmed]
[17:13] <teward> now, note, I already know the answer
[17:14] <teward> considering it's my bug and I'm kinda the unofficial nginx triager
[17:14] <teward> but just consider, if that bug were filed against just the Ubuntu project and no package
[17:14] <teward> and had the NGINX project assigned
[17:14] <teward> would you remove the Ubuntu task?
[17:15] <teward> (if you could)
[17:15] <penguin42> teward: 1) Leave security bugs to the security teams
[17:15] <teward> penguin42: i know that
[17:15] <teward> penguin42: i'm not asking that
[17:15] <teward> penguin42: i think this needs to be defined in policy regardless:
[17:15] <teward> does the Ubuntu bug task ever get removed?
[17:15] <teward> or does it only get Invalid if the package is not in Ubuntu
[17:15] <teward> s/package/program/
[17:16] <penguin42> teward: Why shouldn't it be an ubuntu task?
[17:16] <teward> penguin42: ask Rosco2 and look at their list of bugs they posted
[17:16] <teward> penguin42: they posted 5 (old) bugs.
[17:16] <teward> penguin42: they say "remove the Ubuntu tasks" by saying: [2015-03-01 12:07:34] <Rosco2> These all have Ubuntu tasks that could be deleted
[17:16] <teward> penguin42: my question was "waht's the justification"
[17:16] <penguin42> teward: Sorry yes, I agree
[17:17] <teward> penguin42: as an example, we would not remove the Ubuntu task for a security bug or otherwise just because it has 'upstream project assigned and resolution'
[17:17] <Rosco2> teward: Your nginx bug looks fine to me
[17:17] <teward> penguin42: i already know that bug's a security bug and under the sec team purview... actually it's under my radar
[17:17] <teward> penguin42: but the point was a hypothetical question for Rosco2
[17:17] <penguin42> Rosco2: It all looks perfectly reasonable; it's a bug that needs fixing in the upstream package and when they do it needs fixing in Ubuntu - so it should  have both tasks
[17:18] <Rosco2> okay - we should assign the task to the Ubuntu package rather than delete?
[17:19] <teward> Rosco2: no, we should find the corresponding package and assign it to that
[17:19] <teward> rather than remove the Ubuntu task overall
[17:19] <Rosco2> thanks - that what I meant
[17:19] <teward> Rosco2: if the package doesn't exist in Ubuntu that's one thing, but if it does (and I know for a fact blueman does), that's different
[17:19] <Rosco2> I will try on the 5 bugs and see how they look
[17:20] <penguin42> they're also old bugs, so the question having found the right ubuntu package would be to ask the reporter to check if it's still there; or if you fancy chase down the upstream package version that got the fix to see if it's in
[17:23] <Rosco2> Thanks guys - understood
=== wgrant_ is now known as wgrant