Co-Maintainers wanted for python-lockfile EPEL branches

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi everybody,

I took over python-lockfile some time ago because it was FTBFS in
fedora / orphaned at the time, but it's a dependency of some of my
packages.

However, I have zero interest in maintaining the EPEL branches of that
package, because I have no packages in EPEL myself, and it seems I
can't even figure out how to determine which EPEL packages require
python*-lockfile.

I have received two PRs for the epel7 branch already, and I don't even
know if they're fine or not, so any help would be appreciated.

If nobody steps up within the next two weeks, I will probably retire
the epel7 and epel8 branches of python-lockfile.

Fabio
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux