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

[BUG] pip upgrade to 0.9.3 results in Read-only file system error #1218

Open
2 tasks done
dave0003 opened this issue Jan 22, 2025 · 3 comments
Open
2 tasks done

[BUG] pip upgrade to 0.9.3 results in Read-only file system error #1218

dave0003 opened this issue Jan 22, 2025 · 3 comments
Labels
bug Something isn't working

Comments

@dave0003
Copy link

Describe the bug
After downloading new requirements, upgrading, and then upgrading whoogle-search with pip, the whoogle service won't start anymore, but gives a "Read-only file system error." Doing a fresh install of 0.9.3 gives similar results, with only a slightly different error.

To Reproduce
Steps to reproduce the behavior:

  1. wget https://raw.githubusercontent.com/benbusby/whoogle-search/main/requirements.txt
  2. pip install -r requirements.txt --upgrade
  3. pip install whoogle-search --upgrade
  4. (restart whoogle service, systemctl restart whoogle for me)

Deployment Method

  • pip/pipx

Version of Whoogle Search

  • Latest build from [source] (i.e. GitHub, Docker Hub, pip, etc)
  • 0.9.3

Desktop (please complete the following information):

  • N/A

Smartphone (please complete the following information):

  • N/A

Additional context
After doing a pip upgrade, this is the error in syslog when the whoogle service tries to start.

: Traceback (most recent call last):
:   File "/home/david/whoogle/bin/whoogle-search", line 5, in <module>
:     from app.routes import run_app
:   File "/home/david/whoogle/lib/python3.11/site-packages/app/__init__.py", line 166, in <module>
:     os.symlink(full_cb_path, build_path)
: OSError: [Errno 30] Read-only file system: '/home/david/whoogle/lib/python3.11/site-packages/app/static/css/light-theme.css' -> '/home/david/whoogle/lib/python3.11/site-packages/app/static/build/light-theme.172370c9.css'
: whoogle.service: Main process exited, code=exited, status=1/FAILURE
: whoogle.service: Failed with result 'exit-code'.

The "light-theme.172370c9.css" doesn't exist.

After doing a fresh pip install, this is the error in syslog when the whoogle service tries to start.

: Traceback (most recent call last):
:   File "/home/david/whoogle/bin/whoogle-search", line 5, in <module>
:     from app.routes import run_app
:   File "/home/david/whoogle/lib/python3.11/site-packages/app/__init__.py", line 91, in <module>
:     os.makedirs(app.config['CONFIG_PATH'])
:   File "<frozen os>", line 225, in makedirs
: OSError: [Errno 30] Read-only file system: '/home/david/whoogle/lib/python3.11/site-packages/app/static/config'
: whoogle.service: Main process exited, code=exited, status=1/FAILURE
: whoogle.service: Failed with result 'exit-code'.

In this case, the whole "config" directory is missing.

(pathnames slightly sanitized)

@dave0003 dave0003 added the bug Something isn't working label Jan 22, 2025
@benbusby
Copy link
Owner

Are you using a virtual environment when installing whoogle? I believe the read-only filesystem issue only happens when you're installing the package outside of a venv (not sure why previous versions hadn't thrown this error though). If the upgrade command was performed outside of the virtual environment, it would ignore that it was an "upgrade" and just install it regularly.

@dave0003
Copy link
Author

I am using a virtual environment, but I am installing everything while inside the virtual environment.

For example:

python3 -m venv /home/david/whoogle
cd /home/david/whoogle
source bin/activate
pip install whoogle-search --upgrade

@benbusby
Copy link
Owner

Hmm ok. I haven't been able to reproduce this on any of my machines yet, but I'll try to look into it more later.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants