Package: libldap-ruby
Version: 0.9.7
Tags: patch upstream
Libruby ldap creates LDAP::Mod objects by copying pointers, not
strings, which means that when the original string is garbage
collected, the Mod objects are corrupted.
Attached is a patch that is also being submitted upstream, but as
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Upon further experimentation, I discovered taht I was in fact
apparently mistake with regard to unstable. 2.6.10-1-686-smp boots
with no problems, without requiring and ACPI/noapic nonsense. Still
don't have the requisite logs for the 2.6.8 boot up -
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'll try to do what you said as soon as I can gank a nullmodem cable
from a friend. However, I should clarify a major mistake that
happened because it was really late at night when I sent this, aside
from typos: Adding noapic/acpi=off does *not*
Package: kernel-image-2.6-686-smp
Version: 101
Severity: critical
Justification: breaks the whole system
Tested on both testing and unstable. On my (old) dual-P3 system (Asus
CUV4X-D), booting the SMP kernels for 2.6.8 or 2.6.10 causes a hand on boot,
with the message Kernel panic: attempted
4 matches
Mail list logo
