* 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 usin
> (But I meant that change - with dropping the LD_ASSUME_KERNEL hack, this
> problem should AFAICS also disappear.)
Well, none of the current packages should be linking against -lpthread; I don't
see why continuing to not link them against -lpthread should solve any
bugs. Am I missing something?
I'm pleased to report that d-i is working again on hppa, and is now using
2.6.8 kernels. All changes required to make this happen are committed to
the debian-cd and debian-installer source trees, and I've uploaded new udebs
where necessary.
Once another d-i release candidate becomes available,
> (But I meant that change - with dropping the LD_ASSUME_KERNEL hack, this
> problem should AFAICS also disappear.)
Well, none of the current packages should be linking against -lpthread; I don't
see why continuing to not link them against -lpthread should solve any
bugs. Am I missing something?
I'm pleased to report that d-i is working again on hppa, and is now using
2.6.8 kernels. All changes required to make this happen are committed to
the debian-cd and debian-installer source trees, and I've uploaded new udebs
where necessary.
Once another d-i release candidate becomes available,
gettext (0.14.1-7) unstable; urgency=medium
* Fixed remaining vulnerability in autopoint, where temporary directories
were created using an unknown umask (Closes: #286392).
Patch by Bruno Haible. Thanks to Javier for the report.
-- Santiago Vila <[EMAIL PROTECTED]> Tue, 11 Jan 2005 17
gettext (0.14.1-7) unstable; urgency=medium
* Fixed remaining vulnerability in autopoint, where temporary directories
were created using an unknown umask (Closes: #286392).
Patch by Bruno Haible. Thanks to Javier for the report.
-- Santiago Vila <[EMAIL PROTECTED]> Tue, 11 Jan 2005 17
On Mon, Jan 17, 2005 at 09:30:30AM +0100, Matthias Klose wrote:
> python2.3 (2.3.4-19) unstable; urgency=low
> * Enable the build of the fpectl module (closes: #288575).
> The module was missing in 2.3 and 2.4, the 2.4 version already
> migrated to testing.
Approved.
Thanks,
--
Steve Langase
python2.3 (2.3.4-19) unstable; urgency=low
* Enable the build of the fpectl module (closes: #288575).
The module was missing in 2.3 and 2.4, the 2.4 version already
migrated to testing.
Thanks, Matthias
On Mon, Jan 17, 2005 at 09:30:30AM +0100, Matthias Klose wrote:
> python2.3 (2.3.4-19) unstable; urgency=low
> * Enable the build of the fpectl module (closes: #288575).
> The module was missing in 2.3 and 2.4, the 2.4 version already
> migrated to testing.
Approved.
Thanks,
--
Steve Langase
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
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 a
python2.3 (2.3.4-19) unstable; urgency=low
* Enable the build of the fpectl module (closes: #288575).
The module was missing in 2.3 and 2.4, the 2.4 version already
migrated to testing.
Thanks, Matthias
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble?
13 matches
Mail list logo