Your message dated Wed, 18 Jan 2006 16:32:16 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#348000: fixed in newpki-server 2.0.0+rc1-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; 13 Jan 2006 23:13:05 +0000
>From [EMAIL PROTECTED] Fri Jan 13 15:13:05 2006
Return-path: <[EMAIL PROTECTED]>
Received: from mobilewave.waldi.eu.org ([82.139.201.22])
by spohr.debian.org with esmtp (Exim 4.50)
id 1ExY6T-0007e3-AR
for [EMAIL PROTECTED]; Fri, 13 Jan 2006 15:13:05 -0800
Received: by mobilewave.waldi.eu.org (Postfix, from userid 1000)
id CD802187B1; Sat, 14 Jan 2006 00:13:18 +0100 (CET)
Date: Sat, 14 Jan 2006 00:13:18 +0100
From: Bastian Blank <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: newpki-server - FTBFS: error: 'const class NewpkiThread' has no member
named 'SleepInterrupt'
Message-ID: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <[EMAIL PROTECTED]>
User-Agent: Mutt/1.5.11
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: newpki-server
Version: 2.0.0+rc1-1
Severity: serious
There was an error while trying to autobuild your package:
> Automatic build of newpki-server_2.0.0+rc1-1 on debian-31 by sbuild/s390 85
[...]
> if g++ -DHAVE_CONFIG_H -I. -I. -I.. -DLOCALEDIR=\"/usr/share/locale\"
> -I/usr/include/newpki -Wall -g -O2 -MT newpki_server-AsynchJobs.o -MD -MP
> -MF ".deps/newpki_server-AsynchJobs.Tpo" -c -o newpki_server-AsynchJobs.o
> `test -f './AsynchJobs.cpp' || echo './'`./AsynchJobs.cpp; \
> then mv -f ".deps/newpki_server-AsynchJobs.Tpo"
> ".deps/newpki_server-AsynchJobs.Po"; else rm -f
> ".deps/newpki_server-AsynchJobs.Tpo"; exit 1; fi
> ../AsynchJobs.cpp: In static member function 'static void
> AsynchJobs::ThreadConfigurationPush(const NewpkiThread*, void*)':
> ../AsynchJobs.cpp:411: error: 'const class NewpkiThread' has no member named
> 'SleepInterrupt'
> make[3]: *** [newpki_server-AsynchJobs.o] Error 1
> make[3]: Leaving directory `/build/buildd/newpki-server-2.0.0+rc1/src'
> make[2]: *** [all-recursive] Error 1
> make[2]: Leaving directory `/build/buildd/newpki-server-2.0.0+rc1'
> make[1]: *** [all] Error 2
> make[1]: Leaving directory `/build/buildd/newpki-server-2.0.0+rc1'
> make: *** [build] Error 2
> ******************************************************************************
> Build finished at 20060113-1500
> FAILED [dpkg-buildpackage died]
Bastian
---------------------------------------
Received: (at 348000-close) by bugs.debian.org; 19 Jan 2006 00:41:44 +0000
>From [EMAIL PROTECTED] Wed Jan 18 16:41:43 2006
Return-path: <[EMAIL PROTECTED]>
Received: from katie by spohr.debian.org with local (Exim 4.50)
id 1EzNiq-0005zZ-CN; Wed, 18 Jan 2006 16:32:16 -0800
From: Pierre Chifflier <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: $Revision: 1.65 $
Subject: Bug#348000: fixed in newpki-server 2.0.0+rc1-2
Message-Id: <[EMAIL PROTECTED]>
Sender: Archive Administrator <[EMAIL PROTECTED]>
Date: Wed, 18 Jan 2006 16:32:16 -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
X-CrossAssassin-Score: 2
Source: newpki-server
Source-Version: 2.0.0+rc1-2
We believe that the bug you reported is fixed in the latest version of
newpki-server, which is due to be installed in the Debian FTP archive:
newpki-server_2.0.0+rc1-2.diff.gz
to pool/main/n/newpki-server/newpki-server_2.0.0+rc1-2.diff.gz
newpki-server_2.0.0+rc1-2.dsc
to pool/main/n/newpki-server/newpki-server_2.0.0+rc1-2.dsc
newpki-server_2.0.0+rc1-2_i386.deb
to pool/main/n/newpki-server/newpki-server_2.0.0+rc1-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.
Pierre Chifflier <[EMAIL PROTECTED]> (supplier of updated newpki-server 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: Tue, 17 Jan 2006 10:57:21 +0100
Source: newpki-server
Binary: newpki-server
Architecture: source i386
Version: 2.0.0+rc1-2
Distribution: unstable
Urgency: low
Maintainer: Pierre Chifflier <[EMAIL PROTECTED]>
Changed-By: Pierre Chifflier <[EMAIL PROTECTED]>
Description:
newpki-server - PKI based on the OpenSSL low-level API (server package)
Closes: 348000 348340
Changes:
newpki-server (2.0.0+rc1-2) unstable; urgency=low
.
* Depend on correct libnewpki2 package (Closes: #348340)
* Build-Depend on the same package (Closes: #348000)
Files:
26fc5c59f4ebe34138c2b4f8e60aa368 688 net optional newpki-server_2.0.0+rc1-2.dsc
0cb25fbfd5c93f80234f7ecb44461036 41328 net optional
newpki-server_2.0.0+rc1-2.diff.gz
17cf40f9f61fce43f97b26fddea7c276 387530 net optional
newpki-server_2.0.0+rc1-2_i386.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
iD8DBQFDztwEw3ao2vG823MRAj9SAJ9sANoPBToWz9++RspImiicEfB3YQCePhcr
UKL5c6Njjkh+n0BeHWceaM4=
=l0Jx
-----END PGP SIGNATURE-----
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
