From 21fe1ffb95947a480b1eaba127287fee96e552f7 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Mon, 5 Sep 2016 16:00:51 -0400 Subject: comment --- ...comment_1_62d1c8450430a6124d676598c28a8683._comment | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) create mode 100644 doc/bugs/git-annex.cabal__58___persistent___61____61__2.2.4.1/comment_1_62d1c8450430a6124d676598c28a8683._comment diff --git a/doc/bugs/git-annex.cabal__58___persistent___61____61__2.2.4.1/comment_1_62d1c8450430a6124d676598c28a8683._comment b/doc/bugs/git-annex.cabal__58___persistent___61____61__2.2.4.1/comment_1_62d1c8450430a6124d676598c28a8683._comment new file mode 100644 index 000000000..9237988f1 --- /dev/null +++ b/doc/bugs/git-annex.cabal__58___persistent___61____61__2.2.4.1/comment_1_62d1c8450430a6124d676598c28a8683._comment @@ -0,0 +1,18 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2016-09-05T20:00:33Z" + content=""" +You have presented cabal with some dependency situation that causes its +solver to blow up. But AFAICS this is only the case in your own particular +environment; it's not the case in my envionment, or Debian's +environment, etc. + +If homebrew needs particular dependency versions, you could specify them +locally in a local cabal.config file. Or you could use stack which +should always find a consistent set of dependencies. + +I don't think it makes sense for git-annex to pin down versions like +this just because one build environment is having trouble. So I don't +plan to apply this patch. +"""]] -- cgit v1.2.3