-
Notifications
You must be signed in to change notification settings - Fork 779
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
Appimage Island build fails #1993
Comments
VakarisZ
added
the
Bug
An error, flaw, misbehavior or failure in the Monkey or Monkey Island.
label
Jun 8, 2022
mssalvatore
added a commit
that referenced
this issue
Jun 9, 2022
When pipenv dumps the lock file to a requirements.txt, it does not include the `sys_platform` directive. This causes pip to attempt to install win32 packages, which fails. By using `pypenv sync --system` instead, only packages applicable to Linux are installed. Fixes #1993
cakekoa
added a commit
that referenced
this issue
Feb 27, 2023
Switch from using `pipenv sync --system` to using the requirements file generated from `pipenv requirements`. The `pipenv sync --system` command (added in #1993) does not work in newer versions of pipenv. It uses the python version of the system rather than the one specified by the --python flag. The `pipenv requirements` command has been added that only pulls from the Pipfile.lock file (pypa/pipenv#4959, pypa/pipenv#5200), and fixed to only dump out requirements for the appropriate system (see pypa/pipenv#5092).
cakekoa
added a commit
that referenced
this issue
Feb 27, 2023
Switch from using `pipenv sync --system` to using the requirements file generated from `pipenv requirements`. The `pipenv sync --system` command (added in #1993) does not work in newer versions of pipenv. It uses the python version of the system rather than the one specified by the --python flag. The `pipenv requirements` command has been added that only pulls from the Pipfile.lock file (pypa/pipenv#4959, pypa/pipenv#5200), and fixed to only dump out requirements for the appropriate system (see pypa/pipenv#5092).
cakekoa
added a commit
that referenced
this issue
Feb 27, 2023
Switch from using `pipenv sync --system` to using the requirements file generated from `pipenv requirements`. The `pipenv sync --system` command (added in #1993) does not work in newer versions of pipenv. It uses the python version of the system rather than the one specified by the --python flag. The `pipenv requirements` command has been added that only pulls from the Pipfile.lock file (pypa/pipenv#4959, pypa/pipenv#5200), and fixed to only dump out requirements for the appropriate system (see pypa/pipenv#5092).
mssalvatore
pushed a commit
that referenced
this issue
Feb 27, 2023
Switch from using `pipenv sync --system` to using the requirements file generated from `pipenv requirements`. The `pipenv sync --system` command (added in #1993) does not work in newer versions of pipenv. It uses the python version of the system rather than the one specified by the --python flag. The `pipenv requirements` command has been added that only pulls from the Pipfile.lock file (pypa/pipenv#4959, pypa/pipenv#5200), and fixed to only dump out requirements for the appropriate system (see pypa/pipenv#5092).
mssalvatore
pushed a commit
that referenced
this issue
Feb 28, 2023
Switch from using `pipenv sync --system` to using the requirements file generated from `pipenv requirements`. The `pipenv sync --system` command (added in #1993) does not work in newer versions of pipenv. It uses the python version of the system rather than the one specified by the --python flag. The `pipenv requirements` command has been added that only pulls from the Pipfile.lock file (pypa/pipenv#4959, pypa/pipenv#5200), and fixed to only dump out requirements for the appropriate system (see pypa/pipenv#5092).
mssalvatore
pushed a commit
that referenced
this issue
Mar 1, 2023
Switch from using `pipenv sync --system` to using the requirements file generated from `pipenv requirements`. The `pipenv sync --system` command (added in #1993) does not work in newer versions of pipenv. It uses the python version of the system rather than the one specified by the --python flag. The `pipenv requirements` command has been added that only pulls from the Pipfile.lock file (pypa/pipenv#4959, pypa/pipenv#5200), and fixed to only dump out requirements for the appropriate system (see pypa/pipenv#5092).
mssalvatore
pushed a commit
that referenced
this issue
Mar 1, 2023
Switch from using `pipenv sync --system` to using the requirements file generated from `pipenv requirements`. The `pipenv sync --system` command (added in #1993) does not work in newer versions of pipenv. It uses the python version of the system rather than the one specified by the --python flag. The `pipenv requirements` command has been added that only pulls from the Pipfile.lock file (pypa/pipenv#4959, pypa/pipenv#5200), and fixed to only dump out requirements for the appropriate system (see pypa/pipenv#5092).
mssalvatore
pushed a commit
that referenced
this issue
Mar 1, 2023
Switch from using `pipenv sync --system` to using the requirements file generated from `pipenv requirements`. The `pipenv sync --system` command (added in #1993) does not work in newer versions of pipenv. It uses the python version of the system rather than the one specified by the --python flag. The `pipenv requirements` command has been added that only pulls from the Pipfile.lock file (pypa/pipenv#4959, pypa/pipenv#5200), and fixed to only dump out requirements for the appropriate system (see pypa/pipenv#5092).
mssalvatore
pushed a commit
that referenced
this issue
Mar 1, 2023
Switch from using `pipenv sync --system` to using the requirements file generated from `pipenv requirements`. The `pipenv sync --system` command (added in #1993) does not work in newer versions of pipenv. It uses the python version of the system rather than the one specified by the --python flag. The `pipenv requirements` command has been added that only pulls from the Pipfile.lock file (pypa/pipenv#4959, pypa/pipenv#5200), and fixed to only dump out requirements for the appropriate system (see pypa/pipenv#5092).
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
We get an error building the appimage:
This error appears because when building the AppImage we first create a
requirements.txt
file. This file is created disregarding the the system markers.To Reproduce
Steps to reproduce the behavior:
Expected behavior
Create a virtual environment in the appimage and do
pipenv sync
in there instead of creating the requirements file.Machine version (please complete the following information):
Tasks
The text was updated successfully, but these errors were encountered: