From magnus at therning.org  Thu May  1 07:10:42 2014
From: magnus at therning.org (Magnus Therning)
Date: Thu, 1 May 2014 09:10:42 +0200
Subject: [arch-haskell] What does "failed to finalize package" mean?
In-Reply-To: <CAGgpxwkcXEkN5a0iU8yGWSMiMdFc6Kno75z03Eca37=tGNs=5g@mail.gmail.com>
References: <CAGgpxwkcXEkN5a0iU8yGWSMiMdFc6Kno75z03Eca37=tGNs=5g@mail.gmail.com>
Message-ID: <20140501071042.GA5724@tatooine.lan>

On Wed, Apr 30, 2014 at 02:56:02PM -0700, Richard Wallace wrote:
> I'm trying to add gtk2hs-buildtools and am getting that error
> 
>   $ cblrepo add gtk2hs-buildtools,0.12.5.2
>   $ cblrepo pkgbuild --ghc-version 7.8.2-1
>   Failed to finalize package: gtk2hs-buildtools
> 
> In digging into the source, it looks like this means a dependency
> was not able to be found.  But all the things that gtk2hs-buildtools
> depends on are provided by ghc, so I'm a bit at a loss. Any idea
> what is going on?

Yes, that sounds right to me.

I suspect it's the following interesting combination that's causing
it:

 1. When adding you use the standard ghc (which I think still is 7.6
    on the latest release of `cblrepo`).
 2. When building the package you tell `cblrepo` to use Ghc 7.8.2
 3. The gtk2hs-buildtools.cabal file contains the following:

        if impl(ghc >= 7.7)
            build-depends: hashtables

I think this combination means that your database doesn't record the
dependency on hashtables, but on generating the PKGBUILD the
dependency appears.

I really ought to get around to making a new release of `cblrepo`!

/M

-- 
Magnus Therning                      OpenPGP: 0xAB4DFBA4 
email: magnus at therning.org   jabber: magnus at therning.org
twitter: magthe               http://therning.org/magnus

Most software today is very much like an Egyptian pyramid with
millions of bricks piled on top of each other, with no structural
integrity, but just done by brute force and thousands of slaves.
     -- Alan Kay
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
URL: <http://www.haskell.org/pipermail/arch-haskell/attachments/20140501/32bad45d/attachment.sig>

From rwallace at thewallacepack.net  Thu May  1 16:43:56 2014
From: rwallace at thewallacepack.net (Richard Wallace)
Date: Thu, 1 May 2014 09:43:56 -0700
Subject: [arch-haskell] What does "failed to finalize package" mean?
In-Reply-To: <20140501071042.GA5724@tatooine.lan>
References: <CAGgpxwkcXEkN5a0iU8yGWSMiMdFc6Kno75z03Eca37=tGNs=5g@mail.gmail.com>
 <20140501071042.GA5724@tatooine.lan>
Message-ID: <CAGgpxw=G3Df6=AYu5Q2wjRX0o4u3Zr3oatmfaoW1CHsVN6kb7A@mail.gmail.com>

*sigh* I completely missed those last few lines of the gtk2hs-buildtools
cabal file.  Thanks.

I wonder if the error message cblrepo gives could include missing
dependencies, so we wouldn't be left guessing.

Rich


On Thu, May 1, 2014 at 12:10 AM, Magnus Therning <magnus at therning.org>wrote:

> On Wed, Apr 30, 2014 at 02:56:02PM -0700, Richard Wallace wrote:
> > I'm trying to add gtk2hs-buildtools and am getting that error
> >
> >   $ cblrepo add gtk2hs-buildtools,0.12.5.2
> >   $ cblrepo pkgbuild --ghc-version 7.8.2-1
> >   Failed to finalize package: gtk2hs-buildtools
> >
> > In digging into the source, it looks like this means a dependency
> > was not able to be found.  But all the things that gtk2hs-buildtools
> > depends on are provided by ghc, so I'm a bit at a loss. Any idea
> > what is going on?
>
> Yes, that sounds right to me.
>
> I suspect it's the following interesting combination that's causing
> it:
>
>  1. When adding you use the standard ghc (which I think still is 7.6
>     on the latest release of `cblrepo`).
>  2. When building the package you tell `cblrepo` to use Ghc 7.8.2
>  3. The gtk2hs-buildtools.cabal file contains the following:
>
>         if impl(ghc >= 7.7)
>             build-depends: hashtables
>
> I think this combination means that your database doesn't record the
> dependency on hashtables, but on generating the PKGBUILD the
> dependency appears.
>
> I really ought to get around to making a new release of `cblrepo`!
>
> /M
>
> --
> Magnus Therning                      OpenPGP: 0xAB4DFBA4
> email: magnus at therning.org   jabber: magnus at therning.org
> twitter: magthe               http://therning.org/magnus
>
> Most software today is very much like an Egyptian pyramid with
> millions of bricks piled on top of each other, with no structural
> integrity, but just done by brute force and thousands of slaves.
>      -- Alan Kay
>
> _______________________________________________
> arch-haskell mailing list
> arch-haskell at haskell.org
> http://www.haskell.org/mailman/listinfo/arch-haskell
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.haskell.org/pipermail/arch-haskell/attachments/20140501/b2d4c120/attachment.html>

From magnus at therning.org  Fri May  2 21:35:09 2014
From: magnus at therning.org (Magnus Therning)
Date: Fri, 2 May 2014 23:35:09 +0200
Subject: [arch-haskell] What does "failed to finalize package" mean?
In-Reply-To: <CAGgpxw=G3Df6=AYu5Q2wjRX0o4u3Zr3oatmfaoW1CHsVN6kb7A@mail.gmail.com>
References: <CAGgpxwkcXEkN5a0iU8yGWSMiMdFc6Kno75z03Eca37=tGNs=5g@mail.gmail.com>
 <20140501071042.GA5724@tatooine.lan>
 <CAGgpxw=G3Df6=AYu5Q2wjRX0o4u3Zr3oatmfaoW1CHsVN6kb7A@mail.gmail.com>
Message-ID: <20140502213509.GA9201@tatooine.lan>

On Thu, May 01, 2014 at 09:43:56AM -0700, Richard Wallace wrote:
> *sigh* I completely missed those last few lines of the
> gtk2hs-buildtools cabal file.  Thanks.
> 
> I wonder if the error message cblrepo gives could include missing
> dependencies, so we wouldn't be left guessing.

That should be fairly easy actually.  Please add a ticket to the
cblrepo bug tracker [^1].

/M

[^1]: https://github.com/magthe/cblrepo/issues

-- 
Magnus Therning                      OpenPGP: 0xAB4DFBA4 
email: magnus at therning.org   jabber: magnus at therning.org
twitter: magthe               http://therning.org/magnus

What gets measured, gets done.
     -- Tom Peters
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
URL: <http://www.haskell.org/pipermail/arch-haskell/attachments/20140502/63d4258f/attachment.sig>

From tensor5 at gmail.com  Sat May  3 09:48:37 2014
From: tensor5 at gmail.com (Nicola Squartini)
Date: Sat, 3 May 2014 11:48:37 +0200
Subject: [arch-haskell] haskell-src-exts: Illegal instruction (core
	dumped)
In-Reply-To: <CAOWyexLFy0qejE=dNERGMh9bZS7bB8=do9PV+Ob-R9NrcaYhXg@mail.gmail.com>
References: <CAOWyexJ0hWTmV89r+cZCVxR3j7R3ZR7MfNmMkgmx_mRwvLHeZw@mail.gmail.com>
 <20140426071936.GA2112@tatooine.lan>
 <CAOWyex+cv3gqtuuuRORPQQAkPH1nqwiocqCJ7jnC7kJuBxm29Q@mail.gmail.com>
 <CAOWyexJFPrvFBVq5xwjL=OYHJT5Qbs1hwb4zz+2WTVXfJRkLkg@mail.gmail.com>
 <20140427195300.GB22526@tatooine.lan>
 <CAOWyexJeyTLpZ_AEy5doERE_e=NVJcgAHgyJ_XoXgMj4yaQpSQ@mail.gmail.com>
 <20140427203259.GA20979@tatooine.lan>
 <CAOWyexJStgJjmK421B+4SFLZkfUXiqF5KCgdrrCgY4KoTzRHCg@mail.gmail.com>
 <20140427215529.GA22848@tatooine.lan>
 <CAOWyexKicg1UhXJ=bvG8N+a+BZ7v3-T5OiudF8O4no3+vwTjuw@mail.gmail.com>
 <20140428041019.GA1212@tatooine.lan>
 <CAOWyexLFy0qejE=dNERGMh9bZS7bB8=do9PV+Ob-R9NrcaYhXg@mail.gmail.com>
Message-ID: <CAOWyexL7RZ-JHoLkfxYtvAfuJX+puZdYuvc3309KyQ_btuC--A@mail.gmail.com>

It has been proposed here
https://groups.google.com/forum/#!topic/llvm-dev/gGivQ38EHIY that LLVM
should not autodetect the cpu by default, but only if the flag -mcpu=native
is passed. This is what GCC does already with -march=native.

BTW Magnus, did you try the patch that I sent yet?

Nicola


On Mon, Apr 28, 2014 at 3:11 PM, Nicola Squartini <tensor5 at gmail.com> wrote:

> I've made a patch for HSE. Can you  compile the package with this patch?
> But don't commit it to your repo yet, just send the binary to me first and
> I'll see if it solves the issue with the illegal instruction.
>
> Thanks
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.haskell.org/pipermail/arch-haskell/attachments/20140503/d7010328/attachment.html>

From rwallace at thewallacepack.net  Wed May  7 16:45:29 2014
From: rwallace at thewallacepack.net (Richard Wallace)
Date: Wed, 7 May 2014 09:45:29 -0700
Subject: [arch-haskell] Adding non-Hackage apps to habs
Message-ID: <CAGgpxwkyGiju=SKih9p39f4jYm-5c6is93xx1r1qUoCP_BFKjw@mail.gmail.com>

Hello,

I'd like to get aura[1] added to habs.  I didn't realize when I started
that it isn't up on Hackage yet.  I did some experimenting trying to get it
added to habs, but it looks like there isn't really a way to add it to the
cblrepo.db since it isn't on Hackage.

It looks like the only way to get aura added is to create a static
directory with the PKGBUILD.  Would this be an acceptable approach or
should I push the maintainer to get aura added to Hackage instead (he said
that he will add version 2.0 to Hackage, but I can try and push to get the
current version up on Hackage)?

Thanks,
Rich
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.haskell.org/pipermail/arch-haskell/attachments/20140507/41c58d29/attachment.html>

From magnus at therning.org  Thu May  8 10:42:37 2014
From: magnus at therning.org (Magnus Therning)
Date: Thu, 8 May 2014 12:42:37 +0200
Subject: [arch-haskell] Adding non-Hackage apps to habs
In-Reply-To: <CAGgpxwkyGiju=SKih9p39f4jYm-5c6is93xx1r1qUoCP_BFKjw@mail.gmail.com>
References: <CAGgpxwkyGiju=SKih9p39f4jYm-5c6is93xx1r1qUoCP_BFKjw@mail.gmail.com>
Message-ID: <CAAExw5tt2fkZ2qi=i=X_JOOMJG44LXKgDi77mTzTGw5yMsg34Q@mail.gmail.com>

On Wed, May 7, 2014 at 6:45 PM, Richard Wallace
<rwallace at thewallacepack.net> wrote:
> Hello,
>
> I'd like to get aura[1] added to habs.  I didn't realize when I started that
> it isn't up on Hackage yet.  I did some experimenting trying to get it added
> to habs, but it looks like there isn't really a way to add it to the
> cblrepo.db since it isn't on Hackage.
>
> It looks like the only way to get aura added is to create a static directory
> with the PKGBUILD.  Would this be an acceptable approach or should I push
> the maintainer to get aura added to Hackage instead (he said that he will
> add version 2.0 to Hackage, but I can try and push to get the current
> version up on Hackage)?

There is currently no way to add a package that isn't on Hackage.
This is fairly deeply rooted in `cblrepo` but I have started taking a
few steps in the direction where it'd be possible to have more than
one Hackage the idea was to make it possible to use something like
yackage[1].  Yackage has been deprecated, but on the other hand
hackage itself is available via hackage :)

The maintenance burden is too high for me to keep any package
statically in habs:

1. Updates are not found automatically
2. PKGBUILDs can't be generated automatically (IIRC)

Hackage is the way forward!

/M

[1]: http://hackage.haskell.org/package/yackage

-- 
Magnus Therning                      OpenPGP: 0xAB4DFBA4
email: magnus at therning.org   jabber: magnus at therning.org
twitter: magthe               http://therning.org/magnus

