ANN: stack-0.1.10.0

35 views
Skip to first unread message

Emanuel Borsboom

unread,
Dec 4, 2015, 6:57:21 PM12/4/15
to haskel...@haskell.org, haskel...@googlegroups.com, “commercialhaskell@googlegroups.com”

Release notes:

  • The Stack home page is now at haskellstack.org, which shows the documentation rendered by readthedocs.org. Note: this has necessitated some changes to the links in the documentation’s markdown source code, so please check the links on the website before submitting a PR to fix them.
  • The locations of the Ubuntu and Debian package repositories have changed to have correct URL semantics according to Debian’s guidelines #1378. The old locations will continue to work for some months, but we suggest that you adjust your /etc/apt/sources.list.d/fpco.list to the new location to avoid future disruption.
  • openSUSE and SUSE Linux Enterprise packages are now available, thanks to @mimi1vx. Note: there will be some lag before these pick up new versions, as they are based on Stackage LTS.

Major changes:

  • Support for building inside a Nix-shell providing system dependencies #1285
  • Add optional GPG signing on stack upload --sign or with stack sig sign ...

Other enhancements:

  • Print latest applicable version of packages on conflicts #508
  • Support for packages located in Mercurial repositories #1397
  • Only run benchmarks specified as build targets #1412
  • Support git-style executable fall-through (stack something executes stack-something if present) #1433
  • GHCi now loads intermediate dependencies #584
  • --work-dir option for overriding .stack-work #1178
  • Support detailed-0.9 tests #1429
  • Docker: improved POSIX signal proxying to containers #547

Bug fixes:

  • Show absolute paths in error messages in multi-package builds #1348
  • Docker-built binaries and libraries in different path #911 #1367
  • Docker: --resolver argument didn’t effect selected image tag
  • GHCi: Spaces in filepaths caused module loading issues #1401
  • GHCi: cpp-options in cabal files weren’t used #1419
  • Benchmarks couldn’t be run independently of eachother #1412
  • Send output of building setup to stderr #1410

Geraldus

unread,
Dec 5, 2015, 2:50:15 AM12/5/15
to Emanuel Borsboom, haskel...@haskell.org, haskel...@googlegroups.com, “commercialhaskell@googlegroups.com”
Thank you!  It's nice to see new homepage and pretty documentation! 

сб, 5 дек. 2015 г. в 4:57, Emanuel Borsboom <ma...@fpcomplete.com>:
--
You received this message because you are subscribed to the Google Groups "haskell-stack" group.
To unsubscribe from this group and stop receiving emails from it, send an email to haskell-stac...@googlegroups.com.
To post to this group, send email to haskel...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/haskell-stack/CACGj5vLb32C9kBxXjSYN1nP8Vc77wgo2MDoFRShoHscYgYKqZg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Jens Petersen

unread,
Dec 10, 2015, 3:09:18 AM12/10/15
to Emanuel Borsboom, haskell-stack
Hi, thanks for the stack releases.

I am having trouble building stack-0.1.10.0 for Fedora.

The last version I successfully build was actually 0.1.6.0.
I think 0.1.8.0 ((how about dropping the .0 suffix?:)) required
ghc-7.10 and so I left it.

For 0.1.10.0 I get a Template Haskell related linking error:

```
:
Configuring conduit-combinators-1.0.3...
Building conduit-combinators-1.0.3...
Installed conduit-combinators-1.0.3
Configuring stack-0.1.10.0...
Building stack-0.1.10.0...
Failed to install stack-0.1.10.0
Last 10 lines of the build log (
/builddir/build/BUILD/stack-0.1.10.0/.cabal-sandbox/logs/stack-0.1.10.0.log
):
During interactive linking, GHCi couldn't find the following symbol:
templatezmhaskell_LanguageziHaskellziTHziSyntax_zdfMonadQzuzdczgzgze_closure
This may be due to you not asking GHCi to load extra object files,
archives or DLLs needed by your current session. Restart GHCi, specifying
the missing library using the -L/path/to/object/dir and -lmissinglibname
flags, or simply by naming the relevant files on the GHCi command line.
Alternatively, this link failure might indicate a bug in GHCi.
If you suspect the latter, please send a bug report to:
glasgow-ha...@haskell.org
cabal: Error: some packages failed to install:
stack-0.1.10.0 failed during the building phase. The exception was:
ExitFailure 1
```

This happens with both 32bit and 64bit builds using ghc-7.10.2 and 7.10.3.
Anyone else seen this problem? Any ideas?

I can report it in github too if it helps or even file a ghc bug if
that is where the problem is.

Jens

Emanuel Borsboom

unread,
Dec 10, 2015, 7:10:12 PM12/10/15
to Jens Petersen, haskell-stack
See https://github.com/commercialhaskell/stack/issues/1351#issuecomment-162186143 and https://github.com/commercialhaskell/stack/issues/1450 for investigation I've done into this.  I haven't had confirmation whether upgrading to a newer cabal-install fixes it, so I'd be interested to know whether that works for you.  Another option is to use an older version of stack to build itself using the stack-7.8.yaml included in the repo (e.g. `stack --stack-yaml=stack-7.8.yaml build`).

Jens Petersen

unread,
Dec 11, 2015, 4:14:49 AM12/11/15
to Emanuel Borsboom, haskell-stack
Hi Emanuel,

On 11 December 2015 at 09:10, Emanuel Borsboom <ma...@fpcomplete.com> wrote:
> See https://github.com/commercialhaskell/stack/issues/1351#issuecomment-162186143
> and https://github.com/commercialhaskell/stack/issues/1450 for investigation I've done into this.

I see thanks for the explanation - nice cabal hell... ;)

> I haven't had confirmation whether upgrading to a
> newer cabal-install fixes it, so I'd be interested to know whether that
> works for you.

Oh, I think it probably does for ghc-7.10, but maybe not for ghc-7.8.4
(dunno if it needs newer Cabal too?)
Now I got ghc-7.10 and cabal-install-1.22 to build it. :-)
(lts-2 seems not new enough to build stack-0.1.10.)

> Another option is to use an older version of stack to build
> itself using the stack-7.8.yaml included in the repo (e.g. `stack
> --stack-yaml=stack-7.8.yaml build`).

Okay I managed also to build it also with cabal-install-1.22 and
https://www.stackage.org/lts-3/cabal.config.
But then I realized from what you wrote that this is not actually necessary.

Thanks for your help!

Jens
Reply all
Reply to author
Forward
0 new messages