Github messages for voidlinux
 help / color / mirror / Atom feed
From: mdkcore0 <mdkcore0@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] nextcloud-client: update to 3.11.0
Date: Fri, 05 Jan 2024 16:36:38 +0100	[thread overview]
Message-ID: <20240105153638.O3m3sQT9PMXA95YXekzQ2hGkAFRKj-03ijpHanyqras@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-47713@inbox.vuxu.org>

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

There is an updated pull request by mdkcore0 against master on the void-packages repository

https://github.com/mdkcore0/void-packages update-nextcloud
https://github.com/void-linux/void-packages/pull/47713

nextcloud-client: update to 3.11.0
#### Testing the changes
- I tested the changes in this PR: **NO**

#### Local build testing
- I built this PR locally for my native architecture: x86_64-libc WIP
- I built this PR locally for these architectures:
  - armv7l (crossbuild) WIP


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

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

From d006f162b81f9d79a34341a430cf6f3bd0906d2e Mon Sep 17 00:00:00 2001
From: Rodrigo Oliveira <mdkcore@qtrnn.io>
Date: Fri, 5 Jan 2024 12:26:56 -0300
Subject: [PATCH] nextcloud-client: update to 3.11.0

---
 srcpkgs/nextcloud-client/template | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/srcpkgs/nextcloud-client/template b/srcpkgs/nextcloud-client/template
index 5bada5e710fec..b761bc9b4da5b 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.10.1
+version=3.11.0
 revision=1
 build_style=cmake
 configure_args="-DBUILD_UPDATER=NO -Wno-dev"
@@ -8,6 +8,7 @@ hostmakedepends="pkg-config inkscape"
 makedepends="qt5-tools-devel qt5-declarative-devel qt5-webchannel-devel
  qt5-location-devel qtkeychain-qt5-devel sqlite-devel libcloudproviders-devel
  qt5-quickcontrols2-devel qt5-websockets-devel qt5-svg-devel karchive-devel
+ qt5-plugin-mysql qt5-plugin-odbc qt5-plugin-pgsql qt5-plugin-sqlite qt5-plugin-tds
  $(vopt_if dolphin 'extra-cmake-modules kio-devel')
  $(vopt_if webengine 'qt5-webengine-devel')"
 depends="qt5-graphicaleffects"
@@ -19,7 +20,7 @@ license="GPL-2.0-or-later"
 homepage="https://nextcloud.com/clients/"
 changelog="https://github.com/nextcloud/desktop/releases"
 distfiles="https://github.com/nextcloud/desktop/archive/v${version}.tar.gz"
-checksum=11355941f2b2d83a72868c3dd6101ec1968e6cabb67834a0684ba860faedcee4
+checksum=75d53751411a7544ed5b9f23c3e71c19a96f4096313d76dad77314c3773319d9
 # https://github.com/void-linux/void-packages/pull/33358#discussion_r724518549
 make_check=ci-skip
 

  parent reply	other threads:[~2024-01-05 15:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-12 14:36 [PR PATCH] " mdkcore0
2023-12-12 14:54 ` [PR PATCH] [Updated] " mdkcore0
2024-01-04 23:27 ` mdkcore0
2024-01-05 15:36 ` mdkcore0 [this message]
2024-01-05 20:19 ` mdkcore0
2024-01-05 21:25 ` mdkcore0
2024-01-05 21:26 ` mdkcore0
2024-01-23 19:14 ` [PR PATCH] [Merged]: " ahesford

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=20240105153638.O3m3sQT9PMXA95YXekzQ2hGkAFRKj-03ijpHanyqras@z \
    --to=mdkcore0@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).