Comment 1 for bug 460138

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.