Package Details: hydrus 670-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: 51
Popularity: 0.97
First Submitted: 2015-02-28 18:11 (UTC)
Last Updated: 2026-04-30 01:09 (UTC)

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 2 3 4 5 6 7 8 9 .. 15 Next › Last »

simona commented on 2023-07-12 08:29 (UTC)

==> Building documentation...
Traceback (most recent call last):
File "/bin/mkdocs", line 5, in <module>
from mkdocs.main import cli
ModuleNotFoundError: No module named 'mkdocs'
==> ERRORE: Si è verificato un errore in build().

classicsc commented on 2023-07-10 00:08 (UTC)

Since svg support was added recently (https://github.com/hydrusnetwork/hydrus/commit/799c85ea745d4b18affb8b80ad0d65d68d2e2e22), you now need the qt6-svg package otherwise hydrus-client will fail to start with this error:

Traceback (most recent call last):
  File "/opt/hydrus/hydrus/hydrus_client_boot.py", line 24, in <module>
    from hydrus.client.gui import QtInit
  File "/opt/hydrus/hydrus/client/gui/QtInit.py", line 142, in <module>
    from qtpy import QtSvg
  File "/usr/lib/python3.11/site-packages/qtpy/QtSvg.py", line 15, in <module>
    from PyQt6.QtSvg import *
ImportError: libQt6Svg.so.6: cannot open shared object file: No such file or directory

Critical boot error occurred! Details written to hydrus_crash.log in either db dir or user dir!

Score_Under commented on 2023-05-11 15:26 (UTC)

Thanks for the tip, I've confirmed the same on my own machine & added that to the list of required dependencies

guyven commented on 2023-05-11 14:57 (UTC)

After upgrading from version 526-1 to 527-1 I was unable to launch the application until I manually installed the qt6-multimedia package. This may need to be added to the dependency list, I have not done any in-depth investigation.

This was the error before adding this package:

v527, 2023/05/11 10:56:05: hydrus client started
v527, 2023/05/11 10:56:05: hydrus client failed
v527, 2023/05/11 10:56:05: Traceback (most recent call last):
File "/opt/hydrus/hydrus/hydrus_client_boot.py", line 244, in boot
from hydrus.client import ClientController
File "/opt/hydrus/hydrus/client/ClientController.py", line 43, in <module>
from hydrus.client.gui import ClientGUI
File "/opt/hydrus/hydrus/client/gui/ClientGUI.py", line 92, in <module>
from hydrus.client.gui.pages import ClientGUIManagement
File "/opt/hydrus/hydrus/client/gui/pages/ClientGUIManagement.py", line 39, in <module>
from hydrus.client.gui.canvas import ClientGUICanvas
File "/opt/hydrus/hydrus/client/gui/canvas/ClientGUICanvas.py", line 42, in <module>
from hydrus.client.gui.canvas import ClientGUICanvasMedia
File "/opt/hydrus/hydrus/client/gui/canvas/ClientGUICanvasMedia.py", line 7, in <module>
from qtpy import QtMultimediaWidgets as QMW
File "/usr/lib/python3.11/site-packages/qtpy/QtMultimediaWidgets.py", line 19, in <module>
from PySide6.QtMultimediaWidgets import *
ImportError: libQt6MultimediaWidgets.so.6: cannot open shared object file: No such file or directory

v527, 2023/05/11 10:56:05: hydrus client shut down

misagh commented on 2023-04-25 18:59 (UTC)

Thanks for finally making it happen. It's really appreciated. I will report if there are any issues.

joehillen commented on 2023-04-25 18:41 (UTC)

hydrus-docs-dummy

Thank you

Score_Under commented on 2023-04-23 16:04 (UTC) (edited on 2023-04-23 18:06 (UTC) by Score_Under)

The python2 issue was reported and fixed some time ago. I want to know what issue people are having now, after that migration. If the deps take a long time to install, that is surely only an issue when they are being removed between each build, but you should not be removing them if you intend to rebuild the software regularly.

As for mkdocs and its dependencies constantly breaking, I have never seen their compilation fail in recent memory, and barring quirks of my build system (i.e. no automatic dependency gathering and strict package name validation), neither has my build server:

I mentioned this last time and it bears repeating, this PKGBUILD already has a mechanism for excluding the docs makedeps: simply turn off docs in makepkg.conf. I have been asking people to tell me why this isn't an acceptable solution for them but all I've got are crickets, so what do I do with that?

Since this is clearly an issue that's still important to some regulars on here, maybe I'll try another tack: stub out docs in a readily available aur package that "provides" docs, and then split the package. Watch this space.

Upd: It's been split, and the dummy is in hydrus-docs-dummy. I've tried with yay and paru, and paru looks like it does a much better job (with yay showing a surprising failure to resolve dependencies), though neither seem to offer the alternative package by default.

misagh commented on 2023-04-23 05:36 (UTC)

I don't understand what more we can tell you: mkdocs and its dependencies are a mess that constantly break. They frequently won't compile / install, and even if they do, they significantly increase the installation time of this package as mkdocs wants to not only compile, but run a million tests.

Worst part is, this is not entirely your responsibility because it's the hydrus developer who has created this dependency. However, since they "officially" ship hydrus in such a way that all deps are included, they don't care that this dependency causes issues in this aur package, which makes it our problem, and we already told you what solution we want: remove mkdocs and all its dependencies.

Also, I don't believe its reasonable to expect people here to identify and debug the actual issue beyond what has already been reported, due to python2 being EOL, and many of those dependencies being unmaintained.

Again, just separate the docs and the application. For the past couple of years, many of us have had to do this manually with this package anyways.

Kirtai commented on 2023-04-13 03:23 (UTC)

Ok, it's working fine now. I had the version just before the one where you added the QT_API=pyqt6 setting. It worked with "QT_API=pyqt6" too but then I updated.

Thanks :)

Score_Under commented on 2023-04-13 01:33 (UTC)

@Kirtai, I experienced the same issue when testing, and it seems to be some bad interaction with the Pyside6 API. I tried to work around this by setting QT_API=pyqt6 in the hydrus-client script, but of course if you override QT_API yourself or if you run it via any other script, it may not work correctly. Can you tell me if you have an existing QT_API environment variable, and if you're running it through that script?

« First ‹ Previous 1 2 3 4 5 6 7 8 9 .. 15 Next › Last »