On Sat, Oct 13, 2012 at 1:35 PM, Fabio Riga wrote:

2012/10/13 Ramana Kumar

...

I'm not sure why that error happened but it happened to me too.

The problem seems to be that those files were not part of any package, but now are in ghc.

Thanks :) So deleting them before upgrading was the right move.

...

I removed the offending files manually and tried again, and ran into more problems (although everything installed, there were many warnings about interface files being the wrong version and being skipped). So I'm not sure what the correct way out is. Perhaps it will require some manual removals then reinstalls.

This is a problem with ghc-pkg version. For previous version of ghc I had to do:

$ pacman -Rcs ghc

then reinstall ghc and needed haskell-* packages. I think you'll want to remove the offending files before installing ghc again. I hope this solve the problem.

Thanks for the information. I am going to try reinstalling ghc and then all my haskell-* packages, and hopefully it will go through smoothly. By the way, what's the progress on haskell-extra, and did you find out where haskell-old lives (in case haskell-extra still depends on haskell-old)?

Fabio

_______________________________________________ arch-haskell mailing list arch-haskell@haskell.org http://www.haskell.org/mailman/listinfo/arch-haskell

2012/10/13 Fabio Riga :

2012/10/13 Ramana Kumar

...

I'm not sure why that error happened but it happened to me too.

The problem seems to be that those files were not part of any package, but now are in ghc.

...

I removed the offending files manually and tried again, and ran into more problems (although everything installed, there were many warnings about interface files being the wrong version and being skipped). So I'm not sure what the correct way out is. Perhaps it will require some manual removals then reinstalls.

This is a problem with ghc-pkg version. For previous version of ghc I had to do:

$ pacman -Rcs ghc

then reinstall ghc and needed haskell-* packages. I think you'll want to remove the offending files before installing ghc again. I hope this solve the problem.

Fabio

Why is it that every single time there is a ghc-update, I have to remove everything and reinstall everything haskell related. Haskell is such a cool language but keeping a Haskell environment up-to-date is sometimes just a real pain. Sorry for the rant. Thomas

On 15 October 2012 11:00, Thomas Friedrich wrote:

2012/10/13 Fabio Riga :

...

2012/10/13 Ramana Kumar

...

I'm not sure why that error happened but it happened to me too.

The problem seems to be that those files were not part of any package, but now are in ghc.

...

I removed the offending files manually and tried again, and ran into more problems (although everything installed, there were many warnings about interface files being the wrong version and being skipped). So I'm not sure what the correct way out is. Perhaps it will require some manual removals then reinstalls.

This is a problem with ghc-pkg version. For previous version of ghc I had to do:

$ pacman -Rcs ghc

then reinstall ghc and needed haskell-* packages. I think you'll want to remove the offending files before installing ghc again. I hope this solve the problem.

Why is it that every single time there is a ghc-update, I have to remove everything and reinstall everything haskell related. Haskell is such a cool language but keeping a Haskell environment up-to-date is sometimes just a real pain.

As Haskell newbie and new born Hakyll users, I've found recent replies [1] by Ian Ross interesting: "I'm also using Arch Linux on x86_64. I would strongly recommend *not* using the Arch packages for most Haskell things. I use hsenv instead." I haven't switched myself and I still use the packages, but I started to wonder if Ian's got the point indeed. [1] https://groups.google.com/d/topic/hakyll/9G1qXBA4raU/discussion Best regards, -- Mateusz Loskot, http://mateusz.loskot.net

From user's perspective, I guess I agree the Arch packages should be

Ramana, preferred. I'm new to Haskell, so I'm not able to comment on packaging strategies. I simply listen to what experts say, trying to make my own sense of it. -- Mateusz Łoskot (sent from mobile, apology for top-post or broken quotes) On 15 Oct 2012 17:22, "Ramana Kumar" wrote:

