From: steinex <steinex@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] miniflux: update to 2.0.43.
Date: Fri, 17 Mar 2023 18:14:53 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42821@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/42821
miniflux: update to 2.0.43.
<!-- 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/42821.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-miniflux-42821.patch --]
[-- Type: text/x-diff, Size: 1029 bytes --]
From 8a7a00fae969a6af80ccda93ec89248d4d7492f9 Mon Sep 17 00:00:00 2001
From: Frank Steinborn <steinex@nognu.de>
Date: Fri, 17 Mar 2023 17:54:55 +0100
Subject: [PATCH] miniflux: update to 2.0.43.
---
srcpkgs/miniflux/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/miniflux/template b/srcpkgs/miniflux/template
index 308e2974e03b..3fbc518fd466 100644
--- a/srcpkgs/miniflux/template
+++ b/srcpkgs/miniflux/template
@@ -1,6 +1,6 @@
# Template file for 'miniflux'
pkgname=miniflux
-version=2.0.42
+version=2.0.43
revision=1
build_style=go
go_import_path="miniflux.app"
@@ -11,7 +11,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=f050b2bc9839dd485047b9d7820dbb669668fd13135aa8b49dc0ad304e509fd5
+checksum=47bd2cf4fabcfff8589c24069e3d5b399cea55e60437585d3d1c1bd6a22e69b6
system_accounts="_miniflux"
post_install() {
next reply other threads:[~2023-03-17 17:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-17 17:14 steinex [this message]
2023-03-18 6:24 ` [PR PATCH] [Merged]: " paper42
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-42821@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).