Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

requirements-test.txt is missed in pypuppetdb-1.1.0.tar.gz from https://pypi.org/simple/pypuppetdb/ #158

Closed
sergiik opened this issue Sep 5, 2019 · 1 comment · Fixed by #159

Comments

@sergiik
Copy link

sergiik commented Sep 5, 2019

wget https://files.pythonhosted.org/packages/30/d0/15605e4476cb634251cc04e10ad50caaf566586b9cccf7de6c73014b5c4f/pypuppetdb-1.1.0.tar.gz#sha256=4a02dd45a398b30a940bb019b110bbd741c2a5a2772186a7c3c2faca0b0a41e3

$ tar -ztf pypuppetdb-1.1.0.tar.gz | grep requirements
pypuppetdb-1.1.0/requirements.txt

As you see there is no requirements-test.txt but it's required by setup.py

@bastelfreak
Copy link
Member

Hi,
do you have any idea why it is missing in the release? It exists within the git tag:

$ git checkout v1.1.0 
Note: switching to 'v1.1.0'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by switching back to a branch.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -c with the switch command. Example:

  git switch -c <new-branch-name>

Or undo this operation with:

  git switch -

Turn off this advice by setting config variable advice.detachedHead to false

HEAD is now at 19305fe Merge pull request #157 from bastelfreak/rel110
$ cat requirements-test.txt
-r requirements.txt
coveralls
bandit
coverage==4.0
mock==1.0.1
pytest==3.0.1
pytest-cov==2.2.1
pytest-pep8==1.0.5
cov-core==1.15.0
$

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants