Your message dated Sun, 08 Jan 2006 21:47:06 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#347038: fixed in ripperx 2.6.7-2
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:41 +0000
>From [EMAIL PROTECTED] Sun Jan 08 17:41:41 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 1Evlzc-0000rU-MQ
for [EMAIL PROTECTED]; Sun, 08 Jan 2006 17:38:42 -0800
Received: from userid 1000 by chistera.yi.org with local (Exim 4.60)
id 1Evlz6-0006tz-R7
for [EMAIL PROTECTED]; Mon, 09 Jan 2006 02:38:08 +0100
From: Adeodato =?utf-8?B?U2ltw7M=?= <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: ripperx: 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:08 +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: ripperx
Version: 2.6.7-1
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 347038-close) by bugs.debian.org; 9 Jan 2006 05:50:35 +0000
>From [EMAIL PROTECTED] Sun Jan 08 21:50:35 2006
Return-path: <[EMAIL PROTECTED]>
Received: from katie by spohr.debian.org with local (Exim 4.50)
id 1Evps2-0000c1-UV; Sun, 08 Jan 2006 21:47:06 -0800
From: tony mancill <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: $Revision: 1.65 $
Subject: Bug#347038: fixed in ripperx 2.6.7-2
Message-Id: <[EMAIL PROTECTED]>
Sender: Archive Administrator <[EMAIL PROTECTED]>
Date: Sun, 08 Jan 2006 21:47:06 -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: ripperx
Source-Version: 2.6.7-2
We believe that the bug you reported is fixed in the latest version of
ripperx, which is due to be installed in the Debian FTP archive:
ripperx_2.6.7-2.diff.gz
to pool/main/r/ripperx/ripperx_2.6.7-2.diff.gz
ripperx_2.6.7-2.dsc
to pool/main/r/ripperx/ripperx_2.6.7-2.dsc
ripperx_2.6.7-2_i386.deb
to pool/main/r/ripperx/ripperx_2.6.7-2_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.
tony mancill <[EMAIL PROTECTED]> (supplier of updated ripperx 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, 8 Jan 2006 20:07:28 -0800
Source: ripperx
Binary: ripperx
Architecture: source i386
Version: 2.6.7-2
Distribution: unstable
Urgency: low
Maintainer: tony mancill <[EMAIL PROTECTED]>
Changed-By: tony mancill <[EMAIL PROTECTED]>
Description:
ripperx - a GTK-based audio CD ripper/encoder
Closes: 347038
Changes:
ripperx (2.6.7-2) unstable; urgency=low
.
* update outdated xlibs-dev dependencies (closes: #347038)
Files:
860a2a161968f08b813623a85295a381 606 sound optional ripperx_2.6.7-2.dsc
0905926e30a54e379dd0e32930097acb 537 sound optional ripperx_2.6.7-2.diff.gz
5f5c247eda1f4fcea1a1a98c1b9fa8dd 116648 sound optional ripperx_2.6.7-2_i386.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
iD8DBQFDwfcbpdwBkPlyvgMRAj+UAJ9u1RMTFoc655UZHalOg4fUzmYLgACfbDvy
NagFXuywYsrTIzSdD24SeLI=
=uGMw
-----END PGP SIGNATURE-----
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
