I like to see python26-jinga2 package in EPEL5.
This is currently not possible due to missing dependencies but I'll try
to provide some patches once it it is unblocked.
Is there a consensus on whether we should create py26 subpackages from the main packages or have completely separate specfiles?
Both options are quite possible and it depends on a few factors:
A cursory look I see you have same version in EPEL5 and rawhide and your rawhide
already has a python3 variant.
As such if it were me adding a with_python26 option makes a lot of sense. I'm happy to provide
a patch once the markupsafe is in place.
> A cursory look I see you have same version in EPEL5 and rawhide and your
> already has a python3 variant.
I was mistaken here , I now see that EPEL5 is 2.2.1 where as devel is
I am unsure of the significance here but I expect a new python26-jinga2
package probably make sense.
python26-markupsafe is now on its way to the testing repo.
Created attachment 475667 [details]
F15 spec file adapted for python26-jinja2 in EPEL5
This is a python26-jinja2 .spec file suitable for EPEL5.
I am hoping you might like to submit it for review... Once you have checked it of course.
(In reply to comment #4)
> This is a python26-jinja2 .spec file suitable for EPEL5.
> I am hoping you might like to submit it for review... Once you have checked it
> of course.
Will do so, but I'm currently a busy, so not before end of next week.
python26-jinja2-2.5.5-4.el5 has been pushed to the Fedora EPEL 5 stable repository.