Your message dated Sun, 06 Nov 2005 08:45:15 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#283742: fixed in sdlgfx 2.0.13-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; 1 Dec 2004 00:03:53 +0000
>From [EMAIL PROTECTED] Tue Nov 30 16:03:53 2004
Return-path: <[EMAIL PROTECTED]>
Received: from mx04.stofanet.dk [212.10.10.14] 
        by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
        id 1CZHyL-0006eL-00; Tue, 30 Nov 2004 16:03:53 -0800
Received: from 3e6b6468.rev.stofanet.dk ([62.107.100.104] 
helo=dell.halfdans.lokalnet)
        by mx04.stofanet.dk (envelope-from
        <[EMAIL PROTECTED]>)
        with esmtp id 1CZHyI-0002MC-2M; Wed, 01 Dec 2004 01:03:50 +0100
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Rasmus Toftdahl Olesen <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: sdlgfx: New upstream version available
Bcc: Rasmus Toftdahl Olesen <[EMAIL PROTECTED]>
X-Mailer: reportbug 3.2
Date: Wed, 01 Dec 2004 01:03:18 +0100
Message-Id: <[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25 
        (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_2004_03_25
X-Spam-Level: 

Package: sdlgfx
Severity: normal

New upstream version available, version 2.0.12, in particular version 2.0.10
included an interger-overflow fix for drawing filled polygons.

I hit this patch when drawing a "larger than usual" polygon, about the size of
a 640x480 screen. No reason to bother about how to expose the patch, i copied
thje debian dir of 2.0.9-4 (debian source) to the 2.0.12 upstream dir and
added a new debian/changelog line, and everything builded cleanly.

-- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (990, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.9
Locale: LANG=da_DK, LC_CTYPE=da_DK (charmap=ISO-8859-1)

---------------------------------------
Received: (at 283742-close) by bugs.debian.org; 6 Nov 2005 16:46:35 +0000
>From [EMAIL PROTECTED] Sun Nov 06 08:46:35 2005
Return-path: <[EMAIL PROTECTED]>
Received: from joerg by spohr.debian.org with local (Exim 3.36 1 (Debian))
        id 1EYndr-0001IZ-00; Sun, 06 Nov 2005 08:45:15 -0800
From: Sam Hocevar (Debian packages) <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: lisa $Revision: 1.30 $
Subject: Bug#283742: fixed in sdlgfx 2.0.13-1
Message-Id: <[EMAIL PROTECTED]>
Sender: Joerg Jaspert <[EMAIL PROTECTED]>
Date: Sun, 06 Nov 2005 08:45:15 -0800
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: sdlgfx
Source-Version: 2.0.13-1

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

libsdl-gfx1.2-4_2.0.13-1_i386.deb
  to pool/main/s/sdlgfx/libsdl-gfx1.2-4_2.0.13-1_i386.deb
libsdl-gfx1.2-dev_2.0.13-1_i386.deb
  to pool/main/s/sdlgfx/libsdl-gfx1.2-dev_2.0.13-1_i386.deb
sdlgfx_2.0.13-1.diff.gz
  to pool/main/s/sdlgfx/sdlgfx_2.0.13-1.diff.gz
sdlgfx_2.0.13-1.dsc
  to pool/main/s/sdlgfx/sdlgfx_2.0.13-1.dsc
sdlgfx_2.0.13.orig.tar.gz
  to pool/main/s/sdlgfx/sdlgfx_2.0.13.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.
Sam Hocevar (Debian packages) <[EMAIL PROTECTED]> (supplier of updated sdlgfx 
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, 16 Oct 2005 18:17:55 +0200
Source: sdlgfx
Binary: libsdl-gfx1.2-4 libsdl-gfx1.2-dev
Architecture: source i386
Version: 2.0.13-1
Distribution: unstable
Urgency: low
Maintainer: Sam Hocevar (Debian packages) <[EMAIL PROTECTED]>
Changed-By: Sam Hocevar (Debian packages) <[EMAIL PROTECTED]>
Description: 
 libsdl-gfx1.2-4 - drawing and graphical effects extension for SDL
 libsdl-gfx1.2-dev - development files for SDL_gfx
Closes: 283742
Changes: 
 sdlgfx (2.0.13-1) unstable; urgency=low
 .
   * New upstream release (Closes: #283742).
   * Re-ran the autogen.sh process.
   * debian/control:
     + Set policy to 3.6.2.1.
     + Changed library package name to reflect soname change.
Files: 
 b2f7d524bcac8abac4d910a2c521b96b 632 libs optional sdlgfx_2.0.13-1.dsc
 b1ce778232db0b1979695f0a5a945a13 598297 libs optional sdlgfx_2.0.13.orig.tar.gz
 d7bd48132f9ce8c66126576b295fbd5b 276345 libs optional sdlgfx_2.0.13-1.diff.gz
 e3a2732c84baf1ebe3580e0e43aea5b6 39002 libs optional 
libsdl-gfx1.2-4_2.0.13-1_i386.deb
 a350fe75910d4da93979ea16abf8238a 398142 libdevel optional 
libsdl-gfx1.2-dev_2.0.13-1_i386.deb

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

iD8DBQFDUn7KfPP1rylJn2ERAn/zAJwLxXO5++N+EikbffWSKn7qyUk+KwCfSapL
TD09G+/FGAHrND656sSDs3E=
=zF6Z
-----END PGP SIGNATURE-----


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

Reply via email to