Daily update of the state of Hackage wrt. GHC 6.10 release candidates.
Lots of packages were updated today, Cabal 1.6 and cabal-install 0.6
were also put out. Things are in a good shape.
Note that you'll need a "soft dep" in your cabal index file,
base < 4
parsec < 3
HaXml == 1.13.*
On Thu, Oct 09, 2008 at 03:37:32PM +0200, Christian Maeder wrote:
> Ian Lynagh wrote:
> > Please test as much as possible; bugs are much cheaper if we find them
> > before the release!
>
> How about a test-suite?
Good point: I've addde one to
http://www.haskell.org/ghc/dist/stable/dist/6.10.1-rc-
Hi,
On Oct 10, 2008, at 4:45 PM, denis wrote:
Greg, folks,
port install ghc worked after 7 hours or so, but then
sudo port -v install hs-ghc-paths (on which pandoc apparently depends)
=>
# from: sudo port -v install hs-ghc-paths
# run: 10 Oct 2008 22:35 in /opt/local Denis.local mac 10.4.1
On 10/11/08, Niklas Broberg <[EMAIL PROTECTED]> wrote:
> dons:
> > A breakdown of the remaing causes for DependencyFailed,
> > [...]
> > 4 hsx-0.4.4
New version uploaded that works with both 6.8.3 and 6.10 rc1 (through
dark cpp magic). I doubt I need to show this trick to anyone el
On Fri, 2008-10-10 at 16:13 +0100, Simon Marlow wrote:
> As far as I can see, you could export a compatibility shim called
> buildVerbose without any difficulty,
Done.
> all I have to do is remove the explicit import list. Or is there a
> better fix you had in mind?
Patches for alex and happy
bulat.ziganshin:
> Hello Don,
>
> Saturday, October 11, 2008, 9:54:10 PM, you wrote:
>
> seems that i misunderstood it: i thought it's a list of base4 vs base3
> changes, but actually it seems like a base30 vs base31?
>
> base3 -> base4 upgrade hints are not documented anywhere?
>
It's a list
Hello Don,
Saturday, October 11, 2008, 9:54:10 PM, you wrote:
seems that i misunderstood it: i thought it's a list of base4 vs base3
changes, but actually it seems like a base30 vs base31?
base3 -> base4 upgrade hints are not documented anywhere?
> bulat.ziganshin:
>> Hello Don,
>>
>> Saturda
bulat.ziganshin:
> Hello Don,
>
> Saturday, October 11, 2008, 9:21:47 PM, you wrote:
> > It collects the 7 or so known issues that break code with GHC 6.10.
>
> i've quickly tried to compile my app with 6.10 (using base4). all the
> problems i got was due to exception handling. catch, finally, th
Hello Don,
Saturday, October 11, 2008, 9:21:47 PM, you wrote:
> It collects the 7 or so known issues that break code with GHC 6.10.
i've quickly tried to compile my app with 6.10 (using base4). all the
problems i got was due to exception handling. catch, finally, throwIO
doesn't work
added to wi
niklas.broberg:
> > So there is a compatibility module in the new syb. Unfortunately,
> > that won't tell you about the moves and rationale. Most of the time,
> > you'll want Data.Data (check "ghc -e ':browse Data.Data'" or the
> > Haddock pages, or google for "syb" in the libraries@ archives):
http://haskell.org/haskellwiki/Upgrading_packages#Typical_breakages_with_GHC_6.10
It collects the 7 or so known issues that break code with GHC 6.10.
Please feel free to clean up, and especially *add techniques for
handling each change*.
If we do this right, with cabal-install being smart, clear
On Sat, Oct 11, 2008 at 18:41, David Menendez <[EMAIL PROTECTED]> wrote:
> 2008/10/11 José Pedro Magalhães <[EMAIL PROTECTED]>:
> > In base4, no Data.Generics.* modules were kept. Instead, a new module,
> > Data.Data, contains all that was in Data.Generics.Basics and most of
> > Data.Generics.Inst
claus.reinke:
> >We've been using the cabal-install build reporting stuff to get more
> >detailed info on build failures with ghc-6.10 vs 6.8. cabal-install
> >generates these build-reports.log files and individual log files for
> >each build.
>
> Since you do have the infrastructure set up: haddo
2008/10/11 José Pedro Magalhães <[EMAIL PROTECTED]>:
> In base4, no Data.Generics.* modules were kept. Instead, a new module,
> Data.Data, contains all that was in Data.Generics.Basics and most of
> Data.Generics.Instances.
Data.Data? Surely we can come up with something better than that.
--
Dav
Hi Christian,
On Fri, Oct 10, 2008 at 05:40:24PM +0200, Christian Maeder wrote:
>
> Not in scope: `readEither'
>
> import GHC.Read (readEither)
>
> and used to work with ghc-6.8.
>
> What should I use as replacement?
>
> P.S. It is also not mentioned in the changes:
We don't guarantee a
On Fri, Oct 10, 2008 at 03:54:07PM -0700, Duncan Coutts wrote:
> On Fri, 2008-10-10 at 15:34 -0700, Don Stewart wrote:
> > arrows fails due to:
> >
> > [ 3 of 12] Compiling Control.Arrow.Transformer.CoState (
> > Control/Arrow/Transformer/CoState.hs,
> > dist/build/Control/Arrow/Transformer/
> So there is a compatibility module in the new syb. Unfortunately,
> that won't tell you about the moves and rationale. Most of the time,
> you'll want Data.Data (check "ghc -e ':browse Data.Data'" or the
> Haddock pages, or google for "syb" in the libraries@ archives):
>
>$ ghc-pkg find-m
Hello,
On Sat, Oct 11, 2008 at 12:16, Claus Reinke <[EMAIL PROTECTED]> wrote:
>
> Pedro: it might be helpful if the haddock pages for the old and new syb
> modules were to point to a syb wiki page (which could then link
> to the relevant threads on libraries@)? Or is that information already in
>
We've been using the cabal-install build reporting stuff to get more
detailed info on build failures with ghc-6.10 vs 6.8. cabal-install
generates these build-reports.log files and individual log files for
each build.
Since you do have the infrastructure set up: haddock is also changing
with ghc
> Btw, I also have problems with the haskell-src-exts that imports
> Data.Generics.Instances (to generate Data and Typeable instances).
> Where would these have moved to in the new base?
ghc-pkg provides general help for finding packages for modules:
$ ghc-pkg find-module Data.Generics.I
Hello,
On Sat, Oct 11, 2008 at 03:52, Niklas Broberg <[EMAIL PROTECTED]>wrote:
>
>
> Though obviously this would only work if the module
> Data.Generics.Instances was preserved under that name somewhere else.
> If it was renamed or changed (which I suspect), then the hassle of
> keeping up to date
Hi Denis,
I haven't built pandoc yet --- I didn't do the port --- but I'll have
a go at it tonight and
let you know what I find.
BTW, did you run
$ sudo port selfupdate
before starting to make sure you had the latest Portfiles for
everything?
Best Wishes,
Greg
On Oct 10, 2008
OK, so we have *56* packages total that no longer compile with GHC 6.10, but
did with 6.8.3. We can now see exactly what broke and why.
I think these potential breakage issues, and how to solve them canonically ,
should be documented on the wiki. Most should have standard solutions, some
might be
All,
We've been using the cabal-install build reporting stuff to get more
detailed info on build failures with ghc-6.10 vs 6.8. cabal-install
generates these build-reports.log files and individual log files for
each build.
Below is a list of packages that worked with 6.8 and fail with 6.10. If
yo
24 matches
Mail list logo
