Your message dated Sun, 09 Oct 2005 06:32:05 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#332893: fixed in missingpy 0.8.0
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)

--------------------------------------
Received: (at submit) by bugs.debian.org; 9 Oct 2005 09:40:16 +0000
>From [EMAIL PROTECTED] Sun Oct 09 02:40:16 2005
Return-path: <[EMAIL PROTECTED]>
Received: from dsl093-039-086.pdx1.dsl.speakeasy.net (tennyson.dodds.net) 
[66.93.39.86] 
        by spohr.debian.org with esmtp (Exim 3.36 1 (Debian))
        id 1EOXfD-0004GI-00; Sun, 09 Oct 2005 02:40:16 -0700
Received: by tennyson.dodds.net (Postfix, from userid 1000)
        id 4B1B97038; Sun,  9 Oct 2005 02:40:16 -0700 (PDT)
Date: Sun, 9 Oct 2005 02:40:16 -0700
From: Steve Langasek <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: libghc6-missingpy-dev: unsatisfiable dependency on 
libghc6-missingh-dev (= 0.11.2)
Message-ID: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
        protocol="application/pgp-signature"; boundary="kVXhAStRUZ/+rrGn"
Content-Disposition: inline
User-Agent: Mutt/1.5.9i
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 
        (1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level: 
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE 
        autolearn=no version=2.60-bugs.debian.org_2005_01_02


--kVXhAStRUZ/+rrGn
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Package: libghc6-missingpy-dev
Version: 0.2.1
Severity: grave
Justification: renders package unusable

The current version of libghc6-missingpy-dev is uninstallable in unstable
because it depends on libghc6-missing-dev (=3D 0.11.2), and unstable curren=
tly
has version 0.11.5.  Perhaps this was meant to be (>=3D 0.11.5) instead?

Since gmp must be updated in testing for the C++ ABI transition, bringing
with it at the same time gcc-4.0, ghc6, and missingh, missingpy will be
removed from testing pending the resolution of this bug.

Thanks,
--=20
Steve Langasek                   Give me a lever long enough and a Free OS
Debian Developer                   to set it on, and I can move the world.
[EMAIL PROTECTED]                                   http://www.debian.org/

--kVXhAStRUZ/+rrGn
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

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

iD8DBQFDSOWAKN6ufymYLloRAi2FAJ0aPeDFIMFTMuSFZClBmYybV9EjvwCgg020
Wqx0kbwT9cRgQzrNUb8pjdM=
=ldxe
-----END PGP SIGNATURE-----

--kVXhAStRUZ/+rrGn--

---------------------------------------
Received: (at 332893-close) by bugs.debian.org; 9 Oct 2005 13:38:25 +0000
>From [EMAIL PROTECTED] Sun Oct 09 06:38:25 2005
Return-path: <[EMAIL PROTECTED]>
Received: from katie by spohr.debian.org with local (Exim 3.36 1 (Debian))
        id 1EObHZ-0006AO-00; Sun, 09 Oct 2005 06:32:05 -0700
From: John Goerzen <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: $Revision: 1.56 $
Subject: Bug#332893: fixed in missingpy 0.8.0
Message-Id: <[EMAIL PROTECTED]>
Sender: Archive Administrator <[EMAIL PROTECTED]>
Date: Sun, 09 Oct 2005 06:32:05 -0700
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 
        (1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level: 
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER 
        autolearn=no version=2.60-bugs.debian.org_2005_01_02

Source: missingpy
Source-Version: 0.8.0

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

libghc6-missingpy-dev_0.8.0_i386.deb
  to pool/main/m/missingpy/libghc6-missingpy-dev_0.8.0_i386.deb
missingpy_0.8.0.dsc
  to pool/main/m/missingpy/missingpy_0.8.0.dsc
missingpy_0.8.0.tar.gz
  to pool/main/m/missingpy/missingpy_0.8.0.tar.gz



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 [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
John Goerzen <[EMAIL PROTECTED]> (supplier of updated missingpy 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 [EMAIL PROTECTED])


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

Format: 1.7
Date: Sun,  9 Oct 2005 08:25:19 -0500
Source: missingpy
Binary: libghc6-missingpy-dev
Architecture: source i386
Version: 0.8.0
Distribution: unstable
Urgency: low
Maintainer: John Goerzen <[EMAIL PROTECTED]>
Changed-By: John Goerzen <[EMAIL PROTECTED]>
Description: 
 libghc6-missingpy-dev - Python interface and utility library for Haskell
Closes: 332893
Changes: 
 missingpy (0.8.0) unstable; urgency=low
 .
   * Updated control file to have a more liberal dependency on MissingH.
     Closes: #332893.
   * Sync Debian package version with version listed in MissingPy.cabal.
Files: 
 f70d2e7af8eb4c014ee5e379a2d4fe51 688 devel optional missingpy_0.8.0.dsc
 8e47b7a60259240111251b3646fa4135 187454 devel optional missingpy_0.8.0.tar.gz
 406d495aa571882ea13a7daec292990e 97438 devel optional 
libghc6-missingpy-dev_0.8.0_i386.deb

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

iD8DBQFDSRsW7B2mSKdID5ERAoQuAJ0YRI77d+xepbrHSm69tcx8JPQlkACeL5yc
j/zLzXmdOrAbIOmoB+sYyWk=
=75rs
-----END PGP SIGNATURE-----


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to