The workaround of using a ? worked. I guess nobody cares to have honest
full file manifests for debs.
see
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=61008
a patch to fix the behaviour has been supplied.
As a workaround for your situation without the patch: remove any
'set colour on' lines from your ~/.ircrc and the system /etc/irc/*
scripts and ircII as is without the patch will use
*/
/* Written by Bisqwit ([EMAIL PROTECTED]) */
+ /* Reworked to support default terminal color, allowing use of
+* color on non-black background terminals. 20061129
+*-- Gregory P. Smith ([EMAIL PROTECTED
Package: abcde
Version: 2.2.6-1
Followup-For: Bug #355296
When trying to rip this CD:
http://www.freedb.org/freedb_search_fmt.php?cat=classicalid=4a0e9206
DTITLE=Beethoven / Beethoven: Symphony No.3 Eroica * Overtures
The * gets expanded by abcde, then the expansion is processes (spaces
Package: python2.3-crypto
Version: 2.0+dp1-2
Severity: important
[EMAIL PROTECTED]:~$ python
Python 2.3.5 (#2, Feb 9 2005, 11:41:59)
[GCC 3.3.5 (Debian 1:3.3.5-8)] on linux2
Type help, copyright, credits or license for more information.
from Crypto.Hash import SHA256
s = SHA256.new()
On Mon, Feb 14, 2005 at 11:02:23AM +1100, Donovan Baarda wrote:
On Sat, 2005-02-12 at 17:35 -0800, Gregory P. Smith wrote:
I've created an OpenSSL version of the sha module. trivial to modify
to be a md5 module. Its a first version with cleanup to be done and
such. being managed
I've created an OpenSSL version of the sha module. trivial to modify
to be a md5 module. Its a first version with cleanup to be done and
such. being managed in the SF patch manager:
https://sourceforge.net/tracker/?func=detailaid=1121611group_id=5470atid=305470
enjoy. i'll do more cleanup
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/how/whether to include the openssl md5 implementation
sources so that win32 can use
The md5.h/md5c.c files allow copy and use, but no modification of
the files. There are some alternative implementations, i.e. in glibc,
openssl, so a replacement should be sage. Any other requirements when
considering a replacement?
Matthias
I believe the plan for md5 and sha1 and
9 matches
Mail list logo
