Github messages for voidlinux
 help / color / mirror / Atom feed
From: classabbyamp <classabbyamp@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New packages: vaultwarden-web-2022.8.1, vaultwarden-1.25.1
Date: Tue, 06 Sep 2022 07:27:57 +0200	[thread overview]
Message-ID: <20220906052757.nDNl66AefFLfXrnl-VKlBfBGMMQWfD8tw3cr_lPwdkM@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-37258@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1788 bytes --]

New comment by classabbyamp on void-packages repository

https://github.com/void-linux/void-packages/pull/37258#issuecomment-1237674008

Comment:
I know I said the opposite before, but thinking about it again, i think pulling the patch from upstream is best

this worked for me:
```patch
diff --git a/srcpkgs/vaultwarden-web/template b/srcpkgs/vaultwarden-web/template
index 47f3f41d62..557c3e1952 100644
--- a/srcpkgs/vaultwarden-web/template
+++ b/srcpkgs/vaultwarden-web/template
@@ -2,17 +2,26 @@
 pkgname=vaultwarden-web
 version=2022.8.1
 revision=1
-wrksrc="clients-web-v${version}"
+_patch_ver=2022.8.0
+create_wrksrc=yes
+build_wrksrc="clients-web-v${version}"
 hostmakedepends="git nodejs"
 short_desc="Web vault builds for vaultwarden"
 maintainer="Joel Beckmeyer <joel@beckmeyer.us>"
 license="GPL-3.0-or-later"
-# patches need to be pulled from
-# https://github.com/dani-garcia/bw_web_builds/tree/master/patches into the
-# patches directory
 homepage="https://github.com/dani-garcia/bw_web_builds"
-distfiles="https://github.com/bitwarden/clients/archive/web-v${version}.tar.gz"
-checksum=9dff38f13d8be047fe0fd6426bda3c409bb222b787bd6b21a3559f5d29255a92
+distfiles="https://github.com/bitwarden/clients/archive/web-v${version}.tar.gz
+ https://raw.githubusercontent.com/dani-garcia/bw_web_builds/master/patches/v${_patch_ver}.patch"
+checksum="9dff38f13d8be047fe0fd6426bda3c409bb222b787bd6b21a3559f5d29255a92
+ 1199bcf5edb0cad2e0fc1e839b5bdc690565d6af5b32cc1c38348f0b13c69ee9"
+
+post_extract() {
+       mv v$_patch_ver.patch ${build_wrksrc}
+}
+
+post_patch() {
+       patch -Np1 -i v$_patch_ver.patch
+}
 
 do_configure() {
        npm ci --ignore-scripts
```
I'm going to do some testing with it and we can get this merged :)

  parent reply	other threads:[~2022-09-06  5:27 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-23 17:23 [PR PATCH] New packages: vaultwarden-web-2.28.1, vaultwarden-1.25.0 TinfoilSubmarine
2022-05-23 17:28 ` [PR PATCH] [Updated] " TinfoilSubmarine
2022-05-23 18:07 ` [PR REVIEW] " classabbyamp
2022-05-23 18:07 ` classabbyamp
2022-05-23 18:07 ` classabbyamp
2022-05-23 19:02 ` TinfoilSubmarine
2022-05-23 19:22 ` classabbyamp
2022-05-23 19:23 ` classabbyamp
2022-05-23 20:30 ` [PR PATCH] [Updated] " TinfoilSubmarine
2022-05-23 20:32 ` TinfoilSubmarine
2022-05-24 11:58 ` TinfoilSubmarine
2022-06-06 13:10 ` TinfoilSubmarine
2022-06-07 18:13 ` [PR PATCH] [Updated] New packages: vaultwarden-web-2022.05.0, vaultwarden-1.25.0 TinfoilSubmarine
2022-06-08 12:23 ` TinfoilSubmarine
2022-06-28 13:48 ` [PR PATCH] [Updated] " TinfoilSubmarine
2022-06-28 13:49 ` TinfoilSubmarine
2022-07-11 13:00 ` [PR PATCH] [Updated] New packages: vaultwarden-web-2022.5.2, vaultwarden-1.25.0 TinfoilSubmarine
2022-07-19 15:53 ` [PR PATCH] [Updated] New packages: vaultwarden-web-2022.6.0, vaultwarden-1.25.0 TinfoilSubmarine
2022-07-28 19:40 ` [PR PATCH] [Updated] New packages: vaultwarden-web-2022.6.2, vaultwarden-1.25.1 TinfoilSubmarine
2022-09-04 22:49 ` TinfoilSubmarine
2022-09-06  5:27 ` New packages: vaultwarden-web-2022.8.1, vaultwarden-1.25.1 classabbyamp
2022-09-06  5:27 ` classabbyamp [this message]
2022-09-06  5:32 ` [PR REVIEW] " classabbyamp
2022-09-06 13:37 ` [PR PATCH] [Updated] " TinfoilSubmarine
2022-09-06 16:49 ` [PR PATCH] [Merged]: " classabbyamp

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220906052757.nDNl66AefFLfXrnl-VKlBfBGMMQWfD8tw3cr_lPwdkM@z \
    --to=classabbyamp@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).