Github messages for voidlinux
 help / color / mirror / Atom feed
From: ninewise <ninewise@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] lastpass-cli: update to 1.3.7
Date: Tue, 19 Dec 2023 23:10:43 +0100	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-47838@inbox.vuxu.org> (raw)

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

There is a new pull request by ninewise against master on the void-packages repository

https://github.com/ninewise/void-packages update/lastpass-cli
https://github.com/void-linux/void-packages/pull/47838

lastpass-cli: update to 1.3.7
<!-- Uncomment relevant sections and delete options which are not applicable -->

#### Testing the changes
- I tested the changes in this PR: **YES**

<!--
#### New package
- This new package conforms to the [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements): **YES**|**NO**
-->

<!-- Note: If the build is likely to take more than 2 hours, please add ci skip tag as described in
https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->
#### Local build testing
- I built this PR locally for my native architecture, x86_64-glibc

A patch file from https://github.com/void-linux/void-packages/pull/47838.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-update/lastpass-cli-47838.patch --]
[-- Type: text/x-diff, Size: 1141 bytes --]

From d3efc6638a93082ae6b8686dc161a73022a1b35e Mon Sep 17 00:00:00 2001
From: Felix Van der Jeugt <felix.vanderjeugt@posteo.net>
Date: Tue, 19 Dec 2023 23:06:13 +0100
Subject: [PATCH] lastpass-cli: update to 1.3.7

---
 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 26a2d4de5d4ae..e80021a122610 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=5
+version=1.3.7
+revision=1
 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://github.com/lastpass/${pkgname}/blob/v${version}/CHANGELOG.md"
 distfiles="https://github.com/lastpass/${pkgname}/archive/v${version}.tar.gz"
-checksum=f38e1ee7e06e660433a575a23b061c2f66ec666d746e988716b2c88de59aed73
+checksum=3fb1373fc05d568599da7657fcff801cbaa704254f00bb8e13d4510cb236be90
 
 CFLAGS="-fcommon"
 

             reply	other threads:[~2023-12-19 22:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-19 22:10 ninewise [this message]
2023-12-19 23:50 ` [PR PATCH] [Updated] " ninewise
2023-12-19 23:55 ` ninewise
2023-12-20 10:26 ` [PR REVIEW] " classabbyamp
2023-12-20 20:40 ` [PR PATCH] [Updated] " ninewise
2023-12-20 23:04 ` [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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-47838@inbox.vuxu.org \
    --to=ninewise@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).