Vaultwarden 1.29.1 is out
sjorge opened this issue · comments
Looks like we're a few version behind, I currently don't have a build box setup.
I'll try to find some time but it's been busy here. Although I don't expect any issues just bumping the verison.
Trying to build an update but gettting this with both the current commited build.sh and with a bumped version
==== opt/ooce/bin/vaultwarden ====
unused search path=/opt/ooce/pgsql-14/lib/amd64 (RUNPATH/RPATH from file /opt/ooce/pgsql-14/lib/amd64/libpq.so.5) <remove search path?>
unreferenced object=/lib/64/libnsl.so.1; unused dependency of /opt/ooce/pgsql-14/lib/amd64/libpq.so.5 <remove lib or -zignore?>
unreferenced object=/lib/64/libnsl.so.1; unused dependency of /opt/ooce/mariadb-10.6/lib/amd64/libmariadb.so.3 <remove lib or -zignore?>
unreferenced object=/lib/64/libm.so.2; unused dependency of /opt/ooce/pgsql-14/lib/amd64/libpq.so.5 <remove lib or -zignore?>
unreferenced object=/lib/64/libm.so.2; unused dependency of /opt/ooce/mariadb-10.6/lib/amd64/libmariadb.so.3 <remove lib or -zignore?>
NEEDED=librt.so.1 <dependency no longer necessary>
NEEDED=libpthread.so.1 <dependency no longer necessary>
I get the same error both unmodified and with this applied
root@omnios:/build/omnios-extra/build/vaultwarden# git diff
diff --git a/build/vaultwarden/build.sh b/build/vaultwarden/build.sh
index 0aa05376..a2e5cc0f 100755
--- a/build/vaultwarden/build.sh
+++ b/build/vaultwarden/build.sh
@@ -17,15 +17,15 @@
. ../../lib/build.sh
PROG=vaultwarden
-VER=1.28.0
+VER=1.29.1
PKG=ooce/application/vaultwarden
SUMMARY="Bitwarden compatible server"
DESC="Unofficial Bitwarden compatible server written in Rust, formerly known "
DESC+="as bitwarden_rs"
DANIGARCIA=$GITHUB/dani-garcia
-WEBVAULTVER=2023.3.0b
-WEBVAULTSHA256=ac3d27cbbb0dabb09cba0029c0b4d13b4f866fa3ae4eaa2dfd1f3880800ce19c
+WEBVAULTVER=2023.7.1
+WEBVAULTSHA256=0d7ea02eb13cc7b29c875af7ecc787c0a4990c22df13a024f0589e6faa3703d4
set_arch 64
Hold on, I was booted in my onu BE not the main up to date one.
No effect, same issues.
Hi @sjorge, you can take those rpath messages as "warnings" or guidance for omnios-extra.
I guess you should be good to open the PR with the bumped package versions if this is the only "problem".
This built successfully for me so I filed PR #1333