update-remote-product.py doesn't initialise the remote bug tracker before calling getRemoteProduct()

Bug #333354 reported by Graham Binns
4
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
High
Graham Binns

Bug Description

At the moment the update-remote-product script doesn't call initializeRemoteBugDB() on the ExternalBugTracker before calling getRemoteProduct(). This leads to an exception because the remote bug hasn't been pulled from the remote bug tracker.

Graham Binns (gmb)
Changed in malone:
assignee: nobody → gmb
importance: Undecided → High
milestone: none → 2.2.2
status: New → In Progress
Revision history for this message
Björn Tillenius (bjornt) wrote : Bug fixed by a commit

Fixed in RF 7842.

Changed in malone:
status: In Progress → Fix Committed
Graham Binns (gmb)
Changed in malone:
status: Fix Committed → Fix Released
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.