From: bitmeise <bitmeise@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] hledger: update to 1.20.2
Date: Tue, 29 Dec 2020 22:12:50 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-27534@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 517 bytes --]
There is a new pull request by bitmeise against master on the void-packages repository
https://github.com/bitmeise/void-packages hledger1201
https://github.com/void-linux/void-packages/pull/27534
hledger: update to 1.20.2
@q66, I often have problems updating this package and they are usually resolved by deleting stack.yaml. My knowledge of the Haskell ecosystem is very limited. Is this file still necessary for anything?
A patch file from https://github.com/void-linux/void-packages/pull/27534.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-hledger1201-27534.patch --]
[-- Type: text/x-diff, Size: 1488 bytes --]
From 48f90187b6a4f69f71109a50c24ab6988ae9f125 Mon Sep 17 00:00:00 2001
From: Ameise <ameise@bitparlament.de>
Date: Tue, 29 Dec 2020 22:04:53 +0100
Subject: [PATCH] hledger: update to 1.20.2
---
srcpkgs/hledger/files/stack.yaml | 6 ------
srcpkgs/hledger/template | 4 ++--
2 files changed, 2 insertions(+), 8 deletions(-)
delete mode 100644 srcpkgs/hledger/files/stack.yaml
diff --git a/srcpkgs/hledger/files/stack.yaml b/srcpkgs/hledger/files/stack.yaml
deleted file mode 100644
index fdb69b61aee..00000000000
--- a/srcpkgs/hledger/files/stack.yaml
+++ /dev/null
@@ -1,6 +0,0 @@
-resolver: lts-16.13
-packages:
-- hledger-lib
-- hledger
-- hledger-ui
-- hledger-web
diff --git a/srcpkgs/hledger/template b/srcpkgs/hledger/template
index cb7b195d085..45974a08a6a 100644
--- a/srcpkgs/hledger/template
+++ b/srcpkgs/hledger/template
@@ -1,6 +1,6 @@
# Template file for 'hledger'
pkgname=hledger
-version=1.19.1
+version=1.20.2
revision=1
build_style=haskell-stack
makedepends="zlib-devel ncurses-devel"
@@ -10,7 +10,7 @@ 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=9324592f7c9caf8aee856aed3ea4407f1ba8a2119a39143ef6b83c11c5d3029c
+checksum=1ccc7d0306e9bcb0fad2d550e57b4db9bdb7e9907fc0418e17c72313b4342b26
nopie_files="/usr/bin/hledger"
nocross=yes # Can't yet cross compile Haskell
next reply other threads:[~2020-12-29 21:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-29 21:12 bitmeise [this message]
2021-01-05 4:23 ` q66
2021-01-05 12:06 ` bitmeise
2021-01-05 12:07 ` bitmeise
2021-01-13 18:45 ` bitmeise
2021-01-16 7:30 ` slotThe
2021-01-16 7:31 ` slotThe
2021-01-16 14:26 ` bitmeise
2021-01-16 17:57 ` [PR PATCH] [Updated] " bitmeise
2021-01-16 18:57 ` bitmeise
2021-01-30 16:33 ` [PR PATCH] [Updated] hledger: update to 1.20.3 bitmeise
2021-01-30 16:34 ` hledger: update to 1.20.4 bitmeise
2021-02-04 5:59 ` [PR PATCH] [Closed]: " 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-27534@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).