Package Details: bitwarden_rs-vault 2.12.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: 7
Popularity: 0.455778
First Submitted: 2018-07-13 18:10
Last Updated: 2019-10-10 18:47

Pinned Comments

mqs commented on 2019-02-09 20:32

Please report bugs with this unofficial release (server AND apps/extensions) here or at https://github.com/dani-garcia/bitwarden/issues/new first. Please DO NOT file issues at official bitwarden channels except you know exactly what you're doing.

It can be quite bad for the maintainer (kspearrin) to spend some effort in trying to find your issue, only to find out that the issue is not his fault at all but lies in bitwarden_rs. See also https://github.com/dani-garcia/bitwarden_rs/issues/336

Latest Comments

1 2 Next › Last »

mqs commented on 2019-09-13 23:24

@sauyon The missing python2 dependency is probably the fault of node-gyp (https://bugs.archlinux.org/task/62277?project=5&string=node-gyp ). I added it here and will keep it until it's added there.

I also added nodejs-lts-dubnium to the make-dependencies to make sure that an older version of nodejs is used, which should fix the issues encountered by @tohojo and @bjo (for me it does)

sauyon commented on 2019-09-03 21:17

I believe that python2 is at least a make dependency; the build is looking for /usr/bin/python2 and failing for me.

Also, using nodejs-lts-dubnium to work around the issues below works for me.

bjo commented on 2019-09-03 15:43

I had the same issue as tojoho and downgraded to node-carbon-lts

mqs commented on 2019-09-03 15:35

Sorry, I'm not near any archlinux system for another week, but I'll investigate/try as soon as i'm able to. did you try to downgrade nodejs (if thats possible for you)? have you tried the solution from your stackoverflow link?

Edit: i'm not into nodejs at all but did you try clearing your npm cache?

tohojo commented on 2019-09-03 15:01

It seems this is incompatible with nodejs 12?

I'm getting compile errors that point to this: https://stackoverflow.com/questions/57271334/npm-install-failing-saying-no-member-named-isneardeath

dcelasun commented on 2019-03-05 19:50

It works, thanks!

mqs commented on 2019-03-05 19:13

@dcelasun Could you try again? I added a fix which should work.

dcelasun commented on 2019-03-05 13:21

I just downloaded and extracted the snapshot.

A way to handle that case would be nice.

mqs commented on 2019-03-05 13:17

Can you share how you downloaded the package from the aur? if you do git clonehttps://aur.archlinux.org/bitwarden_rs-vault.git it should work just fine.

git submodule update (and therefore npm run sub:init) need to be run in a git repository[1]. The helpers I know (yay and the old pacaur) download packages via git clone, so this hasn't really mattered before.

I can add a patch file to 'disable' the submodule update run, if you still think that it is neccessary.

[1] Originally it meant updating the jslib submodule, but as the source code is downloaded as a tarball, it really only works because the AUR package is a cloned git repository.

dcelasun commented on 2019-03-05 10:12

Running makepkg fails for me while trying to init a git submodule:

> bitwarden-web@2.8.0 postinstall /home/dcelasun/builds/bitwarden_rs-vault/src/web-2.8.0
> npm run sub:init


> bitwarden-web@2.8.0 sub:init /home/dcelasun/builds/bitwarden_rs-vault/src/web-2.8.0
> git submodule update --init --recursive

fatal: not a git repository (or any of the parent directories): .git
npm ERR! code ELIFECYCLE
npm ERR! errno 128
npm ERR! bitwarden-web@2.8.0 sub:init: `git submodule update --init --recursive`
npm ERR! Exit status 128
npm ERR!
npm ERR! Failed at the bitwarden-web@2.8.0 sub:init 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/dcelasun/builds/bitwarden_rs-vault/src/npm-cache/_logs/2019-03-05T10_09_39_489Z-debug.log
npm ERR! code ELIFECYCLE
npm ERR! errno 128
npm ERR! bitwarden-web@2.8.0 postinstall: `npm run sub:init`
npm ERR! Exit status 128
npm ERR!
npm ERR! Failed at the bitwarden-web@2.8.0 postinstall 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/dcelasun/builds/bitwarden_rs-vault/src/npm-cache/_logs/2019-03-05T10_09_39_529Z-debug.log
==> ERROR: A failure occurred in build().

EDIT: As a workaround, after the build fails, I've removed the postinstall line from $srcdir/web-2.8.0/package.json and used makepkg -e which fixed the problem.