On 24 January 2015 at 14:36, Felix Schwarz <fschwarz(a)fedoraproject.org>
wrote:
Hi Till,
sorry: somehow I totally misunderstood what you wrote me earlier + I didn't
occur to me that also subpackages might cause the main package to be
removed.
Anyhow I can just hope you accept apologies.
Now it seems as if I have to do something to save a part of EPEL5's Python
stack from removal.
As a first step I disabled the babel-python26 package in git. (The
changelog
entry is not entirely correct, as I saw now only python26-distribute goes
away, not python26 itself.)
actually python26 should go away also. the entire python26 stack has been
EOL by the developers
Theoretically babel could also work without setuptools/distribute but
that
will cause reduced functionality (and not egg metadata) which is currently
provided. Personally I'd rather keep installed babel-python26 installs
as-is
(= just remove the subpackage) than dropping setuptools support and
regressing
in functionality. Please let me know if there are any objections.
What's next? Do I have to trigger a build or even push an update?
I believe a build needs to be triggered.
Felix
_______________________________________________
epel-devel mailing list
epel-devel(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/epel-devel
--
Stephen J Smoogen.