Remote Installation Script fails
envgap__txoof__PaperPi-120
01 / FAILURE SIGNATURE
Captured in a clean container
ERROR: Could not open requirements file: [Errno 2] No such file or directory: 'requirements.txt'
02 / ENVIRONMENT RECIPE
- Base commit
406e0fb2fa26eadcab7e3f61ea53a3ff798b8450- Manifest
requirements.txt- Reproduce
python3 -m pip install -r requirements.txt- Run under trace
python3 -c "import importlib; m=importlib.import_module('paperpi'); print(getattr(m,'__version__','ok'))"
Reference environment fix used for admission
--- /dev/null +++ b/requirements.txt @@ -0,0 +1,10 @@ +# Generated from Pipfile.lock for PaperPi +# Core dependencies +argconfigparse==0.2.7 +epdlib==0.6.1.3 +pillow==10.0.0 +rpi.gpio==0.7.1 +spidev==3.6 + +# IT8951 display driver (git-based) +git+https://github.com/GregDMeyer/IT8951.git@67215164a7fc471bc6904f72ad55e51030905a97#egg=it8951
03 / ORIGINAL ISSUE TEXT
txoof/PaperPi #120 · read the original issue
**Describe the bug**
Install can't get past the PIP venv. Tried twice but I don't understand the error messages presented around the PIP dependencies.
**To Reproduce**
Steps to reproduce the behavior:
1. Run Install Script
2. See error below
```
USER@Argon:~ $ /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/txoof/PaperPi/main/install/remote_install.sh)"
installing PaperPi from branch: main
cloning git repo into /tmp/PaperPi_rY5ya
Cloning into '/tmp/PaperPi_rY5ya'...
remote: Enumerating objects: 2020, done.
remote: Counting objects: 100% (495/495), done.
remote: Compressing objects: 100% (274/274), done.
remote: Total 2020 (delta 265), reused 399 (delta 218), pack-reused 1525
Receiving objects: 100% (2020/2020), 96.65 MiB | 4.11 MiB/s, done.
Resolving deltas: 100% (944/944), done.
Updating files: 100% (807/807), done.
sucessfully cloned branch https://github.com/txoof/PaperPi.git into /tmp/PaperPi_rY5ya
/tmp/PaperPi_rY5ya
[sudo] password for USER:
==> /usr/bin/sudo /tmp/PaperPi_rY5ya/install/install.sh
checking if paperpi-daemon.service is running
paperpi-daemon.service not running
done
checking for required debian packages
found debian packages for PaperPi module debian_packages-crypto.txt
checking libcairo2
found debian packages for PaperPi module debian_packages-paperpi.txt
checking libtiff5
checking libopenjp2-7
checking python3-pip
checking libatlas-base-dev
checking libjpeg-dev
required packages installed
installing required python packages with pip3
successfully installed requirements
Removing existing installation found at /usr/local/paperpi
Installing files to /usr/local/paperpi
Creating virtual environment for paperpi in /usr/local/paperpi
/usr/local/paperpi /home/USER
Creating a virtualenv for this project...
Pipfile: /usr/local/paperpi/Pipfile
Using /usr/bin/python3.9 (3.9.2) to create virtualenv...
⠼ Creating virtual environment...created virtual environment CPython3.9.2.final.0-64 in 596ms
creator CPython3Posix(dest=/usr/local/paperpi/.venv, clear=False, no_vcs_ignore=False, global=False)
seeder FromAppData(download=False, pip=bundle, setuptools=bundle, wheel=bundle, via=copy, app_data_dir=/root/.local/share/virtualenv)
added seed packages: pip==23.2.1, setuptools==68.0.0, wheel==0.41.0
activators BashActivator,CShellActivator,FishActivator,NushellActivator,PowerShellActivator,PythonActivator
✔ Successfully created virtual environment!
Virtualenv location: /usr/local/paperpi/.venv
Pipfile.lock not found, creating...
Locking [packages] dependencies...
Building requirements...
Resolving dependencies...
Resolving dependencies...
✘ Locking Failed!
⠋ Locking...
CRITICAL:pipenv.patched.pip._internal.resolution.resolvelib.factory:Cannot install -r /tmp/pipenv-1f8cvnzx-requirements/pipenv-rdzy4lku-constraints.txt (line 3) because these package versions have conflicting dependencies.
[ResolutionFailure]: File "/usr/local/lib/python3.9/dist-packages/04 / LABELS
Labels checked by running the task · needs human review
No supported category has been assigned.
Label rules and the text that matched
[]
Historical install-only results are not EnvGap validation.
Default recipe; commands are ecosystem conventions, not issue-specific.
Preparation uses current registries. Historical package availability is not enforced here; execution metadata records this limitation separately from the oracle's date-bounding policy.