@luukvbaal: :o
I'll work on switching over to them, cool! :)
Git Clone URL: | https://aur.archlinux.org/jackett.git (read-only, click to copy) |
---|---|
Package Base: | jackett |
Description: | Use many torrent trackers with software that supports torznab/potato feeds. |
Upstream URL: | https://github.com/Jackett/Jackett |
Licenses: | GPL-2.0-or-later |
Submitter: | bgiesing |
Maintainer: | txtsd |
Last Packager: | txtsd |
Votes: | 54 |
Popularity: | 0.65 |
First Submitted: | 2015-06-20 00:06 (UTC) |
Last Updated: | 2024-12-27 06:44 (UTC) |
« First ‹ Previous 1 .. 4 5 6 7 8 9 10 11 12 13 Next › Last »
@luukvbaal: :o
I'll work on switching over to them, cool! :)
There are now native linux releases, mono is no longer required. https://github.com/Jackett/Jackett#install-on-linux-amdx64
@XMgVwrR6jCWDM75: 0.10.842 is a pre-release, not a realease.
@XMgVwrR6jCWDM75, this package tracks releases, not pre-releases.
@hashworks, this package tracks releases, not pre-releases.
You've got your Jackett set to update itself and probably have the pre-release check box ticked. If you want to avoid these conflicts, disable self update. You'd probably be fine just unchecking the pre-release updates box too.
Hey, I don't know if it is just my install, but it seems every time I am doing an update of jackett I am getting some conflicting file error message:
error: failed to commit transaction (conflicting files)
jackett: /usr/lib/jackett/Definitions/btworld.yml exists in filesystem
jackett: /usr/lib/jackett/Definitions/racing4everyone.yml exists in filesystem
jackett: /usr/lib/jackett/Definitions/rgu.yml exists in filesystem
jackett: /usr/lib/jackett/Definitions/sukebei-pantsu.yml exists in filesystem
jackett: /usr/lib/jackett/Definitions/sukebeinyaasi.yml exists in filesystem
jackett: /usr/lib/jackett/Definitions/xbytes2.yml exists in filesystem
Errors occurred, no packages were upgraded.<br>
Once I delete these files or do a pacman --force on the installation it works just fine. I have noticed this over a few upgrade cycles. Not that big deal, but not good for unattended installations.
@limaxray, thanks for catching and reporting that typo! @DGuyo, thanks for fixing it. Sorry! :)
@limaxray
Should be fixed now.
There's a typo on the last 2 lines of the package() function - {$pkgdir} instead of ${pkgdir} - this causes the jackett.conf files to not to be installed to sysusers.d and tmpfiles.d, so the jackett user and it's home directory are not created on new installs.
Pinned Comments
fryfrog commented on 2021-10-02 17:27 (UTC) (edited on 2023-01-09 18:30 (UTC) by fryfrog)
See also jackett-mono for platforms w/o net5 and jackett-bin for pre-compiled binaries.