Package Details: hydrus 601-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: custom
Conflicts: hydrus-docs-dummy
Submitter: Score_Under
Maintainer: Score_Under
Last Packager: Score_Under
Votes: 40
Popularity: 0.89
First Submitted: 2015-02-28 18:11 (UTC)
Last Updated: 2024-12-04 21:42 (UTC)

Dependencies (40)

Required by (2)

Sources (5)

Latest Comments

« First ‹ Previous 1 .. 8 9 10 11 12 13

aelius commented on 2016-01-26 18:58 (UTC)

Looks like you might need to add more dependencies. Crash.log: ImportError: No module named lxml ImportError: No module named request extra/python2-lxml extra/python2-requests

aelius commented on 2015-10-05 21:24 (UTC)

OK, thanks for the input. This might be an upstream bug, but in case it isn't: 05:08:03 PM: Warning: Mismatch between the program and library build versions detected. The library used 3.0 (wchar_t,compiler with C++ ABI 1008,wx containers,compatible with 2.8), and wxPython used 3.0 (wchar_t,compiler with C++ ABI 1002,wx containers,compatible with 2.8). [1] 19178 segmentation fault (core dumped) hydrus-client

Score_Under commented on 2015-09-24 04:27 (UTC)

On two separate occasions I've intended to reply to you but ended up getting distracted and not hitting the reply button. I wouldn't be opposed to someone else cloning this package for a git version (or maybe I could make one myself?), but I would be hesitant to make/maintain one for a few reasons: 1. It's easy to do it yourself by removing "#commit=...." from the source list. If you're using an AUR automator like pacaur or yaourt, you can use the option to view the PKGBUILD before you update as your opportunity to make this change. 2. Picking by commit is an effective way to ensure that the source has not been tampered with 3. Sometimes the patches may leave the code inconsistent, e.g. if the Hydrus dev adds another "help" option 4. I would need to push the same code to two different repositories each time

aelius commented on 2015-09-16 22:41 (UTC)

What do you think about making a git version of this package, complete with your patches and other tweaks? While the hydrus git is exclusively used for releases, it would still be useful to have the aur-git version, to update hydrus the moment the dev releases an update. The git version would also require no maintenance on your part so long as the patches still apply.

aelius commented on 2015-09-02 03:27 (UTC)

If desktop-file-utils is not installed, an error is thrown during install (but the install succeeds and hydrus works fine). Perhaps you should add it as a requirement, suppress the error, or remove whatever is calling it.

Score_Under commented on 2015-02-28 18:42 (UTC)

This has a few differences from the original so I feel I should explain them here: * hydrus-client and hydrus-server are very small scripts which run the client and server respectively, rather than making you use "python2 /opt/hydrus/client.pyw". * the paths-in-opt patch file tweaks Hydrus' use of paths so that it doesn't choke when it's in a read-only part of /opt, and makes it store read-write data in ~/.local/share/hydrus * the running-the-server patch file alters how it runs the server from the client - instead of making it figure out which python executable to use (it chooses wrong anyway), it will just run the "hydrus-server" script

« First ‹ Previous 1 .. 8 9 10 11 12 13