From: Leo Famulari <leo@famulari.name>
To: Timothy Sample <samplet@ngyro.com>
Cc: 32517@debbugs.gnu.org
Subject: [bug#32517] [PATCH 0/7] Fix git-annex dependencies.
Date: Fri, 24 Aug 2018 18:01:45 -0400 [thread overview]
Message-ID: <20180824220145.GA1954@jasmine.lan> (raw)
In-Reply-To: <87a7pc31jz.fsf@ngyro.com>
[-- Attachment #1: Type: text/plain, Size: 443 bytes --]
On Thu, Aug 23, 2018 at 11:07:12PM -0400, Timothy Sample wrote:
> Hi Guix,
>
> This patch fixes several Haskell packages needed for building git-annex.
> Mostly the packages are updated to work with our new versions of
> ghc-conduit and ghc-resourcet.
Thanks! Can you clarify if git-annex is supposed to build with these
patches?
I applied them on recent master branch and tried building git-annex but
ghc-aeson fails to build.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-08-24 22:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-24 3:07 [bug#32517] [PATCH 0/7] Fix git-annex dependencies Timothy Sample
2018-08-24 3:09 ` [bug#32517] [PATCH 1/7] gnu: ghc-monad-logger: Update to 0.3.29 Timothy Sample
2018-08-24 3:09 ` [bug#32517] [PATCH 2/7] gnu: ghc-xml-conduit: Update to 1.8.0 Timothy Sample
2018-08-24 3:09 ` [bug#32517] [PATCH 3/7] gnu: ghc-feed: Update to 1.0.0.0 Timothy Sample
2018-08-24 3:09 ` [bug#32517] [PATCH 4/7] gnu: ghc-persistent: Update to 2.8.2 Timothy Sample
2018-08-24 3:09 ` [bug#32517] [PATCH 5/7] gnu: ghc-warp: Update to 3.2.18.1 Timothy Sample
2018-08-24 3:09 ` [bug#32517] [PATCH 6/7] gnu: ghc-persistent-sqlite: Update to 2.8.2 Timothy Sample
2018-08-24 3:09 ` [bug#32517] [PATCH 7/7] gnu: ghc-esqueleto: Update to commit b81e0d9 Timothy Sample
2018-08-24 22:01 ` Leo Famulari [this message]
2018-08-24 23:53 ` [bug#32517] [PATCH 0/7] Fix git-annex dependencies Timothy Sample
2018-10-02 9:49 ` Ludovic Courtès
2018-10-02 13:56 ` bug#32517: " Timothy Sample
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180824220145.GA1954@jasmine.lan \
--to=leo@famulari.name \
--cc=32517@debbugs.gnu.org \
--cc=samplet@ngyro.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).