Fails to get branches with launchpadlib 1.9.7
Bug #730777 reported by
dobey
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Tarmac |
Fix Released
|
Critical
|
dobey |
Bug Description
With the new launchpadlib, tarmac is failing to find branches. This appears to be due to the Launchpad object's __init__ API breaking in the new launchpadlib, and so tarmac ends up connecting to the default staging server, where many of the branches don't actually exist in launchpad's db. It seems some new positional arguments were added to the __init__, and tarmac was relying on the position of keyword arguments prior; so both ends broke. According to Leonard's e-mail, we should switch to using the Launchpad.
Related branches
lp:~dobey/tarmac/login-with
- Paul Hummer: Approve
-
Diff: 35 lines (+5/-13)1 file modifiedtarmac/bin/commands.py (+5/-13)
Changed in tarmac: | |
status: | In Progress → Fix Committed |
Changed in tarmac: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.