Your message dated Sat, 21 Jan 2006 21:02:40 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Fixed in xmem 1.20-21
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:39:33 +0000
>From [EMAIL PROTECTED] Sun Jan 08 17:39:33 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 1Evm0S-0001P2-MF
for [EMAIL PROTECTED]; Sun, 08 Jan 2006 17:39:33 -0800
Received: from userid 1000 by chistera.yi.org with local (Exim 4.60)
id 1Evlzw-00074S-ES
for [EMAIL PROTECTED]; Mon, 09 Jan 2006 02:39:00 +0100
From: Adeodato =?utf-8?B?U2ltw7M=?= <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: xmem: 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:39:00 +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: xmem
Version: 1.20-19
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 346825-done) by bugs.debian.org; 21 Jan 2006 20:02:56 +0000
>From [EMAIL PROTECTED] Sat Jan 21 12:02:56 2006
Return-path: <[EMAIL PROTECTED]>
Received: from mail.irb.hr ([161.53.22.8] ident=UNKNOWN)
by spohr.debian.org with esmtp (Exim 4.50)
id 1F0Owq-0002yg-AS
for [EMAIL PROTECTED]; Sat, 21 Jan 2006 12:02:56 -0800
Received: from diziet.irb.hr (diziet.irb.hr [161.53.22.31])
by mail.irb.hr (8.13.4/8.13.4/Debian-3) with ESMTP id k0LK2TK1029137
for <[EMAIL PROTECTED]>; Sat, 21 Jan 2006 21:02:29 +0100
Received: from diziet.irb.hr (localhost [127.0.0.1])
by diziet.irb.hr (8.13.5/8.13.5/Debian-3) with ESMTP id k0LK2eRV019650
for <[EMAIL PROTECTED]>; Sat, 21 Jan 2006 21:02:40 +0100
Received: (from [EMAIL PROTECTED])
by diziet.irb.hr (8.13.5/8.13.5/Submit) id k0LK2eRg019648;
Sat, 21 Jan 2006 21:02:40 +0100
From: Matej Vela <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Fixed in xmem 1.20-21
Date: Sat, 21 Jan 2006 21:02:40 +0100
Message-ID: <[EMAIL PROTECTED]>
User-Agent: Gnus/5.110004 (No Gnus v0.4) Emacs/21.4 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Scanned-By: MIMEDefang 2.51 on 161.53.22.8
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=-3.0 required=4.0 tests=BAYES_00 autolearn=no
version=2.60-bugs.debian.org_2005_01_02
Source: xmem
Source-Version: 1.20-21
Now that xmem is orphaned, NMU-fixed bugs can be closed.
The original .changes file follows.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.7
Date: Thu, 19 Jan 2006 17:05:41 +0100
Source: xmem
Binary: xmem
Architecture: source powerpc
Version: 1.20-21
Distribution: unstable
Urgency: low
Maintainer: Marc 'HE' Brockschmidt <[EMAIL PROTECTED]>
Changed-By: Marc 'HE' Brockschmidt <[EMAIL PROTECTED]>
Description:
xmem - Visual indicator of amount of memory/swap usage
Closes: 346825
Changes:
xmem (1.20-21) unstable; urgency=low
.
* QA upload.
* debian/control: Add build-dep on libxaw8-dev to fix FTBFS. (Closes:
#346825)
.
* Housekeeping:
+ Moved binary to /usr/bin/xmem
+ debian/menu: Quoted all strings
+ Updated build stuff to debhelper 5 (rewrote debian/rules)
+ Updated Standards-Version to 3.6.2
Files:
0a1db9fb990f2a84f2dfe2b52e0706b9 544 x11 optional xmem_1.20-21.dsc
b6e377f6b06a2b444a74a0146bae8c38 13383 x11 optional xmem_1.20-21.tar.gz
171062bf44ba12c359986b88f3f70a3c 21276 x11 optional xmem_1.20-21_powerpc.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
iD8DBQFDz76YmO5zOp3h7rERAg+7AJ9pOoZ8+9xZXs1LFY0HkNTsHKU0egCggKy3
BtZppOHCOcnOlkV8hbpxTR4=
=44L+
-----END PGP SIGNATURE-----
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
