libdb*, mutex and threading

2005-01-16 Thread Andreas Barth
Hi, libdb* has some important/RC-bugs about mutex support and threading. After looking deeper at it, it seems to me that the way to go is to use the solution from db4.3, namely to add --enable-pthreadsmutexes to configure (and disable it by default) and don't use LD_ASSUME_KERNEL. (Not using LD_AS

Re: Re: Dropping 2.4 hppa kernel-image packages

2005-01-16 Thread Sven Luther
On Sun, Jan 16, 2005 at 01:18:59AM -0500, Andres Salomon wrote: > On Fri, 14 Jan 2005 02:47:01 -0500, Joey Hess wrote: > [...] > > > > It's been no secret that the 2.4 kernel was not in good shape and hppa > > folk were happier with 2.6. But this idea of just dropping 2.4 > > altogether was a supr

Re: libdb*, mutex and threading

2005-01-16 Thread Kurt Roeckx
On Sun, Jan 16, 2005 at 01:24:57PM +0100, Andreas Barth wrote: > This will solve the following bugs: > db2: > (not reported) packages compiled on 2.6 have issues on 2.4 > (not reported) Fast mutex support for mips and amd64 mutex/spinlocks also seem to be missing for ia64, powerpc and arm. > db3:

Re: libdb*, mutex and threading

2005-01-16 Thread Andreas Barth
* Kurt Roeckx ([EMAIL PROTECTED]) [050116 22:45]: > On Sun, Jan 16, 2005 at 01:24:57PM +0100, Andreas Barth wrote: > > db4.2: > > #232305: libdb4.2: Hangs on SMP (HyperThreaded P4) system using slapd > > 2.1.25-1 > There doesn't seem to be a fix for this? Or did I miss > something? AFAICS, this

Re: [Pkg-db-devel] Re: libdb*, mutex and threading

2005-01-16 Thread Clint Adams
> > > db4.2: > > > #232305: libdb4.2: Hangs on SMP (HyperThreaded P4) system using slapd > > > 2.1.25-1 > > > There doesn't seem to be a fix for this? Or did I miss > > something? > > AFAICS, this is fixed with changing configure to never link to pthread, > and not using LD_ASSUME_KERNEL. When

Re: [Pkg-db-devel] Re: libdb*, mutex and threading

2005-01-16 Thread Andreas Barth
* Clint Adams ([EMAIL PROTECTED]) [050116 23:25]: > > > > db4.2: > > > > #232305: libdb4.2: Hangs on SMP (HyperThreaded P4) system using slapd > > > > 2.1.25-1 > > > There doesn't seem to be a fix for this? Or did I miss > > > something? > > AFAICS, this is fixed with changing configure to nev

gnupg 1.2.5 vs. 1.4

2005-01-16 Thread Lance W. Haverkamp
gnupg has been at version 1.4 for a month now. Our developer information page for gnupg says: Testing Status # 167 days old (needed 10 days) # Not touching package, as requested by freeze (contact Debian-release if update is needed) # Not considered Is there a reason gnupg has been frozen at

Re: gnupg 1.2.5 vs. 1.4

2005-01-16 Thread Steve Langasek
On Sun, Jan 16, 2005 at 11:51:43PM -0700, Lance W. Haverkamp wrote: > gnupg has been at version 1.4 for a month now. Our developer > information page for gnupg says: > Testing Status > # 167 days old (needed 10 days) > # Not touching package, as requested by freeze (contact Debian-release > if