Re: Swift traceback on Rawhide F17

2011-11-16 Thread Pete Zaitcev
On Thu, 17 Nov 2011 06:25:24 + Mark McLoughlin wrote: > > Unfortunately, no, I use the 1.4.0 that came with Rawhide. > > I'd love to use 1.4.3, if only I knew how to find the SRPM. > > Looks like it's not anywhere at Koji. > David - please and pretty please push your 1.4.3 packaging somewher

Re: Swift traceback on Rawhide F17

2011-11-16 Thread Mark McLoughlin
On Wed, 2011-11-16 at 22:00 -0700, Pete Zaitcev wrote: > On Wed, 16 Nov 2011 15:07:18 + > Mark McLoughlin wrote: > > > > LookupError: Entry point 'tempauth' not found in egg 'swift' (dir: > > > /usr/lib/python2.7/site-packages; protocols: paste.filter_factory, > > > paste.filter_app_factory

Re: openstack in EPEL status

2011-11-16 Thread Toshio Kuratomi
On Wed, Nov 16, 2011 at 06:20:14PM +, Pádraig Brady wrote: > On 11/16/2011 05:42 PM, Toshio Kuratomi wrote: > > About unittests, we probably want to either disable just the specific > > unittests or add a compat package with the newer versions of nose. RHEL6 > > seems to include 0.10.4 and t

Re: Swift traceback on Rawhide F17

2011-11-16 Thread Pete Zaitcev
On Wed, 16 Nov 2011 15:07:18 + Mark McLoughlin wrote: > > LookupError: Entry point 'tempauth' not found in egg 'swift' (dir: > > /usr/lib/python2.7/site-packages; protocols: paste.filter_factory, > > paste.filter_app_factory; entry_points: ) > > This is with 1.4.3? Is it David's packaging?

Re: openstack in EPEL status

2011-11-16 Thread Pádraig Brady
On 11/16/2011 07:11 PM, Steve Traylen wrote: > 2011/11/16 Pádraig Brady : >> python-nose is not new enough to build. The correct version wasn't >>specified in the spec though and the resultant error crashed RHEL once: >> https://bugzilla.redhat.com/show_bug.cgi?id=753505 >>I hacked to

Re: openstack in EPEL status

2011-11-16 Thread Pádraig Brady
On 11/16/2011 05:42 PM, Toshio Kuratomi wrote: > On Wed, Nov 16, 2011 at 10:09:36AM +, Pádraig Brady wrote: >> >> Yes it's awkward. Here are my rebuild notes for 0.6.8 on RHEL 6.2 >> >> python-nose is not new enough to build. The correct version wasn't >> specified in the spec though and th

Re: openstack in EPEL status

2011-11-16 Thread Steve Traylen
2011/11/16 Pádraig Brady : > python-nose is not new enough to build.  The correct version wasn't >    specified in the spec though and the resultant error crashed RHEL once: >      https://bugzilla.redhat.com/show_bug.cgi?id=753505 >    I hacked together an updated python-nose to allow running sqla

Re: openstack in EPEL status

2011-11-16 Thread Toshio Kuratomi
On Wed, Nov 16, 2011 at 10:09:36AM +, Pádraig Brady wrote: > > Yes it's awkward. Here are my rebuild notes for 0.6.8 on RHEL 6.2 > > python-nose is not new enough to build. The correct version wasn't > specified in the spec though and the resultant error crashed RHEL once: > ht

Re: Swift traceback on Rawhide F17

2011-11-16 Thread Mark McLoughlin
Hi Pete, On Tue, 2011-11-15 at 23:49 -0700, Pete Zaitcev wrote: > Hi, Alan: > > Does the following look familiar to you by any chance (after swift-init > main start): > > Traceback (most recent call last): > File "/usr/bin/swift-proxy-server", line 22, in > run_wsgi(conf_file, 'proxy-serv

Swift traceback on Rawhide F17

2011-11-16 Thread Pete Zaitcev
Hi, Alan: Does the following look familiar to you by any chance (after swift-init main start): Traceback (most recent call last): File "/usr/bin/swift-proxy-server", line 22, in run_wsgi(conf_file, 'proxy-server', default_port=8080, **options) .. File "/usr/lib/python2.7/

Re: openstack in EPEL status

2011-11-16 Thread Pádraig Brady
On 11/16/2011 12:53 AM, Toshio Kuratomi wrote: > Yep. It's not too hard to package parallel installable versions. Getting > software to use it is the hard part. You can use setuptools to set python to > find the correct versions (which is the recommendations in the guidelines I > believe). T