checkwatches can't detect private SourceForge bugs any more

Bug #340959 reported by Graham Binns
2
Affects Status Importance Assigned to Milestone
Launchpad itself
Triaged
Low
Unassigned

Bug Description

Since SourceForge changed its theme checkwatches hasn't been able to detect when bugs are private. This is because the fact that the bug is private is no longer part of the error message on private bug pages (see http://sourceforge.net/tracker/index.php?func=detail&aid=1102982&group_id=93438&atid=604309 for an example). This is now recorded in the OOPS log as an UnparseableBugData instance.

The code in components/externalbugtracker/sourceforge.py circa line 65 should be updated to deal with the new error page.

Graham Binns (gmb)
Changed in malone:
importance: Undecided → Low
status: New → Triaged
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.