Your message dated Tue, 26 Oct 2010 08:03:51 +0300
with message-id <[email protected]>
and subject line Re: Bug#572632: cabal-install: causes 'Warning: Module
`Prelude' is deprecated'
has caused the Debian Bug report #572632,
regarding cabal-install: causes 'Warning: Module `Prelude' is deprecated'
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
572632: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=572632
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: cabal-install
Version: 0.8.0-1
Severity: normal
If I configure a package using its own Setup.hs script, everything is fine
(regardless of whether I use Setup.hs or the cabal command for building),
but if I configure a package using the cabal command, I start getting
"Warning: Module `Prelude' is deprecated" warnings.
In the attached project:
a...@kukkaseppele:~/scratch/foobar$ cabal configure
Resolving dependencies...
Configuring foobar-0.0...
a...@kukkaseppele:~/scratch/foobar$ cabal build
Preprocessing executables for foobar-0.0...
Building foobar-0.0...
[1 of 1] Compiling Main ( foobar.hs,
dist/build/foobar/foobar-tmp/Main.o )
foobar.hs:1:0:
Warning: Module `Prelude' is deprecated:
You are using the old package `base' version 3.x.
Future GHC versions will not support base version 3.x. You
should update your code to use the new base version 4.x.
foobar.hs:3:0:
Warning: Definition but no type signature for `main'
Inferred type: main :: m ()
Linking dist/build/foobar/foobar ...
a...@kukkaseppele:~/scratch/foobar$ cabal clean
cleaning...
a...@kukkaseppele:~/scratch/foobar$ runghc Setup.hs configure
Configuring foobar-0.0...
a...@kukkaseppele:~/scratch/foobar$ cabal build
Preprocessing executables for foobar-0.0...
Building foobar-0.0...
[1 of 1] Compiling Main ( foobar.hs,
dist/build/foobar/foobar-tmp/Main.o )
foobar.hs:3:0:
Warning: Definition but no type signature for `main'
Inferred type: main :: m ()
Linking dist/build/foobar/foobar ...
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1,
'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.33-ibid-1 (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages cabal-install depends on:
ii libc6 2.10.2-6 Embedded GNU C Library: Shared lib
ii libffi5 3.0.9-1 Foreign Function Interface library
ii libgmp3c2 2:4.3.2+dfsg-1 Multiprecision arithmetic library
ii zlib1g 1:1.2.3.4.dfsg-3 compression library - runtime
Versions of packages cabal-install recommends:
ii ghc6 6.12.1-12 GHC - the Glasgow Haskell Compilat
cabal-install suggests no packages.
-- no debconf information
foobar.tar.gz
Description: GNU Zip compressed data
--- End Message ---
--- Begin Message ---
reopen 572632
thanks
On Mon, Oct 25, 2010 at 11:07:31PM +0100, Iain Lane wrote:
> This isn't a bug, it's just a different implementation of the cabal
> library features. `cabal' the executable is more careful about
> exposing warnings identified by the API than Setup.hs, which uses it
> directly. This is deliberate. It may be a poor choice, but a choice it
> is. :-)
That, unfortunately, makes no sense. I probably should have given the
following test in the bug report, but I assumed you'd try it yourself without
prodding:
For some reason, cabal the executable is bogusly choosing the old base:
a...@kukkaseppele:~/scratch/hgfhfg/foobar$ cabal -v configure
[...]
selecting base-3.0.3.2 (installed) and 4.2.0.0 (installed)
[...]
Dependency base ==3.0.3.2: using base-3.0.3.2
[...]
Whereas Setup.hs does no such thing:
a...@kukkaseppele:~/scratch/hgfhfg/foobar$ runghc Setup.hs -v configure
Configuring foobar-0.0...
Dependency base -any: using base-4.2.0.0
[...]
The package being configured here was attached to the original report.
This is NOT a case of cabal the executable being more strict, this is about
cabal the executable being buggy.
(I'll retract that if you provide a convincing reason why cabal the executable
chooses the version 3 base. I regard it unlikely that you'll be able to supply
one, as the Setup.hs configuration shows that it is not forced by the actual
dependencies.)
--
Antti-Juhani Kaijanaho, Jyväskylä, Finland
http://antti-juhani.kaijanaho.fi/newblog/
http://www.flickr.com/photos/antti-juhani/
signature.asc
Description: Digital signature
--- End Message ---
