Your message dated Thu, 12 Jan 2006 08:02:10 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#346950: fixed in wmsensors 1.0.4-5 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:40:49 +0000 >From [EMAIL PROTECTED] Sun Jan 08 17:40:49 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 1Evm0D-0001Jr-Uo for [EMAIL PROTECTED]; Sun, 08 Jan 2006 17:39:18 -0800 Received: from userid 1000 by chistera.yi.org with local (Exim 4.60) id 1Evlzf-000705-4I for [EMAIL PROTECTED]; Mon, 09 Jan 2006 02:38:43 +0100 From: Adeodato =?utf-8?B?U2ltw7M=?= <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: wmsensors: 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:43 +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: wmsensors Version: 1.0.4-4 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 346950-close) by bugs.debian.org; 12 Jan 2006 16:10:33 +0000 >From [EMAIL PROTECTED] Thu Jan 12 08:10:33 2006 Return-path: <[EMAIL PROTECTED]> Received: from katie by spohr.debian.org with local (Exim 4.50) id 1Ex4tu-0001pM-1C; Thu, 12 Jan 2006 08:02:10 -0800 From: Luk Claes <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] X-Katie: $Revision: 1.65 $ Subject: Bug#346950: fixed in wmsensors 1.0.4-5 Message-Id: <[EMAIL PROTECTED]> Sender: Archive Administrator <[EMAIL PROTECTED]> Date: Thu, 12 Jan 2006 08:02: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: wmsensors Source-Version: 1.0.4-5 We believe that the bug you reported is fixed in the latest version of wmsensors, which is due to be installed in the Debian FTP archive: wmsensors_1.0.4-5.diff.gz to pool/main/w/wmsensors/wmsensors_1.0.4-5.diff.gz wmsensors_1.0.4-5.dsc to pool/main/w/wmsensors/wmsensors_1.0.4-5.dsc wmsensors_1.0.4-5_i386.deb to pool/main/w/wmsensors/wmsensors_1.0.4-5_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. Luk Claes <[EMAIL PROTECTED]> (supplier of updated wmsensors 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, 12 Jan 2006 16:01:41 +0100 Source: wmsensors Binary: wmsensors Architecture: source i386 Version: 1.0.4-5 Distribution: unstable Urgency: high Maintainer: Debian QA Group <[EMAIL PROTECTED]> Changed-By: Luk Claes <[EMAIL PROTECTED]> Description: wmsensors - WindowMaker dock applet for lmsensors Closes: 346950 Changes: wmsensors (1.0.4-5) unstable; urgency=high . * Debian QA upload. * Split xlibs-dev build-dep (Closes: #346950). Files: cf3d0f9cbd941bb1bdbed1f96150bc60 653 x11 optional wmsensors_1.0.4-5.dsc e83912a81286d1c34655975120e23111 12808 x11 optional wmsensors_1.0.4-5.diff.gz 0eb046e49e767feda5302e608318474d 20580 x11 optional wmsensors_1.0.4-5_i386.deb -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFDxnZn5UTeB5t8Mo0RAtMIAJwLqTIRvL6EwwAtkuo5nJQBLrCmMQCcCmc2 b7cZd9toKIWo4dZLXLQpOLY= =Hpez -----END PGP SIGNATURE----- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]