EPEL, RHEL-5Server and RHEL-5Client

Stephen John Smoogen smooge at gmail.com
Thu Jul 12 18:27:52 UTC 2007


On 7/12/07, Thorsten Leemhuis <fedora at leemhuis.info> wrote:
>
>
> On 12.07.2007 20:08, Rex Dieter wrote:
> > Konstantin Ryabitsev wrote:
> >
> >> So, here's a fun situation:
> >>
> >> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=246444
> >>
> >> In brief:
> >>
> >> * python-imaging in EPEL conflicts with python-imaging in RHEL-5Client
> >> * upstream (RHEL5) requests to remove python-imaging because EPEL is
> >> not supposed to override upstream
> >> * removing python-imaging will break dependencies in RHEL-5Server
> >
> > remove it from epel, and RHEL-5Server folks will probably have to live with
> > broken deps.
>
> +1
>
> A real long term solution might be to have a kind of dynamic exclude
> list (done by a yum-plugin with pre-generated lists maybe? no idea, just
> thinking loud) that would exclude all packages depending on
> python-imaging on EL5Server.
>

I wont be able to install plone or anything pythonish because of this
on server but I can on client?

Proposal:

Compile a version of python-imaging that matches what is in the base
OS. The EPEL version is 1.0.6 and the supplied version is 1.0.5. That
sounds the most reasonable.


-- 
Stephen J Smoogen. -- CSIRT/Linux System Administrator
How far that little candle throws his beams! So shines a good deed
in a naughty world. = Shakespeare. "The Merchant of Venice"




More information about the epel-devel-list mailing list