[lp-set-dupe] no longer reassigns dupes
Bug #576477 reported by
Rolf Leggewie
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| ubuntu-dev-tools (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
Binary package hint: ubuntu-dev-tools
I just tried to mark a bunch of tickets as dupes to bug 403714 with "lp-set-dup 403714 393980 403876 403277". 393980 failed because it already had a dupe of its own (lp-set-dupe previously handled this well). the last two were private (I think the script used to handle that as well).
current package in lucid:
ii ubuntu-dev-tools 0.99 useful tools for Ubuntu developers
Revision history for this message
| Michael Bienia (geser) wrote | #1 |
Revision history for this message
| Rolf Leggewie (r0lf) wrote | #2 |
Revision history for this message
| Benjamin Drung (bdrung) wrote | #3 |
| Changed in ubuntu-dev-tools (Ubuntu): | |
| status: | New → Incomplete |
| summary: |
- lp-set-dupe no longer reassigns dupes + [lp-set-dupe] no longer reassigns dupes |
Revision history for this message
| Rolf Leggewie (r0lf) wrote | #4 |
| Changed in ubuntu-dev-tools (Ubuntu): | |
| status: | Incomplete → Fix Released |
To post a comment you must log in.
What kind of access did you grant ubuntu-dev-tools through the LP API (does it have write-access to private data)? Did you get any warnings that the script doesn't have enough permissions?
If you didn't grant u-d-t write-access to private data, lp-set-dupe doesn't have enough permissions to re-dupe private bugs. That would explain why it didn't re-dupe the last two bugs and also failed at 393980 as 393981 which was dupe to it is also private.