> -----Original Message----- > From: [email protected] > [mailto:[email protected]] > On Behalf Of Monty Taylor > Sent: 02 January 2012 13:25 > To: [email protected] > Subject: Re: [Openstack] Glance functional tests failing > > > > On 01/02/2012 12:56 PM, Ewan Mellor wrote: > >> -----Original Message----- From: Soren Hansen > >> [mailto:[email protected]] Sent: 02 January 2012 02:36 To: Ewan > >> Mellor Cc: Jay Pipes; [email protected] Subject: Re: > >> [Openstack] Glance functional tests failing > >> > >> 2012/1/1 Ewan Mellor <[email protected]>: > >>> How has a keystone change managed to break Glance when we're > >>> pinning > >> Keystone at a specific version? > >> > >> Could you try blowing away your .venv directory and trying again? > >> Perhaps there's a stale Keystone lying around in there. It won't > >> get replaced, because it already fulfills the stated requirement > >> (given by egg=keystone). Perhaps we should change pip-requires to > >> read "egg=keystone-dev" or something. > > > > This is a completely clean venv. I've checked though, and I ended up > > with the wrong version of keystone inside the venv. The changeset > > declaration inside pip-requires is observed by pip (it says "Could > > not find a tag or branch 'b9dd...', assuming commit) but when I look > > at .venv/src/keystone, the working tree is at current HEAD. It > > hasn't actually checked out that changeset. > > > > I see that the venv has a version of pip installed. My system one is > > 0.8.2 but the one that's been put into the venv is 0.7.2. I also > > notice that the code for checking out specific changesets is > > different between the two. Do you know what decided to put an old > > version of pip inside the venv? install_venv.py just calls > > easy_install pip, with no specified version number. I don't know if > > that's relevant to this case, but it seems worth a look. > > I think that is relevant. There is a bug in pip that was fixed in 0.8.1 > related to git revision numbers. We should make that be: > > easy_install "pip>1.0"
Yes, that fixed it. I don't know why it doesn't choose the latest version when you specify without a version number and you're in a fresh environment, but anyway, forcing it worked. http://review.openstack.org/2736. Cheers, Ewan. _______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : [email protected] Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
