From: sburris0 <sburris0@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] signal-backup-decode: update to 0.2.1
Date: Sun, 11 Apr 2021 03:50:50 +0200 [thread overview]
Message-ID: <20210411015050.d_xfbhwrA1hJOWpD-NHUG6md3C4xUj3mtinBln6kMg4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-29502@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1606 bytes --]
There is an updated pull request by sburris0 against master on the void-packages repository
https://github.com/sburris0/void-packages patch-1
https://github.com/void-linux/void-packages/pull/29502
signal-backup-decode: update to 0.2.1
<!-- Mark items with [x] where applicable -->
#### General
- [ ] This is a new package and it conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements)
#### Have the results of the proposed changes been tested?
- [ ] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
- [x] I generally don't use the affected packages but briefly tested this PR
<!--
If GitHub CI cannot be used to validate the build result (for example, if the
build is likely to take several hours), make sure to
[skip CI](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration).
When skipping CI, uncomment and fill out the following section.
Note: for builds that are likely to complete in less than 2 hours, it is not
acceptable to skip CI.
-->
<!--
#### Does it build and run successfully?
(Please choose at least one native build and, if supported, at least one cross build. More are better.)
- [x] I built this PR locally for my native architecture, (ARCH-LIBC)
- [ ] I built this PR locally for these architectures (if supported. mark crossbuilds):
- [ ] aarch64-musl
- [ ] armv7l
- [ ] armv6l-musl
-->
A patch file from https://github.com/void-linux/void-packages/pull/29502.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-patch-1-29502.patch --]
[-- Type: text/x-diff, Size: 1216 bytes --]
From 77cafbdaf4142a615ae1fac65bbb3afac4132ea9 Mon Sep 17 00:00:00 2001
From: Spencer Burris <sburris@posteo.net>
Date: Mon, 15 Mar 2021 18:47:05 -0700
Subject: [PATCH] signal-backup-decode: update to 0.2.3
---
srcpkgs/signal-backup-decode/template | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/srcpkgs/signal-backup-decode/template b/srcpkgs/signal-backup-decode/template
index 119546b61ea7..747736adeb5e 100644
--- a/srcpkgs/signal-backup-decode/template
+++ b/srcpkgs/signal-backup-decode/template
@@ -1,7 +1,7 @@
# Template file for 'signal-backup-decode'
pkgname=signal-backup-decode
-version=0.2.0
-revision=2
+version=0.2.3
+revision=1
build_style=cargo
hostmakedepends="pkg-config"
makedepends="openssl-devel sqlite-devel"
@@ -9,5 +9,5 @@ short_desc="Decode Signal Android Backups"
maintainer="Spencer Burris <sburris@posteo.net>"
license="GPL-3.0-or-later"
homepage="https://github.com/pajowu/signal-backup-decode"
-distfiles="${homepage}/archive/${version}.tar.gz"
-checksum=9a454bb894963e7f6301bdcd3db2c7978fb0cfb7e6fce3f4f553ccad7f955fe9
+distfiles="${homepage}/archive/v${version}.tar.gz"
+checksum=e7727b6628004cd027e374bcd8a004d8c3e68b3ba03e82ce2c9e04ee58623ed2
next prev parent reply other threads:[~2021-04-11 1:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-16 1:48 [PR PATCH] " sburris0
2021-03-16 1:50 ` [PR PATCH] [Updated] " sburris0
2021-03-16 1:56 ` sburris0
2021-03-16 1:58 ` sburris0
2021-03-16 2:01 ` sburris0
2021-03-16 20:07 ` tibequadorian
2021-04-10 16:53 ` [PR PATCH] [Updated] " sburris0
2021-04-10 16:57 ` sburris0
2021-04-10 22:31 ` tibequadorian
2021-04-11 1:50 ` sburris0 [this message]
2021-04-11 1:59 ` signal-backup-decode: update to 0.2.3 sburris0
2021-04-11 3:47 ` [PR PATCH] [Closed]: " ericonr
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=20210411015050.d_xfbhwrA1hJOWpD-NHUG6md3C4xUj3mtinBln6kMg4@z \
--to=sburris0@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).