Package Details: fatrat-git 1.2.0.b2.r60.g1b0dd1f6-1

Git Clone URL: (read-only, click to copy)
Package Base: fatrat-git
Description: Qt download and upload manager
Upstream URL:
Licenses: GPL-3.0-only
Conflicts: fatrat
Provides: fatrat
Submitter: pmattern
Maintainer: xiota
Last Packager: xiota
Votes: 2
Popularity: 0.000000
First Submitted: 2015-08-14 16:54 (UTC)
Last Updated: 2024-01-27 02:47 (UTC)

Pinned Comments

Latest Comments

1 2 Next › Last »

pmattern commented on 2023-03-09 06:40 (UTC)

Migrating the web interface to Boost.Beast is still wip. Branch develop oth does feature BitTorrent since yesterday. So all in all switching to that branch seemed like the better decision.

Compiling that branch I couldn't see the need to tweak build settings like linker flags. Feel free to let me know, if I missed something out.

<deleted-account> 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 ?