fas username: @jhli package: libsafec issues to fix: https://bugzilla.redhat.com/show_bug.cgi?id=2045831 nonresponsive maintainer bug: https://bugzilla.redhat.com/show_bug.cgi?id=2159807 fedora-devel mail: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/F35RUC52UA6IHRFWPVHN6ZXY5RB5FVVX/ comainainers: none I am interested in comaintaining the package: yes additional notes:
This is a ticket for the Fedora's Policy for nonresponsive package maintainers.
+1
Metadata Update from @churchyard: - Issue assigned to jhli - Issue tagged with: nonresponsive maintainer
No builds since 2020…
@jhli ping
Added @aekoroglu as a co-maintainer.
FTR there are no other packages:
amatyuko is main admin of rpms/intel-ipp-crypto-mb rpms/intel-ipp-crypto-mb co-maintainers: @aekoroglu amatyuko has a bugzilla override on rpms/intel-ipp-crypto-mb
Sorry, I've cross-posted the previous comment to the wrong ticket. Here are the correct data. There are 2 packages, both of them co-maintained by @aekoroglu now
jhli is main admin of rpms/ipmctl rpms/ipmctl co-maintainers: @aekoroglu, @spontsle jhli has a bugzilla override on rpms/ipmctl jhli is main admin of rpms/libsafec rpms/libsafec co-maintainers: @aekoroglu jhli has a bugzilla override on rpms/libsafec
The early versions of ipmctl (01.00.00.xxxx) depended on this package. I would guess this package was originally added to support those. New releases of ipmctl do not depend on it.
I was not able to reach @jhli last time I tried. I should probably try to be the main admin for ipmctl.
@jhli Do you still want to maintain your Fedora packages?
APPROVED (+2,0,-0)
@spontsle is the main admin of ipmctl
@aekoroglu is the main admin of libsafec
jhli is watching rpms/ipmctl jhli is no longer watching rpms/ipmctl jhli is watching rpms/libsafec jhli is no longer watching rpms/libsafec
Metadata Update from @churchyard: - Issue tagged with: pending announcement
Announced: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/DGN45BVWSCHYPVHMKA5ZOOWAXCEB4ZPQ/
Metadata Update from @decathorpe: - Issue close_status updated to: Accepted - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.