On Thu, 25 Jul 2019 at 08:46, Stephen John Smoogen <smooge@xxxxxxxxx> wrote:
On Thu, 25 Jul 2019 at 08:21, Miro Hrončok <mhroncok@xxxxxxxxxx> wrote:On 17. 07. 19 0:00, Miro Hrončok wrote:
> ...we need 1 or 2 new components for python34-pip and python2-pip - either
> we have each in a separate component or we create a new component that
> builds both (called python-pip-epel maybe?).
What is the advice here? If I want it to be just one package, what shall be its
name?
Sorry, I completely missed that there were points you needed answers on. Are there any others in the proposal we need to focus on?
And there are clearly multiple based around this one:
however IIRC we cannot have the same component name as in RHEL. If that is indeed the case, python3-setuptools needs to be
retired and a new python34-setuptools component needs to be created in epel7. Is my assumption correct?Yes your assumption is correct. Koji uses src.rpm names to determine what it pulls into a buildroot. That means that the python34 items need to have non-conflicting names with the python3 ones shipped by upstream.. or we will just start building with python34 or worse.
Would it make sense to just retire python34 completely from EPEL at the 7.7 release date?
--Stephen J Smoogen.
Stephen J Smoogen.
_______________________________________________ epel-devel mailing list -- epel-devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to epel-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/epel-devel@xxxxxxxxxxxxxxxxxxxxxxx
