==> Synchronizing chroot copy [/home/leming/armv8/root] -> [leming]...done
==> Making package: vaultwarden-web 2025.10.1.0-1 (Sun Nov  2 03:24:32 2025)
==> Retrieving sources...
  -> Updating vaultwarden-web git repo...
==> WARNING: Skipping verification of source file PGP signatures.
==> Validating source files with sha512sums...
    vaultwarden-web ... Passed
==> Validating source files with b2sums...
    vaultwarden-web ... Passed
==> Making package: vaultwarden-web 2025.10.1.0-1 (Sun Nov  2 03:24:40 2025)
==> Checking runtime dependencies...
==> Installing missing dependencies...
[?25lresolving dependencies...
looking for conflicting packages...

Packages (4) liburing-2.12-1  mariadb-libs-12.0.2-1  postgresql-libs-18.0-1
             vaultwarden-1.34.3-1

Total Download Size:   15.84 MiB
Total Installed Size:  72.68 MiB

:: Proceed with installation? [Y/n] 
:: Retrieving packages...
 vaultwarden-1.34.3-1-aarch64 downloading...
 mariadb-libs-12.0.2-1-aarch64 downloading...
 postgresql-libs-18.0-1-aarch64 downloading...
 liburing-2.12-1-aarch64 downloading...
checking keyring...
checking package integrity...
loading package files...
checking for file conflicts...
checking available disk space...
:: Processing package changes...
installing liburing...
installing mariadb-libs...
Optional dependencies for mariadb-libs
    krb5: for gssapi authentication [installed]
installing postgresql-libs...
installing vaultwarden...

Configure the server via its environment variables in /etc/vaultwarden.env.

If vaultwarden is run at ports >1024, you should apply these systemd unit
options via a drop-in file:
[Service]
CapabilityBoundingSet=
AmbientCapabilities=
PrivateUsers=yes

If the service produces too much noise in your journal, you can redirect stdout
to /dev/null (vaultwarden will still also write to /var/log/vaultwarden.log if
configured to do so):
[Service]
StandardOutput=null

Create or edit drop-in file:
# systemctl edit vaultwarden

Start vaultwarden and enable its systemd service:
# systemctl enable --now vaultwarden
Optional dependencies for vaultwarden
    vaultwarden-web: for the web app
:: Running post-transaction hooks...
(1/4) Creating system user accounts...
Creating group 'vaultwarden' with GID 969.
Creating user 'vaultwarden' (vaultwarden user) with UID 969 and GID 969.
(2/4) Reloading system manager configuration...
  Skipped: Current root is not booted.
(3/4) Creating temporary files...
(4/4) Arming ConditionNeedsUpdate...
[?25h==> Checking buildtime dependencies...
==> Installing missing dependencies...
[?25lresolving dependencies...
looking for conflicting packages...

Packages (14) c-ares-1.34.5-1  libngtcp2-1.17.0-1  libuv-1.51.0-1
              node-gyp-11.5.0-1  nodejs-nopt-7.2.1-1  perl-error-0.17030-2
              perl-mailtools-2.22-2  perl-timedate-2.33-8  semver-7.7.3-1
              simdjson-1:4.1.0-1  zlib-ng-2.2.5-1  git-2.51.2-2
              nodejs-lts-krypton-24.11.0-2  npm-11.6.2-1

Total Download Size:    25.51 MiB
Total Installed Size:  137.87 MiB

:: Proceed with installation? [Y/n] 
:: Retrieving packages...
 nodejs-lts-krypton-24.11.0-2-aarch64 downloading...
 git-2.51.2-2-aarch64 downloading...
 npm-11.6.2-1-any downloading...
 node-gyp-11.5.0-1-any downloading...
 libuv-1.51.0-1-aarch64 downloading...
 c-ares-1.34.5-1-aarch64 downloading...
 simdjson-1:4.1.0-1-aarch64 downloading...
 libngtcp2-1.17.0-1-aarch64 downloading...
 zlib-ng-2.2.5-1-aarch64 downloading...
 perl-mailtools-2.22-2-any downloading...
 perl-timedate-2.33-8-any downloading...
 semver-7.7.3-1-any downloading...
 perl-error-0.17030-2-any downloading...
 nodejs-nopt-7.2.1-1-any downloading...
checking keyring...
checking package integrity...
loading package files...
checking for file conflicts...
checking available disk space...
:: Processing package changes...
installing perl-error...
installing perl-timedate...
installing perl-mailtools...
installing zlib-ng...
installing git...
Optional dependencies for git
    git-zsh-completion: upstream zsh completion
    tk: gitk and git gui
    openssh: ssh transport and crypto
    man: show help with `git command --help`
    perl-libwww: git svn
    perl-term-readkey: git svn and interactive.singlekey setting
    perl-io-socket-ssl: git send-email TLS support
    perl-authen-sasl: git send-email TLS support
    perl-cgi: gitweb (web interface) support
    python: git svn & git p4
    subversion: git svn
    org.freedesktop.secrets: keyring credential helper
    libsecret: libsecret credential helper [installed]
    less: the default pager for git [installed]
installing c-ares...
installing libngtcp2...
installing libuv...
installing simdjson...
installing nodejs-lts-krypton...
Optional dependencies for nodejs-lts-krypton
    npm: nodejs package manager [pending]
installing nodejs-nopt...
installing semver...
installing node-gyp...
Optional dependencies for node-gyp
    gcc: to build C++ modules [installed]
    make: to build C++ modules [installed]
    python: to build C++ modules
installing npm...
Optional dependencies for npm
    git: for dependencies using Git URL's [installed]
:: Running post-transaction hooks...
(1/4) Creating system user accounts...
Creating group 'git' with GID 968.
Creating user 'git' (git daemon user) with UID 968 and GID 968.
(2/4) Reloading system manager configuration...
  Skipped: Current root is not booted.
(3/4) Arming ConditionNeedsUpdate...
(4/4) Checking for old perl modules...
[?25h==> Retrieving sources...
==> WARNING: Skipping all source file integrity checks.
==> Extracting sources...
  -> Creating working copy of vaultwarden-web git repo...
Cloning into 'vaultwarden-web'...
done.
Switched to a new branch 'makepkg'
==> Starting prepare()...
⠙⠹⠸⠼⠴⠦⠧⠇⠏⠋⠙⠹⠸⠼⠴⠦⠧⠇⠏⠋⠙⠹npm warn ERESOLVE overriding peer dependency
⠸npm warn While resolving: eslint-plugin-rxjs-angular@2.0.1
npm warn Found: eslint@9.26.0
npm warn node_modules/eslint
npm warn   dev eslint@"9.26.0" from the root project
npm warn   23 more (@angular-eslint/builder, ...)
npm warn
npm warn Could not resolve dependency:
npm warn peer overridden eslint@"9.26.0" (was "^8.0.0") from eslint-plugin-rxjs-angular@2.0.1
npm warn node_modules/eslint-plugin-rxjs-angular
npm warn   dev eslint-plugin-rxjs-angular@"2.0.1" from the root project
⠸⠼⠴⠦⠧⠇⠏⠋⠙⠹⠸npm warn EBADENGINE Unsupported engine {
npm warn EBADENGINE   package: '@bitwarden/clients@0.0.0',
npm warn EBADENGINE   required: { node: '~22', npm: '~10' },
npm warn EBADENGINE   current: { node: 'v24.11.0', npm: '11.6.2' }
npm warn EBADENGINE }
⠼⠴⠦⠧⠇⠏⠋⠙npm warn skipping integrity check for git dependency ssh://git@github.com/electron/node-gyp.git
⠹⠸⠼⠴⠦⠧⠇⠏⠋⠙⠹⠸⠼⠴⠦⠧⠇⠏⠋⠙⠹⠸⠼⠴⠦⠧⠇⠏⠋⠙⠹⠸⠼⠴⠦⠧⠇⠏⠋⠙⠹⠸⠼⠴⠦npm warn deprecated lodash.isequal@4.5.0: This package is deprecated. Use require('node:util').isDeepStrictEqual instead.
⠦⠧⠇⠏⠋⠙⠹⠸npm warn deprecated inflight@1.0.6: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
⠼⠴⠦⠧⠇⠏⠋⠙⠹⠸⠼⠴⠦⠧⠇⠏⠋npm warn deprecated domexception@4.0.0: Use your platform's native DOMException instead
⠋⠙⠹⠸⠼⠴⠦⠧⠇⠏npm warn deprecated abab@2.0.6: Use your platform's native atob() and btoa() methods instead
⠏⠋⠙⠹⠸⠼⠴npm warn deprecated boolean@3.2.0: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.
⠴⠦⠧⠇⠏⠋⠙⠹⠸⠼⠴⠦⠧⠇⠏⠋⠙⠹⠸⠼npm warn deprecated @npmcli/move-file@2.0.1: This functionality has been moved to @npmcli/fs
⠴⠦⠧⠇⠏⠋⠙⠹⠸⠼⠴⠦⠧⠇⠏⠋⠙⠹⠸⠼⠴⠦⠧⠇⠏⠋⠙⠹⠸⠼⠴⠦⠧⠇⠏⠋npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported
⠋npm warn deprecated rimraf@2.6.3: Rimraf versions prior to v4 are no longer supported
⠋⠙npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported
⠙npm warn deprecated rimraf@3.0.2: Rimraf versions prior to v4 are no longer supported
⠹npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported
⠹npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported
⠹⠸⠼⠴⠦npm warn deprecated rimraf@3.0.2: Rimraf versions prior to v4 are no longer supported
⠦npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported
⠧⠇⠏⠋⠙⠹⠸⠼⠴⠦npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported
⠦npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported
⠦npm warn deprecated rimraf@3.0.2: Rimraf versions prior to v4 are no longer supported
⠦⠧⠇npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported
⠇npm warn deprecated rimraf@3.0.2: Rimraf versions prior to v4 are no longer supported
⠇npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported
⠇⠏⠋⠙⠹⠸⠼⠴npm warn deprecated rimraf@3.0.2: Rimraf versions prior to v4 are no longer supported
⠴npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported
⠦⠧npm warn deprecated glob@8.1.0: Glob versions prior to v9 are no longer supported
⠧⠇⠏⠋⠙⠹⠸⠼⠴⠦⠧⠇⠏npm warn deprecated rimraf@3.0.2: Rimraf versions prior to v4 are no longer supported
⠏npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported
⠏⠋npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported
⠋⠙⠹npm warn deprecated glob@8.1.0: Glob versions prior to v9 are no longer supported
⠹npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported
⠸⠼⠴⠦⠧⠇⠏⠋⠙⠹⠸⠼⠴⠦⠧⠇⠏⠋⠙⠹⠸⠼⠴⠦⠧⠇⠏⠋⠙⠹⠸⠼⠴⠦⠧⠇⠏⠋⠙⠹⠸⠼⠴⠦⠧⠇⠏⠋⠙⠹⠸⠼⠴⠦⠧⠇⠏⠋⠙⠹⠸⠼⠴⠦⠧⠇⠏⠋⠙⠹⠸⠼⠴⠦⠧⠇⠏⠋⠙⠹⠸⠼⠴⠦⠧⠇⠏⠋⠙⠹⠸⠼⠴⠦⠧⠇npm warn gitignore-fallback No .npmignore file found, using .gitignore for file exclusion. Consider creating a .npmignore file to explicitly control published files.
⠏⠋⠙⠹⠸⠼⠴⠦⠧⠇⠏⠋⠙⠹⠸⠼⠴⠦⠧⠇⠏⠋⠙⠹⠸⠼⠴⠦⠧⠇⠏⠋⠙⠹⠸⠼⠴⠦⠧⠇⠏⠋⠙⠹⠸⠼⠴⠦⠧⠇⠏⠋⠙⠹⠸⠼⠴⠦⠧⠇⠏⠋⠙⠹⠸⠼⠴⠦⠧⠇⠏⠋⠙⠹⠸⠼⠴⠦⠧⠇⠏⠋⠙⠹⠸⠼⠴⠦npm warn deprecated vis@4.21.0: Please consider using https://github.com/visjs
⠦⠧⠇⠏⠋⠙⠹⠸⠼⠴⠦⠧⠇⠏⠋⠙⠹⠸⠼⠴⠦⠧⠇⠏⠋⠙⠹⠸⠼⠴⠦⠧⠇⠏⠋⠙⠹⠸⠼⠴⠦⠧⠇⠏⠋⠙⠹⠸⠼⠴⠦⠧⠇⠏⠋⠙⠹⠸⠼⠴⠦⠧⠇⠏⠋⠙⠹npm error code 1npm error path /build/vaultwarden-web/src/vaultwarden-web/node_modules/bufferutil
⠸npm error command failed
⠸npm error command sh -c node-gyp-build
⠸npm error gyp info it worked if it ends with ok
npm error gyp info using node-gyp@11.2.0
npm error gyp info using node@24.11.0 | linux | arm64
npm error gyp ERR! find Python 
npm error gyp ERR! find Python Python is not set from command line or npm configuration
npm error gyp ERR! find Python Python is not set from environment variable PYTHON
npm error gyp ERR! find Python checking if "python3" can be used
npm error gyp ERR! find Python - executable path is ""
npm error gyp ERR! find Python - "" could not be run
npm error gyp ERR! find Python checking if "python" can be used
npm error gyp ERR! find Python - executable path is ""
npm error gyp ERR! find Python - "" could not be run
npm error gyp ERR! find Python 
npm error gyp ERR! find Python **********************************************************
npm error gyp ERR! find Python You need to install the latest version of Python.
npm error gyp ERR! find Python Node-gyp should be able to find and use Python. If not,
npm error gyp ERR! find Python you can try one of the following options:
npm error gyp ERR! find Python - Use the switch --python="/path/to/pythonexecutable"
npm error gyp ERR! find Python (accepted by both node-gyp and npm)
npm error gyp ERR! find Python - Set the environment variable PYTHON
npm error gyp ERR! find Python - Set the npm configuration variable python:
npm error gyp ERR! find Python npm config set python "/path/to/pythonexecutable"
npm error gyp ERR! find Python For more information consult the documentation at:
npm error gyp ERR! find Python https://github.com/nodejs/node-gyp#installation
npm error gyp ERR! find Python **********************************************************
npm error gyp ERR! find Python 
npm error gyp ERR! configure error 
npm error gyp ERR! stack Error: Could not find any Python installation to use
npm error gyp ERR! stack at PythonFinder.fail (/build/vaultwarden-web/src/vaultwarden-web/node_modules/node-gyp/lib/find-python.js:306:11)
npm error gyp ERR! stack at PythonFinder.findPython (/build/vaultwarden-web/src/vaultwarden-web/node_modules/node-gyp/lib/find-python.js:164:17)
npm error gyp ERR! stack at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
npm error gyp ERR! stack at async configure (/build/vaultwarden-web/src/vaultwarden-web/node_modules/node-gyp/lib/configure.js:27:18)
npm error gyp ERR! stack at async run (/build/vaultwarden-web/src/vaultwarden-web/node_modules/node-gyp/bin/node-gyp.js:81:18)
npm error gyp ERR! System Linux 6.17.5-2-aarch64-ARCH
npm error gyp ERR! command "/usr/bin/node" "/build/vaultwarden-web/src/vaultwarden-web/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
npm error gyp ERR! cwd /build/vaultwarden-web/src/vaultwarden-web/node_modules/bufferutil
npm error gyp ERR! node -v v24.11.0
npm error gyp ERR! node-gyp -v v11.2.0
npm error gyp ERR! not ok
⠸npm error A complete log of this run can be found in: /build/.npm/_logs/2025-11-02T08_24_48_619Z-debug-0.log
⠸==> ERROR: A failure occurred in prepare().
    Aborting...
==> ERROR: Build failed, check /home/leming/armv8/leming/build