Github messages for voidlinux
 help / color / mirror / Atom feed
From: glaulher <glaulher@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] knotes: update to 21.04.2.
Date: Thu, 01 Jul 2021 00:46:10 +0200	[thread overview]
Message-ID: <20210630224610.svx6tJx7Yfsay3CJ0Tl7QOvgVQED-JwDcAodGnwzoIk@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-31683@inbox.vuxu.org>

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

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

https://github.com/glaulher/void-packages knotes
https://github.com/void-linux/void-packages/pull/31683

knotes: update to 21.04.2.
<!-- 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)
- [x] I built this PR locally for these architectures (if supported. mark crossbuilds):
  - [ ] aarch64-musl
  - [x] armv7l
  - [ ] armv6l-musl
-->


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

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

From 6f363a0c9b4339812f1c81c732f95f5a7af3211f Mon Sep 17 00:00:00 2001
From: glaulher <glaulher.developer@gmail.com>
Date: Wed, 30 Jun 2021 19:45:44 -0300
Subject: [PATCH] knotes: update to 21.04.2.

---
 srcpkgs/knotes/template | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/srcpkgs/knotes/template b/srcpkgs/knotes/template
index a9aa128194d5..e9eadc430a98 100644
--- a/srcpkgs/knotes/template
+++ b/srcpkgs/knotes/template
@@ -1,6 +1,6 @@
 # Template file for 'knotes'
 pkgname=knotes
-version=21.04.1
+version=21.04.2
 revision=1
 build_style=cmake
 hostmakedepends="extra-cmake-modules qt5-qmake qt5-host-tools libxslt
@@ -10,6 +10,6 @@ makedepends="akonadi-notes-devel kcalutils-devel kdelibs4support-devel kdnssd-de
 short_desc="Popup notes"
 maintainer="Orphaned <orphan@voidlinux.org>"
 license="GPL-2.0-or-later, GFDL-1.2-only"
-homepage="https://kde.org/applications/en/utilities/org.kde.knotes"
+homepage="https://apps.kde.org/knotes/"
 distfiles="${KDE_SITE}/release-service/${version}/src/${pkgname}-${version}.tar.xz"
-checksum=64940415fc5115ecd5433fd82894dfe7cf37593662521efa09891f7f2bba8e2a
+checksum=9f43299b1bc14b96380b262b26314d7053b5b8242e7faa0560d5b7d98d0f683d

  parent reply	other threads:[~2021-06-30 22:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-27 16:25 [PR PATCH] " glaulher
2021-06-28 14:28 ` [PR REVIEW] " ericonr
2021-06-29 17:19 ` [PR PATCH] [Updated] " glaulher
2021-06-29 18:05 ` ericonr
2021-06-30 22:46 ` glaulher [this message]
2021-06-30 22:57 ` glaulher
2021-07-01  0:31 ` [PR PATCH] [Merged]: " 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=20210630224610.svx6tJx7Yfsay3CJ0Tl7QOvgVQED-JwDcAodGnwzoIk@z \
    --to=glaulher@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).