Latest upstream release: 3.0.11 Current version in Fedora Rawhide: 3.0.10 URL: ftp://sourceware.org/pub/libffi/ Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring
Latest upstream release: 3.0.12 Current version in Fedora Rawhide: 3.0.11 URL: ftp://sourceware.org/pub/libffi/ Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring
Latest upstream release: 3.0.13rc1 Current version in Fedora Rawhide: 3.0.11 URL: ftp://sourceware.org/pub/libffi/ Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring
Latest upstream release: 3.0.13 Current version in Fedora Rawhide: 3.0.11 URL: ftp://sourceware.org/pub/libffi/ Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring
Latest upstream release: 3.1 Current version/release in Fedora Rawhide: 3.0.13-5.fc21 URL: ftp://sourceware.org/pub/libffi/ Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring
Latest upstream release: 3.2.1 Current version/release in Fedora Rawhide: 3.1-6.fc22 URL: ftp://sourceware.org/pub/libffi/ Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring Soon this service will be implemented by a new system: https://github.com/fedora-infra/anitya/ It will require to manage monitored projects via a new web interface. Please make yourself familiar with the new system to ease the transition.
Can we get libffi updated, please? The new versions bring support required for correct function of gcc-go on x86, additional fixes for ppc and s390 are post 3.2.1.
Latest upstream release: 3.3-rc0 Current version/release in rawhide: 3.1-23.fc31 URL: https://sourceware.org/libffi/ Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream. Based on the information from anitya: https://release-monitoring.org/project/1611/
The following Sources of the specfile are not valid URLs so we cannot automatically build the new version for you. Please use URLs in your Source declarations if possible. - ffi-multilib.h - ffitarget-multilib.h
Latest upstream release: 3.3-rc1 Current version/release in rawhide: 3.1-23.fc31 URL: https://sourceware.org/libffi/ Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream. Based on the information from anitya: https://release-monitoring.org/project/1611/
Latest upstream release: 3.3-rc2 Current version/release in rawhide: 3.1-23.fc31 URL: https://sourceware.org/libffi/ Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream. Based on the information from anitya: https://release-monitoring.org/project/1611/
Latest upstream release: 3.3 Current version/release in rawhide: 3.1-23.fc31 URL: https://sourceware.org/libffi/ Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream. Based on the information from anitya: https://release-monitoring.org/project/1611/
Anthony, could you please update the package?
libffi-3.1-24.fc32.aarch64 has a critical bug on Aarch64 related to CPU caches: * https://github.com/libffi/libffi/issues/470 * https://github.com/libffi/libffi/commit/44a6c28545186d78642487927952844156fc7ab5 The bug has been fixed one year ago and is part of libffi 3.3 released in November 2019. test_ctypes of Python 3.6 does crash on Fedora Rawhide because of this: https://bugzilla.redhat.com/show_bug.cgi?id=1797052#c5 libffi-3.1-24.fc32.aarch64 is based on libffi 3.1 released in 2014.
This package has changed maintainer in the Fedora. Reassigning to the new maintainer of this component.
DJ and I are working on the libffi 3.1 -> 3.4 SONAME bump transition. We have a new package request out for libffi3.1.
Latest upstream release: 3.4-rc1 Current version/release in rawhide: 3.1-28.fc34 URL: https://sourceware.org/libffi/ Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/ More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream. Based on the information from anitya: https://release-monitoring.org/project/1611/
An unexpected error occurred while downloading the new package sources; please report this as a bug on the-new-hotness issue tracker.
DJ and I are waiting for libffi 3.4 to release, and then we'll handle the SONAME bump smoothly for Fedora 35.
Latest upstream release: 3.4.0-rc2 Current version/release in rawhide: 3.1-28.fc34 URL: https://sourceware.org/libffi/ Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/ More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream. Based on the information from anitya: https://release-monitoring.org/project/1611/
for the record, I see test failures on aarch64, ppc64le, x86_64 (armv7 and s390x are OK) when building commit ee3ef737857e13cc01a15dbef298478d90188805 in our multi-arch CI (internal to RH). Commit 9fa94c607852081adce33547bde292fe4313cff7 was green on all our arches.
(In reply to Dan Horák from comment #24) > for the record, I see test failures on aarch64, ppc64le, x86_64 (armv7 and > s390x are OK) when building commit ee3ef737857e13cc01a15dbef298478d90188805 > in our multi-arch CI (internal to RH). Commit > 9fa94c607852081adce33547bde292fe4313cff7 was green on all our arches. There were new test cases inserted between those commits, and then a subsequent commit removed compiler warnings that would cause test-case failures (https://github.com/libffi/libffi/commit/1ed0aa73806872f0c31dccf2c689c762239d3353). Looking forward to the 3.4.2 tests (this one: https://github.com/libffi/libffi/commit/f9ea41683444ebe11cfa45b05223899764df28fb ). Thanks!
good news, we do the CI rebuilds daily, if there is a change, so we will see later today
Latest upstream release: 3.4.2 Current version/release in rawhide: 3.1-28.fc34 URL: https://sourceware.org/libffi/ Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/ More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream. Based on the information from anitya: https://release-monitoring.org/project/1611/
One or more of the new sources for this package are identical to the old sources. This is most likely caused either by identical source files between releases, for example service files, or the specfile does not use version macro in its source URLs. If this is the second case, then please update the specfile to use version macro in its source URLs.
Skipping the scratch build because an SRPM could not be built: ['git', 'commit', '-a', '-m', 'Update to 3.4.2 (#873990)'] returned 1: b'On branch rawhide\nYour branch is up to date with \'origin/rawhide\'.\n\nUntracked files:\n (use "git add <file>..." to include in what will be committed)\n\tSRPMS/\n\nnothing added to commit but untracked files present (use "git add" to track)\n'
I have a side-tag in Fedora Rawhide already with libffi3.1 and libffi (3.4.2) in testing. In the side-tag I tested: dnf PASS gobject-introspection PASS glib2 PASS p11-kit PASS rubygem-ffi PASS python3.9 PASS guile22 PASS git-annex PASS php PASS It looks quite good and libffi3.1 ensures operation of old binaries with compat package.
Hello, is there please some update on rebasing libffi to newer version?
(In reply to Zuzana Miklankova from comment #31) > Hello, is there please some update on rebasing libffi to newer version? Yes, this is blocked on me. The work is done, but in Rawhide we need to rebuild a large number of packages and I need to get some help with that.
(In reply to Carlos O'Donell from comment #32) > (In reply to Zuzana Miklankova from comment #31) > > Hello, is there please some update on rebasing libffi to newer version? > > Yes, this is blocked on me. The work is done, but in Rawhide we need to > rebuild a large number of packages and I need to get some help with that. I'll add the note that the rebase came in late in Fedora 35 and so was rejected there, and it was accepted in Fedora 36: https://fedoraproject.org/wiki/Changes/LIBFFI34
> Yes, this is blocked on me. The work is done, but in Rawhide we need to rebuild a large number of packages and I need to get some help with that. And can I help somehow?
I am also available to help with the rebuilds.
I've contacted Carlos via email. I'll start with copr once again to see what builds fine and what doesn't: https://copr.fedorainfracloud.org/coprs/churchyard/libffi-3.4/builds/ If there are no major blockers, I'll announce on the devel list, create the side tag and rebuild everything there.
(In reply to Miro Hrončok from comment #36) > I'll start with copr once again to see what builds fine and what doesn't: > > https://copr.fedorainfracloud.org/coprs/churchyard/libffi-3.4/builds/ > > If there are no major blockers, I'll announce on the devel list, create the > side tag and rebuild everything there. Thank you so much for the help with the rebuilds! There are a lot of dependent packages in Fedora that need rebuilds, and your help is much appreciated.
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/ZMPLY67JRCQ2M3SA42L5IDHXEKWP5OA7/
FEDORA-2022-c440651258 has been pushed to the Fedora 36 stable repository. If problem still persists, please make note of it in this bug report.