From rwallace at thewallacepack.net  Thu May  8 16:36:52 2014
From: rwallace at thewallacepack.net (Richard Wallace)
Date: Thu, 8 May 2014 09:36:52 -0700
Subject: [arch-haskell] Adding non-Hackage apps to habs
In-Reply-To: <CAAExw5tt2fkZ2qi=i=X_JOOMJG44LXKgDi77mTzTGw5yMsg34Q@mail.gmail.com>
References: <CAGgpxwkyGiju=SKih9p39f4jYm-5c6is93xx1r1qUoCP_BFKjw@mail.gmail.com>
 <CAAExw5tt2fkZ2qi=i=X_JOOMJG44LXKgDi77mTzTGw5yMsg34Q@mail.gmail.com>
Message-ID: <CAGgpxwns7Hai4BOzHF=QzLxj+wP8H5ZOwsz_068Yc4jt4-852g@mail.gmail.com>

Yup, that's totally reasonable.  After a bit of prodding[1] I think I
convinced him to put the current version of aura up on Hackage.  Once that
happens I'll see about getting it added to the cblrepo db in habs.

Thanks,
Rich

[1] https://aur.archlinux.org/packages/aura/


On Thu, May 8, 2014 at 3:42 AM, Magnus Therning <magnus at therning.org> wrote:

> On Wed, May 7, 2014 at 6:45 PM, Richard Wallace
> <rwallace at thewallacepack.net> wrote:
> > Hello,
> >
> > I'd like to get aura[1] added to habs.  I didn't realize when I started
> that
> > it isn't up on Hackage yet.  I did some experimenting trying to get it
> added
> > to habs, but it looks like there isn't really a way to add it to the
> > cblrepo.db since it isn't on Hackage.
> >
> > It looks like the only way to get aura added is to create a static
> directory
> > with the PKGBUILD.  Would this be an acceptable approach or should I push
> > the maintainer to get aura added to Hackage instead (he said that he will
> > add version 2.0 to Hackage, but I can try and push to get the current
> > version up on Hackage)?
>
> There is currently no way to add a package that isn't on Hackage.
> This is fairly deeply rooted in `cblrepo` but I have started taking a
> few steps in the direction where it'd be possible to have more than
> one Hackage the idea was to make it possible to use something like
> yackage[1].  Yackage has been deprecated, but on the other hand
> hackage itself is available via hackage :)
>
> The maintenance burden is too high for me to keep any package
> statically in habs:
>
> 1. Updates are not found automatically
> 2. PKGBUILDs can't be generated automatically (IIRC)
>
> Hackage is the way forward!
>
> /M
>
> [1]: http://hackage.haskell.org/package/yackage
>
> --
> Magnus Therning                      OpenPGP: 0xAB4DFBA4
> email: magnus at therning.org   jabber: magnus at therning.org
> twitter: magthe               http://therning.org/magnus
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.haskell.org/pipermail/arch-haskell/attachments/20140508/8ac3dea3/attachment.html>

From katelman at gmail.com  Sun May 11 21:49:12 2014
From: katelman at gmail.com (Michael Katelman)
Date: Sun, 11 May 2014 14:49:12 -0700
Subject: [arch-haskell] help upgrading packages
Message-ID: <CAAn2fBB68tP4JFFbRJMD39y5hYiBSgugiKmZaSGfLKNi3=5ZPQ@mail.gmail.com>

I was hoping someone might help me with an issuing I'm having doing a
system upgrade. When I run pacman -Syu, I get:

:: Synchronizing package databases...
haskell-core is up to date
haskell-happstack is up to date
core is up to date
extra is up to date
community is up to date
:: Starting full system upgrade...
warning: haskell-asn1-encoding: local (0.8.1.3-4) is newer than
haskell-core (0.8.1.3-2)
warning: haskell-asn1-parse: local (0.8.1-5) is newer than haskell-core
(0.8.1-2)
warning: haskell-asn1-types: local (0.2.3-3) is newer than haskell-core
(0.2.3-1)
warning: haskell-cipher-aes: local (0.2.7-3) is newer than haskell-core
(0.2.7-1)
warning: haskell-cipher-rc4: local (0.1.4-4) is newer than haskell-core
(0.1.4-1)
warning: haskell-connection: local (0.2.1-3) is newer than haskell-core
(0.2.1-2)
warning: haskell-cprng-aes: local (0.5.2-8) is newer than haskell-core
(0.5.2-1)
warning: haskell-crypto-cipher-types: local (0.0.9-3) is newer than
haskell-core (0.0.9-1)
warning: haskell-crypto-numbers: local (0.2.3-3) is newer than haskell-core
(0.2.3-1)
warning: haskell-crypto-pubkey: local (0.2.4-6) is newer than haskell-core
(0.2.4-1)
warning: haskell-crypto-pubkey-types: local (0.4.2.2-3) is newer than
haskell-core (0.4.2.2-1)
warning: haskell-crypto-random: local (0.0.7-4) is newer than haskell-core
(0.0.7-1)
warning: haskell-http-client-tls: local (0.2.1.1-21) is newer than
haskell-core (0.2.1.1-2)
warning: haskell-http-conduit: local (2.1.2-4) is newer than haskell-core
(2.1.2-2)
warning: haskell-mime-types: local (0.1.0.4-3) is newer than haskell-core
(0.1.0.4-2)
warning: haskell-publicsuffixlist: local (0.1-7) is newer than haskell-core
(0.1-2)
warning: haskell-securemem: local (0.1.3-3) is newer than haskell-core
(0.1.3-1)
warning: haskell-socks: local (0.5.4-10) is newer than haskell-core
(0.5.4-2)
warning: haskell-x509: local (1.4.11-5) is newer than haskell-core
(1.4.11-2)
warning: haskell-x509-store: local (1.4.4-9) is newer than haskell-core
(1.4.4-2)
warning: haskell-x509-validation: local (1.5.0-9) is newer than
haskell-core (1.5.0-2)
resolving dependencies...
looking for inter-conflicts...
error: failed to prepare transaction (could not satisfy dependencies)
:: haskell-connection: requires haskell-network=2.4.2.2-60
:: haskell-connection: requires haskell-tls=1.2.6-5
:: haskell-connection: requires haskell-x509=1.4.11-5
:: haskell-connection: requires haskell-x509-store=1.4.4-9
:: haskell-connection: requires haskell-x509-validation=1.5.0-9
:: haskell-cookie: requires haskell-blaze-builder=0.3.3.2-59
:: haskell-cookie: requires haskell-text=1.1.1.1-1
:: haskell-cprng-aes: requires haskell-cipher-aes=0.2.7-3
:: haskell-cprng-aes: requires haskell-crypto-random=0.0.7-4
:: haskell-http-client-tls: requires haskell-http-client=0.3.2.1-2
:: haskell-http-client-tls: requires haskell-network=2.4.2.2-60
:: haskell-http-client-tls: requires haskell-tls=1.2.6-5
:: haskell-http-conduit: requires haskell-conduit=1.1.1.1-1
:: haskell-http-conduit: requires haskell-http-client=0.3.2.1-2
:: haskell-http-conduit: requires haskell-http-types=0.8.4-4
:: haskell-http-conduit: requires haskell-lifted-base=0.2.2.1-3
:: haskell-http-conduit: requires haskell-monad-control=0.3.2.3-5
:: haskell-http-conduit: requires haskell-resourcet=1.1.2-1
:: haskell-socks: requires haskell-network=2.4.2.2-60
:: haskell-x509-system: requires haskell-x509=1.4.11-5
:: haskell-x509-system: requires haskell-x509-store=1.4.4-9


I really have no idea what to do with this or what would have caused it.
I'm sure it's some important misunderstanding on my part. Any help would be
greatly appreciated.

-Mike
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.haskell.org/pipermail/arch-haskell/attachments/20140511/84de6062/attachment.html>

From tensor5 at gmail.com  Mon May 12 06:49:25 2014
From: tensor5 at gmail.com (Nicola Squartini)
Date: Mon, 12 May 2014 08:49:25 +0200
Subject: [arch-haskell] help upgrading packages
In-Reply-To: <CAAn2fBB68tP4JFFbRJMD39y5hYiBSgugiKmZaSGfLKNi3=5ZPQ@mail.gmail.com>
References: <CAAn2fBB68tP4JFFbRJMD39y5hYiBSgugiKmZaSGfLKNi3=5ZPQ@mail.gmail.com>
Message-ID: <CAOWyexL=PAD53onz1BqtrNJhY3HgX7srKqrBwTVnBLNVMXKTQQ@mail.gmail.com>

http-conduit and its dependencies moved from haskell-happstack to
haskell-core and at that time the package release number reset to one. You
have to manually uninstall and reinstall those packages.

Nicola


On Sun, May 11, 2014 at 11:49 PM, Michael Katelman <katelman at gmail.com>wrote:

> I was hoping someone might help me with an issuing I'm having doing a
> system upgrade. When I run pacman -Syu, I get:
>
> :: Synchronizing package databases...
> haskell-core is up to date
> haskell-happstack is up to date
> core is up to date
> extra is up to date
> community is up to date
> :: Starting full system upgrade...
> warning: haskell-asn1-encoding: local (0.8.1.3-4) is newer than
> haskell-core (0.8.1.3-2)
> warning: haskell-asn1-parse: local (0.8.1-5) is newer than haskell-core
> (0.8.1-2)
> warning: haskell-asn1-types: local (0.2.3-3) is newer than haskell-core
> (0.2.3-1)
> warning: haskell-cipher-aes: local (0.2.7-3) is newer than haskell-core
> (0.2.7-1)
> warning: haskell-cipher-rc4: local (0.1.4-4) is newer than haskell-core
> (0.1.4-1)
> warning: haskell-connection: local (0.2.1-3) is newer than haskell-core
> (0.2.1-2)
> warning: haskell-cprng-aes: local (0.5.2-8) is newer than haskell-core
> (0.5.2-1)
> warning: haskell-crypto-cipher-types: local (0.0.9-3) is newer than
> haskell-core (0.0.9-1)
> warning: haskell-crypto-numbers: local (0.2.3-3) is newer than
> haskell-core (0.2.3-1)
> warning: haskell-crypto-pubkey: local (0.2.4-6) is newer than haskell-core
> (0.2.4-1)
> warning: haskell-crypto-pubkey-types: local (0.4.2.2-3) is newer than
> haskell-core (0.4.2.2-1)
> warning: haskell-crypto-random: local (0.0.7-4) is newer than haskell-core
> (0.0.7-1)
> warning: haskell-http-client-tls: local (0.2.1.1-21) is newer than
> haskell-core (0.2.1.1-2)
> warning: haskell-http-conduit: local (2.1.2-4) is newer than haskell-core
> (2.1.2-2)
> warning: haskell-mime-types: local (0.1.0.4-3) is newer than haskell-core
> (0.1.0.4-2)
> warning: haskell-publicsuffixlist: local (0.1-7) is newer than
> haskell-core (0.1-2)
> warning: haskell-securemem: local (0.1.3-3) is newer than haskell-core
> (0.1.3-1)
> warning: haskell-socks: local (0.5.4-10) is newer than haskell-core
> (0.5.4-2)
> warning: haskell-x509: local (1.4.11-5) is newer than haskell-core
> (1.4.11-2)
> warning: haskell-x509-store: local (1.4.4-9) is newer than haskell-core
> (1.4.4-2)
> warning: haskell-x509-validation: local (1.5.0-9) is newer than
> haskell-core (1.5.0-2)
> resolving dependencies...
> looking for inter-conflicts...
> error: failed to prepare transaction (could not satisfy dependencies)
> :: haskell-connection: requires haskell-network=2.4.2.2-60
> :: haskell-connection: requires haskell-tls=1.2.6-5
> :: haskell-connection: requires haskell-x509=1.4.11-5
> :: haskell-connection: requires haskell-x509-store=1.4.4-9
> :: haskell-connection: requires haskell-x509-validation=1.5.0-9
> :: haskell-cookie: requires haskell-blaze-builder=0.3.3.2-59
> :: haskell-cookie: requires haskell-text=1.1.1.1-1
> :: haskell-cprng-aes: requires haskell-cipher-aes=0.2.7-3
> :: haskell-cprng-aes: requires haskell-crypto-random=0.0.7-4
> :: haskell-http-client-tls: requires haskell-http-client=0.3.2.1-2
> :: haskell-http-client-tls: requires haskell-network=2.4.2.2-60
> :: haskell-http-client-tls: requires haskell-tls=1.2.6-5
> :: haskell-http-conduit: requires haskell-conduit=1.1.1.1-1
> :: haskell-http-conduit: requires haskell-http-client=0.3.2.1-2
> :: haskell-http-conduit: requires haskell-http-types=0.8.4-4
> :: haskell-http-conduit: requires haskell-lifted-base=0.2.2.1-3
> :: haskell-http-conduit: requires haskell-monad-control=0.3.2.3-5
> :: haskell-http-conduit: requires haskell-resourcet=1.1.2-1
> :: haskell-socks: requires haskell-network=2.4.2.2-60
> :: haskell-x509-system: requires haskell-x509=1.4.11-5
> :: haskell-x509-system: requires haskell-x509-store=1.4.4-9
>
>
> I really have no idea what to do with this or what would have caused it.
> I'm sure it's some important misunderstanding on my part. Any help would be
> greatly appreciated.
>
> -Mike
>
> _______________________________________________
> arch-haskell mailing list
> arch-haskell at haskell.org
> http://www.haskell.org/mailman/listinfo/arch-haskell
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.haskell.org/pipermail/arch-haskell/attachments/20140512/846a249d/attachment-0001.html>

