Hi all:
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. Does the plone spec in EPEL have to change? Does the python-imaging in RHEL5 need modifying of some sort? Does python-imaging in EPEL/el4 need modifying (some tag I don't know of)? Or is there some black voodoo magic that is done to fix this?
Regards.
Joel Andres Granados wrote:
Hi all:
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. Does the plone spec in EPEL have to change? Does the python-imaging in RHEL5 need modifying of some sort? Does python-imaging in EPEL/el4 need modifying (some tag I don't know of)? Or is there some black voodoo magic that is done to fix this?
Regards.
Ok, the second mail talks about docutils instead of plone, but its the same situation as stated above. Any suggestions?
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.
Does the plone spec in EPEL have to change? Does the python-imaging in RHEL5 need modifying of some sort? Does python-imaging in EPEL/el4 need modifying (some tag I don't know of)? Or is there some black voodoo magic that is done to fix this?
The proper workaround would be to excludearch ppc for plone and other packages that require python-imaging.
The proper solution would be to ship python-imaging in EL5Server for PPC *or* ship it in EPEL5-PPC only. Going for the latter route might be a best short term fix. Just make EVR lower then the EL5 package, in case EL5Server starts shipping python-imaging sooner or later.
Does that sound like a plan?
CU kurd
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 :-/
Does the plone spec in EPEL have to change? Does the python-imaging in RHEL5 need modifying of some sort? Does python-imaging in EPEL/el4 need modifying (some tag I don't know of)? Or is there some black voodoo magic that is done to fix this?
The proper workaround would be to excludearch ppc for plone and other packages that require python-imaging.
The proper solution would be to ship python-imaging in EL5Server for PPC *or* ship it in EPEL5-PPC only. Going for the latter route might be a best short term fix. Just make EVR lower then the EL5 package, in case EL5Server starts shipping python-imaging sooner or later.
Does that sound like a plan?
Ok, Ill speak with Dan Riek and see what we can do on the RHEL side. Additionally I will build a new python-imaging on the el5 branch with the 1.1.5 version and a release that is lower than the one in RHEL that is only for ppc arch. In this way the situation is fixed immediately and if python-imaging is added to RHELppc in the near future I will dead the package again.
Regards
CU kurd
epel-devel-list mailing list epel-devel-list@redhat.com https://www.redhat.com/mailman/listinfo/epel-devel-list
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.
On 24.07.2007 15:56, 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.
What did you mean exactly? Is it available via RHN these days for PPC also? Then save yourself the work and don't build it for EPEL-PPC -- our scripts can't detect that case currently, but it's safe to ignore the mails in that case.
CU knurd
Thorsten Leemhuis wrote:
On 24.07.2007 15:56, 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.
What did you mean exactly? Is it available via RHN these days for PPC also? Then save yourself the work and don't build it for EPEL-PPC -- our scripts can't detect that case currently, but it's safe to ignore the mails in that case.
Its already in the nightlies for RHEL5.1. In the mean time I have build the python-imaging package in el5 for ppc (only), so I think that takes care of deps for now.
Regards.
Hi,
sorry, I missed that problem. We are going to try to fix that in 5.1 during the Beta.
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?
Regards,
Daniel
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.
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@redhat.com https://www.redhat.com/mailman/listinfo/epel-devel-list
epel-devel@lists.fedoraproject.org
-
Daniel Riek -
Joel Andres Granados -
Thorsten Leemhuis