Package: evolution
Version: 2.2.2-4
Followup-For: Bug #325571
I have the identical problem with identical debugging output from gdb.
In my case the problem only started when I switched to the task view,
and now occurs every time I start evolution. By deleting ~/.evolution
I was able to get evolu
ay to give udev time to create things like
the /dev/sda devices after loading the sata_sil module.
This is something I detailed in the bug report at;
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=273182
--
Donovan Baarda <[EMAIL PROTECTED]>
http://minkirri.apana.org.au/~abo/
--
To UN
Package: mdadm
Version: 1.9.0-2.1
Followup-For: Bug #294404
G'day,
just finished reading the stuff on this bug after finding an apt-get
upgrade to 1.9.0-21 broke my raid. The bug report for #301560 is also
related...
Moving mdadm-raid from S25 to S04 in rcS.d broke things for me. First,
udev a
Is it using the openssl sha interface, or the higher level
EVP interface?
The reason I ask is it would be pretty trivial to modify md5module.c to
use the openssl API for any digest, and would be less risk than
fresh-coding one.
--
Donovan Baarda <[EMAIL PROTECTED]>
http://minkirri.apana
G'day,
From: "Bob Ippolito" <[EMAIL PROTECTED]>
> On Feb 11, 2005, at 6:11 PM, Donovan Baarda wrote:
[...]
> > Given that Python is already dependant on openssl, it makes sense to
> > change
> > md5sum to use it. I have a feeling that openssl internally
thon is already dependant on openssl, it makes sense to change
md5sum to use it. I have a feeling that openssl internally uses md5, so this
way we wont link against two different md5sum implementations.
-
On Fri, 2005-02-11 at 17:15 +1100, Donovan Baarda wrote:
[...]
> I think it would be cleaner and simpler to modify the existing
> md5module.c to use the openssl md5 layer API (this is just a
> search/replace to change the function names). The bigger problem is
> deciding what/ho
On Thu, 2005-02-10 at 23:13 -0500, Bob Ippolito wrote:
> On Feb 10, 2005, at 9:50 PM, Donovan Baarda wrote:
>
> > On Thu, 2005-02-10 at 21:30 -0500, Bob Ippolito wrote:
[...]
> > Only problem with this, is pyopenssl doesn't yet include any mdX or sha
> > modules.
&g
On Thu, 2005-02-10 at 21:30 -0500, Bob Ippolito wrote:
> On Feb 10, 2005, at 9:15 PM, Donovan Baarda wrote:
>
> > On Tue, 2005-02-08 at 11:52 -0800, Gregory P. Smith wrote:
[...]
> One possible alternative would be to bring in something like PyOpenSSL
> <http://pyopenssl.
igrating to the openssl API. If people hassle me, I could
probably do the openssl API migration for Python, but I'm not sure what
the best approach would be to including the source in Python sources.
FWIW, I also have an md4sum module and md4c.c implementation that I'm
happy to cont
10 matches
Mail list logo
