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
>>> wrote:
On 2014-05-12 15:47, Magnus Therning wrote:
[--snip--]
>>
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
>> wrote:
>>> On 2014-05-12 15:47, Magnus Therning wrote:
>>> [--snip--]
>>>
>>> All I needed to install build-wrapper (which I thi
On 2014-05-15 11:35, Magnus Therning wrote:
> On Wed, May 14, 2014 at 10:47 PM, Bardur Arantsson
> 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
>>
>> $ m
On Wed, May 14, 2014 at 10:47 PM, Bardur Arantsson 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 `./Set
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
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-installi
On Mon, May 12, 2014 at 4:02 PM, Dawid Loubser 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
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 n
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 wrote:
> I had a similar issue with a large number of packages.
> I ended up removing and re-installing my entire Ha
On Mon, May 12, 2014 at 3:33 PM, Nicola Squartini wrote:
> On Mon, May 12, 2014 at 2:24 PM, Dawid Loubser
> 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 sh
On Mon, May 12, 2014 at 2:24 PM, Dawid Loubser 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
dependenci
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 tim
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 wrote:
> I was hoping someone might hel
13 matches
Mail list logo