Your message dated Fri, 09 Sep 2005 19:17:10 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#327352: fixed in pike7.4 7.4.325-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 submit) by bugs.debian.org; 9 Sep 2005 12:20:32 +0000
>From [EMAIL PROTECTED] Fri Sep 09 05:20:32 2005
Return-path: <[EMAIL PROTECTED]>
Received: from dsl093-039-086.pdx1.dsl.speakeasy.net (tennyson.dodds.net) 
[66.93.39.86] 
        by spohr.debian.org with esmtp (Exim 3.36 1 (Debian))
        id 1EDhrs-00045m-00; Fri, 09 Sep 2005 05:20:32 -0700
Received: by tennyson.dodds.net (Postfix, from userid 1003)
        id 7798B7046; Fri,  9 Sep 2005 05:20:31 -0700 (PDT)
Date: Fri, 9 Sep 2005 05:20:31 -0700
From: Steve Langasek <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: pike7.4_7.4.325-1: FTBFS: "USE_SSL" define conflicts with libpq-dev
Message-ID: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
        protocol="application/pgp-signature"; boundary="jRHKVT23PllUwdXP"
Content-Disposition: inline
User-Agent: Mutt/1.5.9i
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


--jRHKVT23PllUwdXP
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Package: pike7.4
Version: 7.4.325-1
Severity: serious
Justification: FTBFS

Hi Marek,

The latest version of pike7.4 is failing to build now on arm (and,
presumably, other architectures) because it appears to define USE_SSL
before including postgresql/libpq-fe.h, and the current version of
libpq-fe.h includes the following code:

/* SSL type is needed here only to declare PQgetssl() */
#ifdef USE_SSL
#include <openssl/ssl.h>
#endif

This fails since libpq-dev does not depend on libssl-dev.  You may want
to unset USE_SSL when including libpq-fe.h, or else make pike7.4
build-depend on libssl-dev.

Cheers,
--=20
Steve Langasek                   Give me a lever long enough and a Free OS
Debian Developer                   to set it on, and I can move the world.
[EMAIL PROTECTED]                                   http://www.debian.org/

--jRHKVT23PllUwdXP
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFDIX4PKN6ufymYLloRAgqHAJwLGKLzLqy74Rkux834y4x5L0MrugCdHqIr
pz3SnVXdnoFykn4cClm/Yis=
=GwAq
-----END PGP SIGNATURE-----

--jRHKVT23PllUwdXP--

---------------------------------------
Received: (at 327352-close) by bugs.debian.org; 10 Sep 2005 02:18:29 +0000
>From [EMAIL PROTECTED] Fri Sep 09 19:18:29 2005
Return-path: <[EMAIL PROTECTED]>
Received: from katie by spohr.debian.org with local (Exim 3.36 1 (Debian))
        id 1EDuvW-00083l-00; Fri, 09 Sep 2005 19:17:10 -0700
From: Marek Habersack <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: $Revision: 1.56 $
Subject: Bug#327352: fixed in pike7.4 7.4.325-2
Message-Id: <[EMAIL PROTECTED]>
Sender: Archive Administrator <[EMAIL PROTECTED]>
Date: Fri, 09 Sep 2005 19:17:10 -0700
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

Source: pike7.4
Source-Version: 7.4.325-2

We believe that the bug you reported is fixed in the latest version of
pike7.4, which is due to be installed in the Debian FTP archive:

pike7.4-core_7.4.325-2_i386.deb
  to pool/main/p/pike7.4/pike7.4-core_7.4.325-2_i386.deb
pike7.4-dev_7.4.325-2_all.deb
  to pool/main/p/pike7.4/pike7.4-dev_7.4.325-2_all.deb
pike7.4-doc_7.4.325-2_all.deb
  to pool/main/p/pike7.4/pike7.4-doc_7.4.325-2_all.deb
pike7.4-gdbm_7.4.325-2_i386.deb
  to pool/main/p/pike7.4/pike7.4-gdbm_7.4.325-2_i386.deb
pike7.4-gl_7.4.325-2_i386.deb
  to pool/main/p/pike7.4/pike7.4-gl_7.4.325-2_i386.deb
pike7.4-gtk_7.4.325-2_i386.deb
  to pool/main/p/pike7.4/pike7.4-gtk_7.4.325-2_i386.deb
pike7.4-image_7.4.325-2_i386.deb
  to pool/main/p/pike7.4/pike7.4-image_7.4.325-2_i386.deb
pike7.4-manual_7.4.325-2_all.deb
  to pool/main/p/pike7.4/pike7.4-manual_7.4.325-2_all.deb
pike7.4-meta_7.4.325-2_all.deb
  to pool/main/p/pike7.4/pike7.4-meta_7.4.325-2_all.deb
pike7.4-mysql_7.4.325-2_i386.deb
  to pool/main/p/pike7.4/pike7.4-mysql_7.4.325-2_i386.deb
pike7.4-odbc_7.4.325-2_i386.deb
  to pool/main/p/pike7.4/pike7.4-odbc_7.4.325-2_i386.deb
pike7.4-perl_7.4.325-2_i386.deb
  to pool/main/p/pike7.4/pike7.4-perl_7.4.325-2_i386.deb
pike7.4-pg_7.4.325-2_i386.deb
  to pool/main/p/pike7.4/pike7.4-pg_7.4.325-2_i386.deb
pike7.4-reference_7.4.325-2_all.deb
  to pool/main/p/pike7.4/pike7.4-reference_7.4.325-2_all.deb
pike7.4-sane_7.4.325-2_i386.deb
  to pool/main/p/pike7.4/pike7.4-sane_7.4.325-2_i386.deb
pike7.4-sdl_7.4.325-2_i386.deb
  to pool/main/p/pike7.4/pike7.4-sdl_7.4.325-2_i386.deb
