Your message dated Sun, 6 Nov 2005 13:21:59 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Bug#335402: penguin-command: shouldn't this bug be closed?
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; 23 Oct 2005 19:06:25 +0000
>From [EMAIL PROTECTED] Sun Oct 23 12:06:25 2005
Return-path: <[EMAIL PROTECTED]>
Received: from dslb-082-083-132-160.pools.arcor-ip.net (gleep.earth.sol)
[82.83.132.160]
by spohr.debian.org with esmtp (Exim 3.36 1 (Debian))
id 1ETlAn-0001e5-00; Sun, 23 Oct 2005 12:06:25 -0700
Received: from cts by gleep.earth.sol with local (Exim 4.50)
id 1ETlAn-00048n-0F
for [EMAIL PROTECTED]; Sun, 23 Oct 2005 21:06:25 +0200
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: "Christian T. Steigies" <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: penguin-command: FTBFS: missing build-depends on libsdl-image1.2-dev
X-Mailer: reportbug 3.8
Date: Sun, 23 Oct 2005 21:06:24 +0200
Message-Id: <[EMAIL PROTECTED]>
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: penguin-command
Version: 1.6.9-1
Severity: serious
Justification: FTBFS
Hi Karl,
it seems you forgot a build-depends on libsdl-image1.2-dev, the package has
failed to build on six arches so far.
Automatic build of penguin-command_1.6.9-1 on garkin by sbuild/m68k 69
** Using build dependencies supplied by package:
Build-Depends: debhelper, libpng12-dev, libsdl1.2-dev (>= 1.2.2-3.1),
libjpeg62-dev, libsdl-mixer1.2-dev (>= 1.2.0-1.1), zlib1g-dev, automake,
autoconf
[...]
checking for main in -lSDL_mixer... yes
checking for main in -lSDL_image... no
configure: error: Your system is missing libSDL_image!
make: *** [build-stamp] Error 1
http://buildd.debian.org/build.php?&pkg=penguin-command
Christian
---------------------------------------
Received: (at 335402-done) by bugs.debian.org; 6 Nov 2005 12:22:33 +0000
>From [EMAIL PROTECTED] Sun Nov 06 04:22:33 2005
Return-path: <[EMAIL PROTECTED]>
Received: from imap.gmx.net (mail.gmx.net) [213.165.64.20]
by spohr.debian.org with smtp (Exim 3.36 1 (Debian))
id 1EYjXd-0004Lq-00; Sun, 06 Nov 2005 04:22:33 -0800
Received: (qmail invoked by alias); 06 Nov 2005 12:22:02 -0000
Received: from port-212-202-41-8.dynamic.qsc.de (EHLO [10.0.0.43])
[212.202.41.8]
by mail.gmx.net (mp008) with SMTP; 06 Nov 2005 13:22:02 +0100
X-Authenticated: #364038
Mime-Version: 1.0 (Apple Message framework v746.2)
In-Reply-To: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <[EMAIL PROTECTED]>
Content-Transfer-Encoding: 7bit
From: Karl Bartel <[EMAIL PROTECTED]>
Subject: Re: Bug#335402: penguin-command: shouldn't this bug be closed?
Date: Sun, 6 Nov 2005 13:21:59 +0100
To: Itai Seggev <[EMAIL PROTECTED]>,
[EMAIL PROTECTED]
X-Mailer: Apple Mail (2.746.2)
X-Y-GMX-Trusted: 0
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
> shouldn't this bug be closed? It would seems that this was fixed with
> 1.6.9-2. Right now this bug is the only thing preventing 1.6.10-1
> from entering etch.
Yes, it should. I must have forgotten to close it in through the
changelog.
Thanks,
Karl
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
