Your message dated Sun, 04 Dec 2005 10:32:10 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#341817: fixed in libavg 0.2.0-2
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; 3 Dec 2005 11:38:03 +0000
>From [EMAIL PROTECTED] Sat Dec 03 03:38:03 2005
Return-path: <[EMAIL PROTECTED]>
Received: from dsl093-039-086.pdx1.dsl.speakeasy.net ([66.93.39.86] 
helo=tennyson.dodds.net)
        by spohr.debian.org with esmtp (Exim 4.50)
        id 1EiViM-0005tI-VQ
        for [EMAIL PROTECTED]; Sat, 03 Dec 2005 03:38:03 -0800
Received: by tennyson.dodds.net (Postfix, from userid 1000)
        id 9FB9B7002; Sat,  3 Dec 2005 03:38:01 -0800 (PST)
Date: Sat, 3 Dec 2005 03:38:01 -0800
From: Steve Langasek <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: libavg: obsolete build-dependency on libmagick++6-dev
Message-ID: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
        protocol="application/pgp-signature"; boundary="FFoLq8A0u+X9iRU8"
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


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

Package: libavg
Version: 0.2.0-1
Severity: serious

Hi Torsten,

It appears that libavg has an unsatisfiable build-dependency on
libmagick++6-dev.  The current version of this package is libmagick++9-dev.
Unlike the libavcodec2-dev build-dep, I'm pretty sure that there's no
public third-party repo providing libmagick++6 for etch/sid, so I think this
bug needs to be treated as release-critical.

Also, the package needs a rebuild for the new version of boost.

Cheers,
--=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/

--FFoLq8A0u+X9iRU8
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)

iD8DBQFDkYOYKN6ufymYLloRAgjVAKCO0RwEVb0sZ0htJI1STuyBMAguIwCgq4Sp
EhnNehcUR85l/llAEXh3EuI=
=Yjyt
-----END PGP SIGNATURE-----

--FFoLq8A0u+X9iRU8--

---------------------------------------
Received: (at 341817-close) by bugs.debian.org; 4 Dec 2005 18:36:49 +0000
>From [EMAIL PROTECTED] Sun Dec 04 10:36:49 2005
Return-path: <[EMAIL PROTECTED]>
Received: from katie by spohr.debian.org with local (Exim 4.50)
        id 1Eiyeg-0006ao-E9; Sun, 04 Dec 2005 10:32:10 -0800
From: Torsten Werner <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: $Revision: 1.60 $
Subject: Bug#341817: fixed in libavg 0.2.0-2
Message-Id: <[EMAIL PROTECTED]>
Sender: Archive Administrator <[EMAIL PROTECTED]>
Date: Sun, 04 Dec 2005 10:32:10 -0800
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: libavg
Source-Version: 0.2.0-2

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

libavg_0.2.0-2.diff.gz
  to pool/contrib/liba/libavg/libavg_0.2.0-2.diff.gz
libavg_0.2.0-2.dsc
  to pool/contrib/liba/libavg/libavg_0.2.0-2.dsc
python-libavg_0.2.0-2_i386.deb
  to pool/contrib/liba/libavg/python-libavg_0.2.0-2_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 [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Torsten Werner <[EMAIL PROTECTED]> (supplier of updated libavg 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,  4 Dec 2005 17:42:35 +0100
Source: libavg
Binary: python-libavg
Architecture: source i386
Version: 0.2.0-2
Distribution: unstable
Urgency: low
Maintainer: Torsten Werner <[EMAIL PROTECTED]>
Changed-By: Torsten Werner <[EMAIL PROTECTED]>
Description: 
 python-libavg - libavg Ain't Vector Graphics
Closes: 332522 341817
Changes: 
 libavg (0.2.0-2) unstable; urgency=low
 .
   * changed Build-Depends: libmagick++9-dev | libmagick++6-dev,
     closes: #341817
   * added hint to Christian Marillat's archive to README.Debian,
     closes: #332522
   * changed Build-Depends: libavcodeccvs-dev | libavcodec2-dev
   * some small lintian cleanups
Files: 
 2d5aaef7e613bea628741e4fe407357c 731 contrib/python optional libavg_0.2.0-2.dsc
 d7b768cdce34a2fd6d5f6b8d9bb1703e 1277 contrib/python optional 
libavg_0.2.0-2.diff.gz
 3fdd70524b8a867bef4cfb59068bc7a2 327662 contrib/python optional 
python-libavg_0.2.0-2_i386.deb

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

iD8DBQFDkzO/fY3dicTPjsMRApGHAJ9cyHj9Mt7Ovo6Qci3rtYEAN+o5TgCfel+/
lwgu5FOPABQIDbBBVHwvnDM=
=L6cW
-----END PGP SIGNATURE-----


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

Reply via email to