pike7.4-svg_7.4.325-2_i386.deb
  to pool/main/p/pike7.4/pike7.4-svg_7.4.325-2_i386.deb
pike7.4_7.4.325-2.diff.gz
  to pool/main/p/pike7.4/pike7.4_7.4.325-2.diff.gz
pike7.4_7.4.325-2.dsc
  to pool/main/p/pike7.4/pike7.4_7.4.325-2.dsc
pike7.4_7.4.325-2_all.deb
  to pool/main/p/pike7.4/pike7.4_7.4.325-2_all.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.
Marek Habersack <[EMAIL PROTECTED]> (supplier of updated pike7.4 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,  9 Sep 2005 18:37:21 +0200
Source: pike7.4
Binary: pike7.4-manual pike7.4-dev pike7.4-perl pike7.4-odbc pike7.4-gdbm 
pike7.4-core pike7.4-sane pike7.4-gl pike7.4-sdl pike7.4-pg pike7.4-svg pike7.4 
pike7.4-image pike7.4-meta pike7.4-reference pike7.4-doc pike7.4-mysql 
pike7.4-gtk
Architecture: source i386 all
Version: 7.4.325-2
Distribution: unstable
Urgency: low
Maintainer: Marek Habersack <[EMAIL PROTECTED]>
Changed-By: Marek Habersack <[EMAIL PROTECTED]>
Description: 
 pike7.4    - Recommended meta package for Pike 7.4
 pike7.4-core - Powerful interpreted programming language
 pike7.4-dev - Development files for Pike 7.4
 pike7.4-doc - Pike 7.4 documentation meta package
 pike7.4-gdbm - Gdbm module for Pike
 pike7.4-gl - Mesa module for Pike
 pike7.4-gtk - GTK module for Pike
 pike7.4-image - Image module for Pike
 pike7.4-manual - Pike 7.4 manual
 pike7.4-meta - Meta package for Pike 7.4
 pike7.4-mysql - Mysql module for Pike
 pike7.4-odbc - Odbc module for Pike
 pike7.4-perl - Perl module for Pike
 pike7.4-pg - Postgres module for Pike
 pike7.4-reference - Pike 7.4 reference
 pike7.4-sane - SANE module for Pike
 pike7.4-sdl - SDL module for Pike
 pike7.4-svg - SVG format support for Pike
Closes: 327352
Changes: 
 pike7.4 (7.4.325-2) unstable; urgency=low
 .
   * pike7.4_7.4.325-1: FTBFS: "USE_SSL" define conflicts with libpq-dev
     (Closes: #327352). Build-depends on libssl-dev now.
   * Updated the Standards-Version. No changes.
Files: 
 0a38552c1f3af012eb94680ecfbf6105 1447 interpreters optional 
pike7.4_7.4.325-2.dsc
 88d511dbf07f5c49f762b23791b874ab 31003 interpreters optional 
pike7.4_7.4.325-2.diff.gz
 41ead34203b8c67c68c13fa76a200003 2198924 interpreters optional 
pike7.4-core_7.4.325-2_i386.deb
 396d7c2c057f8678e6a11cb5e0db8bb1 18592 interpreters optional 
pike7.4-mysql_7.4.325-2_i386.deb
 79b432fd556f63c895a005cdb3e37e14 14314 interpreters optional 
pike7.4-pg_7.4.325-2_i386.deb
 65584650b465c3b85ff8754e4ecdd67c 9956 interpreters optional 
pike7.4-odbc_7.4.325-2_i386.deb
 80e2bd8848f255780b214f1353d50c30 17804 interpreters optional 
pike7.4-svg_7.4.325-2_i386.deb
 2f2d7e2fb592677936f9859cf2948f19 375166 interpreters optional 
pike7.4-image_7.4.325-2_i386.deb
 6ff8dde0b5a64f11c48bda9fd62f7e50 31074 interpreters optional 
pike7.4-sdl_7.4.325-2_i386.deb
 1999edc17605e6702e28cffb290d579b 6678 interpreters optional 
pike7.4-gdbm_7.4.325-2_i386.deb
 9b94be36ff8a3251725051fa01bd59bb 152262 interpreters optional 
pike7.4-gtk_7.4.325-2_i386.deb
 97375fa54355d25dc331ee5e86f8241b 43176 interpreters optional 
pike7.4-gl_7.4.325-2_i386.deb
 94bfe86b442c6be8add680e8d6ab2409 9314 interpreters optional 
pike7.4-sane_7.4.325-2_i386.deb
 db4aaa87570032cbf9d4045ce048a694 12690 interpreters optional 
pike7.4-perl_7.4.325-2_i386.deb
 fa84f319dbdbabb5814ef40d7be50e47 13692 interpreters optional 
pike7.4_7.4.325-2_all.deb
 ebf967e31a527dc4f8f96c3b120db085 197666 interpreters optional 
pike7.4-dev_7.4.325-2_all.deb
 62578d6c35f72aa572da5f6e8abd0dc1 3669840 doc optional 
pike7.4-manual_7.4.325-2_all.deb
 d46edfb0117f2d1d6d014490cca03d8c 4555168 doc optional 
pike7.4-reference_7.4.325-2_all.deb
 079980ec98aa6fb6822bbd9fb44caf4a 13530 doc optional 
pike7.4-doc_7.4.325-2_all.deb
 26d08f51b1b9ef06a5520e8f4b6467d6 13622 interpreters optional 
pike7.4-meta_7.4.325-2_all.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFDIj5Mq3909GIf5uoRArvMAJ4uxgszHlx3MQbK4t2vW18MFBIT+wCfWRga
RYxDVXEHULLcJ78gnyrN010=
=DIoO
-----END PGP SIGNATURE-----


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to