-
Notifications
You must be signed in to change notification settings - Fork 45
Scaffolding update #109
Comments
I've ran into this issue too. And the new pipfile got me through the locking process. However, I ran into an issue during the web packing (
|
I have the same issue here. Could you manage to sort it somehow? Or could anybody give a hint. Thank you very much. |
Use the original Pipfile but change
to
|
Thank you very much for your reply. Unfortunately, that does not resolve the problem. Still get: Any suggestions? |
I also added this |
Might not be the most elegant solution but I got past it by removing 2 lines from this file lines 24 and 114. You can find the file on your virtualenv folder. |
To install
In the Pipfile, you should add (we will fix it soon in
Using |
Python 3.6 was end of life in December 2021, so it would be really good to move to a more recent version. Using a manually created virtual environment and removing |
With inveniosoftware/invenio-assets#146 merged, I made the following change to --- a/Pipfile
+++ b/Pipfile
@@ -4,7 +4,8 @@ verify_ssl = true
name = "pypi"
[packages]
-invenio = { version = ">=3.4.0,<3.5.0", extras = ["base", "auth", "metadata", "files", "postgresql", "elasticsearch7" ]}
+invenio = { version = ">=3.5.0a4", extras = ["base", "auth", "metadata", "files", "postgresql", "elasticsearch7" ]}
+invenio-assets = ">= 1.3.0"
lxml = ">=4.3.0,<5.0.0"
marshmallow = ">=3.0.0,<4.0.0"
uwsgi = ">=2.0" I think this implies the real fix is:
|
Describe the bug
After scaffolding the skeleton on 01-getting-started when running the script bootstrap.sh, the python virtual environment stays locking "forever".
The Pipfile in the skeleton might need to be updated.
Steps to Reproduce
cookiecutter gh:inveniosoftware/cookiecutter-invenio-instance -c v3.4 --no-input
./scripts/bootstrap
Expected behavior
Finish installing pipenv dependencies and lock Pipfile.
Aditional Information
I noticed it isn't just about my environment because it also happens on the virtualbox image you provided.
After trying to run
pipenv install --skip-lock
you get the errorDeleting the provided Pipfile and creating one with the dependencies as they appeared solved the problem.
Here is the new Pipfile I used.
The text was updated successfully, but these errors were encountered: