Package Details: bitwarden_rs-vault 2.10.1-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: 6
Popularity: 0.140450
First Submitted: 2018-07-13 18:10
Last Updated: 2019-06-04 13:11

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 »

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.

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

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.