[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#393806: marked as done (Uninstallable due to unmet dep on ghc6 (< 6.4.2-999))

Your message dated Tue, 24 Oct 2006 16:02:18 -0700
with message-id <E1GcVHm-0007dU-9a@spohr.debian.org>
and subject line Bug#393806: fixed in haskelldb 0.9.cvs.601-12
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message --- 
Package: libghc6-haskelldb-dev
Severity: serious
Version: 0.9.cvs.601-11

Hi

Your package is not installable as it depends on ghc6 (< 6.4.2-999) which is
not available in unstable anymore. You might want to consider supporting ghc6 6.6.

Cheers

Luk

-- 
Luk Claes - http://people.debian.org/~luk - GPG key 1024D/9B7C328D
Fingerprint:   D5AF 25FB 316B 53BB 08E7   F999 E544 DE07 9B7C 328D

Attachment: signature.asc
Description: OpenPGP digital signature


--- End Message ---
--- Begin Message --- 
Source: haskelldb
Source-Version: 0.9.cvs.601-12

We believe that the bug you reported is fixed in the latest version of
haskelldb, which is due to be installed in the Debian FTP archive:

haskelldb-bin_0.9.cvs.601-12_i386.deb
  to pool/main/h/haskelldb/haskelldb-bin_0.9.cvs.601-12_i386.deb
haskelldb_0.9.cvs.601-12.diff.gz
  to pool/main/h/haskelldb/haskelldb_0.9.cvs.601-12.diff.gz
haskelldb_0.9.cvs.601-12.dsc
  to pool/main/h/haskelldb/haskelldb_0.9.cvs.601-12.dsc
libghc6-haskelldb-dev_0.9.cvs.601-12_i386.deb
  to pool/main/h/haskelldb/libghc6-haskelldb-dev_0.9.cvs.601-12_i386.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 393806@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Arjan Oosting <arjan@debian.org> (supplier of updated haskelldb package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Wed, 25 Oct 2006 00:13:55 +0200
Source: haskelldb
Binary: haskelldb-bin libghc6-haskelldb-dev
Architecture: source i386
Version: 0.9.cvs.601-12
Distribution: unstable
Urgency: low
Maintainer: Debian QA Group <packages@qa.debian.org>
Changed-By: Arjan Oosting <arjan@debian.org>
Description: 
 haskelldb-bin - Utilities for use with HaskellDB
 libghc6-haskelldb-dev - Haskell library for expressing database queries
Closes: 393806
Changes: 
 haskelldb (0.9.cvs.601-12) unstable; urgency=low
 .
   * QA upload.
   * Rebuild against latest GHC (Closes: #393806)
   * Fix FTBFS with GHC 6.6
   * debian/mk-haskell-depends: add shell script to generate
     ${haskell:Depends} substitution variable.
   * debian/rules: use mk-haskell-depends to generate dependencies on other
     libghc-*-dev packages.
   * src/Database/HaskellDB/Database.hs: fix issue with distinct scoped
     type variables not being distinct.
Files: 
 c9ce5b9e4e9bdb74cadb25924ebefbaf 814 devel optional haskelldb_0.9.cvs.601-12.dsc
 1e77abe0241f9888d16bcb1f7aa38dbd 6020 devel optional haskelldb_0.9.cvs.601-12.diff.gz
 29c887bf3f3c954a9b0f56af7efebef4 915668 libdevel optional libghc6-haskelldb-dev_0.9.cvs.601-12_i386.deb
 ebde215269af143bdf92be4c8815341d 384284 devel optional haskelldb-bin_0.9.cvs.601-12_i386.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)

iD4DBQFFPpfZUALvsZYuOJARAgGCAJdaLiRz+GyrsX0Wo1lUxup4G8l5AKCxRYRC
FduHSp+5YmY6KKG1RuGHAQ==
=SU9g
-----END PGP SIGNATURE-----

--- End Message ---
Reply to: