Package Details: bitwarden_rs-vault 2.2.0-1

Git Clone URL: https://aur.archlinux.org/bitwarden_rs-vault.git (read-only)
Package Base: bitwarden_rs-vault
Description: Integrates the Vault Web-Interface into bitwarden_rs.
Upstream URL: https://github.com/bitwarden/web
Keywords: bitwarden manager password passwordmanager vault web
Licenses: AGPL3
Conflicts: bitwarden_rs-vault-git
Submitter: mqs
Maintainer: mqs
Last Packager: mqs
Votes: 3
Popularity: 1.289425
First Submitted: 2018-07-13 18:10
Last Updated: 2018-09-13 21:14

Latest Comments

dobunzli commented on 2018-09-07 10:46

I can confirm that I had to activate a swap partition to be able to build this package with yay on a raspberry pi3 b+ with 1 Go of RAM.

Thanks for the work.

mqs commented on 2018-08-24 11:23

On my laptop and desktop pc I didn't notice this and on my arm machine with 1gb ram it just didn't finish building 2.1.1-1 after an hour or two, so I enabled swapping (I always have this ready for some other packages) for building 2.1.1-2 and it built quite quickly then ;) So I think this is the normal (even if perhaps not intended) behaviour. I didn't get your error because I canceled the build before it could appear...

Thanks for investigating this!

peoro commented on 2018-08-24 11:14

I'm afraid the explanation is simpler than I thought: the system I'm trying to build this package on was simply running out of ram...

node webpack --config webpack.config.js is taking a huge amount of ram and a lot of time (8 minutes and 1GB of resident memory when the system hangs it dies).

Is this a normal behavior?
I just found the same issue reported 3 hours ago on bitwarden/web: https://github.com/bitwarden/web/issues/250

peoro commented on 2018-08-24 10:27

I followed https://github.com/dani-garcia/bitwarden_rs/blob/master/BUILD.md#install-the-web-vault and it built without any problems.

I'll now try to manually run the steps of this package's PKGBUILD and see if I can find what's up.

mqs commented on 2018-08-24 09:28

I just looked over it and can't seem to find the reason. Even when comparing your build log to all of mine (I even build it successfully on an ntfs partition, where some other aur packages fail), I don't see anything going differently up to the error. The debug log seems to indicate that

gulp prebuild && cross-env NODE_ENV=production webpack --config webpack.config.js

fails on your machine but as it doesn't say why, I'm clueless.

The only thing I can remotely associate to our differences in the build are our linux kernels (I run 4.17.14 and 4.18.4 on x64 and 4.17.12 on armv7, all fairly recent kernels). But I can't really imagine that to be the reason. I also have npm 6.4.0-1,nodejs 10.9.0-1 and npm 6.3.0-1,nodejs 10.8.0-2 installed, respectively. Concerning the error, having installed the gulp package also deosn't make a difference for me.

One thing you could try is follow the instructions at https://github.com/dani-garcia/bitwarden_rs/blob/master/BUILD.md under "Install the web-vault" and see if that works. If it doesn't, try raising an issue on https://github.com/bitwarden/web.

peoro commented on 2018-08-24 08:41

I'm trying to build it on x64. Normally I'm using yay (it was getting the most recent release of this package, 2.1.1-2), but I also just tried cloning the AUR package in a clean directory and using makepkg directly as you suggested. The result is always the same.

I have npm 6.4.0-1, nodejs 10.9.0-1 (just upgraded them - yesterday I was using npm 6.3.0-1 and nodejs 10.8.0-2).

I uploaded the whole makepkg build log at https://pastebin.com/YHa6RUru and /home/peoro/.cache/yay/bitwarden_rs-vault/src/npm-cache/_logs/2018-08-24T07_47_45_614Z-debug.log at https://pastebin.com/B8xXZ3iQ

Thanks for these packages btw!

mqs commented on 2018-08-23 15:54

@peoro : It builds cleanly on x64 and armv7h for me, can you share some more information, e.g. your npm version and the whole build output (did you build with makepkg or some helper?)? Did you build it in a clean directory?

Did you download a snapshot or via git clone? If it's the first, try downloading the package with

git clone <https://aur.archlinux.org/bitwarden_rs-vault.git>

(without <>)

peoro commented on 2018-08-23 14:31

This package is not building for me:

> bitwarden-web@2.1.1 build:prod /home/peoro/.cache/yay/bitwarden_rs-vault/src/web-2.1.1
> gulp prebuild && cross-env NODE_ENV=production webpack --config webpack.config.js

[15:29:18] Using gulpfile ~/.cache/yay/bitwarden_rs-vault/src/web-2.1.1/gulpfile.js
[15:29:18] Starting 'clean'...
[15:29:18] Finished 'clean' after 20 ms
[15:29:18] Starting 'webfonts'...
[15:29:19] Finished 'webfonts' after 573 ms
[15:29:19] Starting 'prebuild'...
[15:29:19] Finished 'prebuild' after 420 μs
clean-webpack-plugin: /home/peoro/.cache/yay/bitwarden_rs-vault/src/web-2.1.1/build/* has been removed.
(node:12937) DeprecationWarning: Tapable.plugin is deprecated. Use new API on `.hooks` instead
(node:12937) DeprecationWarning: Tapable.apply is deprecated. Call apply on the plugin directly instead
DEPRECATION WARNING on line 3, column 8 of /home/peoro/.cache/yay/bitwarden_rs-vault/src/web-2.1.1/src/scss/plugins.scss:
Including .css files with @import is non-standard behaviour which will be removed in future versions of LibSass.
Use a custom importer to maintain this behaviour. Check your implementations documentation on how to create a custom importer.

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! bitwarden-web@2.1.1 build:prod: `gulp prebuild && cross-env NODE_ENV=production webpack --config webpack.config.js`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the bitwarden-web@2.1.1 build:prod script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/peoro/.cache/yay/bitwarden_rs-vault/src/npm-cache/_logs/2018-08-23T13_37_29_751Z-debug.log
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! bitwarden-web@2.1.1 dist: `npm run build:prod && gulp postdist`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the bitwarden-web@2.1.1 dist script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/peoro/.cache/yay/bitwarden_rs-vault/src/npm-cache/_logs/2018-08-23T13_37_29_816Z-debug.log
==> ERROR: A failure occurred in build().
    Aborting...
Error making: bitwarden_rs-vault

Anything I'm missing or should try?