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.)
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?
epel-devel mailing list