Nominating a bug for a distro series affects all package tasks for that distro
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Triaged
|
High
|
Unassigned |
Bug Description
Symptoms
========
Doing a nomination affects all current tasks in the (distro/product). This is surprising and prevents selection of just one facet of a complex bug.
After a nomination is done, its impossible to nominate newly added tasks. This prevents adding series tasks for packages which were identified as affected after the original nomination was accepted.
Trying to workaround the latter restriction via email results in an OOPS: OOPS-816CEMAIL3.
Analysis
========
Nominations are tracked as (bug, *series) pairs, which is insufficient for distributions which have subcomponents. This means that when a bug with several package tasks is nominated for a release, all the packages are effectively nominated, and the unique constraint in the database table prevents a successive nomination when a new package is added to the bug. Further to that, if an existing task is moved outside of the bug context - for example to a different distribution or different product, the nomination becomes entirely bogus : but the datamodel cannot realise that.
Possible solutions
==================
* Make bug nomination link to a bugtask. This would get the thing being nominated from the task, and the series to nomination from from the nomination. Some form of synchronisation to keep nominations fresh (or perhaps just destroy them) when a task changes context (distro,product) will be needed.
* Add a component field to bugnomination - sourcepackagename. This too would require synchronisation in the event that a bug has the matching task removed/retargeted.
description: | updated |
Changed in malone: | |
importance: | Undecided → High |
summary: |
- Nomination for a release on one source package shouldn't affect any - others + Nominating a bug for a distro release affects all package tasks for that + distro |
description: | updated |
tags: | added: oops |
description: | updated |
description: | updated |
Changed in launchpad: | |
assignee: | nobody → Graham Binns (gmb) |
assignee: | Graham Binns (gmb) → nobody |
Changed in launchpad: | |
assignee: | nobody → Graham Binns (gmb) |
assignee: | Graham Binns (gmb) → nobody |
Changed in launchpad: | |
assignee: | nobody → Graham Binns (gmb) |
status: | Triaged → In Progress |
tags: | added: bug-relationships |
tags: | added: bug-nomination |
summary: |
- Nominating a bug for a distro release affects all package tasks for that + Nominating a bug for a distro series affects all package tasks for that distro |
Changed in launchpad: | |
status: | Triaged → New |
status: | New → Incomplete |
status: | Incomplete → Opinion |
status: | Opinion → Invalid |
status: | Invalid → Confirmed |
status: | Confirmed → In Progress |
status: | In Progress → Fix Committed |
status: | Fix Committed → Fix Released |
Changed in launchpad: | |
status: | Fix Released → Triaged |
Changed in launchpad: | |
status: | Triaged → New |
status: | New → Incomplete |
status: | Incomplete → Opinion |
status: | Opinion → Invalid |
status: | Invalid → Confirmed |
status: | Confirmed → In Progress |
status: | In Progress → Fix Committed |
status: | Fix Committed → Fix Released |
Changed in launchpad: | |
status: | Triaged → Fix Released |
Changed in launchpad: | |
status: | Fix Released → Triaged |
information type: | Public → Public Security |
information type: | Public Security → Public |
information type: | Public → Private |
information type: | Private → Public |
Changed in launchpad: | |
assignee: | nobody → faaaaa (faaaaa) |
Changed in launchpad: | |
assignee: | faaaaa (faaaaa) → nobody |
Changed in launchpad: | |
assignee: | nobody → martin (mukamuka) |
assignee: | martin (mukamuka) → nobody |
status: | Triaged → Fix Released |
Changed in launchpad: | |
status: | Fix Released → Triaged |
Changed in launchpad: | |
importance: | Critical → High |
I can reproduce this behaviour especially when I have to work with security bugs.
Nominating different releases for different versions of a source package in one bug report is not possible.
This is a bug and needs to be fixed.