Your message dated Wed, 11 May 2005 17:02:23 -0400
with message-id [EMAIL PROTECTED]
and subject line Bug#305156: fixed in amule 2.0.0-1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your
This RC bug can be closed as soon as the mantainer uploads the new aMule
2.0.0 upstream version that we released on May, 02. This release as a
matter of fact fixes ALL bugs currently on the debian bugtracker for
aMule, so it would be great if this new upstream could be into unstable
ASAP (Julien?)
I agree there, this is a bug for aMule package and maybe a request for
libcurl3 one. However, We're going to release aMule 2.0.0 final for sure
this weekend, making this bug dissapear on the new upstream version
update.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of
reassign 305156 amule
thanks
On Tue, Apr 26, 2005 at 12:48:30PM -0700, Debian Bug Tracking System wrote:
Processing commands for [EMAIL PROTECTED]:
reassign 305156 libcurl3
Bug#305156: amule: linked against libssl
Bug reassigned from package `amule' to `libcurl3'.
Eh, this bug is an RC bug
Package: amule
Version: 1.2.6+rc8-3
Severity: serious
Justification: uknown
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello.
Amule seems to be linked with OpenSSL library being at the same time GPLed.
These are not compatible licenses and you should either use some GPLed
crypto library or
As a matter of fact, is not aMule which forces the OpenSSL linking:
it's the curl package. I would be great if curl had a non-ssl package to
avoid this issues in packages using that library.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL
Hello.
Sure, feel free to reassign this bugreport to libcurl, but all in all it's
problem in amule right now, cause libcurl can be linked against openssl.
So I suppose the correct way would be to fill another bugreport against
libcurl asking its maintainer to provide new binary package not
Well, after some thinking, I decided to drop curl usage from aMule
completely. aMule 2.0.0 final, which should be out this weekend, will no
longer use libcurl, so that solves this issue completely. Thanks for the
input.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of
8 matches
Mail list logo
