Am 25.01.2015 um 21:10 schrieb Till Maas:
> Now it seems as if I have to do something to save a part of
> stack from removal.
You can also just maintain the python packages. AFAIK nobody is really
forcing that python26 is removed from EPEL5, it is just a lack of
interest in package maintainers to care about the affected packages.
I know :-)
Actually I use the python26 packages for some internal scripts but I don't
have enough time to maintain them so I figured it's better to do the work in
private (maybe with a COPR repo) instead of giving other the impression that
this maintained with the same (high) level of attention as other Fedora/EPEL
> What's next? Do I have to trigger a build or even push an
Yes, you need to push an update to make sure that no broken
dependencies stay in the repository. Please do it soon so I can move
forward and retire all packages with broken dependencies in EPEL.
Just to be sure: Is it possible to get a hierarchy-based report so one could
assess why packages are removed? There are so many python packages on the el5
removal list that I don't want to do the checks for every single package...