Hi, On Wed, 2016-11-16 at 13:10 +0300, Devrim Gündüz wrote: > I can do it in the community repo, but not sure if EPEL update will be > accepted > (I have the power to do so, but EPEL policy may be boring sometimes) > > I'll take a look. I already added 20+ more packages to community repo for > pgadmin4. Adding another may not hurt, hopefully, at least for the build > servers.
Oh, just saw python-sphinx10 package in EPEL 6. That brings 1.0.8 to EL6. However, I will need to apply this patch on EL 6: --- docs/en_US/Makefile.sphinx.old 2016-11-16 13:16:31.885343501 +0300 +++ docs/en_US/Makefile.sphinx 2016-11-16 13:16:58.297102473 +0300 @@ -3,7 +3,7 @@ # You can set these variables from the command line. SPHINXOPTS = -SPHINXBUILD = sphinx-build +SPHINXBUILD = sphinx-1.0-build PAPER = BUILDDIR = _build So that it will use that sphinx version. Ok, I think we have a easier solution now, though -docs is not the only blocker in EL6. Let me work on the rest. Regards, -- Devrim GÜNDÜZ EnterpriseDB: http://www.enterprisedb.com PostgreSQL Danışmanı/Consultant, Red Hat Certified Engineer Twitter: @DevrimGunduz , @DevrimGunduzTR
signature.asc
Description: This is a digitally signed message part
