From: akierig <akierig@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] nextcloud-client: update to 3.8.1.
Date: Sat, 29 Apr 2023 08:06:06 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-43665@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 481 bytes --]
There is a new pull request by akierig against master on the void-packages repository
https://github.com/akierig/void-packages nextcloud
https://github.com/void-linux/void-packages/pull/43665
nextcloud-client: update to 3.8.1.
#### 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
A patch file from https://github.com/void-linux/void-packages/pull/43665.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-nextcloud-43665.patch --]
[-- Type: text/x-diff, Size: 664 bytes --]
From 01c2092a2ec97668f181839e8350d55345ea12c9 Mon Sep 17 00:00:00 2001
From: anelki <akierig@fastmail.de>
Date: Sat, 29 Apr 2023 01:04:25 -0500
Subject: [PATCH] nextcloud-client: update to 3.8.1.
---
srcpkgs/nextcloud-client/template | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/srcpkgs/nextcloud-client/template b/srcpkgs/nextcloud-client/template
index 0fa40780a545..e60f5fe94aec 100644
--- a/srcpkgs/nextcloud-client/template
+++ b/srcpkgs/nextcloud-client/template
@@ -1,6 +1,6 @@
# Template file for 'nextcloud-client'
pkgname=nextcloud-client
-version=3.8.0
+version=3.8.1
revision=1
build_style=cmake
configure_args="-Wno-dev"
next reply other threads:[~2023-04-29 6:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-29 6:06 akierig [this message]
2023-04-29 6:12 ` [PR PATCH] [Updated] " akierig
2023-04-30 2:00 ` [PR PATCH] [Merged]: " abenson
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-43665@inbox.vuxu.org \
--to=akierig@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).