Your message dated Fri, 17 Jun 2005 20:18:18 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#312953: fixed in renderext 1:0.9-1
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; 11 Jun 2005 01:06:24 +0000
>From [EMAIL PROTECTED] Fri Jun 10 18:06:24 2005
Return-path: <[EMAIL PROTECTED]>
Received: from cpe-65-26-182-85.indy.res.rr.com (sisyphus.deadbeast.net) 
[65.26.182.85] 
        by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
        id 1DguS8-00037M-00; Fri, 10 Jun 2005 18:06:24 -0700
Received: by sisyphus.deadbeast.net (Postfix, from userid 1000)
        id 8C73D68C03D; Fri, 10 Jun 2005 20:06:23 -0500 (EST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Branden Robinson <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: render: new upstream version (0.9) released 2005-06-10
X-Mailer: reportbug 3.12
Date: Fri, 10 Jun 2005 20:06:23 -0500
Message-Id: <[EMAIL PROTECTED]>
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-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE 
        autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level: 

Package: render
Severity: wishlist

As of a few minutes ago, Keith Packard released Render 0.9.

URL: http://xlibs.freedesktop.org/release/renderext-0.9.tar.gz

Since this is needed to build xorg-x11 from Subversion without a nasty
kludge, I plan to handle this within the next few days (maybe even
tonight).

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: powerpc (ppc)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.9-powerpc-smp
Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)

---------------------------------------
Received: (at 312953-close) by bugs.debian.org; 18 Jun 2005 00:23:29 +0000
>From [EMAIL PROTECTED] Fri Jun 17 17:23:29 2005
Return-path: <[EMAIL PROTECTED]>
Received: from newraff.debian.org [208.185.25.31] (mail)
        by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
        id 1DjR7R-0004lA-00; Fri, 17 Jun 2005 17:23:29 -0700
Received: from joerg by newraff.debian.org with local (Exim 3.35 1 (Debian))
        id 1DjR2Q-00060F-00; Fri, 17 Jun 2005 20:18:18 -0400
From: Branden Robinson <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: lisa $Revision: 1.30 $
Subject: Bug#312953: fixed in renderext 1:0.9-1
Message-Id: <[EMAIL PROTECTED]>
Sender: Joerg Jaspert <[EMAIL PROTECTED]>
Date: Fri, 17 Jun 2005 20:18:18 -0400
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-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
X-Spam-Level: 

Source: renderext
Source-Version: 1:0.9-1

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

render-dev_0.9-1_all.deb
  to pool/main/r/renderext/render-dev_0.9-1_all.deb
renderext_0.9-1.diff.gz
  to pool/main/r/renderext/renderext_0.9-1.diff.gz
renderext_0.9-1.dsc
  to pool/main/r/renderext/renderext_0.9-1.dsc
renderext_0.9.orig.tar.gz
  to pool/main/r/renderext/renderext_0.9.orig.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.
Branden Robinson <[EMAIL PROTECTED]> (supplier of updated renderext 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: Thu, 16 Jun 2005 12:09:26 -0500
Source: renderext
Binary: render-dev
Architecture: source all
Version: 1:0.9-1
Distribution: unstable
Urgency: low
Maintainer: Debian X Strike Force <debian-x@lists.debian.org>
Changed-By: Branden Robinson <[EMAIL PROTECTED]>
Description: 
 render-dev - X Rendering Extension header files and documentation
Closes: 312953
Changes: 
 renderext (1:0.9-1) unstable; urgency=low
 .
   * Merge new upstream 0.9 release.  (Closes: #312953)
     + The following symbols are new:
       - constants: sz_xSpanFix, sz_xTrap, sz_xRenderAddTrapsReq
       - structures: xSpanFix, xTrap, xRenderAddTrapsReq
     If you #include <X11/extensions/renderproto.h> and use any of the above
     symbols, you will need to declare a versioned dependency and/or
     build-dependency on render-dev (>= 1:0.9-1).
 .
   * Rename source package to "renderext" to follow upstream rename.
Files: 
 34f954d68d7deeef8298d2376784e5a0 638 libdevel optional renderext_0.9-1.dsc
 ddb63b719699b5c093df5235f5ef4341 63716 libdevel optional 
renderext_0.9.orig.tar.gz
 69ce5a81533341f512585ae9e9ff665f 3601 libdevel optional renderext_0.9-1.diff.gz
 9116630f293f6974b2b9581eb48de101 26148 libdevel optional 
render-dev_0.9-1_all.deb

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

iEYEARECAAYFAkKxwSoACgkQ6kxmHytGonzAAQCeI/kPndapm8GYF27CsvCgiF2z
nl4AoJSQfd9HkEq7l3P5mPR/YtIpiroS
=AT2T
-----END PGP SIGNATURE-----


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

Reply via email to