From: pullmoll <pullmoll@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] stack: update to 2.3.1, lts-15.5
Date: Sun, 31 May 2020 04:44:14 +0200 [thread overview]
Message-ID: <20200531024414.vDGZpK2PjLQH1tIhnReNLptaQNibmWB7segF7hvaq10@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-22377@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 440 bytes --]
There is an updated pull request by pullmoll against master on the void-packages repository
https://github.com/pullmoll/void-packages stack
https://github.com/void-linux/void-packages/pull/22377
stack: update to 2.3.1, lts-15.5
This still fails to build with errors in src/Stack/Config.hs,
so this is WIP and not yet ready to merge.
[ci skip]
A patch file from https://github.com/void-linux/void-packages/pull/22377.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-stack-22377.patch --]
[-- Type: text/x-diff, Size: 1840 bytes --]
From 516316a03bff238a08fd0bd47f27928f3db90e7f Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?J=C3=BCrgen=20Buchm=C3=BCller?= <pullmoll@t-online.de>
Date: Thu, 28 May 2020 14:25:09 +0200
Subject: [PATCH] stack: update to 2.3.1, lts-15.5
Using "cabal update 'hackage.haskell.org,2020-04-29T20:25:58Z'" to
stick to the successful build report on hackage. In this case:
https://hackage.haskell.org/package/stack-2.3.1/reports/1
[ci skip]
---
srcpkgs/stack/template | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/srcpkgs/stack/template b/srcpkgs/stack/template
index 38817375fa2..fb43114dfb6 100644
--- a/srcpkgs/stack/template
+++ b/srcpkgs/stack/template
@@ -1,8 +1,8 @@
# Template file for 'stack'
pkgname=stack
-version=2.3.0.1
+version=2.3.1
revision=1
-_stackage="lts-15.4"
+_stackage="lts-15.5"
hostmakedepends="cabal-install pkg-config unzip"
makedepends="zlib-devel pcre-devel"
depends="git gmp-devel iana-etc"
@@ -12,15 +12,15 @@ license="BSD-3-Clause"
homepage="https://haskellstack.org"
distfiles="https://github.com/commercialhaskell/${pkgname}/archive/v${version}.tar.gz
https://www.stackage.org/${_stackage}/cabal.config>cabal.config-${_stackage}"
-checksum="a303a144dd3a37479e5b0fbf14d24e8d25d510bb038e413f14680ddb91036fd6
- 4147e6738cf6ef38cfd48048ef0992fb00e786068592e359fdb804e3d9ed4781"
+checksum="6701ddfc6d0be0c2bf0f75c84375e41923c5617f04222c5e582e7011c7f8fb83
+ 6faba729a0c8baf4c00eaa9e6431a846ff4ab398155dcc3558676d850cf42546"
skip_extraction="cabal.config-${_stackage}"
nocross=yes
nopie_files="/usr/bin/stack"
do_build() {
cp ${XBPS_SRCDISTDIR}/${pkgname}-${version}/cabal.config-${_stackage} cabal.config
- HOME=$PWD cabal new-update
+ HOME=$PWD cabal update 'hackage.haskell.org,2020-04-29T20:25:58Z'
HOME=$PWD cabal new-build ${makejobs} --flag disable-git-info
}
next prev parent reply other threads:[~2020-05-31 2:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-28 12:26 [PR PATCH] " pullmoll
2020-05-28 12:29 ` pullmoll
2020-05-31 2:20 ` pullmoll
2020-05-31 2:44 ` pullmoll [this message]
2020-05-31 2:46 ` pullmoll
2020-05-31 11:04 ` [PR PATCH] [Updated] " pullmoll
2020-05-31 11:08 ` [PR PATCH] [Updated] stack: update to 2.3.1 pullmoll
2020-05-31 11:13 ` pullmoll
2020-05-31 11:23 ` pullmoll
2020-05-31 11:57 ` [PR PATCH] [Updated] " pullmoll
2020-05-31 12:25 ` [PR PATCH] [Merged]: " pullmoll
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=20200531024414.vDGZpK2PjLQH1tIhnReNLptaQNibmWB7segF7hvaq10@z \
--to=pullmoll@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).