From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] lastpass-cli: update to 1.3.3
Date: Mon, 07 Oct 2019 07:32:53 +0200 [thread overview]
Message-ID: <20191007053253.MBfr9o5TOvGngPXu-4iuug5mfBhsDBhu3DP6CLo0lDo@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-15191@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 336 bytes --]
There is an updated pull request by TheExpert1337 against master on the void-packages repository
https://github.com/TheExpert1337/void-packages lastpass-cli
https://github.com/void-linux/void-packages/pull/15191
lastpass-cli: update to 1.3.3
A patch file from https://github.com/void-linux/void-packages/pull/15191.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-lastpass-cli-15191.patch --]
[-- Type: text/x-diff, Size: 1871 bytes --]
From 4c3ff46173804159ac773a1e1b954dce4fb48da8 Mon Sep 17 00:00:00 2001
From: TheExpert1337 <tamas.bohm@protonmail.com>
Date: Sun, 6 Oct 2019 19:13:43 +0200
Subject: [PATCH 1/2] lastpass-cli: update to 1.3.3
---
srcpkgs/lastpass-cli/template | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/srcpkgs/lastpass-cli/template b/srcpkgs/lastpass-cli/template
index af29d878e9b..0a1d7549441 100644
--- a/srcpkgs/lastpass-cli/template
+++ b/srcpkgs/lastpass-cli/template
@@ -1,7 +1,7 @@
# Template file for 'lastpass-cli'
pkgname=lastpass-cli
-version=1.3.2
-revision=2
+version=1.3.3
+revision=3
build_style=cmake
make_install_target="install install-doc"
hostmakedepends="asciidoc pkg-config"
@@ -12,7 +12,7 @@ license="GPL-2.0-or-later"
homepage="https://lastpass.com/"
#changelog="https://raw.githubusercontent.com/lastpass/lastpass-cli/master/CHANGELOG.md"
distfiles="https://github.com/lastpass/${pkgname}/archive/v${version}.tar.gz"
-checksum=755338967d8bf39b8c6c9cf46f265896122c01b8e8453e4310ec043d63d8337a
+checksum=f38e1ee7e06e660433a575a23b061c2f66ec666d746e988716b2c88de59aed73
post_install() {
vmkdir usr/share/examples/lpass
From 7e3c0958b9b4b182e66db636882f283917fa6eef Mon Sep 17 00:00:00 2001
From: TheExpert1337 <tamas.bohm@protonmail.com>
Date: Mon, 7 Oct 2019 07:32:31 +0200
Subject: [PATCH 2/2] lastpass-cli: update tp 1.3.3 v2
---
srcpkgs/lastpass-cli/template | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/srcpkgs/lastpass-cli/template b/srcpkgs/lastpass-cli/template
index 0a1d7549441..2b3fd5e5fd6 100644
--- a/srcpkgs/lastpass-cli/template
+++ b/srcpkgs/lastpass-cli/template
@@ -1,7 +1,7 @@
# Template file for 'lastpass-cli'
pkgname=lastpass-cli
version=1.3.3
-revision=3
+revision=1
build_style=cmake
make_install_target="install install-doc"
hostmakedepends="asciidoc pkg-config"
next prev parent reply other threads:[~2019-10-07 5:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-06 17:14 [PR PATCH] " voidlinux-github
2019-10-07 5:32 ` voidlinux-github [this message]
2019-10-07 5:32 ` [PR PATCH] [Updated] " voidlinux-github
2019-10-07 18:06 ` voidlinux-github
2019-10-07 18:06 ` voidlinux-github
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=20191007053253.MBfr9o5TOvGngPXu-4iuug5mfBhsDBhu3DP6CLo0lDo@z \
--to=voidlinux-github@inbox.vuxu.org \
--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).