From dawid.loubser at ibi.co.za  Mon May 12 12:24:58 2014
From: dawid.loubser at ibi.co.za (Dawid Loubser)
Date: Mon, 12 May 2014 14:24:58 +0200
Subject: [arch-haskell] help upgrading packages
In-Reply-To: <CAOWyexL=PAD53onz1BqtrNJhY3HgX7srKqrBwTVnBLNVMXKTQQ@mail.gmail.com>
References: <CAAn2fBB68tP4JFFbRJMD39y5hYiBSgugiKmZaSGfLKNi3=5ZPQ@mail.gmail.com>
 <CAOWyexL=PAD53onz1BqtrNJhY3HgX7srKqrBwTVnBLNVMXKTQQ@mail.gmail.com>
Message-ID: <5370BD9A.4070200@ibi.co.za>

I had a similar issue with a large number of packages.
I ended up removing and re-installing my entire Haskell ecosystem, and
now things work again.

I note the absence of certain packages like haskell-buildwrapper (which
EclipseFP tools needs) - and reading the wiki, it seems confusing at
this time whether the Haskell tinkerer / developer should just be using
cabal-install to install all required packages (even though I know that
cabal is not a package management system) or... what?

What are other Haskell developers here doing currently?

kind regards,
Dawid Loubser


On 12/05/2014 08:49, Nicola Squartini wrote:
> http-conduit and its dependencies moved from haskell-happstack to
> haskell-core and at that time the package release number reset to one.
> You have to manually uninstall and reinstall those packages.
>
> Nicola
>
>
> On Sun, May 11, 2014 at 11:49 PM, Michael Katelman <katelman at gmail.com
> <mailto:katelman at gmail.com>> wrote:
>
>     I was hoping someone might help me with an issuing I'm having
>     doing a system upgrade. When I run pacman -Syu, I get:
>
>     :: Synchronizing package databases...
>     haskell-core is up to date
>     haskell-happstack is up to date
>     core is up to date
>     extra is up to date
>     community is up to date
>     :: Starting full system upgrade...
>     warning: haskell-asn1-encoding: local (0.8.1.3-4) is newer than
>     haskell-core (0.8.1.3-2)
>     warning: haskell-asn1-parse: local (0.8.1-5) is newer than
>     haskell-core (0.8.1-2)
>     warning: haskell-asn1-types: local (0.2.3-3) is newer than
>     haskell-core (0.2.3-1)
>     warning: haskell-cipher-aes: local (0.2.7-3) is newer than
>     haskell-core (0.2.7-1)
>     warning: haskell-cipher-rc4: local (0.1.4-4) is newer than
>     haskell-core (0.1.4-1)
>     warning: haskell-connection: local (0.2.1-3) is newer than
>     haskell-core (0.2.1-2)
>     warning: haskell-cprng-aes: local (0.5.2-8) is newer than
>     haskell-core (0.5.2-1)
>     warning: haskell-crypto-cipher-types: local (0.0.9-3) is newer
>     than haskell-core (0.0.9-1)
>     warning: haskell-crypto-numbers: local (0.2.3-3) is newer than
>     haskell-core (0.2.3-1)
>     warning: haskell-crypto-pubkey: local (0.2.4-6) is newer than
>     haskell-core (0.2.4-1)
>     warning: haskell-crypto-pubkey-types: local (0.4.2.2-3) is newer
>     than haskell-core (0.4.2.2-1)
>     warning: haskell-crypto-random: local (0.0.7-4) is newer than
>     haskell-core (0.0.7-1)
>     warning: haskell-http-client-tls: local (0.2.1.1-21) is newer than
>     haskell-core (0.2.1.1-2)
>     warning: haskell-http-conduit: local (2.1.2-4) is newer than
>     haskell-core (2.1.2-2)
>     warning: haskell-mime-types: local (0.1.0.4-3) is newer than
>     haskell-core (0.1.0.4-2)
>     warning: haskell-publicsuffixlist: local (0.1-7) is newer than
>     haskell-core (0.1-2)
>     warning: haskell-securemem: local (0.1.3-3) is newer than
>     haskell-core (0.1.3-1)
>     warning: haskell-socks: local (0.5.4-10) is newer than
>     haskell-core (0.5.4-2)
>     warning: haskell-x509: local (1.4.11-5) is newer than haskell-core
>     (1.4.11-2)
>     warning: haskell-x509-store: local (1.4.4-9) is newer than
>     haskell-core (1.4.4-2)
>     warning: haskell-x509-validation: local (1.5.0-9) is newer than
>     haskell-core (1.5.0-2)
>     resolving dependencies...
>     looking for inter-conflicts...
>     error: failed to prepare transaction (could not satisfy dependencies)
>     :: haskell-connection: requires haskell-network=2.4.2.2-60
>     :: haskell-connection: requires haskell-tls=1.2.6-5
>     :: haskell-connection: requires haskell-x509=1.4.11-5
>     :: haskell-connection: requires haskell-x509-store=1.4.4-9
>     :: haskell-connection: requires haskell-x509-validation=1.5.0-9
>     :: haskell-cookie: requires haskell-blaze-builder=0.3.3.2-59
>     :: haskell-cookie: requires haskell-text=1.1.1.1-1
>     :: haskell-cprng-aes: requires haskell-cipher-aes=0.2.7-3
>     :: haskell-cprng-aes: requires haskell-crypto-random=0.0.7-4
>     :: haskell-http-client-tls: requires haskell-http-client=0.3.2.1-2
>     :: haskell-http-client-tls: requires haskell-network=2.4.2.2-60
>     :: haskell-http-client-tls: requires haskell-tls=1.2.6-5
>     :: haskell-http-conduit: requires haskell-conduit=1.1.1.1-1
>     :: haskell-http-conduit: requires haskell-http-client=0.3.2.1-2
>     :: haskell-http-conduit: requires haskell-http-types=0.8.4-4
>     :: haskell-http-conduit: requires haskell-lifted-base=0.2.2.1-3
>     :: haskell-http-conduit: requires haskell-monad-control=0.3.2.3-5
>     :: haskell-http-conduit: requires haskell-resourcet=1.1.2-1
>     :: haskell-socks: requires haskell-network=2.4.2.2-60
>     :: haskell-x509-system: requires haskell-x509=1.4.11-5
>     :: haskell-x509-system: requires haskell-x509-store=1.4.4-9
>
>
>     I really have no idea what to do with this or what would have
>     caused it. I'm sure it's some important misunderstanding on my
>     part. Any help would be greatly appreciated.
>
>     -Mike
>
>     _______________________________________________
>     arch-haskell mailing list
>     arch-haskell at haskell.org <mailto:arch-haskell at haskell.org>
>     http://www.haskell.org/mailman/listinfo/arch-haskell
>
>
>
>
> _______________________________________________
> arch-haskell mailing list
> arch-haskell at haskell.org
> http://www.haskell.org/mailman/listinfo/arch-haskell

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.haskell.org/pipermail/arch-haskell/attachments/20140512/621bd666/attachment.html>

From tensor5 at gmail.com  Mon May 12 13:33:11 2014
From: tensor5 at gmail.com (Nicola Squartini)
Date: Mon, 12 May 2014 15:33:11 +0200
Subject: [arch-haskell] help upgrading packages
In-Reply-To: <5370BD9A.4070200@ibi.co.za>
References: <CAAn2fBB68tP4JFFbRJMD39y5hYiBSgugiKmZaSGfLKNi3=5ZPQ@mail.gmail.com>
 <CAOWyexL=PAD53onz1BqtrNJhY3HgX7srKqrBwTVnBLNVMXKTQQ@mail.gmail.com>
 <5370BD9A.4070200@ibi.co.za>
Message-ID: <CAOWyexJ9HSBmh-kkAks-BdJOsnQiYfCWF_ncFYZWWHysdMriRw@mail.gmail.com>

On Mon, May 12, 2014 at 2:24 PM, Dawid Loubser <dawid.loubser at ibi.co.za>wrote:

>  I had a similar issue with a large number of packages.
> I ended up removing and re-installing my entire Haskell ecosystem, and now
> things work again.
>
> Normally this should never happen. It's because Haskell is very strict on
dependencies (despite being lazy on other things).
In this case the reason was that those packages were added to the
repository  [haskell-core] with initial release number set to 1, although
they had been in [haskell-happstack] already for some time and their
release number was higher. I removed those immediately
from [haskell-happstack] to avoid duplicate work, but they must also be
manually removed from local, since pacman always keeps the highest
version-release.

In order to avoid this kind of issues in the future we should either have a
policy to coordinate work between different haskell repositories, or merge
everything into a unique repository and call it simply [haskell].



> I note the absence of certain packages like haskell-buildwrapper (which
> EclipseFP tools needs) - and reading the wiki, it seems confusing at this
> time whether the Haskell tinkerer / developer should just be using
> cabal-install to install all required packages (even though I know that
> cabal is not a package management system) or... what?
>

Personally I don't like installing things using cabal-install because in my
opinion the distro package manager should always be in charge.


> What are other Haskell developers here doing currently?
>
> kind regards,
> Dawid Loubser
>
>
>
> On 12/05/2014 08:49, Nicola Squartini wrote:
>
> http-conduit and its dependencies moved from haskell-happstack to
> haskell-core and at that time the package release number reset to one. You
> have to manually uninstall and reinstall those packages.
>
>  Nicola
>
>
> On Sun, May 11, 2014 at 11:49 PM, Michael Katelman <katelman at gmail.com>wrote:
>
>> I was hoping someone might help me with an issuing I'm having doing a
>> system upgrade. When I run pacman -Syu, I get:
>>
>>  :: Synchronizing package databases...
>> haskell-core is up to date
>> haskell-happstack is up to date
>> core is up to date
>> extra is up to date
>> community is up to date
>> :: Starting full system upgrade...
>> warning: haskell-asn1-encoding: local (0.8.1.3-4) is newer than
>> haskell-core (0.8.1.3-2)
>> warning: haskell-asn1-parse: local (0.8.1-5) is newer than haskell-core
>> (0.8.1-2)
>> warning: haskell-asn1-types: local (0.2.3-3) is newer than haskell-core
>> (0.2.3-1)
>> warning: haskell-cipher-aes: local (0.2.7-3) is newer than haskell-core
>> (0.2.7-1)
>> warning: haskell-cipher-rc4: local (0.1.4-4) is newer than haskell-core
>> (0.1.4-1)
>> warning: haskell-connection: local (0.2.1-3) is newer than haskell-core
>> (0.2.1-2)
>> warning: haskell-cprng-aes: local (0.5.2-8) is newer than haskell-core
>> (0.5.2-1)
>> warning: haskell-crypto-cipher-types: local (0.0.9-3) is newer than
>> haskell-core (0.0.9-1)
>> warning: haskell-crypto-numbers: local (0.2.3-3) is newer than
>> haskell-core (0.2.3-1)
>> warning: haskell-crypto-pubkey: local (0.2.4-6) is newer than
>> haskell-core (0.2.4-1)
>> warning: haskell-crypto-pubkey-types: local (0.4.2.2-3) is newer than
>> haskell-core (0.4.2.2-1)
>> warning: haskell-crypto-random: local (0.0.7-4) is newer than
>> haskell-core (0.0.7-1)
>> warning: haskell-http-client-tls: local (0.2.1.1-21) is newer than
>> haskell-core (0.2.1.1-2)
>> warning: haskell-http-conduit: local (2.1.2-4) is newer than haskell-core
>> (2.1.2-2)
>> warning: haskell-mime-types: local (0.1.0.4-3) is newer than haskell-core
>> (0.1.0.4-2)
>> warning: haskell-publicsuffixlist: local (0.1-7) is newer than
>> haskell-core (0.1-2)
>> warning: haskell-securemem: local (0.1.3-3) is newer than haskell-core
>> (0.1.3-1)
>> warning: haskell-socks: local (0.5.4-10) is newer than haskell-core
>> (0.5.4-2)
>> warning: haskell-x509: local (1.4.11-5) is newer than haskell-core
>> (1.4.11-2)
>> warning: haskell-x509-store: local (1.4.4-9) is newer than haskell-core
>> (1.4.4-2)
>> warning: haskell-x509-validation: local (1.5.0-9) is newer than
>> haskell-core (1.5.0-2)
>> resolving dependencies...
>> looking for inter-conflicts...
>> error: failed to prepare transaction (could not satisfy dependencies)
>> :: haskell-connection: requires haskell-network=2.4.2.2-60
>> :: haskell-connection: requires haskell-tls=1.2.6-5
>> :: haskell-connection: requires haskell-x509=1.4.11-5
>> :: haskell-connection: requires haskell-x509-store=1.4.4-9
>> :: haskell-connection: requires haskell-x509-validation=1.5.0-9
>> :: haskell-cookie: requires haskell-blaze-builder=0.3.3.2-59
>> :: haskell-cookie: requires haskell-text=1.1.1.1-1
>> :: haskell-cprng-aes: requires haskell-cipher-aes=0.2.7-3
>> :: haskell-cprng-aes: requires haskell-crypto-random=0.0.7-4
>> :: haskell-http-client-tls: requires haskell-http-client=0.3.2.1-2
>> :: haskell-http-client-tls: requires haskell-network=2.4.2.2-60
>> :: haskell-http-client-tls: requires haskell-tls=1.2.6-5
>> :: haskell-http-conduit: requires haskell-conduit=1.1.1.1-1
>> :: haskell-http-conduit: requires haskell-http-client=0.3.2.1-2
>> :: haskell-http-conduit: requires haskell-http-types=0.8.4-4
>> :: haskell-http-conduit: requires haskell-lifted-base=0.2.2.1-3
>> :: haskell-http-conduit: requires haskell-monad-control=0.3.2.3-5
>> :: haskell-http-conduit: requires haskell-resourcet=1.1.2-1
>> :: haskell-socks: requires haskell-network=2.4.2.2-60
>> :: haskell-x509-system: requires haskell-x509=1.4.11-5
>> :: haskell-x509-system: requires haskell-x509-store=1.4.4-9
>>
>>
>>  I really have no idea what to do with this or what would have caused
>> it. I'm sure it's some important misunderstanding on my part. Any help
>> would be greatly appreciated.
>>
>>  -Mike
>>
>> _______________________________________________
>> arch-haskell mailing list
>> arch-haskell at haskell.org
>> http://www.haskell.org/mailman/listinfo/arch-haskell
>>
>>
>
>
> _______________________________________________
> arch-haskell mailing listarch-haskell at haskell.orghttp://www.haskell.org/mailman/listinfo/arch-haskell
>
>
>
> _______________________________________________
> arch-haskell mailing list
> arch-haskell at haskell.org
> http://www.haskell.org/mailman/listinfo/arch-haskell
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.haskell.org/pipermail/arch-haskell/attachments/20140512/6e93a61d/attachment-0001.html>

