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

Git Clone URL: https://aur.archlinux.org/flood-git.git (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: https://github.com/jesec/flood
Keywords: rtorrent
Licenses: GPL-3.0-only
Conflicts: nodejs-flood
Provides: nodejs-flood
Submitter: arshlinux
Maintainer: disastro
Last Packager: disastro
Votes: 13
Popularity: 0.000004
First Submitted: 2016-12-15 17:20 (UTC)
Last Updated: 2024-05-09 13:28 (UTC)

Required by (23)

Sources (6)

Latest Comments

1 2 3 Next › Last »

gokberkkocak commented on 2025-01-02 13:57 (UTC) (edited on 2025-01-02 13:57 (UTC) by gokberkkocak)

Upstream project started using pnpm after this commit and uses a pnpm-lock.yaml file in the repo. To not spend resolving dependencies and also build with exact same dependencies as the main branch, this PKGBUILD can be updated as such to use pnpm with --frozen-lockfile flag.

diff --git a/PKGBUILD b/PKGBUILD
index 64202c0..44ff97a 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -9,7 +9,7 @@ url='https://github.com/jesec/flood'
 license=('GPL-3.0-only')
 arch=('any')
 depends=('nodejs')
-makedepends=('git' 'npm')
+makedepends=('git' 'npm' 'pnpm')
 optdepends=('mediainfo')
 backup=('etc/flood/config.js'
         'etc/conf.d/flood')
@@ -37,17 +37,17 @@ pkgver() {
 build() {
     cd "${_pkgname}"

-    npm ci --cache "${srcdir}/npm-cache"
+    pnpm install --frozen-lockfile --cache "${srcdir}/npm-cache"
     npm run build
 }

 package() {
     install -dm755 "${pkgdir}/usr/lib/flood"
     install -D -m 644 "${srcdir}/${_pkgname}/package.json" "${pkgdir}/usr/lib/flood/"
-    install -D -m 644 "${srcdir}/${_pkgname}/package-lock.json" "${pkgdir}/usr/lib/flood/"
+    install -D -m 644 "${srcdir}/${_pkgname}/pnpm-lock.yaml" "${pkgdir}/usr/lib/flood/"

     cd "${pkgdir}/usr/lib/flood/"
-    npm ci --omit=dev --cache "${srcdir}/npm-cache" --ignore-scripts
+    pnpm install --frozen-lockfile --prod --cache "${srcdir}/npm-cache" --ignore-scripts

     cp -r "${srcdir}/${_pkgname}/dist"/* "${pkgdir}/usr/lib/flood/"

To fetch latest dependencies, --frozen-lockfile can be removed from the build() section.

CountMurphy commented on 2024-08-19 16:40 (UTC)

Was able to fix it locally by replacing 

 npm ci --cache "${srcdir}/npm-cache"

with 

npm install

CountMurphy commented on 2024-08-15 14:37 (UTC) (edited on 2024-08-15 14:48 (UTC) by CountMurphy)

Does not build with the latest commit:

npm error The `npm ci` command can only install with an existing package-lock.json or
npm error npm-shrinkwrap.json with lockfileVersion >= 1. Run an install with npm@5 or
npm error later to generate a package-lock.json file, then try again.

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

[Service]
NoNewPriviliges=true
ProtectSystem=full

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.

1 2 3 Next › Last »