Loom plugin uses deprecated APIs

Bug #270352 reported by Jonathan Lange
2
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
High
Jonathan Lange
Loom
Invalid
Undecided
Unassigned

Bug Description

Launchpad Bazaar regularly generates the following OOPSes:

> 8 UnexpectedStderr: Unexpected standard error from subprocess: <string>:4: DeprecationWarning: bzrlib.lockable_files.LockableFiles.get was deprecated in version 1.5.
> Other: 8 Robots: 0 Local: 0
> 4 https://code.launchpad.net/~~lifeless/bzr/versioned_files (Unknown)
> OOPS-988SMPM113, OOPS-988SMPM17, OOPS-988SMPM3, OOPS-988SMPM8
> 4 https://code.launchpad.net/~~lifeless/bzr/switch-relative (Unknown)
> OOPS-988SMPM112, OOPS-988SMPM16, OOPS-988SMPM2, OOPS-988SMPM7
>

The "unexpected standard error" is:
<string>:4: DeprecationWarning: bzrlib.lockable_files.LockableFiles.put was deprecated in version 1.6.

I imagine the fix for this is simple.

Revision history for this message
Jonathan Lange (jml) wrote :

Causing OOPSes, upgrading to High.

Changed in launchpad-bazaar:
importance: Undecided → High
status: New → Triaged
Revision history for this message
Jonathan Lange (jml) wrote :

This appears to have been fixed by the bzr-loom upgrade in the 2.1.9 rollout.

Changed in launchpad-bazaar:
assignee: nobody → jml
milestone: none → 2.1.9
status: Triaged → Fix Released
Changed in bzr-loom:
status: New → Invalid
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.