From magnus at therning.org  Mon May 12 13:47:29 2014
From: magnus at therning.org (Magnus Therning)
Date: Mon, 12 May 2014 15:47:29 +0200
Subject: [arch-haskell] help upgrading packages
In-Reply-To: <CAOWyexJ9HSBmh-kkAks-BdJOsnQiYfCWF_ncFYZWWHysdMriRw@mail.gmail.com>
References: <CAAn2fBB68tP4JFFbRJMD39y5hYiBSgugiKmZaSGfLKNi3=5ZPQ@mail.gmail.com>
 <CAOWyexL=PAD53onz1BqtrNJhY3HgX7srKqrBwTVnBLNVMXKTQQ@mail.gmail.com>
 <5370BD9A.4070200@ibi.co.za>
 <CAOWyexJ9HSBmh-kkAks-BdJOsnQiYfCWF_ncFYZWWHysdMriRw@mail.gmail.com>
Message-ID: <CAAExw5vfvxiAat4cmaiV6Dc8oddSWPRLdvOqwe0eTGf3zE7e7w@mail.gmail.com>

On Mon, May 12, 2014 at 3:33 PM, Nicola Squartini <tensor5 at gmail.com> wrote:
> On Mon, May 12, 2014 at 2:24 PM, Dawid Loubser <dawid.loubser at ibi.co.za>
> wrote:
>>
>> I had a similar issue with a large number of packages.
>> I ended up removing and re-installing my entire Haskell ecosystem, and now
>> things work again.
>>
> Normally this should never happen. It's because Haskell is very strict on
> dependencies (despite being lazy on other things).
> In this case the reason was that those packages were added to the repository
> [haskell-core] with initial release number set to 1, although they had been
> in [haskell-happstack] already for some time and their release number was
> higher. I removed those immediately from [haskell-happstack] to avoid
> duplicate work, but they must also be manually removed from local, since
> pacman always keeps the highest version-release.
>
> In order to avoid this kind of issues in the future we should either have a
> policy to coordinate work between different haskell repositories, or merge
> everything into a unique repository and call it simply [haskell].

Indeed.  This is entirely my fault!

I have not been keeping track of what is available in any other repos
at all.  I was even under the impression that there were no other
maintained repos at the moment.  Clearly I am completely wrong :(

>> I note the absence of certain packages like haskell-buildwrapper (which
>> EclipseFP tools needs) - and reading the wiki, it seems confusing at this
>> time whether the Haskell tinkerer / developer should just be using
>> cabal-install to install all required packages (even though I know that
>> cabal is not a package management system) or... what?
>
> Personally I don't like installing things using cabal-install because in my
> opinion the distro package manager should always be in charge.

The same goes for me.  Occasionally I revert to installing a package
for the local user only, but not even then do I use `cabal install` to
do that, I prefer running `./Setup.hs configure,build,install` myself.

I do mean to look into using `cabal` myself at some point, because I
keep on hearing good things about it.  So far every time I've tried it
I've run into something weird, most recently it was trying to install
an older version of a lib than was needed, and I already had the newer
version installed on my system too.  A lot of terrifyingly clever
people swear by it though, so there has to be something I'm missing
out on!

/M

-- 
Magnus Therning                      OpenPGP: 0xAB4DFBA4
email: magnus at therning.org   jabber: magnus at therning.org
twitter: magthe               http://therning.org/magnus

From katelman at gmail.com  Mon May 12 14:01:41 2014
From: katelman at gmail.com (Michael Katelman)
Date: Mon, 12 May 2014 07:01:41 -0700
Subject: [arch-haskell] help upgrading packages
In-Reply-To: <5370BD9A.4070200@ibi.co.za>
References: <CAAn2fBB68tP4JFFbRJMD39y5hYiBSgugiKmZaSGfLKNi3=5ZPQ@mail.gmail.com>
 <CAOWyexL=PAD53onz1BqtrNJhY3HgX7srKqrBwTVnBLNVMXKTQQ@mail.gmail.com>
 <5370BD9A.4070200@ibi.co.za>
Message-ID: <CAAn2fBDXEH3PkWKeCwBufN3SV0c_TTTjVykHWtPxgD02hC_2xg@mail.gmail.com>

Thanks, all! I ultimately did the same thing: removing and re-installing
the entire Haskell ecosystem. It seems happy now :)

-Mike


On Mon, May 12, 2014 at 5:24 AM, Dawid Loubser <dawid.loubser at ibi.co.za>wrote:

>  I had a similar issue with a large number of packages.
> I ended up removing and re-installing my entire Haskell ecosystem, and now
> things work again.
>
> I note the absence of certain packages like haskell-buildwrapper (which
> EclipseFP tools needs) - and reading the wiki, it seems confusing at this
> time whether the Haskell tinkerer / developer should just be using
> cabal-install to install all required packages (even though I know that
> cabal is not a package management system) or... what?
>
> What are other Haskell developers here doing currently?
>
> kind regards,
> Dawid Loubser
>
>
>
> On 12/05/2014 08:49, Nicola Squartini wrote:
>
> http-conduit and its dependencies moved from haskell-happstack to
> haskell-core and at that time the package release number reset to one. You
> have to manually uninstall and reinstall those packages.
>
>  Nicola
>
>
> On Sun, May 11, 2014 at 11:49 PM, Michael Katelman <katelman at gmail.com>wrote:
>
>> I was hoping someone might help me with an issuing I'm having doing a
>> system upgrade. When I run pacman -Syu, I get:
>>
>>  :: Synchronizing package databases...
>> haskell-core is up to date
>> haskell-happstack is up to date
>> core is up to date
>> extra is up to date
>> community is up to date
>> :: Starting full system upgrade...
>> warning: haskell-asn1-encoding: local (0.8.1.3-4) is newer than
>> haskell-core (0.8.1.3-2)
>> warning: haskell-asn1-parse: local (0.8.1-5) is newer than haskell-core
>> (0.8.1-2)
>> warning: haskell-asn1-types: local (0.2.3-3) is newer than haskell-core
>> (0.2.3-1)
>> warning: haskell-cipher-aes: local (0.2.7-3) is newer than haskell-core
>> (0.2.7-1)
>> warning: haskell-cipher-rc4: local (0.1.4-4) is newer than haskell-core
>> (0.1.4-1)
>> warning: haskell-connection: local (0.2.1-3) is newer than haskell-core
>> (0.2.1-2)
>> warning: haskell-cprng-aes: local (0.5.2-8) is newer than haskell-core
>> (0.5.2-1)
>> warning: haskell-crypto-cipher-types: local (0.0.9-3) is newer than
>> haskell-core (0.0.9-1)
>> warning: haskell-crypto-numbers: local (0.2.3-3) is newer than
>> haskell-core (0.2.3-1)
>> warning: haskell-crypto-pubkey: local (0.2.4-6) is newer than
>> haskell-core (0.2.4-1)
>> warning: haskell-crypto-pubkey-types: local (0.4.2.2-3) is newer than
>> haskell-core (0.4.2.2-1)
>> warning: haskell-crypto-random: local (0.0.7-4) is newer than
>> haskell-core (0.0.7-1)
>> warning: haskell-http-client-tls: local (0.2.1.1-21) is newer than
>> haskell-core (0.2.1.1-2)
>> warning: haskell-http-conduit: local (2.1.2-4) is newer than haskell-core
>> (2.1.2-2)
>> warning: haskell-mime-types: local (0.1.0.4-3) is newer than haskell-core
>> (0.1.0.4-2)
>> warning: haskell-publicsuffixlist: local (0.1-7) is newer than
>> haskell-core (0.1-2)
>> warning: haskell-securemem: local (0.1.3-3) is newer than haskell-core
>> (0.1.3-1)
>> warning: haskell-socks: local (0.5.4-10) is newer than haskell-core
>> (0.5.4-2)
>> warning: haskell-x509: local (1.4.11-5) is newer than haskell-core
>> (1.4.11-2)
>> warning: haskell-x509-store: local (1.4.4-9) is newer than haskell-core
>> (1.4.4-2)
>> warning: haskell-x509-validation: local (1.5.0-9) is newer than
>> haskell-core (1.5.0-2)
>> resolving dependencies...
>> looking for inter-conflicts...
>> error: failed to prepare transaction (could not satisfy dependencies)
>> :: haskell-connection: requires haskell-network=2.4.2.2-60
>> :: haskell-connection: requires haskell-tls=1.2.6-5
>> :: haskell-connection: requires haskell-x509=1.4.11-5
>> :: haskell-connection: requires haskell-x509-store=1.4.4-9
>> :: haskell-connection: requires haskell-x509-validation=1.5.0-9
>> :: haskell-cookie: requires haskell-blaze-builder=0.3.3.2-59
>> :: haskell-cookie: requires haskell-text=1.1.1.1-1
>> :: haskell-cprng-aes: requires haskell-cipher-aes=0.2.7-3
>> :: haskell-cprng-aes: requires haskell-crypto-random=0.0.7-4
>> :: haskell-http-client-tls: requires haskell-http-client=0.3.2.1-2
>> :: haskell-http-client-tls: requires haskell-network=2.4.2.2-60
>> :: haskell-http-client-tls: requires haskell-tls=1.2.6-5
>> :: haskell-http-conduit: requires haskell-conduit=1.1.1.1-1
>> :: haskell-http-conduit: requires haskell-http-client=0.3.2.1-2
>> :: haskell-http-conduit: requires haskell-http-types=0.8.4-4
>> :: haskell-http-conduit: requires haskell-lifted-base=0.2.2.1-3
>> :: haskell-http-conduit: requires haskell-monad-control=0.3.2.3-5
>> :: haskell-http-conduit: requires haskell-resourcet=1.1.2-1
>> :: haskell-socks: requires haskell-network=2.4.2.2-60
>> :: haskell-x509-system: requires haskell-x509=1.4.11-5
>> :: haskell-x509-system: requires haskell-x509-store=1.4.4-9
>>
>>
>>  I really have no idea what to do with this or what would have caused
>> it. I'm sure it's some important misunderstanding on my part. Any help
>> would be greatly appreciated.
>>
>>  -Mike
>>
>> _______________________________________________
>> arch-haskell mailing list
>> arch-haskell at haskell.org
>> http://www.haskell.org/mailman/listinfo/arch-haskell
>>
>>
>
>
> _______________________________________________
> arch-haskell mailing listarch-haskell at haskell.orghttp://www.haskell.org/mailman/listinfo/arch-haskell
>
>
>
> _______________________________________________
> arch-haskell mailing list
> arch-haskell at haskell.org
> http://www.haskell.org/mailman/listinfo/arch-haskell
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.haskell.org/pipermail/arch-haskell/attachments/20140512/3c7aa635/attachment.html>

