Arch Linux User Repository

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.

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.

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

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.

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

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

internal/modules/cjs/loader.js:818
  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 {
  code: 'MODULE_NOT_FOUND',
  requireStack: []
}

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.

Thanks I'll look into changing to it soon

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.

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.

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

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 the seedbox user.

/etc/tmpfiles.d/flood.conf:

d   /var/lib/flood/server/db    0750    seedbox   seedbox

/etc/systemd/system/flood.service.d/override.conf:

[Service]
User=seedbox

-  npm install --production
+  npm install
+  npm run build

Done

(Fix included)

Hiya,

Flood now fails to start after recent upstream updates (installation completes successfully):

# systemctl status flood.service

flood.service - Flood rTorrent Web UI
   Loaded: loaded (/etc/systemd/system/flood.service; disabled; vendor preset: disabled)
   Active: failed (Result: exit-code) since Sat 2018-05-26 12:05:13 BST; 4s ago
   Process: 16395 ExecStart=/usr/bin/npm start --production /srv/flood (code=exited, status=1/FAILURE)
   Main PID: 16395 (code=exited, status=1/FAILURE)

May 26 12:05:13 HOST npm[16395]: npm ERR! errno 1
May 26 12:05:13 HOST npm[16395]: npm ERR! flood@1.0.0 start: `node server/bin/start.js "/srv/flood"`
May 26 12:05:13 HOST npm[16395]: npm ERR! Exit status 1
May 26 12:05:13 HOST npm[16395]: npm ERR!
May 26 12:05:13 HOST npm[16395]: npm ERR! Failed at the flood@1.0.0 start script.
May 26 12:05:13 HOST npm[16395]: npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
May 26 12:05:13 HOST npm[16395]: npm ERR! A complete log of this run can be found in:
May 26 12:05:13 HOST npm[16395]: npm ERR!     /srv/flood/.npm/_logs/2018-05-26T11_05_13_249Z-debug.log
May 26 12:05:13 HOST systemd[1]: flood.service: Main process exited, code=exited, status=1/FAILURE
May 26 12:05:13 HOST systemd[1]: flood.service: Failed with result 'exit-code'.

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:

-  npm install --production
+  npm install
+  npm run build

I've compiled this updated PKGBUILD locally & have successfully got Flood running.

Thank you

^_^