Package: wnpp
Severity: normal
Package in good shape, upstream responsive and has a Debian guest
account for debugging failures.
--
Jens Peter Secher, GPG fingerprint 0EE5978AFE63E8A1.
A. Because it breaks the logical sequence of discussion.
Q. Why is top posting bad?
--
To UNSUBSCRIBE, ema
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Executive summary: libcrypto++8 will be replaced by libcrypto++9.
Please try to rebuild against libcrypto++-dev version 5.6.1-1 from
Experimental. The plan is to prepare version 5.6.1-2 for upload to
Unstable around March 2011. If this would mess
escription : libfilter-crypto-perl is a library to create runnable Perl
files encrypted with OpenSSL libcrypto
Filter::Crypto provides a Perl source code decryption filter for running
files that have been encrypted via the
Filter::Crypto::CryptFile|Filter::Crypto::CryptFile module.
.
You should
James Westby <[EMAIL PROTECTED]> writes:
>> It is true that gnutls uses libgcrypt, but libgcrypt doesn't provide
>> anything like the same symbols as libcrypto.
>
> What functionality are you after? libgcrypto provides most of the
> ciphers of libcrypto (the big p
On (08/06/06 16:47), Thomas Bushnell BSG wrote:
>
> Is there a GPL-compatible libcrypto replacement? The only libcrypto I
> know of is the one bundled with openssl, which AFAICT is under the
> same license as openssl itself, which is GPL-incompatible.
Correct.
> We have gnutls a
Ron Johnson <[EMAIL PROTECTED]> writes:
> Would it be statically linked?
No. Take a look at the symbols in libcrypto, and notice that they are
not in any of those libraries.
It is the case that libssl requires libcrypto, and that
libgnutls-openssl does not need anything like t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thomas Bushnell BSG wrote:
> Is there a GPL-compatible libcrypto replacement? The only libcrypto I
> know of is the one bundled with openssl, which AFAICT is under the
> same license as openssl itself, which is GPL-incompatible.
>
>
Is there a GPL-compatible libcrypto replacement? The only libcrypto I
know of is the one bundled with openssl, which AFAICT is under the
same license as openssl itself, which is GPL-incompatible.
We have gnutls as a replacement for openssl itself, but what about
libcrypto?
(Indeed, some things
Florian Weimer <[EMAIL PROTECTED]> writes:
> There's another problem with libtool:
>
> [...]
> ./libtool: line 4120: test: : integer expression expected
> ./libtool: line 4120: test: : integer expression expected
> creating reloadable object files...
> ./libtool: line 4154: test: : integer express
* Jens Peter Secher:
> Steve Langasek <[EMAIL PROTECTED]> writes:
>
>> Below is a list of libraries which appear to be blocking other packages that
>> need to go through the C++ transition[1] and which are themselves ready to
>> go through the ABI transition.
&
* Florian Weimer:
> * Nathanael Nerode:
>
>> I'd be interested in working on tracking down the linking problems, but I
>> don't want to duplicate your work. Are your patches-so-far available
>> somewhere?
>
> I think I've found the linking bug. Details later.
The link problem is caused by cod
* Nathanael Nerode:
> I'd be interested in working on tracking down the linking problems, but I
> don't want to duplicate your work. Are your patches-so-far available
> somewhere?
I think I've found the linking bug. Details later.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subjec
[EMAIL PROTECTED] wrote:
> I am fighting with libcrypto++ but so far I am loosing.
This is an exceedingly nasty library. There is way too much templatization in
this library, and GCC spews warnings like there's no tomorrow.
I'd be interested in working on tracking down the lin
On Sat, Jul 23, 2005 at 01:33:28AM +0200, Jens Peter Secher wrote:
> GCC4 does definitely not like a mix of templates and anonymous enums
> [1,2] but there are easy fixes for this.
[1] clearly stats this as illegal according to the C++ standard.
> What is worse, it seems that GCC4 silently refuse
On Sat, 2005-07-23 at 01:33 +0200, Jens Peter Secher wrote:
> I am fighting with libcrypto++ but so far I am loosing.
>
> GCC4 does definitely not like a mix of templates and anonymous enums
> [1,2] but there are easy fixes for this.
>
> What is worse, it seems that GCC4 s
Steve Langasek <[EMAIL PROTECTED]> writes:
> Below is a list of libraries which appear to be blocking other packages that
> need to go through the C++ transition[1] and which are themselves ready to
> go through the ABI transition.
[...]
> libcrypto++
I am fighting with libcry
16 matches
Mail list logo
