From: steinex <steinex@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] miniflux: update to 2.0.37.
Date: Sat, 28 May 2022 12:01:49 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-37329@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1259 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/37329
miniflux: update to 2.0.37.
Also add log service.
<!-- 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 [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-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/37329.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-miniflux-37329.patch --]
[-- Type: text/x-diff, Size: 1437 bytes --]
From 3f38682a723e4c82e952d11392bb0b97f872e341 Mon Sep 17 00:00:00 2001
From: Frank Steinborn <steinex@nognu.de>
Date: Sat, 28 May 2022 11:15:08 +0200
Subject: [PATCH] miniflux: update to 2.0.37.
Also add log service.
---
srcpkgs/miniflux/files/miniflux/log/run | 1 +
srcpkgs/miniflux/template | 4 ++--
2 files changed, 3 insertions(+), 2 deletions(-)
create mode 120000 srcpkgs/miniflux/files/miniflux/log/run
diff --git a/srcpkgs/miniflux/files/miniflux/log/run b/srcpkgs/miniflux/files/miniflux/log/run
new file mode 120000
index 000000000000..3a5b4a586051
--- /dev/null
+++ b/srcpkgs/miniflux/files/miniflux/log/run
@@ -0,0 +1 @@
+/usr/bin/vlogger
\ No newline at end of file
diff --git a/srcpkgs/miniflux/template b/srcpkgs/miniflux/template
index 886d40df8a9f..036854db19e2 100644
--- a/srcpkgs/miniflux/template
+++ b/srcpkgs/miniflux/template
@@ -1,6 +1,6 @@
# Template file for 'miniflux'
pkgname=miniflux
-version=2.0.36
+version=2.0.37
revision=1
wrksrc="v2-${version}"
build_style=go
@@ -12,7 +12,7 @@ license="Apache-2.0"
homepage="https://miniflux.app"
changelog="https://raw.githubusercontent.com/miniflux/v2/master/ChangeLog"
distfiles="https://github.com/miniflux/v2/archive/${version}.tar.gz"
-checksum=15ac4ad4ab6f87de2143a85f52252e80d7c216a69aab334363e1972b81f231fd
+checksum=fa647ea15ade5ec2ed64648a34d6df30553f1358f7365a3f7301ff4fd212b635
system_accounts="_miniflux"
post_install() {
next reply other threads:[~2022-05-28 10:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-28 10:01 steinex [this message]
2022-05-28 23:06 ` [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-37329@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).