Re: Non-responsive maintainer check for libffi maintainer

2020-02-24 Thread Jeff Law
On Mon, 2020-02-24 at 13:02 +, devel- requ...@lists.fedoraproject.org wrote: > > Date: Mon, 24 Feb 2020 12:10:49 +0100 > From: Miro Hrončok > Subject: Re: Non-responsive maintainer check for libffi maintainer > To: Anthony Green > Cc: Development discussions

Re: Non-responsive maintainer check for libffi maintainer

2020-02-24 Thread Christopher Engelhard
On 2/24/2020 1:46 AM, Anthony Green wrote: >I would be very happy if somebody could pick up the libffi packaging > responsibility from me. I'd be happy to adopt libffi, but given that I am a VERY new packager and this is a pretty core package, I think it would be best if someone with a bit

Re: Non-responsive maintainer check for libffi maintainer

2020-02-24 Thread Miro Hrončok
On 24. 02. 20 1:46, Anthony Green wrote: I would be very happy if somebody could pick up the libffi packaging responsibility from me. Suggestion: Try announcing on devel list that you are seeking co-maintainers (from a separate thread). If that doesn't help, orphan the package and see who

Re: Non-responsive maintainer check for libffi maintainer

2020-02-23 Thread Anthony Green
Miro, I would be very happy if somebody could pick up the libffi packaging responsibility from me. For what it's worth, I'm about to make _another_ ABI-changing upstream release (to .so.8). An opaque object type (trampoline) is changing size in order to support Intel's Control-Flow

Non-responsive maintainer check for libffi maintainer

2020-02-23 Thread Miro Hrončok
Hello Anthony, I am trying to determine if you are still interested in maintaining your Fedora packages, namely libffi. I cannot see any activity in Koji since 2017, but there were some commits in https://src.fedoraproject.org/rpms/libffi/commits/master cca 8 months ago, which is confusing.