Ask Your Question
1

What causes "versioning for this project requires either an sdist or an access to an upstream git repository" Exception when running stack.sh?

asked 2013-04-24 19:56:00 -0500

anonymous user

Anonymous

updated 2013-09-05 21:28:10 -0500

nickchase gravatar image

Hi, After running the script stack.sh i have the following exception raising from the setup.py file in openstack_dashboard/common:

versioning for this project requires either an sdist or an access to an upstream git repository

edit retag flag offensive close merge delete

Comments

1

Can you please provide more details about how you set up your devstack environment?

fifieldt gravatar imagefifieldt ( 2013-05-15 04:50:01 -0500 )edit

Did you try it with an updated build?

Keshy gravatar imageKeshy ( 2013-06-06 18:04:20 -0500 )edit

Are you still having this issue?

koolhead17 gravatar imagekoolhead17 ( 2013-08-12 13:15:25 -0500 )edit

I'm also getting this problem. When I invoke "keystone-all" I get a traceback ending in: Exception: Versioning for this project requires either an sdist tarball, or access to an upstream git repository.

Mark Parker gravatar imageMark Parker ( 2013-10-18 04:29:38 -0500 )edit

I got the same error when installing keystone-havana-stable from source.

jayesh gravatar imagejayesh ( 2013-11-20 07:50:28 -0500 )edit

1 answer

Sort by » oldest newest most voted
0

answered 2013-11-13 22:05:26 -0500

fifieldt gravatar image

This is from the following code:

openstack.common.setup.get_version(package_name, pre_version=None)[source]

    Get the version of the project. First, try getting it from PKG-INFO, if it exists. If it does, that means we’re in a distribution tarball or that install has happened. Otherwise, if there is no PKG-INFO file, pull the version from git.

    We do not support setup.py version sanity in git archive tarballs, nor do we support packagers directly sucking our git repo into theirs. We expect that a source tarball be made from our git repo - or that if someone wants to make a source tarball from a fork of our repo with additional tags in it that they understand and desire the results of doing that.

It basically means that during the install, there was no PKG-INFO file, and the connection to git to get the version failed.

This should not happen when installing devstack. If you encounter this error when installing devstack, it is almost certainly intermittent and you should simply run ./stack.sh again.

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

[hide preview]

Get to know Ask OpenStack

Resources for moderators

Question Tools

Stats

Asked: 2013-04-24 19:56:00 -0500

Seen: 3,098 times

Last updated: Nov 13 '13