Package Details: bitwarden_rs-vault 2.16.2-1

Git Clone URL: https://aur.archlinux.org/bitwarden_rs-vault.git (read-only, click to copy)
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-bin, bitwarden_rs-vault-git
Submitter: mqs
Maintainer: mqs
Last Packager: mqs
Votes: 11
Popularity: 0.47
First Submitted: 2018-07-13 18:10
Last Updated: 2020-10-11 16:59

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_rs/issues/new?template=bug_report.md 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 3 4 Next › Last »

pinembour commented on 2020-10-14 11:05

@mqs Okay after a closer look the bulid step took a split second to finish with no log whatsoever so the problem was there. It seems my npm package got corrupted, so I reinstalled it and it works fine now. Thank you for your time

mqs commented on 2020-10-14 09:45

@pinembour I just build the package from scratch and I don't have your issues. The build directory is created relatively late into the process, so if something failed it may not be there for the next step.

Could you share some logs and what exact commands you used to build the package?

pinembour commented on 2020-10-14 06:07

I'm getting an error on this version ( 2.16.2-1 ). The cp command inside the package() block fails with cp: cannot stat '$srcdir/web-2.16.2/build': no such file or directory. I'm getting this on a clean build as well, and as far as I can see there is no build directory in the dowloaded sources.

setboolean commented on 2020-09-20 23:52

@mqs compiled it today using nodejs-lts-erbium, everything i tried so far works as expected.

mqs commented on 2020-09-20 23:02

@setboolean at the time I added that there were some problems with nodejs>=12 (or at least I wrote that in the comment in the PKGBUILD). But this was a year(?) ago so it could be working again. If you want to try that, you're welcome, although I probably will do it myself when the next release comes.

I'll also remove the python2 dependency since the related issue has been resolved and python2 is not used anymore.

setboolean commented on 2020-09-20 13:29

Is there a particular reason for using nodejs-lts-dubnium instead of nodejs-lts-erbium?

grawlinson commented on 2020-05-22 22:47

Apologies, I'll stop doing that. I'm just overexcited because this is such an awesome little bit of software! :D

mqs commented on 2020-05-22 12:58

@grawlinson As always, thank you for the notification, but I will update only if there is a bitwarden_rs version which (reliably) supports the new vault version[1] or if you can explain why it is important to update now. If you want cutting edge, please use the bitwarden_rs-vault-git package and give feedback if something is not working as intended. This package is supposed to be somewhat stable. Not "debian-stable" but "was tested by upstream"-stable.

I'm resetting the outdated-marker now.

[1] Specifically, I will update this package if the changelog of the bitwarden_rs release contains the magical line "Update web vault to version xy", which has not happened yet.

mqs commented on 2020-03-21 22:40

@grawlinson

I've just noticed the first URL in the pinned comment returns a 404, possibly due to it linking to dani-garcia/bitwarden, rather than dani-garcia/bitwarden_rs.

Whoops, fixed, thanks!

If stuff breaks, I file a bug report with upstream. Doesn't happen too often, thankfully!

I would usually agree with you but this here is a special case because it doesn't only have to be compatible with archlinux, but also with bitwarden_rs, which is not really tested until the release. So what I do is mostly wait for the "Update web vault to version xy" line in the bitwarden_rs release changelogs before uploading a new version here.

As this happened just now, here is your new version ;-)

grawlinson commented on 2020-03-14 10:04

No particular reason, I usually update my PKGBUILDs when upstream releases a new version. If stuff breaks, I file a bug report with upstream. Doesn't happen too often, thankfully!

I've just noticed the first URL in the pinned comment returns a 404, possibly due to it linking to dani-garcia/bitwarden, rather than dani-garcia/bitwarden_rs.