Github messages for voidlinux
 help / color / mirror / Atom feed
From: steinex <steinex@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] miniflux: update to 2.0.44.
Date: Mon, 08 May 2023 10:52:26 +0200	[thread overview]
Message-ID: <20230508085226.ZLOMF9djVbNH7PWTazG_pNkFOhb2k0JPp1aeL1ger3Y@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-43803@inbox.vuxu.org>

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

There is an updated 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/43803

miniflux: update to 2.0.44.
<!-- 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/43803.patch is attached

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

From 1960f9c1eeceefae1515be0cce97cb6fa0b4f222 Mon Sep 17 00:00:00 2001
From: Frank Steinborn <steinex@nognu.de>
Date: Mon, 8 May 2023 10:30:09 +0200
Subject: [PATCH] miniflux: update to 2.0.44.

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

diff --git a/srcpkgs/miniflux/template b/srcpkgs/miniflux/template
index fa99084cb46a..1e22a1146957 100644
--- a/srcpkgs/miniflux/template
+++ b/srcpkgs/miniflux/template
@@ -1,7 +1,7 @@
 # Template file for 'miniflux'
 pkgname=miniflux
-version=2.0.43
-revision=2
+version=2.0.44
+revision=1
 build_style=go
 go_import_path="miniflux.app"
 go_ldflags="-X miniflux.app/version.Version=${version}"
@@ -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=47bd2cf4fabcfff8589c24069e3d5b399cea55e60437585d3d1c1bd6a22e69b6
+checksum=9b3d873c21dde5eafc947be5394cd1bdd6d4f49ba62e5d796a526176647d9404
 system_accounts="_miniflux"
 
 post_install() {

  parent reply	other threads:[~2023-05-08  8:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-08  8:45 [PR PATCH] " steinex
2023-05-08  8:48 ` [PR PATCH] [Updated] " steinex
2023-05-08  8:52 ` steinex [this message]
2023-05-09 13:21 ` [PR PATCH] [Merged]: " abenson

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=20230508085226.ZLOMF9djVbNH7PWTazG_pNkFOhb2k0JPp1aeL1ger3Y@z \
    --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).