From: bitmeise <bitmeise@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] hledger: update to 1.21
Date: Sat, 13 Mar 2021 20:52:39 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-29442@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1192 bytes --]
There is a new pull request by bitmeise against master on the void-packages repository
https://github.com/bitmeise/void-packages hledger121
https://github.com/void-linux/void-packages/pull/29442
hledger: update to 1.21
#### General
- [ ] This is a new package and it conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements)
#### Have the results of the proposed changes been tested?
- [X] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
- [ ] I generally don't use the affected packages but briefly tested this PR
#### Does it build and run successfully?
- [X] I built this PR locally for my native architecture, (x86_64-glibc)
- [ ] I built this PR locally for these architectures (if supported. mark crossbuilds):
- [ ] aarch64-musl
- [ ] armv7l
- [ ] armv6l-musl
#### Remarks
Removed installation of .5 man pages, since they have been removed upstream in https://github.com/simonmichael/hledger/commit/a7e9e9ac0ecb29a57a2e543c313a5f79b921d6de
A patch file from https://github.com/void-linux/void-packages/pull/29442.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-hledger121-29442.patch --]
[-- Type: text/x-diff, Size: 1226 bytes --]
From 911a74ea998622bce77290342cc716345b3e9def Mon Sep 17 00:00:00 2001
From: Bitmeise <ameise@bitparlament.de>
Date: Sat, 13 Mar 2021 20:43:32 +0100
Subject: [PATCH] hledger: update to 1.21
---
srcpkgs/hledger/template | 7 ++-----
1 file changed, 2 insertions(+), 5 deletions(-)
diff --git a/srcpkgs/hledger/template b/srcpkgs/hledger/template
index aaad04b778c0..b34e8ccd4652 100644
--- a/srcpkgs/hledger/template
+++ b/srcpkgs/hledger/template
@@ -1,6 +1,6 @@
# Template file for 'hledger'
pkgname=hledger
-version=1.20.4
+version=1.21
revision=1
build_style=haskell-stack
makedepends="zlib-devel ncurses-devel"
@@ -10,15 +10,12 @@ license="GPL-3.0-or-later"
homepage="http://hledger.org/"
changelog="https://hackage.haskell.org/package/hledger-${version}/changelog"
distfiles="https://github.com/simonmichael/${pkgname}/archive/${version}.tar.gz"
-checksum=1213854ee7cf94913652706139b4c7f619af4394f5e70856b859f3c0ed07b2a4
+checksum=55a83947852ff088b244447ae0d0d96b8902d867b9b0773ebd1dab2e64e98ecd
nopie_files="/usr/bin/hledger"
nocross=yes # Can't yet cross compile Haskell
post_install() {
vman hledger/hledger.1
- for manpage in hledger-lib/*.5; do
- vman $manpage
- done
}
hledger-ui_package() {
next reply other threads:[~2021-03-13 19:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-13 19:52 bitmeise [this message]
2021-03-14 15:02 ` [PR PATCH] [Merged]: " ericonr
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-29442@inbox.vuxu.org \
--to=bitmeise@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).