Package Details: paperless-ngx-venv 2.15.3-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: 2.17
First Submitted: 2024-11-02 15:19 (UTC)
Last Updated: 2025-04-20 20:25 (UTC)

Required by (0)

Sources (10)

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

« First ‹ Previous 1 .. 6 7 8 9 10 11 12 13 Next › Last »

amo commented on 2023-03-13 18:09 (UTC)

Sorry for my lack of communication. I had a very busy time with some final examinations, but now everything is done and I am happy to have passed!

I know, 1.13.0 has been released a while ago already. I prepared the package update and noticed a small issue: die paperless.conf file is missing in this release. This was fixed already and the fix will be part of the next release I guess. Pushing a package update that is missing the config file is not a big deal for people only updating their paperless installations. It would require changes to the PKGBUILD which would need to be reverted in the next update. Besides, it creates a disproportionately big fuzz for users installing the package for the first time. For these reasons and because I think that the next release with the fix is coming very soon anyway, I prefer to hold back the update and wait for 1.13.1.

@Tweety: Yes, I noticed that too. The issue has been reported and fixed upstream already. I have asked twice for a new release upstream so that the AUR package can be updated to build without error again, but there has not been any reaction yet.

Tweety commented on 2023-03-13 16:27 (UTC)

Hi all,

I just tried that out-of-date version using yay installer. Dependency installation of python-django-celery-results fails due to an error in requirements/test.txt (I have noted a solution here: https://aur.archlinux.org/packages/python-django-celery-results ).

Looking forward to seeing 1.13 Version in the future...

greez2all Tweety

lorner commented on 2023-03-05 02:42 (UTC) (edited on 2023-03-05 02:46 (UTC) by lorner)

As of Mar 4, I'm still getting the billiard error with this package v1.12.2-1.

  • v1.12.2-1 includes python-celery (unversioned)
  • python-celery is currently 5.2.7 (5.3.0b2 released 2 weeks ago)
  • verified with celery --version
  • python-celery 5.2.7 includes python-billiard (unversioned)
  • python-billiard is current 4.1
  • Starting in 4.0, buf_t was removed from compat.py
  • celery 5.2.7 still has not updated to changes in python-billiard 4.0 and this throws an exception.

Solution: sudo pip3 install billiard==3.6.4.0 to downgrade package, as suggested below. Not sure how this will affect future automatic updates.

As of today, celery/conceurrency/asynpool.py still calls for import buf_t from billiard, but that has been removed from recent commits. Celery needs to either update dependency, or force to sync with 3.6.4.0

DudeDu commented on 2023-02-01 07:53 (UTC)

Thank you very much, sorry that i missed the comment about it. Thanks for your work!

amo commented on 2023-01-29 12:41 (UTC)

@DudeDu Your error mentions billiard. Please downgrade python-billiard as advised in the previous comments.

DudeDu commented on 2023-01-29 11:14 (UTC) (edited on 2023-01-29 11:15 (UTC) by DudeDu)

Hi amo,

the paperless-task-queue.service stopped working for me. Last few entries in systemctl status paperless-task-queue.service are:
File "<frozen importlib._bootstrap>", line 688, in _load_unlocked File "<frozen importlib._bootstrap_external>", line 883, in exec_module File "<frozen importlib._bootstrap>", line 241, in _call_with_frames_removed File "/usr/lib/python3.10/site-packages/celery/concurrency/prefork.py", line 19, in <module> from .asynpool import AsynPool File "/usr/lib/python3.10/site-packages/celery/concurrency/asynpool.py", line 29, in <module> from billiard.compat import buf_t, isblocking, setblocking : ImportError: cannot import name 'buf_t' from 'billiard.compat' (/usr/lib/python3.10/site-packages/billiard/compat.py)

amo commented on 2023-01-25 17:50 (UTC)

I just pushed the update to 1.12.0. If you created a temporary symlink for nltk-data with the previous release, you can now unlink /usr/local/share/nltk_data.

amo commented on 2023-01-14 14:57 (UTC) (edited on 2023-01-14 16:19 (UTC) by amo)

Thank you @pipep for your report, you were absolutely right about the error. Somehow it did not come up on my testing machine but on my production machine it did...

Simply disabling the NLTK-feature sounds more like a sad workaround. A real solution is to install the python-nltk and nltk-data packages. I just added them to the dependencies and pushed a new package release. They should install as paperless dependencies when updating paperless-ngx.

Unfortunately, we have to add one more (hopefully just temporary) step to make it work: ln -s /usr/share/nltk_data /usr/local/share/nltk_data sets a symlink from the path where paperless expects the nltk_data to be to where it actually is installed. The installation path of the archlinux package is correct according to the nltk documentation and in my opinion paperless-ngx should change the default path where it expects nltk_data to the correct one. I already created a pull request, we will see if they accept it. If so, we can remove the symlink. Another valid option is probably to set the PAPERLESS_NLTK_DIR in paperless.conf, but I did not test it.

pipep commented on 2023-01-14 09:20 (UTC) (edited on 2023-01-14 09:21 (UTC) by pipep)

I solved the error inserting PAPERLESS_ENABLE_NLTK=false in /etc/paperless.conf

amo commented on 2023-01-14 08:22 (UTC)

@pipep I'm sorry but I can't reproduce the error. Neither by dropping a file onto the web UI nor by putting a file into the consume folder. I don't have python-ntlk installed.