Package Details: paperless-ngx-venv 2.20.0-1

Git Clone URL: https://aur.archlinux.org/paperless-ngx-venv.git (read-only, click to copy)
Package Base: paperless-ngx-venv
Description: paperless-ngx: scan, index and archive all your physical documents
Upstream URL: https://docs.paperless-ngx.com/
Keywords: documents paperless
Licenses: GPL-3.0-or-later
Conflicts: paperless, paperless-ng, paperless-ngx
Provides: paperless, paperless-ngx-venv
Replaces: paperless-ngx
Submitter: AlphaJack
Maintainer: AlphaJack (atomicfs, shtrophic)
Last Packager: shtrophic
Votes: 29
Popularity: 0.027397
First Submitted: 2024-11-02 15:19 (UTC)
Last Updated: 2025-11-22 22:31 (UTC)

Pinned Comments

shtrophic commented on 2025-04-14 20:22 (UTC) (edited on 2025-04-14 20:32 (UTC) by shtrophic)

For people not using redis: there is now an "automated patching mechanism" that will instead use the next best fork of redis that is available on your system as the Requires= dependency in *.service. This way, anyone can use their favorite fork of it. Keep in mind that upstream does not explicitly say that forks of redis work as well, and this further makes the built paperless-ngx-venv package non-portable. Happy experimenting :)

Latest Comments

1 2 3 4 5 6 .. 14 Next › Last »

shtrophic commented on 2025-10-17 05:14 (UTC)

Yes :)

npreining commented on 2025-10-16 20:26 (UTC)

@shtrophic thanks for accepting the patch. Concerning Python packages, I guess you mean --system-site-packages --- yes, I didn't incldue that since I expected problems with versions, but I didn't know that there was another package with exactly that problems.

Thanks for your work on paperless, greatly appreciated!

shtrophic commented on 2025-10-16 19:06 (UTC) (edited on 2025-10-17 05:13 (UTC) by shtrophic)

Thanks for investigating. I've added your patch. About --system-site-packages: maybe you don't know, but before this PKGBUILD another one paperless-ngx existed that tried to use arch python packages as much as possible - causing many issues since upstream totally lags behind in many packages. The -venv version superseded it.

npreining commented on 2025-10-15 21:44 (UTC)

I found the reason for the problems with the builds. You use

uv venv -q "$srcdir/venv"

This is problematic because if the user running yay has already installed a python distribution using uv, with uv python, then uv will use this python. But later on it is supposed to run as user paperless which does not have the uv managed python installed.

I suggest calling instead

uv venv --clear --no-managed-python ....

to ensure that the system provided python is used, otherwise the one in .local/share/uv/python/ is used.

Adding this --no-managed-python ensures that the system python is used for creating the venv. The --clear ensures that a new .venv is created.

You could also depend on some Arch provided python packages, and include --system-site-packages, but this might be dangerous if some package is later removed from the user.

shtrophic commented on 2025-09-20 11:49 (UTC)

Sounds like some sort of umask issue. Can you reproduce this when built in a chroot?

AlexBocken commented on 2025-09-20 11:32 (UTC)

I can confirm that the current build process messes up the venv. Incorrect permissions prohibit the usage of the venv python in the installed location.

I could fix my error by manually rebuilding the venv in the /usr/lib/paperless location and using the paperless user.

AlexBocken commented on 2025-09-19 08:23 (UTC) (edited on 2025-09-19 08:28 (UTC) by AlexBocken)

Getting the following error on trying to migrate the database on upgrade:

sudo -u paperless paperless-manage migrate
Traceback (most recent call last):
  File "/usr/share/paperless/src/manage.py", line 10, in <module>
    execute_from_command_line(sys.argv)
    ~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^
  File "/usr/lib/python3.13/site-packages/django/core/management/__init__.py", line 442, in execute_from_command_line
    utility.execute()
    ~~~~~~~~~~~~~~~^^
  File "/usr/lib/python3.13/site-packages/django/core/management/__init__.py", line 416, in execute
    django.setup()
    ~~~~~~~~~~~~^^
  File "/usr/lib/python3.13/site-packages/django/__init__.py", line 24, in setup
    apps.populate(settings.INSTALLED_APPS)
    ~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.13/site-packages/django/apps/registry.py", line 91, in populate
    app_config = AppConfig.create(entry)
  File "/usr/lib/python3.13/site-packages/django/apps/config.py", line 193, in create
    import_module(entry)
    ~~~~~~~~~~~~~^^^^^^^
  File "/usr/lib/python3.13/importlib/__init__.py", line 88, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
           ~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "<frozen importlib._bootstrap>", line 1387, in _gcd_import
  File "<frozen importlib._bootstrap>", line 1360, in _find_and_load
  File "<frozen importlib._bootstrap>", line 1324, in _find_and_load_unlocked
ModuleNotFoundError: No module named 'drf_spectacular'

Weird thing is that I can confirm it to be installed in the venv, has the venv activation changed somehow?

npreining commented on 2025-05-25 09:34 (UTC) 

❯ pacman -Q | grep paperless
paperless-ngx-venv 2.16.2-1

❯ pacman -Qo $(sudo -u paperless which paperless-manage)
[sudo] password for norbert: 
/usr/bin/paperless-manage is owned by paperless-ngx-venv 2.16.2-1

AlD commented on 2025-05-25 09:12 (UTC)

Output of

$ pacman -Q | grep paperless
$ pacman -Qo $(sudo -u paperless which paperless-manage)

could be interesting.

npreining commented on 2025-05-25 09:07 (UTC)

Thanks for your comment - that worked:

❯ bash -c "source /usr/lib/paperless/bin/activate && python -c 'import django'" && echo success
success

Do I need to activate the env for the sudo run, too?

1 2 3 4 5 6 .. 14 Next › Last »