This bug is part of the non-responsive maintainer procedure for adeza, following https://docs.fedoraproject.org/en-US/fesco/Policy_for_nonresponsive_package_maintainers/.
Please respond if you are still active in Fedora and want to maintain python-execnet.
Huh? One of the requirements went stable only yesterday.
Will look into this now.
I'm following the non-repsonsive maintainer procedure for Alfredo.
As reported in devel-list, Alfredo was using a @redhat email but he is not an employee anymore, so the account is unreachable. As the procedure requires a BZ to be opened and the ticket requires a component, I opened against python-execnet as it is the package I realized with that he was not active anymore.
But adeza is not the main maintainer of this package ... Maybe another package would be more appropriate.
See also bug 2033140.
Switching component and reopening.
The BZ was not for non-responsive maintainers of python-execnet, but a non-responsive check for Alfredo that happens to be one of the admins.
So, what action do you need from adeza here?
Is there an update needed? a bug? I don't see any bugs open... (aside this one)
Nothing, I'm just following the non-responsive maintainer procedure for Alfredo, not the package, that requires a BZ to be opened. We need this open until FESCO completes the procedure.
I am a bit confused. Is someone planning to take repoze-lru package?
Justin Caratzas, you are currently admin. Are you planning to maintain this package?
If yes, I need an EPEL9 build.
If nobody takes it, I will. It's needed for TurboGears package, even if it should be simply to remove it's dependency, but lru looks to be simple package, so it's better to leave it in Fedora/EPEL.
I'm not planning to take repoze-lru package.
aekoroglu has already taken this package. Thanks.