From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: [PR PATCH] fierce: update to 1.4.0.
Date: Sun, 10 Nov 2019 20:20:33 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-16334@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 314 bytes --]
There is a new pull request by abenson against master on the void-packages repository
https://github.com/abenson/void-packages fierce_1.4.0
https://github.com/void-linux/void-packages/pull/16334
fierce: update to 1.4.0.
A patch file from https://github.com/void-linux/void-packages/pull/16334.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-fierce_1.4.0-16334.patch --]
[-- Type: text/x-diff, Size: 939 bytes --]
From ace81d0e3c1e4f3a230578557f3770903601880e Mon Sep 17 00:00:00 2001
From: Andrew Benson <abenson+void@gmail.com>
Date: Sun, 10 Nov 2019 09:18:00 -1000
Subject: [PATCH] fierce: update to 1.4.0.
---
srcpkgs/fierce/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/fierce/template b/srcpkgs/fierce/template
index 86dedb39ad2..ed4d3949f5e 100644
--- a/srcpkgs/fierce/template
+++ b/srcpkgs/fierce/template
@@ -1,6 +1,6 @@
# Template file for 'fierce'
pkgname=fierce
-version=1.3.0
+version=1.4.0
revision=1
archs=noarch
build_style=python3-module
@@ -12,4 +12,4 @@ maintainer="Andrew Benson <abenson+void@gmail.com>"
license="GPL-3.0-or-later"
homepage="https://github.com/mschwager/fierce"
distfiles="${homepage}/archive/${version}.tar.gz"
-checksum=ca6938c6ecb2cb3ff0484ee3d90566e044bf35c30237e921d439310fa6cb788b
+checksum=6ff85428e06aa71fb4b52de4eef3cf1b6ebcb0f43cf1fcf0150f5e8dcb67b9d1
next reply other threads:[~2019-11-10 19:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-10 19:20 voidlinux-github [this message]
2019-11-11 6:20 ` [PR PATCH] [Merged]: " voidlinux-github
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-16334@inbox.vuxu.org \
--to=voidlinux-github@inbox.vuxu.org \
--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).