On 24.07.2007 16:04, Daniel Riek wrote:
sorry, I missed that problem.
Well, it's a corner case only a few users might hit, so its not a big
problem afaics (nevertheless one we should better fix).
We are going to try to fix that in 5.1
during the Beta.
Great.
I might have missed how you want to handle this in EPEL: in RHEL you
will have to update to 5.1 to get python-imaging. So do you want to keep
lower n-v-r in EPEL?
Yeah, we could do that as interim solution for now and have the missing
package only in EPEL5-PCC with a lower n-v-r -- shouldn't hurt anyone
afaics, as we don't replace anything from RHEL. And when RHEL 5.1 comes
out it will replace the package from EPEL.
Cu
knurd
On Tue, 2007-07-24 at 15:56 +0200, Joel Andres Granados wrote:
> Joel Andres Granados wrote:
>> Thorsten Leemhuis wrote:
>>> On 24.07.2007 11:14, Joel Andres Granados wrote:
>>>
>>>> Received two automated email (attached) stating that plone depends
>>>> on python-imaging for el5.
>>>> python-imaging for el5 terminated from EPEL due to its existence in
>>>> both RHEL5 Client and Server.
>>>> Additionally the mail states that the broken dependency is only
>>>> valid for ppc, as I don't see the other arch listed.
>>>>
>>> Reason for that afaics: there is no PPC-EL5Client, thus the package from
>>> it could not be added to the server, thus python-imaging is still
>>> missing on PPC.
>>>
>> strange :-/
> python-imaging already in RHEL ppc. going to build for EPEL for ppc to
> see if it fixes deps. Probably it will not go
> past that first build as RHEL5.1 will include the package.
>
> Regards.
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> epel-devel-list mailing list
> epel-devel-list(a)redhat.com
>
https://www.redhat.com/mailman/listinfo/epel-devel-list