Seeking co-maintainer for libffi package

[Anthony Green]

Hello -- I'm the current Fedora maintainer for libffi, as well as the
upstream author/maintainer.   I'm looking for help with libffi
packaging.  Specifically, we need to roll out a new ABI-breaking
release (required for ARM64 and Intel CET support), and I don't have
the volunteer time available to create the requisite compat packages,
monitor all of the rebuilds, etc.   It would be best if this person
had some Fedora packaging experience under their belt, given some of
the complexities involved and the criticality of libffi to the whole
platform.

Thanks!

AG

-- 
Anthony Green <green(a)redhat.com&gt;
Senior Principal Solutions Architect, Financial Services

[Antonio Trande]

Add me as co-maintainer, please.
I'm using libffi as dependency for a couple of packages.

On 25/02/20 16:56, Anthony Green wrote:
>  Hello -- I'm the current Fedora maintainer for libffi, as well as
> the
>  upstream author/maintainer.   I'm looking for help with libffi
>  packaging.  Specifically, we need to roll out a new ABI-breaking
>  release (required for ARM64 and Intel CET support), and I don't have
>  the volunteer time available to create the requisite compat packages,
>  monitor all of the rebuilds, etc.   It would be best if this person
>  had some Fedora packaging experience under their belt, given some of
>  the complexities involved and the criticality of libffi to the whole
>  platform.
>  
>  Thanks!
>  
>  AG
>   
-- 
---
Antonio Trande
Fedora Project
mailto 'sagitter at fedoraproject dot org'
GPG key: 0x7B30EE04E576AA84
GPG key server: https://keys.openpgp.org/

[Richard Shaw]

On Tue, Feb 25, 2020 at 9:57 AM Anthony Green <green(a)redhat.com&gt; wrote:

>  Hello -- I'm the current Fedora maintainer for libffi, as well as
> the
>  upstream author/maintainer.   I'm looking for help with libffi
>  packaging.  Specifically, we need to roll out a new ABI-breaking
>  release (required for ARM64 and Intel CET support), and I don't have
>  the volunteer time available to create the requisite compat packages,
>  monitor all of the rebuilds, etc.   It would be best if this person
>  had some Fedora packaging experience under their belt, given some of
>  the complexities involved and the criticality of libffi to the whole
>  platform.
>  
While API/ABI breaking changes within a release is discouraged, it's still
might be the right thing to do. You could create a side tag and make sure
all dependent packages have been rebuilt or ported over first, and them
merge them back in with a single bodhi update.

Thanks,
Richard

[Florian Weimer]

* Richard Shaw:

>  While API/ABI breaking changes within a release is discouraged,
> it's
>  still might be the right thing to do. 
libffi within a Fedora release?  That seems rather ... involved because
Python depends on it.

I don't think we'll need ABI changes for CET support, and we plan to
port CET support into Fedora 31's (and 32's) libffi 3.1 version.  But I
won't be able to work on this before April at least.

The justification for the first soname bump (to .7) does not appear to
be correct to me: introducing symbol versioning does not need a soname
bump with the GNU ELF implementation, and the aarch64 change only
affects Mach-O targets, not ELF targets.  The ELF ABI is in fact
unchanged.

If I'm counting correctly, we currently use only 20 out of 36 bytes for
the aarch64 trampoline, so there's room for future BTI support as well.

Thanks,
Florian

[Anthony Green]

Thank you for all of the offers.  The team that maintains glibc
(Carlos, Florian and DJ) has stepped up to help with libffi packaging.
I think that this is the right group to handle libffi for now.

Thanks again,

AG

On Tue, Feb 25, 2020 at 10:56 AM Anthony Green <green(a)redhat.com&gt; wrote:
>  Hello -- I'm the current Fedora maintainer for libffi, as well as the
>  upstream author/maintainer.   I'm looking for help with libffi
>  packaging.  Specifically, we need to roll out a new ABI-breaking
>  release (required for ARM64 and Intel CET support), and I don't have
>  the volunteer time available to create the requisite compat packages,
>  monitor all of the rebuilds, etc.   It would be best if this person
>  had some Fedora packaging experience under their belt, given some of
>  the complexities involved and the criticality of libffi to the whole
>  platform.
>
>  Thanks!
>
>  AG
>
>  --
>  Anthony Green <green(a)redhat.com&gt;
>  Senior Principal Solutions Architect, Financial Services 


-- 
Anthony Green <green(a)redhat.com&gt;
Senior Principal Solutions Architect, Financial Services
[phone]

[Miro Hrončok]

On 26. 02. 20 12:19, Anthony Green wrote:
>  Thank you for all of the offers.  The team that maintains glibc
>  (Carlos, Florian and DJ) has stepped up to help with libffi packaging.
>  I think that this is the right group to handle libffi for now. 
Thanks!

-- 
Miro Hrončok
--
Phone: [phone]
IRC: mhroncok