From dawid.loubser at ibi.co.za  Mon May 12 14:02:49 2014
From: dawid.loubser at ibi.co.za (Dawid Loubser)
Date: Mon, 12 May 2014 16:02:49 +0200
Subject: [arch-haskell] help upgrading packages
In-Reply-To: <CAAExw5vfvxiAat4cmaiV6Dc8oddSWPRLdvOqwe0eTGf3zE7e7w@mail.gmail.com>
References: <CAAn2fBB68tP4JFFbRJMD39y5hYiBSgugiKmZaSGfLKNi3=5ZPQ@mail.gmail.com>	<CAOWyexL=PAD53onz1BqtrNJhY3HgX7srKqrBwTVnBLNVMXKTQQ@mail.gmail.com>	<5370BD9A.4070200@ibi.co.za>	<CAOWyexJ9HSBmh-kkAks-BdJOsnQiYfCWF_ncFYZWWHysdMriRw@mail.gmail.com>
 <CAAExw5vfvxiAat4cmaiV6Dc8oddSWPRLdvOqwe0eTGf3zE7e7w@mail.gmail.com>
Message-ID: <5370D489.9030906@ibi.co.za>

I'm afraid that I am not one of those 'terrifyingly clever' people you
speak of, Magnus, but in the past I have had a world of pain trying to
use a mixture of packages between cabal and pacman.

