Heads-up: ghc-7.0.1-1 => testing

Hey, As you may have noticed, ghc-7.0.1 was just released. I've built the package and did some preliminary testing and the basics work fine. So, anticipating the next haskell-platform version with ghc-7.0.1, I'll upload this to testing in the next 24 hours so we can start whacking at it. NOTE that nothing else has been built on this yet, so everything else is bound to fail if you're following the testing repository. --vk

On Tue, Nov 16, 2010 at 08:17, Vesa Kaihlavirta
Hey,
As you may have noticed, ghc-7.0.1 was just released. I've built the package and did some preliminary testing and the basics work fine.
So, anticipating the next haskell-platform version with ghc-7.0.1, I'll upload this to testing in the next 24 hours so we can start whacking at it.
NOTE that nothing else has been built on this yet, so everything else is bound to fail if you're following the testing repository.
Wow! Thanks for being so quick with getting this into testing :-) /M -- Magnus Therning (OpenPGP: 0xAB4DFBA4) magnus@therning.org Jabber: magnus@therning.org http://therning.org/magnus identi.ca|twitter: magthe

On 2010/11/16 Vesa Kaihlavirta
Hey,
As you may have noticed, ghc-7.0.1 was just released. I've built the package and did some preliminary testing and the basics work fine.
So, anticipating the next haskell-platform version with ghc-7.0.1, I'll upload this to testing in the next 24 hours so we can start whacking at it.
NOTE that nothing else has been built on this yet, so everything else is bound to fail if you're following the testing repository.
Is it too late to use the "new" [staging] repository instead of [testing] for this ? It was aimed at large rebuilds, and it looks it is the case here. Many incompatibilities are expected: if GHC7 is supposed to enter the main repositories in 2011, [testing] may be too early. For example, the current version of mtl cannot be built with GHC7, but mtl-1.1.1.0 is compatible. I see that HP2011 may set mtl2 to be the standard, so we have the choice of either: * follow haskell-platform ML and choose to build the proposed contents of HP2011 in a test repo * keep HP2010 versions of the libraries unless they are incompatible with GHC7, and then do the minimal upgrade so that most packages remain compatible. -- Rémy.

On 2010/11/22 Rémy Oudompheng
* keep HP2010 versions of the libraries unless they are incompatible with GHC7, and then do the minimal upgrade so that most packages remain compatible.
I put up a small repository at [remy-haskell] Server = http://dev.archlinux.org/~remy/haskell/$arch It should contain HP2010 versions of libraries except for the following upgrades (incompatibilities with GHC7): deepseq 1.1.1.0 -> 1.1.0.1 HTTP 4000.0.9 -> 4000.0.10 mtl 1.1.0.2 -> 1.1.1.0 I have also put network, parsec, tar, xhtml in the same version as in [extra]. -- Rémy.

On 2010/11/24 Rémy Oudompheng
deepseq 1.1.1.0 -> 1.1.0.1 HTTP 4000.0.9 -> 4000.0.10 mtl 1.1.0.2 -> 1.1.1.0
As you may have noticed, ghc-7* was moved to [staging] by other devs. I began rebuilding current versions of libraries when they were compatible. I would like your approval to do the following: deepseq 1.1.1.0 -> 1.1.0.1 (version 1.1.1.0 is incompatible with GHC7 because it specifies a wrong version range, but the source code is identical, so this upgrade is absolutely harmless) mtl 1.1.0.2 -> 1.1.1.0 (version 1.1.0.2 is incompatible with GHC7, but it looks like 1.1.1.0 is API-compatible. It seems HP2011 will choose mtl 2.* however) Those packages would also end up in the [staging] repo. -- Rémy.

On 2010/11/26 Rémy Oudompheng
On 2010/11/24 Rémy Oudompheng
wrote: deepseq 1.1.1.0 -> 1.1.0.1 HTTP 4000.0.9 -> 4000.0.10 mtl 1.1.0.2 -> 1.1.1.0
As you may have noticed, ghc-7* was moved to [staging] by other devs. I began rebuilding current versions of libraries when they were compatible. I would like your approval to do the following:
deepseq 1.1.1.0 -> 1.1.0.1 (version 1.1.1.0 is incompatible with GHC7 because it specifies a wrong version range, but the source code is identical, so this upgrade is absolutely harmless) mtl 1.1.0.2 -> 1.1.1.0 (version 1.1.0.2 is incompatible with GHC7, but it looks like 1.1.1.0 is API-compatible. It seems HP2011 will choose mtl 2.* however)
Those packages would also end up in the [staging] repo.
Most libraries are now in [staging]. I've built darcs as an example: it needs several patches to work, I've tken them from http://darcs.vm.spiny.org.uk/~ganesh/darcs-2.5-ghc7-2/ Rémy.

On 2010/11/27 Rémy Oudompheng
Most libraries are now in [staging]. I've built darcs as an example: it needs several patches to work, I've tken them from http://darcs.vm.spiny.org.uk/~ganesh/darcs-2.5-ghc7-2/
I've also rebuilt packages in [community] : xmonad required a patch currently in darcs (the current release is quite old), and I have updated gtk2hs along the way. -- Rémy.

Hi Rémy,
As you may have noticed, ghc-7* was moved to [staging] by other devs. I began rebuilding current versions of libraries when they were compatible. I would like your approval to do the following:
deepseq 1.1.1.0 -> 1.1.0.1 mtl 1.1.0.2 -> 1.1.1.0
personally, I am all for it. I'd very much like to have GHC7, and those updates seem comparatively minor, so I'd say go for it! At the same time, I am a little concerned about the state of [extra]. There are problems that have been known for several weeks, yet they don't seem to get fixed. That makes me wonder about our priorities. The most annoying bug so far is that haskell-tar hasn't been built with --enable-shared. This means that no package that depends on haskell-tar -- such as haskell-archlinux -- can be built with --enable-shared. This is probably not a big issue for random ArchLinux users, but it sure does make my life inconvenient, because I'm trying to work with the latest version of our tool-chain, which sets --enable-shared by default. Also, several packages don't include Haddock documentation, such as haskell-regex-base, haskell-regex-compat, haskell-regex-posix, and haskell-hunit. Again, this is not exactly a show-stopper grade problem, but every so often I do work on a laptop without network access, and having the reference documentation installed locally on disk is quite helpful in that situation. I have reported those problems on this list before, and I have also filed bug reports in the ArchLinux tracker, but I cannot seem to get a response. So, if I had to choose between an ArchDev working on fixing those problems and an ArchDev working on GHC7 support, I'd rather have the problems in the existing package base fixed fist. Just my 2 cents ... Take care, Peter

On 2010/11/29 Peter Simons
Also, several packages don't include Haddock documentation, such as haskell-regex-base, haskell-regex-compat, haskell-regex-posix, and haskell-hunit. Again, this is not exactly a show-stopper grade problem, but every so often I do work on a laptop without network access, and having the reference documentation installed locally on disk is quite helpful in that situation.
I have reported those problems on this list before, and I have also filed bug reports in the ArchLinux tracker, but I cannot seem to get a response. So, if I had to choose between an ArchDev working on fixing those problems and an ArchDev working on GHC7 support, I'd rather have the problems in the existing package base fixed fist. Just my 2 cents ...
I have fixed those when building packages for GHC7, I'll backport it to the current extra packages. -- Rémy.
participants (4)
-
Magnus Therning
-
Peter Simons
-
Rémy Oudompheng
-
Vesa Kaihlavirta