@shtrophic awesome! Thanks, I will take a look at it.
@AlphaJack I think we could convert this existing package into venv
one. But ultimately it is your decision whether to convert or create a new paperless-ngx-venv
AUR package.
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.89 |
First Submitted: | 2024-11-02 15:19 (UTC) |
Last Updated: | 2025-06-06 13:35 (UTC) |
« First ‹ Previous 1 2 3 4 5 6 7 8 9 .. 14 Next › Last »
@shtrophic awesome! Thanks, I will take a look at it.
@AlphaJack I think we could convert this existing package into venv
one. But ultimately it is your decision whether to convert or create a new paperless-ngx-venv
AUR package.
I came up with a patch (hack) to turn the dependencies into a virtual environment. It is rather large, so I cannot paste it here. I've uploaded it to:
https://liebender.dev/patches/paperless-ngx-venv/
See venv.patch
at the bottom. Other files have the patch applied.
I haven't thoroughly tested this; Services start and run fine though. Feel free to give this a try and let me know. Depending on whether or not this works well enough I can create a paperless-ngx-venv
AUR package, but feel free to apply this patch to this AUR package instead, if you prefer.
Same for Home Assistant.
Yes, a paperless-venv would be a solution. We did this with Salt and since then it just works.
Sorry, for the long silence, I was very stressed with lack of time lately. And to be honest, dealing with paperless-ngx it is a pain. My own instance is broken now for a while (again) and I just do not want to deal with it.
Given how much problematic paperless is with its dependencies, I think I will look into some alternative way to manage this (other than pacman dependencies). Maybe some python virtual environment or something, because this is unmanageable.
The paperless project is lacking behind with dependency versions, often by a lot. And their solution is to just lock the version in their requirements.txt.
I still want to run bare-metal without the use of docker, but the constant struggle with the required obsolete dependencies is just too much.
to be honest this is the first time I heard about valkey
so, what's your assessment?
I think this is more hackish solution than to add uvicorn to a IgnorePkg option in /etc/pacman.conf to prevent pacman from updating it.
0.25 in the mirrors was built against python 3.11, so downgrading it via downgrade
doesn't work. I'm considering to create a PKGBUILD for uvicorn-0.25, but ideally without conflicting uvicorn. That would require patching paperless-ngx to include uvicorn-0.25, however.
@Sir-Photch to be honest this is the first time I heard about valkey
, I was not aware that redis
changed license.
As for the uvicorn
v0.30, those patches look like dirty workaround to me. I think this is more hackish solution than to add uvicorn
to a IgnorePkg
option in /etc/pacman.conf
to prevent pacman from updating it.
paperless-ngx depends on python-django-soft-delete 1.0.13
, 1.0.14 is not yet supported and is causing issues.
https://github.com/paperless-ngx/paperless-ngx/issues/7486
Problem: https://github.com/paperless-ngx/paperless-ngx/issues/5494
paperless-ngx depends on uvicorn 0.25 (fixed dependency), 0.30 is causing issues.
However, a user came up with patches to remedy this problem: https://slonko.net/git/portage/plain/www-apps/paperless-ngx/files/, notably channels-4.1.patch
and uvicorn-0.26.patch
maybe it would make sense to apply these patches?
How does this package handle the switch of the repositories from redis
to valkey
?
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 ofredis
that is available on your system as theRequires=
dependency in*.service
. This way, anyone can use their favorite fork of it. Keep in mind that upstream does not explicitly say that forks ofredis
work as well, and this further makes the builtpaperless-ngx-venv
package non-portable. Happy experimenting :)