It is possible and desirable to manage haskell packages with pacman on Arch Linux! It is just not perfect yet - the arch-haskell project needs your help. Perhaps you could point Ian Ross this way too. (For me personally, using the [haskell] and [haskell-extra] repositories has worked out well so far, and it's nice knowing everything is managed properly by pacman.)

On Mon, Oct 15, 2012 at 5:16 PM, Mateusz Loskot wrote:

...

On 15 October 2012 11:00, Thomas Friedrich wrote:

...

2012/10/13 Fabio Riga :

...

2012/10/13 Ramana Kumar

...

I'm not sure why that error happened but it happened to me too.

The problem seems to be that those files were not part of any package, but now are in ghc.

...

I removed the offending files manually and tried again, and ran into more problems (although everything installed, there were many warnings about interface files being the wrong version and being skipped). So I'm not sure what the correct way out is. Perhaps it will require some manual removals then reinstalls.

This is a problem with ghc-pkg version. For previous version of ghc I had to do:

$ pacman -Rcs ghc

then reinstall ghc and needed haskell-* packages. I think you'll want to remove the offending files before installing ghc again. I hope this solve the problem.

Why is it that every single time there is a ghc-update, I have to remove everything and reinstall everything haskell related. Haskell is such a cool language but keeping a Haskell environment up-to-date is sometimes just a real pain.

As Haskell newbie and new born Hakyll users, I've found recent replies [1] by Ian Ross interesting:

"I'm also using Arch Linux on x86_64. I would strongly recommend *not* using the Arch packages for most Haskell things. I use hsenv instead."

I haven't switched myself and I still use the packages, but I started to wonder if Ian's got the point indeed.

[1] https://groups.google.com/d/topic/hakyll/9G1qXBA4raU/discussion

Best regards, -- Mateusz Loskot, http://mateusz.loskot.net

_______________________________________________ arch-haskell mailing list arch-haskell@haskell.org http://www.haskell.org/mailman/listinfo/arch-haskell

On Mon, Oct 15, 2012 at 05:16:24PM +0100, Mateusz Loskot wrote: [...]

As Haskell newbie and new born Hakyll users, I've found recent replies [1] by Ian Ross interesting:

"I'm also using Arch Linux on x86_64. I would strongly recommend *not* using the Arch packages for most Haskell things. I use hsenv instead."

I haven't switched myself and I still use the packages, but I started to wonder if Ian's got the point indeed.

[1] https://groups.google.com/d/topic/hakyll/9G1qXBA4raU/discussion

As so often it all depends on what your goal is. hsenv compares itself to Python's virtualenv[1]. I've personally written quite a bit of Python code, and used many tools and programs written in Python, without *ever* feeling a need to use virtualenv. The same is, so far at least, true regarding Haskell and hsenv. In neither language have I ever had the need to have more than a single environment around. On the other hand I've often had a need to install libraries on my system. In those cases I personally prefer using the package manager to make libraries available to all users on my system, i.e. I don't use distutils and cabal to install things on my system, just as I don't download tar-balls and run 'sudo make install' (instead I wrap that up in a PKGBUILD and install the resulting package). On the other hand I completely understand why virtualenv/hsenv are useful in some cases. By creating a virtual environment they disconnect you from the whims of upstream (Arch & ArchHaskell), letting you create the exact environment you need and run 'pacman -Syu' without having to worry (too much) about breaking that service your livelihood depends on. /M [1]: https://github.com/Paczesiowa/hsenv#what-is-it -- Magnus Therning OpenPGP: 0xAB4DFBA4 email: magnus@therning.org jabber: magnus@therning.org twitter: magthe http://therning.org/magnus Perl is another example of filling a tiny, short-term need, and then being a real problem in the longer term. -- Alan Kay

On 15 October 2012 17:16, Mateusz Loskot wrote:

On 15 October 2012 11:00, Thomas Friedrich wrote:

...

2012/10/13 Fabio Riga :

...

2012/10/13 Ramana Kumar

...

I'm not sure why that error happened but it happened to me too.

The problem seems to be that those files were not part of any package, but now are in ghc.

...

I removed the offending files manually and tried again, and ran into more problems (although everything installed, there were many warnings about interface files being the wrong version and being skipped). So I'm not sure what the correct way out is. Perhaps it will require some manual removals then reinstalls.

This is a problem with ghc-pkg version. For previous version of ghc I had to do:

$ pacman -Rcs ghc

then reinstall ghc and needed haskell-* packages. I think you'll want to remove the offending files before installing ghc again. I hope this solve the problem.

Why is it that every single time there is a ghc-update, I have to remove everything and reinstall everything haskell related. Haskell is such a cool language but keeping a Haskell environment up-to-date is sometimes just a real pain.

As Haskell newbie and new born Hakyll users, I've found recent replies [1] by Ian Ross interesting:

"I'm also using Arch Linux on x86_64. I would strongly recommend *not* using the Arch packages for most Haskell things. I use hsenv instead."

I haven't switched myself and I still use the packages, but I started to wonder if Ian's got the point indeed.

[1] https://groups.google.com/d/topic/hakyll/9G1qXBA4raU/discussion

This is just an update on the discussion I referred to, Ian posted more details on his blog: http://www.skybluetrades.net/posts/2012/10/13/arch-haskell.html Other users may find it interesting too. Best regards, -- Mateusz Loskot, http://mateusz.loskot.net

2012/10/18 Mateusz Loskot

On 13 October 2012 11:20, Mateusz Loskot wrote:

...

mloskot ~ $ sudo pacman -Syu ... error: failed to commit transaction (conflicting files) ghc: /usr/share/doc/ghc/html/libraries/hslogo-16.png exists in filesystem ghc: /usr/share/doc/ghc/html/libraries/synopsis.png exists in filesystem Errors occurred, no packages were upgraded.

We've diverted the thread a little bit from my original question which seems still unanswered yet.

Does it mean currently there is no reliable cure for the update problem?

Now I updated to ghc-7.6 and the method I already exposed just worked. 1. pacman -Rcs ghc 2. rm -r /usr/share/doc/ghc 3. pacman -S ghc cabal-install haskell-whatever Those file wasn't in any package before, so point 2 is mandatory. I also agree that deinstallling and reinstalling everything Haskell-related is very bad, but this is far more comfortable than using cabal and having 10 versions of every package installed (and likely broken). As Haskell programs are statically compiled, I really don't see the point in using such a tool like hsenv. I stick with the archhaskell system. Just my humble opinion, Fabio

On 19 October 2012 11:42, Fabio Riga wrote:

2012/10/18 Mateusz Loskot

...

On 13 October 2012 11:20, Mateusz Loskot wrote:

...

mloskot ~ $ sudo pacman -Syu ... error: failed to commit transaction (conflicting files) ghc: /usr/share/doc/ghc/html/libraries/hslogo-16.png exists in filesystem ghc: /usr/share/doc/ghc/html/libraries/synopsis.png exists in filesystem Errors occurred, no packages were upgraded.

We've diverted the thread a little bit from my original question which seems still unanswered yet.

Does it mean currently there is no reliable cure for the update problem?

Now I updated to ghc-7.6 and the method I already exposed just worked.

1. pacman -Rcs ghc 2. rm -r /usr/share/doc/ghc 3. pacman -S ghc cabal-install haskell-whatever

Those file wasn't in any package before, so point 2 is mandatory.

Thanks mate, this worked well for me. Best regards, -- Mateusz Loskot, http://mateusz.loskot.net