upstream bugs should not be polled on duplicate bug entries
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Fix Released
|
High
|
Graham Binns |
Bug Description
Now that LP is pulling from bugzilla.
-------
https:/
*** This bug is a duplicate of bug 11334 ***
https:/
Launchpad has imported 45 comments from the remote bug at
https:/
-------
https:/
*** This bug is a duplicate of bug 11334 ***
https:/
Launchpad has imported 45 comments from the remote bug at
https:/
-------
https:/
*** This bug is a duplicate of bug 11334 ***
https:/
Launchpad has imported 45 comments from the remote bug at
https:/
-------
https:/
Launchpad has imported 45 comments from the remote bug at
https:/
Related branches
- Michael Nelson (community): Approve (code)
-
Diff: 131 lines (+107/-6)2 files modifiedlib/lp/bugs/doc/checkwatches.txt (+97/-0)
lib/lp/bugs/scripts/checkwatches.py (+10/-6)
Changed in malone: | |
assignee: | nobody → Graham Binns (gmb) |
Changed in malone: | |
status: | Fix Committed → Fix Released |
Agreed. That's actually pretty easy to fix. Here's what needs to happen (in case someone wants to take a crack at it before one of the Bugs team gets time):
In lib/lp/ bugs/scripts/ checkwatches. py the conditions on lines 780 and 782 should be updated to include the clause `and bug_watch. bug.duplicateof is None`. This will stop the importing and, more importantly, the pushing of comments from or to remote bugs where the Launchpad bug is a duplicate of another Launchpad bug.
The tests in lib/lp/ bugs/doc/ checkwatches. txt should be updated to include tests to cover this change.
Marking this as high; we need to fix this before we enable comment pushing for bugzilla. mozilla. org.