Github messages for voidlinux
 help / color / mirror / Atom feed
From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: nextcloud-client: update to 3.1.2, no shibboleth and webkit support, kwallet subpackage
Date: Wed, 24 Feb 2021 05:18:51 +0100	[thread overview]
Message-ID: <20210224041851.e1QYIrGJ9NoEyX7tJod5siZcGaJlNWSN_GKH9RLhrfc@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-28674@inbox.vuxu.org>

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

There's a merged pull request on the void-packages repository

nextcloud-client: update to 3.1.2, no shibboleth and webkit support, kwallet subpackage
https://github.com/void-linux/void-packages/pull/28674

Description:
* shibboleth is "highly deprecated" by upstream, will be removed in 3.2.
* webkit support is currently ineffective and difficult to fix.
* fix ~dolphin build options
* Edit: add package `nextcloud-client-kwallet` to deal with https://github.com/void-linux/void-packages/issues/26774 . 

<!-- 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?
- [x] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
- [ ] 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)
- [x] I built this PR locally for these architectures (if supported. mark crossbuilds):
  - [x] aarch64-musl
  - [ ] armv7l
  - [ ] armv6l-musl
-->


  parent reply	other threads:[~2021-02-24  4:18 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-11 20:25 [PR PATCH] [WIP] nextcloud-client: update to 3.1.2, remove shibboleth and wekbit support yopito
2021-02-11 20:35 ` ericonr
2021-02-11 20:35 ` ericonr
2021-02-11 23:27 ` paper42
2021-02-11 23:34 ` yopito
2021-02-11 23:35 ` [PR PATCH] [Updated] " yopito
2021-02-13 20:12 ` [PR PATCH] [Updated] [WIP] nextcloud-client: update to 3.1.2, remove shibboleth and webkit support yopito
2021-02-13 20:16 ` yopito
2021-02-13 20:28 ` ericonr
2021-02-14 20:52 ` [PR PATCH] [Updated] " yopito
2021-02-14 21:01 ` yopito
2021-02-15  8:45 ` [PR PATCH] [Updated] " yopito
2021-02-15  8:46 ` yopito
2021-02-16  5:48 ` [PR REVIEW] nextcloud-client: update to 3.1.2, no shibboleth and webkit support, kwallet subpackage fosslinux
2021-02-17 22:49 ` [PR PATCH] [Updated] " yopito
2021-02-24  4:18 ` ericonr [this message]
2021-02-24 16:30 ` q66
2021-02-24 16:30 ` q66
2021-02-25  7:33 ` yopito
2021-02-25 10:06 ` q66
2021-02-25 19:18 ` yopito

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=20210224041851.e1QYIrGJ9NoEyX7tJod5siZcGaJlNWSN_GKH9RLhrfc@z \
    --to=ericonr@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).