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

Git Clone URL: https://aur.archlinux.org/fatrat-git.git (read-only, click to copy)
Package Base: fatrat-git
Description: Qt download and upload manager
Upstream URL: https://github.com/LubosD/fatrat
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

« First ‹ Previous 1 2

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 https://github.com/arvidn/libtorrent/issues/1021#issuecomment-246963100. 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 fatrat.dolezel.info 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.: http://dolezel.info/projects So, please change it in PKGBUILD. Thanks Max

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

@kotyz It's true that fatrat.dolezel.info isn't accessible since some days. But this looks rather like a server problem, it's still stated as official homepage on http://www.dolezel.info/projects and similar subdomains like twinkle.dolezel.info are still active as well. The web interface of git.dolezel.info 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 - https://github.com/LubosD/fatrat/ Please change the source=() line in the PKGBUILD to source=("git://github.com/LubosD/fatrat.git") Also, the project website at http://fatrat.dolezel.info/ is inaccessible.

« First ‹ Previous 1 2