[SRU] python-cffi and libffi in Groovy need a no-change rebuild
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
libffi (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Groovy |
Won't Fix
|
High
|
Unassigned | ||
Hirsute |
Fix Released
|
Undecided
|
Unassigned | ||
python-cffi (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Groovy |
Won't Fix
|
High
|
Unassigned | ||
Hirsute |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
[Impact]
* Users of studio-controls have been reporting bugs against studio-controls upstream on Github. For reference, see https:/
* Per the bug report, the following error is being thrown: SystemError: ffi_prep_closure(): bad user_data (it seems that the version of the libffi library seen at runtime is different from the 'ffi.h' file seen at compile-time)
* Based on this error, and based on the build time of python-cffi and libffi in relation to cffi, it appears as though python-cffi and libffi were built on an older version of cffi. This explains the error.
[Test Case]
* A certain number of users have reported that simply running studio-controls causes this error.
[Where problems could occur]
* Since this is a no-change rebuild being requested, the possibility of breakage is slim to none. We are introducing no new changes here, but rather, resolving a regression that happened as a result of a newer version of cffi being introduced without a rebuild of dependencies.
* If any problems happen, it would be a result of applications using python-cffi and expecting this bug with built-in workarounds. I can't imagine such a case exists, so this is just a stretch.
Changed in python-cffi (Ubuntu Hirsute): | |
status: | New → Fix Released |
Changed in python-cffi (Ubuntu Groovy): | |
importance: | Undecided → High |
Changed in python-cffi (Ubuntu Groovy): | |
status: | New → Incomplete |
Changed in libffi (Ubuntu Groovy): | |
status: | New → Incomplete |
python-cffi in Groovy was built against libbfi 3.4~20200819gea d65ca871- 0ubuntu3, which is still the current version.
Build Log: https:/ /launchpadlibra rian.net/ 495225981/ buildlog_ ubuntu- groovy- amd64.python- cffi_1. 14.2-1_ BUILDING. txt.gz
I would expect that if this issue occurred, it would also be visible in python-cffi's autopkgtests, which run the comprehensive upstream testsuite.