From: sbromberger <sbromberger@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] restic: update to 0.15.0.
Date: Sat, 14 Jan 2023 02:05:41 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41629@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 682 bytes --]
There is a new pull request by sbromberger against master on the void-packages repository
https://github.com/sbromberger/void-packages master
https://github.com/void-linux/void-packages/pull/41629
restic: update to 0.15.0.
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **YES**
#### Local build testing
- I built this PR locally for my native architecture, (x86-64-LIBC)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
- aarch64
- armv6l
A patch file from https://github.com/void-linux/void-packages/pull/41629.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-master-41629.patch --]
[-- Type: text/x-diff, Size: 1057 bytes --]
From 6e6339fdda1643d479944a339cfb595367ea0837 Mon Sep 17 00:00:00 2001
From: Seth Bromberger <github@bromberger.com>
Date: Fri, 13 Jan 2023 20:03:20 -0500
Subject: [PATCH] restic: update to 0.15.0.
---
srcpkgs/restic/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/restic/template b/srcpkgs/restic/template
index 2c39c1b02a36..a0f3c5955928 100644
--- a/srcpkgs/restic/template
+++ b/srcpkgs/restic/template
@@ -1,6 +1,6 @@
# Template file for 'restic'
pkgname=restic
-version=0.14.0
+version=0.15.0
revision=1
build_style=go
go_import_path=github.com/restic/restic
@@ -12,7 +12,7 @@ license="BSD-2-Clause"
homepage="https://restic.net/"
changelog="https://raw.githubusercontent.com/restic/restic/master/CHANGELOG.md"
distfiles="https://github.com/restic/restic/releases/download/v${version}/restic-${version}.tar.gz"
-checksum=78cdd8994908ebe7923188395734bb3cdc9101477e4163c67e7cc3b8fd3b4bd6
+checksum=85a6408cfb0798dab52335bcb00ac32066376c32daaa75461d43081499bc7de8
post_install() {
vlicense LICENSE
next reply other threads:[~2023-01-14 1:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-14 1:05 sbromberger [this message]
2023-01-14 1:08 ` [PR PATCH] [Updated] " sbromberger
2023-01-14 1:08 ` sbromberger
2023-01-15 11:21 ` [PR PATCH] [Merged]: " paper42
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-41629@inbox.vuxu.org \
--to=sbromberger@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).