Package Details: flood-git 4.8.2.r4.g812f351-1

Git Clone URL: (read-only, click to copy)
Package Base: flood-git
Description: A modern web UI for various torrent clients with a Node.js backend and React frontend.
Upstream URL:
Keywords: rtorrent
Licenses: GPL-3.0-only
Conflicts: nodejs-flood
Provides: nodejs-flood
Submitter: arshlinux
Maintainer: disastro
Last Packager: disastro
Votes: 13
Popularity: 0.000175
First Submitted: 2016-12-15 17:20 (UTC)
Last Updated: 2024-05-09 13:28 (UTC)

Latest Comments

1 2 3 Next › Last »

disastro commented on 2024-05-09 13:35 (UTC)

Fixed along with other small things, nodejs-husky not required, thank you

jholmer commented on 2024-05-09 12:14 (UTC)

Latest git is failing to build, giving the error sh: line 1: husky: command not found. Possibly a missing dependency on nodejs-husky, the build succeeds if I install that manually.

solsticedhiver commented on 2022-08-20 00:06 (UTC) (edited on 2022-08-20 00:41 (UTC) by solsticedhiver)

Could you fix the description field, please. No prepending of package name and flood is a web UI for more than rTorrent now. The site says "A modern web UI for various torrent clients with a Node.js backend and React frontend"

Same for the systemd service title

About the systemd.service file, one could harden it a bit (in line with what the wiki of flood says) with


disastro commented on 2022-02-17 18:51 (UTC)

Oh my god I can't believe I've missed that, obvious oversight. I'm just adding it to the backup field so a pacnew/pacsave file is created instead, like is intended and done with repo packages.

radu242 commented on 2022-02-16 16:18 (UTC) (edited on 2022-02-16 16:18 (UTC) by radu242)

Could the /etc/conf.d/flood file not be installed by this package? This overwrites the FLOOD_ARGS set in there on every update.

@disastro, I can send a patch doing a little more than removing the install -Dm644 "${srcdir}/flood.conf.d" "$pkgdir/etc/conf.d/flood" line in, if it helps.

disastro commented on 2021-03-20 15:49 (UTC)

Yeah that is what the old systemd service did too, but it will update unless you have overridden it. I guess I could also remove package.json so npm start would show a different error but either way it's not gonna work and there is really no reason for it to work, npm is not needed

emacsomancer commented on 2021-03-20 15:47 (UTC)

I must be starting it in a funny way. For whatever reason I used to start flood by running npm start in the /usr/lib/flood directory.

disastro commented on 2021-03-20 15:33 (UTC)

"node --use_strict dist/index.js" is not a command either the service file or /usr/bin/flood runs

emacsomancer commented on 2021-03-20 15:30 (UTC)

With the new version, I get an error when I try to (re)start:

> flood@4.5.0 start
> node --use_strict dist/index.js

  throw err;

Error: Cannot find module '/usr/lib/flood/dist/index.js'
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:815:15)
    at Function.Module._load (internal/modules/cjs/loader.js:667:27)
    at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:60:12)
    at internal/main/run_main_module.js:17:47 {
  requireStack: []

disastro commented on 2021-02-28 12:27 (UTC)

Soon did mean something else back a month ago but I've been and will be busy for another week at least, expect an update then. Basically have a near complete PKGBUILD already that lacks at least systemd testing.