Package Details: fatrat-git 1.2.0_beta2.52.gedfd535-1

Git Clone URL: (read-only, click to copy)
Package Base: fatrat-git
Description: Qt Download/Upload Manager
Upstream URL:
Licenses: custom: GPL2 + complement
Conflicts: fatrat
Provides: fatrat
Submitter: pmattern
Maintainer: pmattern
Last Packager: pmattern
Votes: 2
Popularity: 0.000000
First Submitted: 2015-08-14 16:54 (UTC)
Last Updated: 2018-09-16 18:04 (UTC)

Pinned Comments

Latest Comments

commented on 2018-08-19 09:44 (UTC)


pmattern commented on 2017-01-20 20:47 (UTC)

> Installed curl-git with pacaur works as expected. That's a misunderstanding. I was proposing to install an other package making use of the syntax in a similar way to see whether the problem you're facing is restricted to fatrat-git. E. g. you could install cower from the AUR or build curl (!) from the official repositories, both of which are using the syntax in variable source. To build curl install abs, run binary abs as root, make a copy of /var/abs/core/curl and invoke makepkg therein. That aside I started wondering whether your shell may be the culprit as it's the shell expansion which is going wrong. So I tried zsh instead of my default bash but still couldn't reproduce your findings. Which one are you running and are you using some particular settings?

rig0rmortis commented on 2017-01-04 04:11 (UTC) (edited on 2017-01-04 04:12 (UTC) by rig0rmortis)

I'm using aura. Manually building with makepkg -si failed on dependency as well though, and I changed the PKGBUILD to explicitly state out `qt5-tools` `qt5-svg` `qt5-webengine` and I was able to install as expected. I unfortunately don't know too much more, I am only familiar with rpm specs and syntax has bit me before :) I'd be more than willing to try anything else out since I'm not actually sure what the issue is here. I've been using aura and/or manual makepkg for AUR packages for quite some time but I'm not sure if I've encountered another pkgbuild with that syntax. Installed curl-git with pacaur works as expected.

pmattern commented on 2017-01-02 20:55 (UTC)

The said syntax is frequently used in packages of both the official repositories and the AUR to name a source archive and its corresponding PGP key in variable source, see e. g. curl or cower, which made me adopt it in variables [make]depends. Maybe this does not make too much sense but technically it should not represent an issue either as all three variables in question are of type array. And indeed makepkg as well as yaourt and pacaur are accepting the current PKGBUILD without any problems here. So I'd tend to say it's an issue of the tool you're using to build. Could you state which one it is and/or try and have it build a package making use of the syntax in variable source like the said cower?

rig0rmortis commented on 2016-12-28 15:16 (UTC) (edited on 2016-12-28 15:22 (UTC) by rig0rmortis)

I get the following error trying to install this version, but `fatrat` succeeds... "The dependency 'qt5-' could not be found. You may need to search for a package to satisfy it." EDIT: looks like you might have left a typo: depends=('curl' 'libtorrent-rasterbar' 'pion-git' "qt5-"{tools,svg,webengine}) should be "qt5-{tools,svg,webengine}", no?

pmattern commented on 2016-12-27 21:41 (UTC)

Assuming you're talking about the web interface it simply hadn't been enabled so far but now it is. I couldn't get FatRat to compile against the current stable release of Pion so a VCS package was needed. Also, the invocation of fatrat-conf from the FAQ at seems to write the first directive only so ~/.config/Dolezel/fatrat.conf has to be complemented with a stanza like > [remote] > enable=true > port=<port> > password=<password> manually. That aside the web interface seems to work quite well here. To authenticate either admin or fatrat can be used. You may want to test at your side as well and report back.

Tweek commented on 2016-12-21 12:34 (UTC)

Hi, I have somes trouble with the webui pluggin. Do you have any issues ?

pmattern commented on 2016-11-01 21:45 (UTC)

BitTorrent may be the most important protocol for you but it cannot be considered this application's primary purpose. More importantly, stating "does not make sense" is pretty pointless without naming alternatives. Did you read the explanation in the commit messages why I've disabled BitTorrent? Unlike the latest commit message suggests FatRat upstream still isn't adjusted to libtorrent-rasterbar 1.1.x. Series 1.0.x still suffers from a rather important security hole as the corresponding fix hasn't made it into a release yet. Btw. I've asked for this in So instead of complaining you could e. g. replace your package libtorrent-rasterbar-109 with something more recent including the security fix. This would allow for re-enabling BitTorrent in this package in a reasonable way.

maxdevaine commented on 2016-11-01 19:07 (UTC)

Disable torrent function (-DWITH_BITTORRENT=OFF) in primary torrent download manager does not make sense ...

maxdevaine commented on 2016-07-19 21:49 (UTC)

Hi, please change dependency from "libtorrent-rasterbar<=1:1.0.9" to "libtorrent-rasterbar-109" (only until time when will be supported newest version of libtorrent) Thanks Max

pmattern commented on 2015-09-28 21:43 (UTC)

So I asked the author about those address woes: To no surprise still is the official homepage, lacking availability was just a server issue. Regarding the Git repositories both can be used, the one on GitHub being the more reliable one in the long run. Adjusted PKGBUILD accordingly. Hopefully all jimmies are unrustled now.

maxdevaine commented on 2015-09-28 12:39 (UTC)

@pmattern Yes, I thought that the url is a problem. Right url is on github. Lubos Dolezel is my buddy, so this I know. And other his projects have been moved to github too, for example Darling, Twinkle etc.: So, please change it in PKGBUILD. Thanks Max

pmattern commented on 2015-09-27 21:00 (UTC)

@kotyz It's true that isn't accessible since some days. But this looks rather like a server problem, it's still stated as official homepage on and similar subdomains like are still active as well. The web interface of isn't working either atm but the actual repo still does. All in all I'd agree that both URLs are something to keep an eye on but don't see the need to change anything so far. @maxdevaine What exactly makes you think this package is out-of-date? If you've got the URLs in mind see my notes above. Also, these aren't covered by that flag at all. As for the actual package version you are aware it's derived by pkgver() in PKBUILD (which is common practice regarding VCS packages in AUR)?

kotyz commented on 2015-09-24 09:16 (UTC)

Sources moved to github - Please change the source=() line in the PKGBUILD to source=("git://") Also, the project website at is inaccessible.