Your message dated Thu, 12 Jan 2006 17:02:19 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#347057: fixed in sapphire 0.15.8-7 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 maintonly) by bugs.debian.org; 9 Jan 2006 01:41:42 +0000 >From [EMAIL PROTECTED] Sun Jan 08 17:41:42 2006 Return-path: <[EMAIL PROTECTED]> Received: from 84-120-75-62.onocable.ono.com ([84.120.75.62] helo=chistera.yi.org) by spohr.debian.org with esmtp (Exim 4.50) id 1Evlzm-0000re-Fg for [EMAIL PROTECTED]; Sun, 08 Jan 2006 17:38:51 -0800 Received: from userid 1000 by chistera.yi.org with local (Exim 4.60) id 1Evlz7-0006uN-9V for [EMAIL PROTECTED]; Mon, 09 Jan 2006 02:38:09 +0100 From: Adeodato =?utf-8?B?U2ltw7M=?= <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: sapphire: FTBFS: build-depends on removed xlibs-dev Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit Message-Id: <[EMAIL PROTECTED]> Date: Mon, 09 Jan 2006 02:38:09 +0100 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 Package: sapphire Version: 0.15.8-6 Severity: serious Hello, This is a serious bug filed against your package because it build-depends on xlibs-dev, which as announced in [1] a while ago, is no longer available in sid. This makes your package fail to build from source. [1] http://lists.debian.org/debian-devel-announce/2005/11/msg00022.html To fix this bug, you need to update your build-dependencies and substitute xlibs-dev for the list of individual X development libraries that your package needs to be built. You can find detailed information about how to do that in the DependsXlibsDev wiki page [2]. [2] http://wiki.debian.org/DependsXlibsDev As indicated by the Release Team [3], the full transition from XFree86 to Xorg is a release blocker for Etch, which means that Etch will not be released until this bug is fixed (or your package removed from testing). So, please, try to fix in a timely manner. [3] http://lists.debian.org/debian-devel-announce/2005/10/msg00004.html The number of affected packages by the xlibs-dev transition is huge, so if you feel like helping with patches or uploads, feel free to follow the instructions contained in the wiki page above. A list of affected packages can be found here [4]. [4] http://people.debian.org/~adeodato/release-usertag/transition-xlibs-dev Finally, if there's a strong reason for which your package should not be NMUed, please note so in this bug report. Prospective NMUers will read your reasoning, and will decide if it's strong enough to delay their upload. Thanks for your collaboration! -- Adeodato Simó dato at net.com.org.es Debian Developer adeodato at debian.org --------------------------------------- Received: (at 347057-close) by bugs.debian.org; 13 Jan 2006 01:11:06 +0000 >From [EMAIL PROTECTED] Thu Jan 12 17:11:06 2006 Return-path: <[EMAIL PROTECTED]> Received: from katie by spohr.debian.org with local (Exim 4.50) id 1ExDKd-0002VF-Kg; Thu, 12 Jan 2006 17:02:19 -0800 From: Chris Boyle <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] X-Katie: $Revision: 1.65 $ Subject: Bug#347057: fixed in sapphire 0.15.8-7 Message-Id: <[EMAIL PROTECTED]> Sender: Archive Administrator <[EMAIL PROTECTED]> Date: Thu, 12 Jan 2006 17:02:19 -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: sapphire Source-Version: 0.15.8-7 We believe that the bug you reported is fixed in the latest version of sapphire, which is due to be installed in the Debian FTP archive: sapphire_0.15.8-7.diff.gz to pool/main/s/sapphire/sapphire_0.15.8-7.diff.gz sapphire_0.15.8-7.dsc to pool/main/s/sapphire/sapphire_0.15.8-7.dsc sapphire_0.15.8-7_i386.deb to pool/main/s/sapphire/sapphire_0.15.8-7_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. Chris Boyle <[EMAIL PROTECTED]> (supplier of updated sapphire 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: Fri, 13 Jan 2006 00:48:53 +0000 Source: sapphire Binary: sapphire Architecture: source i386 Version: 0.15.8-7 Distribution: unstable Urgency: low Maintainer: Chris Boyle <[EMAIL PROTECTED]> Changed-By: Chris Boyle <[EMAIL PROTECTED]> Description: sapphire - A minimal but configurable X11R6 window manager Closes: 347057 Changes: sapphire (0.15.8-7) unstable; urgency=low . * Update Build-Depends for Xorg. (closes: #347057) Files: d19ce40171e65f4ffedea5c9a38549f7 593 x11 optional sapphire_0.15.8-7.dsc 2b19bc5a39a8eaf1888e1d6a872a7e9c 27926 x11 optional sapphire_0.15.8-7.diff.gz b9908026c67e9b821df3e8c2282a0802 55478 x11 optional sapphire_0.15.8-7_i386.deb -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFDxvlyRi6ArLfYbg8RAsp0AKC+0cq59ybfHuekOdYLjXyB8EEzkgCghAl8 tz9wX7iaBZXT1oSQy0fX+0U= =3Rsk -----END PGP SIGNATURE----- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]