Remote watch wrongly says upstream bug # "appears not to exist"
Bug #460138 reported by
Sumana Harihareswara
This bug report is a duplicate of:
Bug #383467: BugWatch updates on bug trackers with large numbers of watches fall behind quickly.
Edit
Remove
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Triaged
|
High
|
Unassigned | ||
Bug Description
https:/
has been told it has a remote watch on a GNOME bug. The Update Status page tells me:
GNOME Bug Tracker bug #505000 appears not to exist. Check that the bug number is correct.
But the URL that Launchpad has for the remote watch:
https:/
does indeed exist, with an XML feed at
| tags: |
added: bugwatch removed: gnome remotewatch upstream |
| affects: | launchpad → malone |
| Changed in malone: | |
| status: | New → Triaged |
| importance: | Undecided → High |
Revision history for this message
| Graham Binns (gmb) wrote | #1 |
To post a comment you must log in.
This is actually, in a weird way, a duplicate of our old friend bug 383467.
The way this has happened is as follows:
1. We've tried to solve bug 383467 by creating a method of forcing updates.
2. When we've run checkwatches with the --reset switch, we've run into problems connecting to the remote Bugzilla
3. Therefore all the watches that didn't get updated at the time (for there were other bugs that caused problems, too) were left with a "no such remote bug" error recorded against them.
4. But because of bug 383467, the watches have yet to be updated again, some three or four weeks after the last time we tried to update them en masse.