touch-packages team mailing list archive

[Chris J Arges <1513958@xxxxxxxxxxxxxxxxxx>]

Hello dann, or anyone else affected,

Accepted libffi into trusty-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/libffi/3.1~rc1+r3.0.13-12ubuntu0.1
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: libffi (Ubuntu Trusty)
       Status: In Progress => Fix Committed

** Tags added: verification-needed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libffi in Ubuntu.
https://bugs.launchpad.net/bugs/1513958

Title:
  arm64: failure with small objects passed on stack

Status in libffi package in Ubuntu:
  Fix Released
Status in libffi source package in Trusty:
  Fix Committed

Bug description:
  [Impact]
  It isn't possible to build newer versions of python-cffi on trusty/arm64 because it's test cases will fail due to this bug. The thing that's biting me is that cloud-archive:liberty is incomplete on arm64, making key packages uninstallable on arm64 (e.g. nova-compute).

  Additionally, libffi is used by several languages in Ubuntu (python,
  ruby, haskell, etc), so this may also be causing issues in the closed
  set of Ubuntu/trusty packages. I don't have evidence either way.

  [TestCase]
  Build python-cffi_1.1.2-1ubuntu2 from wily on trusty/arm64. With unfixed libffi, the build will fail during dh_auto_test in the
  "TestFFI.test_struct_by_value" test case.

  [Regression Risk]
  The fix is in the aarch64-specific code, so there's a negligible risk of regression on other platforms. This exact fix was included in vivid and wily and no regressions have been triaged to libffi in those releases.

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