Had a very happy time using just pacman until *haskell-buildwrapper*
disappeared recently, and I could no longer use my favourite Haskell IDE :-(
I don't want to even try installing it using cabal, becuase then I'll be
back in package-dependency hell.

I have to say, I appreciate your efforts into making Haskell easy to use
on Arch so very much - I don't mean to complain at all!

regards,
Dawid


On 12/05/2014 15:47, Magnus Therning wrote:
> On Mon, May 12, 2014 at 3:33 PM, Nicola Squartini <tensor5 at gmail.com> wrote:
>> On Mon, May 12, 2014 at 2:24 PM, Dawid Loubser <dawid.loubser at ibi.co.za>
>> wrote:
>>> I had a similar issue with a large number of packages.
>>> I ended up removing and re-installing my entire Haskell ecosystem, and now
>>> things work again.
>>>
>> Normally this should never happen. It's because Haskell is very strict on
>> dependencies (despite being lazy on other things).
>> In this case the reason was that those packages were added to the repository
>> [haskell-core] with initial release number set to 1, although they had been
>> in [haskell-happstack] already for some time and their release number was
>> higher. I removed those immediately from [haskell-happstack] to avoid
>> duplicate work, but they must also be manually removed from local, since
>> pacman always keeps the highest version-release.
>>
>> In order to avoid this kind of issues in the future we should either have a
>> policy to coordinate work between different haskell repositories, or merge
>> everything into a unique repository and call it simply [haskell].
> Indeed.  This is entirely my fault!
>
> I have not been keeping track of what is available in any other repos
> at all.  I was even under the impression that there were no other
> maintained repos at the moment.  Clearly I am completely wrong :(
>
>>> I note the absence of certain packages like haskell-buildwrapper (which
>>> EclipseFP tools needs) - and reading the wiki, it seems confusing at this
>>> time whether the Haskell tinkerer / developer should just be using
>>> cabal-install to install all required packages (even though I know that
>>> cabal is not a package management system) or... what?
>> Personally I don't like installing things using cabal-install because in my
>> opinion the distro package manager should always be in charge.
> The same goes for me.  Occasionally I revert to installing a package
> for the local user only, but not even then do I use `cabal install` to
> do that, I prefer running `./Setup.hs configure,build,install` myself.
>
> I do mean to look into using `cabal` myself at some point, because I
> keep on hearing good things about it.  So far every time I've tried it
> I've run into something weird, most recently it was trying to install
> an older version of a lib than was needed, and I already had the newer
> version installed on my system too.  A lot of terrifyingly clever
> people swear by it though, so there has to be something I'm missing
> out on!
>
> /M
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.haskell.org/pipermail/arch-haskell/attachments/20140512/1398f92f/attachment-0001.html>

From magnus at therning.org  Mon May 12 14:25:48 2014
From: magnus at therning.org (Magnus Therning)
Date: Mon, 12 May 2014 16:25:48 +0200
Subject: [arch-haskell] help upgrading packages
In-Reply-To: <5370D489.9030906@ibi.co.za>
References: <CAAn2fBB68tP4JFFbRJMD39y5hYiBSgugiKmZaSGfLKNi3=5ZPQ@mail.gmail.com>
 <CAOWyexL=PAD53onz1BqtrNJhY3HgX7srKqrBwTVnBLNVMXKTQQ@mail.gmail.com>
 <5370BD9A.4070200@ibi.co.za>
 <CAOWyexJ9HSBmh-kkAks-BdJOsnQiYfCWF_ncFYZWWHysdMriRw@mail.gmail.com>
 <CAAExw5vfvxiAat4cmaiV6Dc8oddSWPRLdvOqwe0eTGf3zE7e7w@mail.gmail.com>
 <5370D489.9030906@ibi.co.za>
Message-ID: <CAAExw5tfDAdzO3VF984zegDEtXOVoW530GFu2VR+R3zcvEkMbg@mail.gmail.com>

On Mon, May 12, 2014 at 4:02 PM, Dawid Loubser <dawid.loubser at ibi.co.za> wrote:
> I'm afraid that I am not one of those 'terrifyingly clever' people you speak
> of, Magnus, but in the past I have had a world of pain trying to use a
> mixture of packages between cabal and pacman.
>
> Had a very happy time using just pacman until haskell-buildwrapper
> disappeared recently, and I could no longer use my favourite Haskell IDE :-(
> I don't want to even try installing it using cabal, becuase then I'll be
> back in package-dependency hell.
>
> I have to say, I appreciate your efforts into making Haskell easy to use on
> Arch so very much - I don't mean to complain at all!

Create a new issue for it on the github page[1], or even better dig
into `cblrepo`, add it yourself, and send me a pull request ;)

/M

[1]: https://github.com/archhaskell/habs/issues

-- 
Magnus Therning                      OpenPGP: 0xAB4DFBA4
email: magnus at therning.org   jabber: magnus at therning.org
twitter: magthe               http://therning.org/magnus

From xyne at archlinux.ca  Mon May 12 20:12:41 2014
From: xyne at archlinux.ca (Xyne)
Date: Mon, 12 May 2014 20:12:41 +0000
Subject: [arch-haskell] help upgrading packages
In-Reply-To: <CAAn2fBDXEH3PkWKeCwBufN3SV0c_TTTjVykHWtPxgD02hC_2xg@mail.gmail.com>
References: <CAAn2fBB68tP4JFFbRJMD39y5hYiBSgugiKmZaSGfLKNi3=5ZPQ@mail.gmail.com>
 <CAOWyexL=PAD53onz1BqtrNJhY3HgX7srKqrBwTVnBLNVMXKTQQ@mail.gmail.com>
 <5370BD9A.4070200@ibi.co.za>
 <CAAn2fBDXEH3PkWKeCwBufN3SV0c_TTTjVykHWtPxgD02hC_2xg@mail.gmail.com>
Message-ID: <20140512201241.68ce24ab@archlinux.ca>

On 2014-05-12 07:01 -0700
Michael Katelman wrote:

>Thanks, all! I ultimately did the same thing: removing and re-installing
>the entire Haskell ecosystem. It seems happy now :)
>
>-Mike

FYI, you can downgrade packages to match the current versions in the repo using

pacman -Syuu


For re-installing all of your haskell packages you may find two of my apps
useful: pkg-topological_reinstall and pkg-list_dependents. Both are included in
my pkg_scripts package [1].

The first was written specifically for dealing with GHC and will generate
scripts to remove GHC and all dependencies then re-install the explicitly
installed packages (with dep resolution). You can do more with it (e.g. add
intermediate steps) by tweaking the generated scripts (which are very simple).

The second app will simply list all dependents of a target package so that you
can create your own scripts.

[1] http://xyne.archlinux.ca/projects/pkg_scripts/

Regards,
Xyne

From spam at scientician.net  Wed May 14 20:47:39 2014
From: spam at scientician.net (Bardur Arantsson)
Date: Wed, 14 May 2014 22:47:39 +0200
Subject: [arch-haskell] help upgrading packages
In-Reply-To: <CAAExw5vfvxiAat4cmaiV6Dc8oddSWPRLdvOqwe0eTGf3zE7e7w@mail.gmail.com>
References: <CAAn2fBB68tP4JFFbRJMD39y5hYiBSgugiKmZaSGfLKNi3=5ZPQ@mail.gmail.com>
 <CAOWyexL=PAD53onz1BqtrNJhY3HgX7srKqrBwTVnBLNVMXKTQQ@mail.gmail.com>
 <5370BD9A.4070200@ibi.co.za>
 <CAOWyexJ9HSBmh-kkAks-BdJOsnQiYfCWF_ncFYZWWHysdMriRw@mail.gmail.com>
 <CAAExw5vfvxiAat4cmaiV6Dc8oddSWPRLdvOqwe0eTGf3zE7e7w@mail.gmail.com>
Message-ID: <ll0kpb$s62$1@ger.gmane.org>

On 2014-05-12 15:47, Magnus Therning wrote:
[--snip--]
> The same goes for me.  Occasionally I revert to installing a package
> for the local user only, but not even then do I use `cabal install` to
> do that, I prefer running `./Setup.hs configure,build,install` myself.
> 
> I do mean to look into using `cabal` myself at some point, because I
> keep on hearing good things about it.  So far every time I've tried it
> I've run into something weird, most recently it was trying to install
> an older version of a lib than was needed, and I already had the newer
> version installed on my system too.  A lot of terrifyingly clever
> people swear by it though, so there has to be something I'm missing
> out on!

Gah! Just try it!

All I needed to install build-wrapper (which I think was the inital
"problem" package in this thread) was to do

$ mkdir somewhere/buildwrapper
$ cd somewhere/buildwrapper
$ cabal sandbox init
$ cabal install buildwrapper

Add "somewhere/buildwrapper" to $PATH. Bonus points for using "stow" or
similar.

The key point in the above recipe is to *NOT* have all kinds of
libraries installed system-wide (aka. via pacman). It usually works
better that way.

Disclaimer: I haven't actually used buildwrapper personally, but one
assumes that it just acts as an executable and doesn't install things
into its own environment or other weird things.

Regards,


From magnus at therning.org  Thu May 15 09:35:28 2014
From: magnus at therning.org (Magnus Therning)
Date: Thu, 15 May 2014 11:35:28 +0200
Subject: [arch-haskell] help upgrading packages
In-Reply-To: <ll0kpb$s62$1@ger.gmane.org>
References: <CAAn2fBB68tP4JFFbRJMD39y5hYiBSgugiKmZaSGfLKNi3=5ZPQ@mail.gmail.com>
 <CAOWyexL=PAD53onz1BqtrNJhY3HgX7srKqrBwTVnBLNVMXKTQQ@mail.gmail.com>
 <5370BD9A.4070200@ibi.co.za>
 <CAOWyexJ9HSBmh-kkAks-BdJOsnQiYfCWF_ncFYZWWHysdMriRw@mail.gmail.com>
 <CAAExw5vfvxiAat4cmaiV6Dc8oddSWPRLdvOqwe0eTGf3zE7e7w@mail.gmail.com>
 <ll0kpb$s62$1@ger.gmane.org>
Message-ID: <CAAExw5u688Ue+t3GVHCu4bvR7d541yVY040e2SEuFFd4K=v3bw@mail.gmail.com>

On Wed, May 14, 2014 at 10:47 PM, Bardur Arantsson <spam at scientician.net> wrote:
> On 2014-05-12 15:47, Magnus Therning wrote:
> [--snip--]
>> The same goes for me.  Occasionally I revert to installing a package
>> for the local user only, but not even then do I use `cabal install` to
>> do that, I prefer running `./Setup.hs configure,build,install` myself.
>>
>> I do mean to look into using `cabal` myself at some point, because I
>> keep on hearing good things about it.  So far every time I've tried it
>> I've run into something weird, most recently it was trying to install
>> an older version of a lib than was needed, and I already had the newer
>> version installed on my system too.  A lot of terrifyingly clever
>> people swear by it though, so there has to be something I'm missing
>> out on!
>
> Gah! Just try it!
>
> All I needed to install build-wrapper (which I think was the inital
> "problem" package in this thread) was to do
>
> $ mkdir somewhere/buildwrapper
> $ cd somewhere/buildwrapper
> $ cabal sandbox init
> $ cabal install buildwrapper
>
> Add "somewhere/buildwrapper" to $PATH. Bonus points for using "stow" or
> similar.
> The key point in the above recipe is to *NOT* have all kinds of
> libraries installed system-wide (aka. via pacman). It usually works
> better that way.

Surely you should then `cabal install` the tool so you don't end up
with a complete sandbox with every dependency of buildwrapper's in it,
no?

For some packages you would have to keep the sandbox around and do it
your way though, e.g. `pandoc` since it contains both a library and
executables.

> Disclaimer: I haven't actually used buildwrapper personally, but one
> assumes that it just acts as an executable and doesn't install things
> into its own environment or other weird things.

Personally I think `cabal` really shines when doing more serious
Haskell development than I do.  I never test my Haskell packages on
anything other than the GHC that's in [haskell-core], and neither do I
test them against any other versions of packages than what's found in
[haskell-core].  My Haskell development is completely in my free time
and for fun.  I think that if I ever am lucky enough find myself using
Haskell professionally I'd quickly see more use in what `cabal` has to
offer.

/M

-- 
Magnus Therning                      OpenPGP: 0xAB4DFBA4
email: magnus at therning.org   jabber: magnus at therning.org
twitter: magthe               http://therning.org/magnus

From prolepsis at gmail.com  Thu May 15 10:54:23 2014
From: prolepsis at gmail.com (Al Matthews)
Date: Thu, 15 May 2014 06:54:23 -0400
Subject: [arch-haskell] rtfm
Message-ID: <CALEf-Y=ZRaJ2SdxO9UAbvUq9qcEKBq0VF7qcrvG4Gb3aO+7kXQ@mail.gmail.com>

Hi list. I'll ask as naively as possible in hopes of helping (me but also)
someone else.

Being new, I've managed to hose my Arch haskell installation fairly well.

I've been tracking haskell-core

[haskell-core]
###Server = http://www.kiwilight.com/haskell/core/$arch
Server = http://xsounds.org/~haskell/core/$arch

and from there

# Pacman won't upgrade packages listed in IgnorePkg and members of
IgnoreGroup

#IgnorePkg = haskell-aeson 0.6.2.1-3
#IgnorePkg = haskell-attoparsec 0.10.4.0-4
#IgnorePkg = haskell-blaze-builder 0.3.3.0-1
#IgnorePkg = haskell-blaze-html 0.6.1.2-1
#IgnorePkg = haskell-blaze-markup 0.5.1.6-1
#IgnorePkg = haskell-data-default 0.5.3-2
#IgnorePkg = haskell-data-default-instances-dlist 0.0.1-2
#IgnorePkg = haskell-dlist 0.5-27
#IgnorePkg = haskell-graphviz
[etc]

, this because I was trying to maintain an installation of Pandoc which
relied on "older"
 packages by the time I had managed to install something newer, maybe
bloomfilter.

Anyway, by now ghc is up to 7.8.2 and I remain with a lot of built-depends
over 7.6.3. pacman is upset.

I hesitate to hack in anything from [haskell-testing] until I'm more
conceptually clear.

I even built big swaths of habs, on my local, to see what would happen, so,
guidance as regards the intended purpose, or advanced use, of some of these
tools is appreciated. Pointers to relevant documentation or system files
are naturally most welcome.

Thank you.

Al Matthews
Atlanta, GA US
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.haskell.org/pipermail/arch-haskell/attachments/20140515/cfdfe212/attachment.html>

From magnus at therning.org  Thu May 15 11:31:24 2014
From: magnus at therning.org (Magnus Therning)
Date: Thu, 15 May 2014 13:31:24 +0200
Subject: [arch-haskell] rtfm
In-Reply-To: <CALEf-Y=ZRaJ2SdxO9UAbvUq9qcEKBq0VF7qcrvG4Gb3aO+7kXQ@mail.gmail.com>
References: <CALEf-Y=ZRaJ2SdxO9UAbvUq9qcEKBq0VF7qcrvG4Gb3aO+7kXQ@mail.gmail.com>
Message-ID: <CAAExw5s6=+xm3OnUV7J3tRQepAcra3Z8kMsbwFe474YVwnPs4Q@mail.gmail.com>

On Thu, May 15, 2014 at 12:54 PM, Al Matthews <prolepsis at gmail.com> wrote:
> Hi list. I'll ask as naively as possible in hopes of helping (me but also)
> someone else.
>
> Being new, I've managed to hose my Arch haskell installation fairly well.

I highly doubt it isn't something we can help you fix! :)

> I've been tracking haskell-core
>
> [haskell-core]
> ###Server = http://www.kiwilight.com/haskell/core/$arch
> Server = http://xsounds.org/~haskell/core/$arch
>
> and from there
>
> # Pacman won't upgrade packages listed in IgnorePkg and members of
> IgnoreGroup
>
> #IgnorePkg = haskell-aeson 0.6.2.1-3
> #IgnorePkg = haskell-attoparsec 0.10.4.0-4
> #IgnorePkg = haskell-blaze-builder 0.3.3.0-1
> #IgnorePkg = haskell-blaze-html 0.6.1.2-1
> #IgnorePkg = haskell-blaze-markup 0.5.1.6-1
> #IgnorePkg = haskell-data-default 0.5.3-2
> #IgnorePkg = haskell-data-default-instances-dlist 0.0.1-2
> #IgnorePkg = haskell-dlist 0.5-27
> #IgnorePkg = haskell-graphviz
> [etc]
>
> , this because I was trying to maintain an installation of Pandoc which
> relied on "older"
>  packages by the time I had managed to install something newer, maybe
> bloomfilter.
>
> Anyway, by now ghc is up to 7.8.2 and I remain with a lot of built-depends
> over 7.6.3. pacman is upset.
>
> I hesitate to hack in anything from [haskell-testing] until I'm more
> conceptually clear.

[haskell-testing] is currently completely empty.  When GHC 7.8 was
release I emptied testing into core.

> I even built big swaths of habs, on my local, to see what would happen, so,
> guidance as regards the intended purpose, or advanced use, of some of these
> tools is appreciated. Pointers to relevant documentation or system files are
> naturally most welcome.

The main thing is probably to fully understand what your goal is.
It's not clear to me, from reading your email what you actually want,
how you tried to get there, and what problems you ran into.

If it's as simple as you just wanting to upgrade your system?
1. Make sure you have no Haskell packages on your ignore list.
2 Try a straight upgrade.  If that fails with `pacman` telling you
that some package depends on ghc-7.6 then that most likely means the
package in question has been dropped from [haskell-core].  Raise an
issue for each such package you can't live without
(https://github.com/archhaskell/habs/issues).
3. Remove all such packages you can live without.
4. Wait until someone's gotten around to re-add the packages that are
crucial to you, then restart from 1.

Of course you can help with step 2 yourself by cloning habs and using
`cblrepo` to add them and verify they build properly.

/M

-- 
Magnus Therning                      OpenPGP: 0xAB4DFBA4
email: magnus at therning.org   jabber: magnus at therning.org
twitter: magthe               http://therning.org/magnus

From prolepsis at gmail.com  Thu May 15 13:07:37 2014
From: prolepsis at gmail.com (Al Matthews)
Date: Thu, 15 May 2014 09:07:37 -0400
Subject: [arch-haskell] rtfm
In-Reply-To: <CAAExw5s6=+xm3OnUV7J3tRQepAcra3Z8kMsbwFe474YVwnPs4Q@mail.gmail.com>
References: <CALEf-Y=ZRaJ2SdxO9UAbvUq9qcEKBq0VF7qcrvG4Gb3aO+7kXQ@mail.gmail.com>
 <CAAExw5s6=+xm3OnUV7J3tRQepAcra3Z8kMsbwFe474YVwnPs4Q@mail.gmail.com>
Message-ID: <CALEf-Y==sv8LYUsr9V-Cpf6-TgPVNOQuq6m0hb7z7kXPE4Hzgg@mail.gmail.com>

> It's not clear to me, from reading your email what you actually want,
how you tried to get there, and what problems you ran into.

Yes, I left out some detail. I did indeed get `pacman` failures based on
ghc-7.6. There were a number. I'll review them as you suggest.

> Of course you can help with step 2 yourself by cloning habs and using
`cblrepo` to add them and verify they build properly.

That makes sense. I can't `man pacman` nor `man cblrepo` at the moment, but
I imagine I can also install these packages directly from the local chroot
that is created in the build process? This (default; no option -l <dir>)
layout confuses me more than I would prefer. That would be my goal: to be
able to build the packages locally if required. Presumably I can also be
helpful by indicating that this process succeeds.


On Thu, May 15, 2014 at 7:31 AM, Magnus Therning <magnus at therning.org>wrote:

> On Thu, May 15, 2014 at 12:54 PM, Al Matthews <prolepsis at gmail.com> wrote:
> > Hi list. I'll ask as naively as possible in hopes of helping (me but
> also)
> > someone else.
> >
> > Being new, I've managed to hose my Arch haskell installation fairly well.
>
> I highly doubt it isn't something we can help you fix! :)
>
> > I've been tracking haskell-core
> >
> > [haskell-core]
> > ###Server = http://www.kiwilight.com/haskell/core/$arch
> > Server = http://xsounds.org/~haskell/core/$arch
> >
> > and from there
> >
> > # Pacman won't upgrade packages listed in IgnorePkg and members of
> > IgnoreGroup
> >
> > #IgnorePkg = haskell-aeson 0.6.2.1-3
> > #IgnorePkg = haskell-attoparsec 0.10.4.0-4
> > #IgnorePkg = haskell-blaze-builder 0.3.3.0-1
> > #IgnorePkg = haskell-blaze-html 0.6.1.2-1
> > #IgnorePkg = haskell-blaze-markup 0.5.1.6-1
> > #IgnorePkg = haskell-data-default 0.5.3-2
> > #IgnorePkg = haskell-data-default-instances-dlist 0.0.1-2
> > #IgnorePkg = haskell-dlist 0.5-27
> > #IgnorePkg = haskell-graphviz
> > [etc]
> >
> > , this because I was trying to maintain an installation of Pandoc which
> > relied on "older"
> >  packages by the time I had managed to install something newer, maybe
> > bloomfilter.
> >
> > Anyway, by now ghc is up to 7.8.2 and I remain with a lot of
> built-depends
> > over 7.6.3. pacman is upset.
> >
> > I hesitate to hack in anything from [haskell-testing] until I'm more
> > conceptually clear.
>
> [haskell-testing] is currently completely empty.  When GHC 7.8 was
> release I emptied testing into core.
>
> > I even built big swaths of habs, on my local, to see what would happen,
> so,
> > guidance as regards the intended purpose, or advanced use, of some of
> these
> > tools is appreciated. Pointers to relevant documentation or system files
> are
> > naturally most welcome.
>
> The main thing is probably to fully understand what your goal is.
> It's not clear to me, from reading your email what you actually want,
> how you tried to get there, and what problems you ran into.
>
> If it's as simple as you just wanting to upgrade your system?
> 1. Make sure you have no Haskell packages on your ignore list.
> 2 Try a straight upgrade.  If that fails with `pacman` telling you
> that some package depends on ghc-7.6 then that most likely means the
> package in question has been dropped from [haskell-core].  Raise an
> issue for each such package you can't live without
> (https://github.com/archhaskell/habs/issues).
> 3. Remove all such packages you can live without.
> 4. Wait until someone's gotten around to re-add the packages that are
> crucial to you, then restart from 1.
>
> Of course you can help with step 2 yourself by cloning habs and using
> `cblrepo` to add them and verify they build properly.
>
> /M
>
> --
> Magnus Therning                      OpenPGP: 0xAB4DFBA4
> email: magnus at therning.org   jabber: magnus at therning.org
> twitter: magthe               http://therning.org/magnus
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.haskell.org/pipermail/arch-haskell/attachments/20140515/26d0b1d5/attachment.html>

From prolepsis at gmail.com  Thu May 15 13:09:32 2014
From: prolepsis at gmail.com (Al Matthews)
Date: Thu, 15 May 2014 09:09:32 -0400
Subject: [arch-haskell] rtfm
In-Reply-To: <CALEf-Y==sv8LYUsr9V-Cpf6-TgPVNOQuq6m0hb7z7kXPE4Hzgg@mail.gmail.com>
References: <CALEf-Y=ZRaJ2SdxO9UAbvUq9qcEKBq0VF7qcrvG4Gb3aO+7kXQ@mail.gmail.com>
 <CAAExw5s6=+xm3OnUV7J3tRQepAcra3Z8kMsbwFe474YVwnPs4Q@mail.gmail.com>
 <CALEf-Y==sv8LYUsr9V-Cpf6-TgPVNOQuq6m0hb7z7kXPE4Hzgg@mail.gmail.com>
Message-ID: <CALEf-Yn2hmUN1OOue2GjUqYGLJC3TcSY6bHPwq7vqPOiNXOn7A@mail.gmail.com>

By this, I mean, build them locally through the Arch scripts, which seem
reasonable; rather than mixing in a .cabal tree if I can help it.


On Thu, May 15, 2014 at 9:07 AM, Al Matthews <prolepsis at gmail.com> wrote:

> > It's not clear to me, from reading your email what you actually want,
> how you tried to get there, and what problems you ran into.
>
> Yes, I left out some detail. I did indeed get `pacman` failures based on
> ghc-7.6. There were a number. I'll review them as you suggest.
>
> > Of course you can help with step 2 yourself by cloning habs and using
> `cblrepo` to add them and verify they build properly.
>
> That makes sense. I can't `man pacman` nor `man cblrepo` at the moment,
> but I imagine I can also install these packages directly from the local
> chroot that is created in the build process? This (default; no option -l
> <dir>) layout confuses me more than I would prefer. That would be my goal:
> to be able to build the packages locally if required. Presumably I can also
> be helpful by indicating that this process succeeds.
>
>
> On Thu, May 15, 2014 at 7:31 AM, Magnus Therning <magnus at therning.org>wrote:
>
>> On Thu, May 15, 2014 at 12:54 PM, Al Matthews <prolepsis at gmail.com>
>> wrote:
>> > Hi list. I'll ask as naively as possible in hopes of helping (me but
>> also)
>> > someone else.
>> >
>> > Being new, I've managed to hose my Arch haskell installation fairly
>> well.
>>
>> I highly doubt it isn't something we can help you fix! :)
>>
>> > I've been tracking haskell-core
>> >
>> > [haskell-core]
>> > ###Server = http://www.kiwilight.com/haskell/core/$arch
>> > Server = http://xsounds.org/~haskell/core/$arch
>> >
>> > and from there
>> >
>> > # Pacman won't upgrade packages listed in IgnorePkg and members of
>> > IgnoreGroup
>> >
>> > #IgnorePkg = haskell-aeson 0.6.2.1-3
>> > #IgnorePkg = haskell-attoparsec 0.10.4.0-4
>> > #IgnorePkg = haskell-blaze-builder 0.3.3.0-1
>> > #IgnorePkg = haskell-blaze-html 0.6.1.2-1
>> > #IgnorePkg = haskell-blaze-markup 0.5.1.6-1
>> > #IgnorePkg = haskell-data-default 0.5.3-2
>> > #IgnorePkg = haskell-data-default-instances-dlist 0.0.1-2
>> > #IgnorePkg = haskell-dlist 0.5-27
>> > #IgnorePkg = haskell-graphviz
>> > [etc]
>> >
>> > , this because I was trying to maintain an installation of Pandoc which
>> > relied on "older"
>> >  packages by the time I had managed to install something newer, maybe
>> > bloomfilter.
>> >
>> > Anyway, by now ghc is up to 7.8.2 and I remain with a lot of
>> built-depends
>> > over 7.6.3. pacman is upset.
>> >
>> > I hesitate to hack in anything from [haskell-testing] until I'm more
>> > conceptually clear.
>>
>> [haskell-testing] is currently completely empty.  When GHC 7.8 was
>> release I emptied testing into core.
>>
>> > I even built big swaths of habs, on my local, to see what would happen,
>> so,
>> > guidance as regards the intended purpose, or advanced use, of some of
>> these
>> > tools is appreciated. Pointers to relevant documentation or system
>> files are
>> > naturally most welcome.
>>
>> The main thing is probably to fully understand what your goal is.
>> It's not clear to me, from reading your email what you actually want,
>> how you tried to get there, and what problems you ran into.
>>
>> If it's as simple as you just wanting to upgrade your system?
>> 1. Make sure you have no Haskell packages on your ignore list.
>> 2 Try a straight upgrade.  If that fails with `pacman` telling you
>> that some package depends on ghc-7.6 then that most likely means the
>> package in question has been dropped from [haskell-core].  Raise an
>> issue for each such package you can't live without
>> (https://github.com/archhaskell/habs/issues).
>> 3. Remove all such packages you can live without.
>> 4. Wait until someone's gotten around to re-add the packages that are
>> crucial to you, then restart from 1.
>>
>> Of course you can help with step 2 yourself by cloning habs and using
>> `cblrepo` to add them and verify they build properly.
>>
>> /M
>>
>> --
>> Magnus Therning                      OpenPGP: 0xAB4DFBA4
>> email: magnus at therning.org   jabber: magnus at therning.org
>> twitter: magthe               http://therning.org/magnus
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.haskell.org/pipermail/arch-haskell/attachments/20140515/431c36f5/attachment.html>

From magnus at therning.org  Thu May 15 14:04:03 2014
From: magnus at therning.org (Magnus Therning)
Date: Thu, 15 May 2014 16:04:03 +0200
Subject: [arch-haskell] rtfm
In-Reply-To: <CALEf-Y==sv8LYUsr9V-Cpf6-TgPVNOQuq6m0hb7z7kXPE4Hzgg@mail.gmail.com>
References: <CALEf-Y=ZRaJ2SdxO9UAbvUq9qcEKBq0VF7qcrvG4Gb3aO+7kXQ@mail.gmail.com>
 <CAAExw5s6=+xm3OnUV7J3tRQepAcra3Z8kMsbwFe474YVwnPs4Q@mail.gmail.com>
 <CALEf-Y==sv8LYUsr9V-Cpf6-TgPVNOQuq6m0hb7z7kXPE4Hzgg@mail.gmail.com>
Message-ID: <CAAExw5tS9VpXpY9q_Hgk2tyz4ymWdA6XgdmCC0R2MCPX3we1Eg@mail.gmail.com>

On Thu, May 15, 2014 at 3:07 PM, Al Matthews <prolepsis at gmail.com> wrote:
>> Of course you can help with step 2 yourself by cloning habs and using
> `cblrepo` to add them and verify they build properly.
>
> That makes sense. I can't `man pacman` nor `man cblrepo` at the moment, but
> I imagine I can also install these packages directly from the local chroot
> that is created in the build process? This (default; no option -l <dir>)
> layout confuses me more than I would prefer. That would be my goal: to be
> able to build the packages locally if required. Presumably I can also be
> helpful by indicating that this process succeeds.

There is no manpage for `cblrepo` yet.  Hopefully you can find out
what you need between the built-in help and the text on
https://github.com/archhaskell/habs/ and
https://github.com/archhaskell/habs/.

You should almost always build using the script in habs, and then all
packages will be built using [haskell-core] to get any dependencies.

The text you refer to is "-l <dir>    Location of chroot (default .)".
 This argument allows you to point out where your chroot is.  I always
run the script in my habs workspace, and keep my chroot in `~/tmp`,
i.e. I use `./makeahpkg -l ~/tmp`.

/M

-- 
Magnus Therning                      OpenPGP: 0xAB4DFBA4
email: magnus at therning.org   jabber: magnus at therning.org
twitter: magthe               http://therning.org/magnus

From spam at scientician.net  Thu May 15 15:29:13 2014
From: spam at scientician.net (Bardur Arantsson)
Date: Thu, 15 May 2014 17:29:13 +0200
Subject: [arch-haskell] help upgrading packages
In-Reply-To: <CAAExw5u688Ue+t3GVHCu4bvR7d541yVY040e2SEuFFd4K=v3bw@mail.gmail.com>
References: <CAAn2fBB68tP4JFFbRJMD39y5hYiBSgugiKmZaSGfLKNi3=5ZPQ@mail.gmail.com>
 <CAOWyexL=PAD53onz1BqtrNJhY3HgX7srKqrBwTVnBLNVMXKTQQ@mail.gmail.com>
 <5370BD9A.4070200@ibi.co.za>
 <CAOWyexJ9HSBmh-kkAks-BdJOsnQiYfCWF_ncFYZWWHysdMriRw@mail.gmail.com>
 <CAAExw5vfvxiAat4cmaiV6Dc8oddSWPRLdvOqwe0eTGf3zE7e7w@mail.gmail.com>
 <ll0kpb$s62$1@ger.gmane.org>
 <CAAExw5u688Ue+t3GVHCu4bvR7d541yVY040e2SEuFFd4K=v3bw@mail.gmail.com>
Message-ID: <ll2mg9$rc8$1@ger.gmane.org>

On 2014-05-15 11:35, Magnus Therning wrote:
> On Wed, May 14, 2014 at 10:47 PM, Bardur Arantsson <spam at scientician.net> wrote:
>> On 2014-05-12 15:47, Magnus Therning wrote:
>> [--snip--]
>>
>> All I needed to install build-wrapper (which I think was the inital
>> "problem" package in this thread) was to do
>>
>> $ mkdir somewhere/buildwrapper
>> $ cd somewhere/buildwrapper
>> $ cabal sandbox init
>> $ cabal install buildwrapper
>>
>> Add "somewhere/buildwrapper" to $PATH. Bonus points for using "stow" or
>> similar.
>> The key point in the above recipe is to *NOT* have all kinds of
>> libraries installed system-wide (aka. via pacman). It usually works
>> better that way.
> 
> Surely you should then `cabal install` the tool so you don't end up
> with a complete sandbox with every dependency of buildwrapper's in it,
> no?
> 

You *do* need to keep the sandbox around (or at least parts of it).
That's where the last "cabal install" line installs to.

> For some packages you would have to keep the sandbox around and do it
> your way though, e.g. `pandoc` since it contains both a library and
> executables.
> 

If you want to use a sandboxed thing as a library then you need to
develop "inside" the sandbox, so e.g. you'd just create a little cabal
file for your project which declares all the dependencies and use cabal
to build your project.

>> Disclaimer: I haven't actually used buildwrapper personally, but one
>> assumes that it just acts as an executable and doesn't install things
>> into its own environment or other weird things.
> 
> Personally I think `cabal` really shines when doing more serious
> Haskell development than I do.  I never test my Haskell packages on
> anything other than the GHC that's in [haskell-core], and neither do I
> test them against any other versions of packages than what's found in
> [haskell-core].  My Haskell development is completely in my free time
> and for fun.  I think that if I ever am lucky enough find myself using
> Haskell professionally I'd quickly see more use in what `cabal` has to
> offer.
> 

Cabal also works beautifully for "hobby" type development. Once you've
created a cabal file you hardly ever need to touch it again. :)

Regards,


From magnus at therning.org  Thu May 15 21:18:18 2014
From: magnus at therning.org (Magnus Therning)
Date: Thu, 15 May 2014 23:18:18 +0200
Subject: [arch-haskell] help upgrading packages
In-Reply-To: <ll2mg9$rc8$1@ger.gmane.org>
References: <CAAn2fBB68tP4JFFbRJMD39y5hYiBSgugiKmZaSGfLKNi3=5ZPQ@mail.gmail.com>
 <CAOWyexL=PAD53onz1BqtrNJhY3HgX7srKqrBwTVnBLNVMXKTQQ@mail.gmail.com>
 <5370BD9A.4070200@ibi.co.za>
 <CAOWyexJ9HSBmh-kkAks-BdJOsnQiYfCWF_ncFYZWWHysdMriRw@mail.gmail.com>
 <CAAExw5vfvxiAat4cmaiV6Dc8oddSWPRLdvOqwe0eTGf3zE7e7w@mail.gmail.com>
 <ll0kpb$s62$1@ger.gmane.org>
 <CAAExw5u688Ue+t3GVHCu4bvR7d541yVY040e2SEuFFd4K=v3bw@mail.gmail.com>
 <ll2mg9$rc8$1@ger.gmane.org>
Message-ID: <20140515211818.GA6176@tatooine.lan>

On Thu, May 15, 2014 at 05:29:13PM +0200, Bardur Arantsson wrote:
> On 2014-05-15 11:35, Magnus Therning wrote:
>> On Wed, May 14, 2014 at 10:47 PM, Bardur Arantsson <spam at scientician.net> wrote:
>>> On 2014-05-12 15:47, Magnus Therning wrote:
>>> [--snip--]
>>>
>>> All I needed to install build-wrapper (which I think was the
>>> inital "problem" package in this thread) was to do
>>>
>>> $ mkdir somewhere/buildwrapper
>>> $ cd somewhere/buildwrapper
>>> $ cabal sandbox init
>>> $ cabal install buildwrapper
>>>
>>> Add "somewhere/buildwrapper" to $PATH. Bonus points for using
>>> "stow" or similar.
>>> The key point in the above recipe is to *NOT* have all kinds of
>>> libraries installed system-wide (aka. via pacman). It usually
>>> works better that way.
>> 
>> Surely you should then `cabal install` the tool so you don't end up
>> with a complete sandbox with every dependency of buildwrapper's in
>> it, no?
> 
> You *do* need to keep the sandbox around (or at least parts of it).
> That's where the last "cabal install" line installs to.

Well, wouldn't you want the binary installed somewhere else, so you
don't need to keep the sandbox around?  Or do you build all your
haskell tools (hlint, hoogle, buildwrapper, hasktags, ghc-mod, etc) in
the same sandbox?

>> For some packages you would have to keep the sandbox around and do
>> it your way though, e.g. `pandoc` since it contains both a library
>> and executables.
> 
> If you want to use a sandboxed thing as a library then you need to
> develop "inside" the sandbox, so e.g. you'd just create a little
> cabal file for your project which declares all the dependencies and
> use cabal to build your project.

That's indeed the case, but that's *not* the point I was trying to
make.  If a package only consists of executables you can use the
`install` target of the Cabal file to install them.  If a package
consists of both a library and executables it's more manual work.

>>> Disclaimer: I haven't actually used buildwrapper personally, but
>>> one assumes that it just acts as an executable and doesn't install
>>> things into its own environment or other weird things.
>> 
>> Personally I think `cabal` really shines when doing more serious
>> Haskell development than I do.  I never test my Haskell packages on
>> anything other than the GHC that's in [haskell-core], and neither
>> do I test them against any other versions of packages than what's
>> found in [haskell-core].  My Haskell development is completely in
>> my free time and for fun.  I think that if I ever am lucky enough
>> find myself using Haskell professionally I'd quickly see more use
>> in what `cabal` has to offer.
> 
> Cabal also works beautifully for "hobby" type development. Once
> you've created a cabal file you hardly ever need to touch it again.
> :)

