Hi Paul,
Thanks for sharing this. It seems there is no straightforward solution for this kind of issue.
It seems there is some kind of intersection between epel and pip. Take TurboGears for example. epel7 does provide the rpm of TurboGears but doesn’t guarantee
it could be installed (epel5 didn’t have this issue, not sure for epel6). This is also applicable to TurboGears2 on epel7 which is supposed to be not old. Then I am not sure why we have TurboGears on epel7? I thought all the rpms on epel were supposed to be
able to be installed, but I might be wrong.
I have just installed TurboGears using pip (current TurboGears on pip is version 1.5.x). Probably we consider migrate our project to TurboGears 1.5.x or even
TurboGears2.
------------------------------
Best Regards
Jacky
From: epel-devel-bounces@lists.fedoraproject.org [mailto:epel-devel-bounces@lists.fedoraproject.org]
On Behalf Of Paul De Audney
Sent: Friday, 14 March 2014 3:59 PM
To: EPEL Development List
Subject: Re: EPEL Dependency broken for TurboGears-1.1.3-8.el7.noarch
When you use PIP make sure you also virtual-env for the application python libraries and environment. This will allow you to install the PIP packages into a isolated python environment for just that application
and not impact the 'system' python environment.
http://stackoverflow.com/questions/5844869/comprehensive-beginners-virtualenv-tutorial
Alternatively you could package the python libraries to RPM yourself if you have to deploy the same setup to many systems (at that point I assume you would be using a tool like chef or puppet, so hand building RPMs might be quicker than
rolling out a virtual-env to all your servers).
On Thu, Mar 13, 2014 at 8:49 PM, Zhiwei Zhu <z_zhu@wargaming.net> wrote:
Hi Christopher,
Got it. Thanks. Have a good day:)
------------------------------
Best Regards
Jacky
-----Original Message-----
From: epel-devel-bounces@lists.fedoraproject.org [mailto:epel-devel-bounces@lists.fedoraproject.org] On Behalf Of Christopher Meng
Sent: Friday, 14 March 2014 2:47 PM
To: EPEL Development List
Subject: Re: EPEL Dependency broken for TurboGears-1.1.3-8.el7.noarch
On Fri, Mar 14, 2014 at 11:40 AM, Zhiwei Zhu <z_zhu@wargaming.net> wrote:
>
> Hi Christopher,
>
>
>
> Thanks for your quick response. I understand the situation and Turbogears-1.1.3 may be old.
>
>
>
> I also tried Turbogears2 (which is TurboGears2-2.3.0) and got these errors:
>
> Error: Package: python-transaction-1.4.1-1.el7.noarch (epel)
>
> Requires: python-zope-interface
>
> Error: Package: python-zope-sqlalchemy-0.7.2-1.el7.noarch (epel)
>
> Requires: python-zope-interface
>
> Error: Package: python-kajiki-0.3.5-1.el7.noarch (epel)
>
> Requires: babel
>
> Error: Package: python-genshi-0.7-3.el7.x86_64 (epel)
>
> Requires: python-babel >= 0.8
>
> Error: Package: python-repoze-who-2.1-1.el7.noarch (epel)
>
> Requires: python-zope-interface
>
> Error: Package: TurboGears2-2.3.0-0.2.git6da6959.el7.noarch (epel)
>
> Requires: python-jinja2
>
> You could try using --skip-broken to work around the problem
>
> You could try running: rpm -Va --nofiles --nodigest
>
>
>
> Do you have any suggestion for this one?
>
> Thanks.
For all packages which can be found from pypi, I'd recommend using pip to install them.
I don't know the plan, maybe the missing packages will never get into EPEL7.
_______________________________________________
epel-devel mailing list
epel-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/epel-devel
EgzO3mXGcK
This e-mail may contain CONFIDENTIAL AND PROPRIETARY INFORMATION and/or PRIVILEGED AND CONFIDENTIAL COMMUNICATION intended solely for the recipient and, therefore, may not be retransmitted to any party outside of the recipient's organization without the prior
written consent of the sender. If you have received this e-mail in error please notify the sender immediately by telephone or reply e-mail and destroy the original message without making a copy. Wargaming.net accepts no liability for any losses or damages
resulting from infected e-mail transmissions and viruses in e-mail attachment. kgzO3mXGcg
_______________________________________________
epel-devel mailing list
epel-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/epel-devel