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

Error during install on debian #241

Closed
tylla opened this issue Oct 5, 2018 · 7 comments
Closed

Error during install on debian #241

tylla opened this issue Oct 5, 2018 · 7 comments

Comments

@tylla
Copy link

tylla commented Oct 5, 2018

While trying the recommended install method for the latest version (0.17) I was stopped with an error:

    running install
    running build
    running install_data
    error: can't copy 'rabbitvcs/util/configspec/configspec.ini': doesn't exist or not a regular file

I suspect that setup.py should contain the real path of the configspec.ini so by correcting line 103:
["rabbitvcs/util/configspec/configspec.ini"]
into
["util/configspec/configspec.ini"]
the install completed successfully.

Is this valid, or there was some other error I missed and the install completed only by chance? :)
I am creating a PR in case my solution is really THE solution.

tylla added a commit to tylla/rabbitvcs that referenced this issue Oct 5, 2018
Solve an error with not existing configspec.ini during install on Debian system. See issue rabbitvcs#241 about details.
@freddii
Copy link

freddii commented Oct 23, 2018

the fix broke it for me:
copying MAINTAINERS -> /usr/share/doc/rabbitvcs
error: can't copy 'util/configspec/configspec.ini': doesn't exist or not a regular file

changing it back to rabbitvcs/util/configspec/configspec.ini solved it for me.

@karate
Copy link

karate commented Oct 29, 2018

Broke it for me as well on Ubuntu 18.04

@karate
Copy link

karate commented Oct 30, 2018

Also broken on Fedora 28.

I think this should be reverted.

@lofidevops
Copy link

This was reverted in ed9893e

@karate
Copy link

karate commented Oct 31, 2018

@adamplumb should we close this issue?

@adamplumb
Copy link

Sorry about this guys, I didn't actually test the PR before merging it in. I think we should close this.

@tylla
Copy link
Author

tylla commented Nov 1, 2018

Sorry from me as well.
Now if only I could find out why this worked on my system.

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

No branches or pull requests

5 participants