But it's overkill.  Do keep in mind that Cabal and `cabal` are two
different things.  Of course I use Cabal in all my packages, but I
don't use `cabal` at all.  The main reason I see for using `cabal`
would be when I need to maintain compatibility with multiple versions
of GHC and or packages I depend on.

/M

-- 
Magnus Therning                      OpenPGP: 0xAB4DFBA4 
email: magnus at therning.org   jabber: magnus at therning.org
twitter: magthe               http://therning.org/magnus

What gets measured, gets done.
     -- Tom Peters
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
URL: <http://www.haskell.org/pipermail/arch-haskell/attachments/20140515/4424989b/attachment.sig>

From spam at scientician.net  Fri May 16 07:12:31 2014
From: spam at scientician.net (Bardur Arantsson)
Date: Fri, 16 May 2014 09:12:31 +0200
Subject: [arch-haskell] help upgrading packages
In-Reply-To: <20140515211818.GA6176@tatooine.lan>
References: <CAAn2fBB68tP4JFFbRJMD39y5hYiBSgugiKmZaSGfLKNi3=5ZPQ@mail.gmail.com>
 <CAOWyexL=PAD53onz1BqtrNJhY3HgX7srKqrBwTVnBLNVMXKTQQ@mail.gmail.com>
 <5370BD9A.4070200@ibi.co.za>
 <CAOWyexJ9HSBmh-kkAks-BdJOsnQiYfCWF_ncFYZWWHysdMriRw@mail.gmail.com>
 <CAAExw5vfvxiAat4cmaiV6Dc8oddSWPRLdvOqwe0eTGf3zE7e7w@mail.gmail.com>
 <ll0kpb$s62$1@ger.gmane.org>
 <CAAExw5u688Ue+t3GVHCu4bvR7d541yVY040e2SEuFFd4K=v3bw@mail.gmail.com>
 <ll2mg9$rc8$1@ger.gmane.org> <20140515211818.GA6176@tatooine.lan>
