From: steinex <steinex@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] miniflux: update to 2.0.39.
Date: Sun, 16 Oct 2022 23:59:10 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39996@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1240 bytes --]
There is a new pull request by steinex against master on the void-packages repository
https://github.com/steinex/void-packages miniflux
https://github.com/void-linux/void-packages/pull/39996
miniflux: update to 2.0.39.
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **YES**
<!--
#### New package
- This new package conforms to the [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements): **YES**|**NO**
-->
<!-- Note: If the build is likely to take more than 2 hours, please add ci skip tag as described in
https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->
<!--
#### Local build testing
- I built this PR locally for my native architecture, (ARCH-LIBC)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
- aarch64-musl
- armv7l
- armv6l-musl
-->
A patch file from https://github.com/void-linux/void-packages/pull/39996.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-miniflux-39996.patch --]
[-- Type: text/x-diff, Size: 1067 bytes --]
From aeb33b87e306b1076d9d24715a7ad7ee11f4c28e Mon Sep 17 00:00:00 2001
From: Frank Steinborn <steinex@nognu.de>
Date: Sun, 16 Oct 2022 23:53:44 +0200
Subject: [PATCH] miniflux: update to 2.0.39.
---
srcpkgs/miniflux/template | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/srcpkgs/miniflux/template b/srcpkgs/miniflux/template
index 77f747c5f349..c586bf6a0ec3 100644
--- a/srcpkgs/miniflux/template
+++ b/srcpkgs/miniflux/template
@@ -1,7 +1,7 @@
# Template file for 'miniflux'
pkgname=miniflux
-version=2.0.38
-revision=2
+version=2.0.39
+revision=1
wrksrc="v2-${version}"
build_style=go
go_import_path="miniflux.app"
@@ -12,7 +12,7 @@ license="Apache-2.0"
homepage="https://miniflux.app"
changelog="https://raw.githubusercontent.com/miniflux/v2/main/ChangeLog"
distfiles="https://github.com/miniflux/v2/archive/${version}.tar.gz"
-checksum=8c2e35a91d9b47a0879bcee4c23f342375293e97cee9639bb44b359b21e14d2a
+checksum=917a09c7b4e518a431f8b3ac9ca5b7193027a21828bb242c890c5b956f646173
system_accounts="_miniflux"
post_install() {
next reply other threads:[~2022-10-16 21:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-16 21:59 steinex [this message]
2022-10-17 20:41 ` [PR PATCH] [Merged]: " Piraty
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-39996@inbox.vuxu.org \
--to=steinex@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).