© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
This doesn't really seem to be a minimal fix, especially since it appears that switching to the Python API but *not* upgrading to u-a-t >= 30 results in a similarly broken experience.
Given the choice between a 1 line diff to debian/control and an architectural change *and also* that same 1-line diff to debian/control it seems clear to me that just the 1-line change is the more appropriate SRU. Is there extra context here that I'm missing that would change this calculus?
If it later turns out that there are bugs that can only reasonably be fixed by switching to the Python API, then that switch can be made for that SRU. I don't think we need to preemptively re-architect this.