Your message dated Fri, 18 Mar 2005 04:02:22 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#300161: fixed in libppd 2:0.10-3
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; 18 Mar 2005 04:21:01 +0000
>From [EMAIL PROTECTED] Thu Mar 17 20:21:01 2005
Return-path: <[EMAIL PROTECTED]>
Received: from mmjgroup.com [192.34.35.33]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1DC8yq-0000uc-00; Thu, 17 Mar 2005 20:21:00 -0800
Received: from mix.mmjgroup.com (mix.mmjgroup.com [192.34.35.16])
by mmjgroup.com (Postfix) with ESMTP id 9FF8116DCE
for <[EMAIL PROTECTED]>; Thu, 17 Mar 2005 21:20:59 -0700 (MST)
Received: by mix.mmjgroup.com (Postfix, from userid 1000)
id 956C48F333; Thu, 17 Mar 2005 21:20:59 -0700 (MST)
Date: Thu, 17 Mar 2005 21:20:59 -0700
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: libppd_2:0.10-2(hppa/unstable): FTBFS: missing build-depends
Message-ID: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.6+20040907i
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-Status: No, hits=-6.4 required=4.0 tests=BAYES_00,HAS_PACKAGE,
NO_REAL_NAME autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level:
Package: libppd
Version: 2:0.10-2
Severity: serious
There was an error while trying to autobuild your package:
> Automatic build of libppd_2:0.10-2 on sarti by sbuild/hppa 1.170.5
> Build started at 20050318-0232
[...]
> ** Using build dependencies supplied by package:
> Build-Depends: debhelper (>= 2), libtool, libglib1.2-dev
[...]
> checking for pkg-config... /usr/bin/pkg-config
> checking for glib-2.0... Package glib-2.0 was not found in the pkg-config
> search path.
> Perhaps you should add the directory containing `glib-2.0.pc'
> to the PKG_CONFIG_PATH environment variable
> No package 'glib-2.0' found
> checking for strdup... yes
[...]
> In file included from emit.c:39:
> ppd.h:41:18: glib.h: No such file or directory
A full build log can be found at:
http://buildd.debian.org/build.php?arch=hppa&pkg=libppd&ver=2:0.10-2
---------------------------------------
Received: (at 300161-close) by bugs.debian.org; 18 Mar 2005 09:08:05 +0000
>From [EMAIL PROTECTED] Fri Mar 18 01:08:04 2005
Return-path: <[EMAIL PROTECTED]>
Received: from newraff.debian.org [208.185.25.31] (mail)
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1DCDSe-0000Og-00; Fri, 18 Mar 2005 01:08:04 -0800
Received: from katie by newraff.debian.org with local (Exim 3.35 1 (Debian))
id 1DCDN8-0003kL-00; Fri, 18 Mar 2005 04:02:22 -0500
From: A Mennucc1 <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: $Revision: 1.55 $
Subject: Bug#300161: fixed in libppd 2:0.10-3
Message-Id: <[EMAIL PROTECTED]>
Sender: Archive Administrator <[EMAIL PROTECTED]>
Date: Fri, 18 Mar 2005 04:02:22 -0500
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-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
X-Spam-Level:
Source: libppd
Source-Version: 2:0.10-3
We believe that the bug you reported is fixed in the latest version of
libppd, which is due to be installed in the Debian FTP archive:
libppd-dev_0.10-3_i386.deb
to pool/main/libp/libppd/libppd-dev_0.10-3_i386.deb
libppd0_0.10-3_i386.deb
to pool/main/libp/libppd/libppd0_0.10-3_i386.deb
libppd_0.10-3.diff.gz
to pool/main/libp/libppd/libppd_0.10-3.diff.gz
libppd_0.10-3.dsc
to pool/main/libp/libppd/libppd_0.10-3.dsc
ppdfilt_0.10-3_i386.deb
to pool/main/libp/libppd/ppdfilt_0.10-3_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.
A Mennucc1 <[EMAIL PROTECTED]> (supplier of updated libppd 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, 18 Mar 2005 09:52:03 +0100
Source: libppd
Binary: libppd-dev ppdfilt libppd0
Architecture: source i386
Version: 2:0.10-3
Distribution: unstable
Urgency: medium
Maintainer: A Mennucc1 <[EMAIL PROTECTED]>
Changed-By: A Mennucc1 <[EMAIL PROTECTED]>
Description:
libppd-dev - postscript PPD file library, development kit
libppd0 - postscript PPD file library
ppdfilt - filter that inserts printer specific commands into print jobs
Closes: 300161
Changes:
libppd (2:0.10-3) unstable; urgency=medium
.
* wrong configure : this version should be compiled with glib 1
(there is no point in using glib2, as long as 'gpr' uses gtk1.2 )
(Closes: #300161)
Files:
6f86cde91fe1509178e12a7dccd4e3fc 602 libs optional libppd_0.10-3.dsc
18bd598178d964e36c69577075736822 550323 libs optional libppd_0.10-3.diff.gz
e0a531949caebbe8e365cbfde974036d 30464 devel optional
libppd-dev_0.10-3_i386.deb
ed1821aae4b735d9a084ac7ec825e616 13734 utils optional ppdfilt_0.10-3_i386.deb
249d060141319941111671c0ac1b75dd 19654 libs optional libppd0_0.10-3_i386.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
iD8DBQFCOpfi9B/tjjP8QKQRAoCSAJ9bu5gaZbKgEQI+tvDsImKMPhY+MwCgg7Zm
acbUDUZwJ27O2wEzu+9boxo=
=TkIb
-----END PGP SIGNATURE-----
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
