Package Details: hydrus 618-1

Git Clone URL: https://aur.archlinux.org/hydrus.git (read-only, click to copy)
Package Base: hydrus
Description: Danbooru-like image tagging and searching system for the desktop
Upstream URL: http://hydrusnetwork.github.io/hydrus/
Licenses: WTFPL
Conflicts: hydrus-docs-dummy
Submitter: Score_Under
Maintainer: Score_Under (turtletowerz)
Last Packager: turtletowerz
Votes: 42
Popularity: 0.68
First Submitted: 2015-02-28 18:11 (UTC)
Last Updated: 2025-04-17 02:36 (UTC)

Dependencies (39)

Required by (3)

Sources (5)

Pinned Comments

turtletowerz commented on 2025-02-05 23:14 (UTC)

The AUR package for JpegXL support is outdated and does not build. If you need JpegXL support, follow the instructions in the comment I posted to update the PKGBUILD.

Latest Comments

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

andiandi commented on 2021-12-25 14:38 (UTC)

Anyone else here who can not play videos within hydrus? Only getting "MPV is not available!" and a button to open videos externally. mpv and it's python bindings are installed.

hydrus 467-1 python-mpv 0.5.2-3 mpv 1:0.34.0-3

misagh commented on 2021-12-16 06:15 (UTC) (edited on 2021-12-16 06:16 (UTC) by misagh)

@Score_Under Thanks. The latest version of Hydrus has fixed this.

Score_Under commented on 2021-12-15 19:33 (UTC)

@misagh I don't think this is directly related to this package, but rather a problem with your installation of python qt5 bindings. If I were in your position I would check pacman -Qs qt5-python-bindings to see which qt5 bindings I have installed, then remove or reinstall them as necessary.

For me right now, I have these:

score@kirisame ~ % pacman -Qs qt5-python-bindings
local/pyside2 5.15.2-3 (qt qt5)
    Enables the use of Qt5 APIs in Python applications
local/python-pyqt5 5.15.6-2 (pyqt5)
    A set of Python bindings for the Qt5 toolkit

I tried removing pyside2 such that hydrus is definitely using pyqt5, and things still worked, so if possible I would say get python-pyqt5, make sure it's all up to date (not held back on an old AUR version or something), and remove the other bindings.

I don't really know your situation but I hope that leads somewhere helpful.

misagh commented on 2021-12-15 10:07 (UTC) (edited on 2021-12-15 10:08 (UTC) by misagh)

Hello, I was advised to report you this issue from the official Hydrus github repo: https://github.com/hydrusnetwork/hydrus/issues/1027

Currently the client is unusable for me due to this bug with the package.

wallcat commented on 2021-11-09 15:04 (UTC) (edited on 2021-11-09 15:04 (UTC) by wallcat)

Got this error after upgrading:

ImportError: libfmt.so.8: cannot open shared object file: No such file or directory

Solved by installing fmt from extra.

mser commented on 2021-08-05 07:38 (UTC)

Note regarding v449:

I’m skipping v449 since it’s an experimental release; if you do want to use it, simply edit the PKGBUILD yourself (your AUR helper should provide that option): change the pkgver and update the commit hash in the source array.

mser commented on 2021-05-07 00:29 (UTC) (edited on 2021-05-12 22:00 (UTC) by mser)

Update for v439:

The issue with python-pyqt5 has been resolved and I've changed the dependency back to qt5-python-bindings.

---OUTDATED INFORMATION---

Note about v438:

For v438, I have swapped out the qt5-python-bindings dependency (which is satisfied by both pyside2 and python-pyqt5) with pyside2 because the v438 release broke the ability to use python-pyqt5 (see here).

I will change the dependency back to qt5-python-bindings once that issue has been resolved (hopefully in v439).

In the meantime, Hydrus should just work if you have both packages installed, because it will default to use pyside2. But if you do have QT_API=PyQt5 set when launching Hydrus, remove that, as it won't work at the moment (and also isn't necessary anymore in general; this was a workaround to force the use of python-pyqt5 when Hydrus didn't work correctly with pyside2 in the past).

mser commented on 2021-04-12 23:37 (UTC)

@Amolith: Glad that fixed it. :)

Amolith commented on 2021-04-12 23:33 (UTC)

@mser

The only thing I can think of how that could happen is that it's loading the module from elsewhere; e.g., if you also installed NumPy via pip.

That would be correct haha. It looks like I forgot to create a virtual env before manually installing requirements for a different application. Thank you so much!

mser commented on 2021-04-12 23:27 (UTC)

@Amolith: From what I can see, your output looks fine (package versions seem correct too).

The error suggests an outdated NumPy version.

The only thing I can think of how that could happen is that it's loading the module from elsewhere; e.g., if you also installed NumPy via pip.

You can try:

➜  python -c "import numpy; print(numpy)"
<module 'numpy' from '/usr/lib/python3.9/site-packages/numpy/__init__.py'>

The path you see here is the one it should use if it you installed it via python-numpy package.

Also

➜  python -c "import sys; print(sys.path)"
['', '/usr/lib/python39.zip', '/usr/lib/python3.9', '/usr/lib/python3.9/lib-dynload', '/usr/lib/python3.9/site-packages']

To see the paths it tries to load modules from in general.

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