[Bug 1912535] Re: [SRU] python-cffi and libffi in Groovy need a no-change rebuild

[Erich Eickmeyer]

Upon further investigation, it appears as though libffi was built on an
older version of cffi, which would probably explain this a little
further. Adding libffi to the bug.


** Summary changed:

- [SRU] python-cffi in Groovy needs a no-change rebuild
+ [SRU] python-cffi and libffi in Groovy need a no-change rebuild

** Also affects: libffi (Ubuntu)
   Importance: Undecided
       Status: New

** Changed in: libffi (Ubuntu Hirsute)
       Status: New => Fix Released

** Description changed:

  [Impact]
  
-  * Users of studio-controls have been reporting bugs against studio-
+  * Users of studio-controls have been reporting bugs against studio-
  controls upstream on Github. For reference, see
  https://github.com/ovenwerks/studio-controls/issues/43
  
-  * Per the bug report, the following error is being thrown: SystemError:
+  * 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, it
- appears as though python-cffi was built on an older version of cffi.
- This explains the error.
+  * 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-
+  * 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
+  * 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
+  * 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: libffi (Ubuntu Groovy)
   Importance: Undecided => High

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to libffi in Ubuntu.
https://bugs.launchpad.net/bugs/1912535

Title:
  [SRU] python-cffi and libffi in Groovy need a no-change rebuild

Status in libffi package in Ubuntu:
  Fix Released
Status in python-cffi package in Ubuntu:
  Fix Released
Status in libffi source package in Groovy:
  New
Status in python-cffi source package in Groovy:
  New
Status in libffi source package in Hirsute:
  Fix Released
Status in python-cffi source package in Hirsute:
  Fix Released

Bug description:
  [Impact]

   * Users of studio-controls have been reporting bugs against studio-
  controls upstream on Github. For reference, see
  https://github.com/ovenwerks/studio-controls/issues/43

   * 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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libffi/+bug/1912535/+subscriptions