Message-ID: <ll4dov$ri6$1@ger.gmane.org>

On 2014-05-15 23:18, Magnus Therning wrote:
> On Thu, May 15, 2014 at 05:29:13PM +0200, Bardur Arantsson wrote:
>> On 2014-05-15 11:35, Magnus Therning wrote:
>>> On Wed, May 14, 2014 at 10:47 PM, Bardur Arantsson <spam at scientician.net> wrote:
>>>> On 2014-05-12 15:47, Magnus Therning wrote:
>>>> [--snip--]
>>>>
>>>> All I needed to install build-wrapper (which I think was the
>>>> inital "problem" package in this thread) was to do
>>>>
>>>> $ mkdir somewhere/buildwrapper
>>>> $ cd somewhere/buildwrapper
>>>> $ cabal sandbox init
>>>> $ cabal install buildwrapper
>>>>
>>>> Add "somewhere/buildwrapper" to $PATH. Bonus points for using
>>>> "stow" or similar.
>>>> The key point in the above recipe is to *NOT* have all kinds of
>>>> libraries installed system-wide (aka. via pacman). It usually
>>>> works better that way.
>>>
>>> Surely you should then `cabal install` the tool so you don't end up
>>> with a complete sandbox with every dependency of buildwrapper's in
>>> it, no?
>>
>> You *do* need to keep the sandbox around (or at least parts of it).
>> That's where the last "cabal install" line installs to.
> 
> Well, wouldn't you want the binary installed somewhere else, so you
> don't need to keep the sandbox around?  Or do you build all your
> haskell tools (hlint, hoogle, buildwrapper, hasktags, ghc-mod, etc) in
> the same sandbox?
> 

What I do for executable-only is pretty simple. I use stow to manage all
non-distro software that I install, so I have one directory
per package, like so:

      ~/stow/ghc-mod/lib/ghc-mod/src
      ~/stow/hums/lib/hums/src
      (etc.)

Each of these directories contains a full sandbox with a locally-run
"cabal install".

For each package I add a "bin" directory, so

     ~/stow/ghc-mod/bin

and put in the necessary relative symlinks:

     ~/stow/ghc-mod-4.0.2/bin
        cpphs -> ../lib/ghc-mod/.cabal-sandbox/bin/cpphs
        ghc-mod -> ../lib/ghc-mod/.cabal-sandbox/bin/ghc-mod
        ghc-modi -> ../lib/ghc-mod/.cabal-sandbox/bin/ghc-modi
        hlint -> ../lib/ghc-mod/.cabal-sandbox/bin/hlint
        HsColour -> ../lib/ghc-mod/.cabal-sandbox/bin/HsColour

And finally use stow to "merge" the package into my ~ directory, so that
all the bin/ symlinks end up in my ~/bin.

(I use stow because I'm pretty pendantic about keeping "packages"
separate from everything else in my $HOME, but you could also just have
a ~/src with a sandbox for every package and add symlinks directly from
your ~/bin into the sandboxes. It's just that since all my non-haskell
non-distro self-built software is managed by stow, I chose to also use
stow for this.)

>>> For some packages you would have to keep the sandbox around and do
>>> it your way though, e.g. `pandoc` since it contains both a library
>>> and executables.
>>
>> If you want to use a sandboxed thing as a library then you need to
>> develop "inside" the sandbox, so e.g. you'd just create a little
>> cabal file for your project which declares all the dependencies and
>> use cabal to build your project.
> 
> That's indeed the case, but that's *not* the point I was trying to
> make.  If a package only consists of executables you can use the
> `install` target of the Cabal file to install them.  If a package
> consists of both a library and executables it's more manual work.

I think we might be talking past each other...

I'm afraid I don't understand what you mean by "more manual work". Using
sandboxes the way I've described above doesn't really work at all for
executable + library situations. (So I offered a different solution to
that problem, namely cabal-ifying your own package that depends on a
library and installing your own package in a sandbox.)

>> Cabal also works beautifully for "hobby" type development. Once
>> you've created a cabal file you hardly ever need to touch it again.
>> :)
> 
> But it's overkill.  Do keep in mind that Cabal and `cabal` are two
> different things.  Of course I use Cabal in all my packages, but I
> don't use `cabal` at all.  The main reason I see for using `cabal`
> would be when I need to maintain compatibility with multiple versions
> of GHC and or packages I depend on.
> 

If we want to get pendantic, it's probably best to say Cabal vs.
cabal-install (which is where the "cabal" executable comes from, for
those who don't know).

I use cabal-install for all development with a .cabal file for each of
my projects, I never use Cabal (the library) directly as I've never
encountered a need to. I've not encountered many packages which use
anything other than the standard boilerplate Setup.hs/Setup.lhs file.
(Some packages with *really* complex build requirements do so, e.g.
Gtk2hs, but I assumed that's not quite the level of complexity we're
talking here.)

Anyway, enough rambling on...

Regards,


From martindemello at gmail.com  Sun May 25 21:35:47 2014
From: martindemello at gmail.com (Martin DeMello)
Date: Sun, 25 May 2014 14:35:47 -0700
Subject: [arch-haskell] aura won't upgrade (looks like a cabal version issue)
Message-ID: <CAFrFfuGJqjD9mLHt4HJhxuCxUtt-cgMUTrhwpFvnaD9qyiDwLA@mail.gmail.com>

I had the same problem (among others) while trying to install
haskell-elm, incidentally. it might be due to there being both

  haskell-core/cabal-install 1.18.0.3-8 [installed]
  extra/cabal-install 1.20.0.1-1 [installed: 1.18.0.3-8]

but haskell-core is before extra in my pacman.conf. full list of repos:

[core]
[haskell-core]
[haskell-happstack]
[infinality-bundle]
[infinality-bundle-fonts]
[extra]
[community]

-----------------------------------------------------------
Here's the issue:

$ cabal --version
cabal-install version 1.18.0.3
using version 1.18.1.3 of the Cabal library

$ sudo aura -A aura
aura >>= Determining dependencies...
aura >>= AUR Packages:
aura

aura >>= Continue? [Y/n] y
aura >>= Building `aura`...
aura >>= Well, building `aura` failed.
aura >>= Dumping makepkg output in 3.. 2.. 1..
==> Making package: aura 1.2.3.4-1 (Sun May 25 14:31:03 PDT 2014)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Downloading aura-1.2.3.4.tar.gz...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100 99115  100 99115    0     0  66012      0  0:00:01  0:00:01 --:--:-- 29312
==> Validating source files with md5sums...
    aura-1.2.3.4.tar.gz ... Passed
==> Extracting sources...
  -> Extracting aura-1.2.3.4.tar.gz with bsdtar
==> Starting build()...

Setup.hs:1:8:
    Could not find module ?Distribution.Simple?
    Perhaps you haven't installed the "dyn" libraries for package
?Cabal-1.20.0.0??
    Use -v to see a list of the files searched for.
==> ERROR: A failure occurred in build().
    Aborting...


aura >>= Would you like to continue anyway? [Y/n] n
aura >>= Building failed.

From magnus at therning.org  Thu May 29 17:03:41 2014
From: magnus at therning.org (Magnus Therning)
Date: Thu, 29 May 2014 19:03:41 +0200
Subject: [arch-haskell] aura won't upgrade (looks like a cabal version
 issue)
In-Reply-To: <CAFrFfuGJqjD9mLHt4HJhxuCxUtt-cgMUTrhwpFvnaD9qyiDwLA@mail.gmail.com>
References: <CAFrFfuGJqjD9mLHt4HJhxuCxUtt-cgMUTrhwpFvnaD9qyiDwLA@mail.gmail.com>
Message-ID: <20140529170341.GA2478@tatooine>

On Sun, May 25, 2014 at 02:35:47PM -0700, Martin DeMello wrote:
> -----------------------------------------------------------
> Here's the issue:
> 
> $ cabal --version
> cabal-install version 1.18.0.3
> using version 1.18.1.3 of the Cabal library
> 
[...]
> Setup.hs:1:8:
>     Could not find module ?Distribution.Simple?
>     Perhaps you haven't installed the "dyn" libraries for package
> ?Cabal-1.20.0.0??
>     Use -v to see a list of the files searched for.
> ==> ERROR: A failure occurred in build().
>     Aborting...

Well, it looks like you have installed Cabal-1.20.0.0 without dyn
libs.

It's easy to get confused by the package cabal-install installing a
tool called `cabal`, while the underlying library is called Cabal.
So, when you run `cabal --version` you are checking which version of
cabal-install you have, and which version of Cabal *it* is using.
However, when you build aura cabal-install isn't used (based on my
reading of it's PKGBUILD), it uses a method that goes straight to
Cabal and it then uses the latest version installed.

/M

-- 
Magnus Therning                      OpenPGP: 0xAB4DFBA4 
email: magnus at therning.org   jabber: magnus at therning.org
twitter: magthe               http://therning.org/magnus

Goto labels should be left-aligned in all caps and should include the
programmer's name, home phone number, and credit card number.
     -- Abdul Nizar
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
URL: <http://www.haskell.org/pipermail/arch-haskell/attachments/20140529/329cdb67/attachment.sig>

From martindemello at gmail.com  Fri May 30 04:45:08 2014
From: martindemello at gmail.com (Martin DeMello)
Date: Thu, 29 May 2014 21:45:08 -0700
Subject: [arch-haskell] aura won't upgrade (looks like a cabal version
	issue)
In-Reply-To: <20140529170341.GA2478@tatooine>
References: <CAFrFfuGJqjD9mLHt4HJhxuCxUtt-cgMUTrhwpFvnaD9qyiDwLA@mail.gmail.com>
 <20140529170341.GA2478@tatooine>
Message-ID: <CAFrFfuFuWUVJ4PtPEBboba+JX0fErt68SD_48KxCDExpRMD8zw@mail.gmail.com>

On Thu, May 29, 2014 at 10:03 AM, Magnus Therning <magnus at therning.org>
wrote:

>
> It's easy to get confused by the package cabal-install installing a
> tool called `cabal`, while the underlying library is called Cabal.
> So, when you run `cabal --version` you are checking which version of
> cabal-install you have, and which version of Cabal *it* is using.
> However, when you build aura cabal-install isn't used (based on my
> reading of it's PKGBUILD), it uses a method that goes straight to
> Cabal and it then uses the latest version installed.
>

Ah, I did indeed get confused by that. I blew away my .cabal and .ghc and
everything installs fine now.

martin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.haskell.org/pipermail/arch-haskell/attachments/20140529/4a5a55fa/attachment.html>