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/

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-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/

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

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/

An unexpected error occurred while downloading the new package sources; please report this as a bug on the-new-hotness issue tracker.

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.

Releases retrieved: 3.4.3
Upstream release that is considered latest: 3.4.3
Current version/release in rawhide: 3.1-19.fc30
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://stg.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://stg.release-monitoring.org/project/1611/


To change the monitoring settings for the project, please visit:
https://src.stg.fedoraproject.org/rpms/libffi

Scratch build failed. Details below:

BuilderException: Build failed:
Command '['rpmbuild', '-D', '_sourcedir .', '-D', '_topdir .', '-bs', '/var/tmp/thn-ffal5my4/libffi.spec']' returned non-zero exit status 1.

StdOut:
error: Bad source: ./libffi-3.4.3.tar.gz: No such file or directory


Traceback:
  File "/usr/local/lib/python3.10/site-packages/hotness/use_cases/package_scratch_build_use_case.py", line 56, in build
    result = self.builder.build(request.package, request.opts)
  File "/usr/local/lib/python3.10/site-packages/hotness/builders/koji.py", line 188, in build
    raise BuilderException(

If you think this issue is caused by some bug in the-new-hotness, please report it on the-new-hotness issue tracker: https://github.com/fedora-infra/the-new-hotness/issues

Releases retrieved: 3.4.4
Upstream release that is considered latest: 3.4.4
Current version/release in rawhide: 3.1-19.fc30
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://stg.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://stg.release-monitoring.org/project/1611/


To change the monitoring settings for the project, please visit:
https://src.stg.fedoraproject.org/rpms/libffi

Scratch build failed. Details below:

BuilderException: Build failed:
Command '['rpmbuild', '-D', '_sourcedir .', '-D', '_topdir .', '-bs', '/var/tmp/thn-6rx5mbu6/libffi.spec']' returned non-zero exit status 1.

StdOut:
error: Bad source: ./libffi-3.4.4.tar.gz: No such file or directory


Traceback:
  File "/usr/local/lib/python3.10/site-packages/hotness/use_cases/package_scratch_build_use_case.py", line 56, in build
    result = self.builder.build(request.package, request.opts)
  File "/usr/local/lib/python3.10/site-packages/hotness/builders/koji.py", line 188, in build
    raise BuilderException(

If you think this issue is caused by some bug in the-new-hotness, please report it on the-new-hotness issue tracker: https://github.com/fedora-infra/the-new-hotness/issues

Releases retrieved: 3.4.5
Upstream release that is considered latest: 3.4.5
Current version/release in rawhide: 3.4.4-7.fc40
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://stg.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://stg.release-monitoring.org/project/1611/


To change the monitoring settings for the project, please visit:
https://src.stg.fedoraproject.org/rpms/libffi

Scratch build failed. Details below:

BuilderException: Build failed:
Command '['rpmbuild', '-D', '_sourcedir .', '-D', '_topdir .', '-bs', '/var/tmp/thn-m0dkefs0/libffi.spec']' returned non-zero exit status 1.

StdOut:
warning: %patchN is deprecated (5 usages found), use %patch N (or %patch -P N)
setting SOURCE_DATE_EPOCH=1707955200
error: Bad file: ./libffi-3.4.5.tar.gz: No such file or directory

RPM build warnings:
    %patchN is deprecated (5 usages found), use %patch N (or %patch -P N)

RPM build errors:
    Bad file: ./libffi-3.4.5.tar.gz: No such file or directory


Traceback:
  File "/usr/local/lib/python3.11/site-packages/hotness/use_cases/package_scratch_build_use_case.py", line 56, in build
    result = self.builder.build(request.package, request.opts)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/hotness/builders/koji.py", line 229, in build
    raise BuilderException(

If you think this issue is caused by some bug in the-new-hotness, please report it on the-new-hotness issue tracker: https://github.com/fedora-infra/the-new-hotness/issues

Created attachment 1819204 [details]
Update to 3.4.5 (#873990)

Releases retrieved: 3.4.6
Upstream release that is considered latest: 3.4.6
Current version/release in rawhide: 3.4.4-7.fc40
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://stg.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://stg.release-monitoring.org/project/1611/


To change the monitoring settings for the project, please visit:
https://src.stg.fedoraproject.org/rpms/libffi

Scratch build failed. Details below:

BuilderException: Build failed:
Command '['rpmbuild', '-D', '_sourcedir .', '-D', '_topdir .', '-bs', '/var/tmp/thn-u9u1dkat/libffi.spec']' returned non-zero exit status 1.

StdOut:
warning: %patchN is deprecated (5 usages found), use %patch N (or %patch -P N)
setting SOURCE_DATE_EPOCH=1708300800
error: Bad file: ./libffi-3.4.6.tar.gz: No such file or directory

RPM build warnings:
    %patchN is deprecated (5 usages found), use %patch N (or %patch -P N)

RPM build errors:
    Bad file: ./libffi-3.4.6.tar.gz: No such file or directory


Traceback:
  File "/usr/local/lib/python3.11/site-packages/hotness/use_cases/package_scratch_build_use_case.py", line 56, in build
    result = self.builder.build(request.package, request.opts)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/hotness/builders/koji.py", line 229, in build
    raise BuilderException(

If you think this issue is caused by some bug in the-new-hotness, please report it on the-new-hotness issue tracker: https://github.com/fedora-infra/the-new-hotness/issues

Created attachment 1819275 [details]
Update to 3.4.6 (#873990)