Search Criteria
Package Details: flood-git 4.7.0.r55.gce4b523d-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/flood-git.git (read-only, click to copy) |
---|---|
Package Base: | flood-git |
Description: | Flood: A web UI for rTorrent with a Node.js backend and React frontend. |
Upstream URL: | https://github.com/jesec/flood |
Keywords: | rtorrent |
Licenses: | GPL3 |
Conflicts: | nodejs-flood |
Provides: | nodejs-flood |
Submitter: | arshlinux |
Maintainer: | disastro |
Last Packager: | disastro |
Votes: | 12 |
Popularity: | 0.26 |
First Submitted: | 2016-12-15 17:20 (UTC) |
Last Updated: | 2022-02-17 18:54 (UTC) |
Dependencies (4)
- nodejs (nodejs6-bin, nodejs-git, nodejs-nightly, fnm, nodejs-lts-fermium, nodejs-lts-gallium)
- git (git-git, git-vfs, git-run-command-patch-git) (make)
- npm (nodejs6-bin, nodejs-nightly) (make)
- mediainfo (mediainfo-git) (optional)
Latest Comments
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 https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=flood-git#n62, 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:
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.
disastro commented on 2021-01-20 18:01 (UTC)
Thanks I'll look into changing to it soon
PlainTextField commented on 2021-01-20 17:45 (UTC) (edited on 2021-01-20 17:45 (UTC) by PlainTextField)
There is a more active fork here: https://github.com/jesec/flood
It removes the Python 2 dependency for node-gyp and uses more recent Node.js packages. It even offers fully static binaries.
disastro commented on 2019-08-18 10:32 (UTC) (edited on 2019-08-18 21:38 (UTC) by disastro)
I've adopted the package and am working on it, stay tuned
EDIT: So, flood still seems kind of a mess to package but I've tried to make it as as sane as possible. It's only been tested lightly so some issues might be lurking around. I couldn't get any to show up though.
solsticedhiver commented on 2018-11-23 19:53 (UTC)
The build fails on ARM when you use nodejs aka v11. This needs to use nodejs-lts-dubnium (v10 LTS)
May be nodejs-lts-dubnium should even be a dep for this package ? Did anyone on x86_64 build it with nodejs v11 ??
arshlinux commented on 2018-07-12 16:07 (UTC) (edited on 2018-07-12 16:09 (UTC) by arshlinux)
For Flood being able to move rTorrent downloads, I suggest to override the
flood
user so it the same user that rTorrent is running under. Let's say it's theseedbox
user./etc/tmpfiles.d/flood.conf
:/etc/systemd/system/flood.service.d/override.conf
:arshlinux commented on 2018-07-10 22:29 (UTC) (edited on 2018-07-12 15:50 (UTC) by arshlinux)
Done
XG_SiNGH commented on 2018-05-26 22:00 (UTC) (edited on 2018-05-26 22:30 (UTC) by XG_SiNGH)
(Fix included)
Hiya,
Flood now fails to start after recent upstream updates (installation completes successfully):
My research has led me here;
https://github.com/jfurrow/flood/issues/510
https://github.com/jfurrow/flood#compiling-assets-and-starting-the-server
It seems npm has removed the --production flag, & so we need to "run build" manually.
We need to update the PKGBUILD like this:
I've compiled this updated PKGBUILD locally & have successfully got Flood running.
Thank you
^_^
arshlinux commented on 2017-05-29 21:25 (UTC)
arshlinux commented on 2017-05-23 22:33 (UTC)
XG_SiNGH commented on 2017-01-09 23:50 (UTC)