Bug#37870: marked as done (Create new C++ project in kdevelop) by Marc Mutz <mutz at kde.org>

[Stephan Kulow]

Your message with subj: Bug#37970: further info re test taking hours

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Tuesday 12 February 2002 23:51, you wrote:
> > Maybe you have a very large keyring?
> > Can you send us the output of
> > time gpg --list-public-keys --with-colons --with-fingerprint
> > *grin*
> >
> > For me, that takes ca. 5 to 10 min on a 500K keyring with a 1GHz
>
> I'll let you know if/when it finishes (350Mhz PIII)
>
> My keyring is about 2MB (around 1000 keys), pretty much all from the
> Debian keyring.

*lol*

> So it is looking like a gpg wishlist bug rather than a kmail bug
> then?

You'll surely want to update to 1.0.7 when it comes out. It is _much_=20
faster with this.

No. It's neither a KMail nor GnuPG bug. It is just that your keyring is=20
much too large ;-)

There's remedy from both sides, though:
Kmail will become non-blocking on pgp/gpg operations in 3.1 and gnupg=20
will cache trust and validity of keys/signatures in 1.0.7 (which is=20
what makes it slow).

Marc

- --=20
Marc Mutz <mutz at kde.org>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE8aaFa3oWD+L2/6DgRAv1wAKDZB1vBZQ3m//vUufUUfanv50pTtQCdFXcH
w2X1D0raOZTcceBay1uWWhY=3D
=3DwQKy
-----END PGP SIGNATURE-----


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'm
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Stephan Kulow
(administrator, KDE bugs database)

Received: (at submit) by bugs.kde.org; 8 Feb 2002 12:29:22 +0000
Received: (qmail 18909 invoked by uid 33); 8 Feb 2002 12:29:22 -0000
Date: 8 Feb 2002 12:29:22 -0000
Message-ID: <20020208122922.18908.qmail at mail.kde.org>
To: submit at bugs.kde.org
Subject: Create new C++ project in kdevelop
From: Wolfgang.Balzer at dlr.de

Package:           kdevelop
Version:           2.0.2 (using KDE 2.2.1 )
Severity:          normal
Installed from:    SuSE
Compiler:          gcc version 2.95.3 20010315 (SuSE)
OS:                Linux (i686) release 2.4.10-SMP
OS/Compiler notes: 

Dear KDE-developers,

when creating a new C++ project in kdevelop the autoconf/automake step generates the following messages:

cat acinclude.m4.in libtool.m4.in >acinclude.m4
aclocal
autoheader
./aclocal.m4:2181: error: m4_defn: undefined macro: _m4_divert_diversion
acfunctions.m4:1108: AM_FUNC_OBSTACK is expanded from...
./aclocal.m4:2181: the top level
autoconf: tracing failed
gmake: *** [all] Error 1
*** fehlgeschlagen ***

The creation of KDE2 application framework works perfectly, but I want to use kdevelop for the development of a general C++ program.

Best regards
Wolfgang

(Submitted via bugs.kde.org)
(Called from KBugReport dialog)