Domenico == Domenico Andreoli [EMAIL PROTECTED] writes:
Domenico unfortunately heimdal bug #316980 makes curl FTBS :(
patches to fix this welcome ;-)
--
Brian May [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL
[ CCing curl-library ml ]
On Mon, Jul 25, 2005 at 12:12:03PM -0400, Aaron M. Ucko wrote:
Domenico Andreoli [EMAIL PROTECTED] writes:
unfortunately heimdal bug #316980 makes curl FTBS :(
:-/ Can you use MIT krb5 instead?
sure :)
i'm not a kerberos guru, i never used it and probably i
Domenico Andreoli [EMAIL PROTECTED] writes:
i'm not a kerberos guru, i never used it and probably i will never be
interested in it. i added this package only after a debian user asked
for GSSAPI support in curl (FYI bug #241553).
Got it. :-)
anybody knows if curl will modify its behaviour
Domenico Andreoli [EMAIL PROTECTED] writes:
unfortunately heimdal bug #316980 makes curl FTBS :(
:-/ Can you use MIT krb5 instead?
--
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
Finger [EMAIL PROTECTED] (NOT a valid e-mail address) for more info.
--
To UNSUBSCRIBE,
On Fri, Jul 22, 2005 at 07:15:18PM +0200, Elimar Riesebieter wrote:
On Mon, 18 Jul 2005 the mental interface of
Domenico Andreoli told:
[...]
i doubt seriously a new package like libcurl3-gnutls is appropriate,
but let me know your opinion.
is this stuff urgent?
Yes!
unfortunately
On Mon, 18 Jul 2005 the mental interface of
Domenico Andreoli told:
[...]
i doubt seriously a new package like libcurl3-gnutls is appropriate,
but let me know your opinion.
is this stuff urgent?
Yes!
Elimar
--
Learned men are the cisterns of knowledge,
not the fountainheads ;-)
--
On Jul 20, sean finney [EMAIL PROTECTED] wrote:
i think that would solve the problem by muting the symptoms. what happens
when the next free-but-not-quite-gpl-compatible licensed software is
linked against libcurl (or something similar)?
Not relevant, gnutls is LGPL'ed.
i know i'm repeating
On Wed, 20 Jul 2005 the mental interface of
Marco d'Itri told:
On Jul 20, sean finney [EMAIL PROTECTED] wrote:
[...]
i know i'm repeating myself here, but the real fix is to politely
solicit the upstream author to change or add a clause to their license
that makes such allowances. that,
On Mon, Jul 18, 2005 at 09:28:27PM -0400, Stephen Frost wrote:
That's not too helpful. I don't really want to support code I did not
understand. I'd rather write it myself or have Steve care about problems
in it...
The idea is to get upstream to include/support it...
The theory sound
On Sun, Jul 17, 2005 at 03:19:54PM -0400, sean finney wrote:
On Sun, Jul 17, 2005 at 09:04:57PM +0200, Elimar Riesebieter wrote:
Why not building curl --without-sssl and --with-gnutls=/usr? Maybe a
NMU?
this is definitely NOT a reason to NMU libcurl. remember that it is
your package that
hi,
On Mon, Jul 18, 2005 at 09:45:09PM +0200, Domenico Andreoli wrote:
i saw the bug report, i'm sorry to not have commented the request which
i find absolutely reasonable. i'll try to figure out if curl may suffer
from limitations due to the use of gnutls in place of openssl.
i would guess
[Don Armstrong]
All that needs to happen is that GPLed packages without an OpenSSL
linking exception either need to:
1) Get a linking exception.
2) Stop linking with OpenSSL.
3) For indirect dependencies: make sure you're only using the bits
of the (for example) libcurl ABI
Peter Samuelson [EMAIL PROTECTED] writes:
[Don Armstrong]
All that needs to happen is that GPLed packages without an OpenSSL
linking exception either need to:
1) Get a linking exception.
2) Stop linking with OpenSSL.
3) For indirect dependencies: make sure you're only using the
On Mon, Jul 18, 2005 at 01:02:53AM -0500, Peter Samuelson wrote:
[Don Armstrong]
All that needs to happen is that GPLed packages without an OpenSSL
linking exception either need to:
3) For indirect dependencies: make sure you're only using the bits
of the (for example)
On Sun, Jul 17, 2005 at 03:19:54PM -0400, sean finney wrote:
Why not building curl --without-sssl and --with-gnutls=/usr? Maybe a
NMU?
this is definitely NOT a reason to NMU libcurl. remember that it is
your package that is broken. of course you could still file a
The same issues as
On Sun, Jul 17, 2005 at 11:09:04PM +0300, Don Armstrong wrote:
On Sun, 17 Jul 2005, Elimar Riesebieter wrote:
apt-get remove --purge libssl0.9.7 gives me tons of packages. Just
an estimation: We need to repack half of all packages then?
NO.[1]
All that needs to happen is that GPLed
On Mon, Jul 18, 2005 at 11:07:41AM +0200, Torsten Landschoff wrote:
apt-get remove --purge libssl0.9.7 gives me tons of packages. Just
an estimation: We need to repack half of all packages then?
NO.[1]
All that needs to happen is that GPLed packages without an OpenSSL
linking
[Bartosz Fenski]
Seems that part of developers think that indirect linking with
OpenSSL is ok, and part think it's not.
Yeah. Well. Stand back and look at why this 'linking' thing matters
in the first place. The point is to determine whether one work is a
derivative of another work. If it
On Mon, Jul 18, 2005 at 05:16:27AM -0500, Peter Samuelson wrote:
[Bartosz Fenski]
Seems that part of developers think that indirect linking with
OpenSSL is ok, and part think it's not.
Yeah. Well. Stand back and look at why this 'linking' thing matters
in the first place. The point is
Torsten Landschoff [EMAIL PROTECTED] writes:
On Sun, Jul 17, 2005 at 11:09:04PM +0300, Don Armstrong wrote:
On Sun, 17 Jul 2005, Elimar Riesebieter wrote:
apt-get remove --purge libssl0.9.7 gives me tons of packages. Just
an estimation: We need to repack half of all packages then?
NO.[1]
* Goswin von Brederlow ([EMAIL PROTECTED]) wrote:
I guess the savest way is to have a libldap-nossl-dev and
libldap-ssl-dev. The former should have anything ssl derived
removed.
No, that was *worse*. We tried that before. The answer really is
reasonably simple- just modify libldap2 to use
hi,
On Mon, Jul 18, 2005 at 11:06:13AM +0200, Torsten Landschoff wrote:
On Sun, Jul 17, 2005 at 03:19:54PM -0400, sean finney wrote:
this is definitely NOT a reason to NMU libcurl. remember that it is
your package that is broken. of course you could still file a
The same issues as with
On 7/18/05, sean finney [EMAIL PROTECTED] wrote:
hi,
On Mon, Jul 18, 2005 at 11:06:13AM +0200, Torsten Landschoff wrote:
On Sun, Jul 17, 2005 at 03:19:54PM -0400, sean finney wrote:
this is definitely NOT a reason to NMU libcurl. remember that it is
your package that is broken. of
Hi Goswin,
On Mon, Jul 18, 2005 at 01:06:01PM +0200, Goswin von Brederlow wrote:
I guess the savest way is to have a libldap-nossl-dev and
libldap-ssl-dev. The former should have anything ssl derived
removed.
No problem. But then I can just build libldap without ssl as the library
built
On Mon, Jul 18, 2005 at 09:06:20AM -0400, Stephen Frost wrote:
No, that was *worse*. We tried that before. The answer really is
reasonably simple- just modify libldap2 to use GNUTLS. That was done w/
an older version of things involved. I expect it'll be done for the
newer stuff.
On Mon, Jul 18, 2005 at 09:29:46AM -0400, sean finney wrote:
The same issues as with libcurl applied to libldap2. They were
considered a bug in libldap2 back then because half the distribution
links it. Gave me a lot of recurring head aches.
yes, and the same with libmysqlclient, which
* Torsten Landschoff ([EMAIL PROTECTED]) wrote:
On Mon, Jul 18, 2005 at 09:06:20AM -0400, Stephen Frost wrote:
No, that was *worse*. We tried that before. The answer really is
reasonably simple- just modify libldap2 to use GNUTLS. That was done w/
an older version of things involved.
On Mon, 2005-07-18 at 16:36 +0200, Torsten Landschoff wrote:
On Mon, Jul 18, 2005 at 09:06:20AM -0400, Stephen Frost wrote:
No, that was *worse*. We tried that before. The answer really is
reasonably simple- just modify libldap2 to use GNUTLS. That was done w/
an older version of
hi,
On Mon, Jul 18, 2005 at 03:40:30PM +0200, Olaf van der Spek wrote:
On 7/18/05, sean finney [EMAIL PROTECTED] wrote:
yes, and the same with libmysqlclient, which is why there's no longer ssl
support in the mysql packages :(
Wouldn't it be possible to support SSL transparently in such a
On Mon, 18 Jul 2005 the mental interface of
Torsten Landschoff told:
Hi Goswin,
On Mon, Jul 18, 2005 at 01:06:01PM +0200, Goswin von Brederlow wrote:
I guess the savest way is to have a libldap-nossl-dev and
libldap-ssl-dev. The former should have anything ssl derived
removed.
hi,
On Mon, Jul 18, 2005 at 09:52:32PM +0200, Elimar Riesebieter wrote:
In summary:
libs linked again ssl need at least two dev-packages:
libfoo-dev.deb and libfoo-ssl-dev.deb
Right?
No. as mentioned earlier, this is no fault of the library
packages in question, and instead is the fault
* sean finney [EMAIL PROTECTED] [050717 21:20]:
On Sun, Jul 17, 2005 at 09:04:57PM +0200, Elimar Riesebieter wrote:
Why not building curl --without-sssl and --with-gnutls=/usr? Maybe a
NMU?
this is definitely NOT a reason to NMU libcurl. remember that it is
your package that is broken.
Hi Stephen,
On Mon, Jul 18, 2005 at 10:53:02AM -0400, Stephen Frost wrote:
Working on that. At least theoretically - when I get time, yada, yada.
Steve Langasek had offered to help with this too. I'll poke him about
it on IRC and see if he's still willing to help.
That's not too helpful.
* Torsten Landschoff ([EMAIL PROTECTED]) wrote:
Hi Stephen,
On Mon, Jul 18, 2005 at 10:53:02AM -0400, Stephen Frost wrote:
Working on that. At least theoretically - when I get time, yada, yada.
Steve Langasek had offered to help with this too. I'll poke him about
it on IRC and see
On Sun, 17 Jul 2005 the mental interface of
Marco d'Itri told:
On Jul 17, Elimar Riesebieter [EMAIL PROTECTED] wrote:
comfortable to build curl against gnutls in general? Any hints?
Upstream developers should get a clue and either properly license their
software, stop using libcurl or
On Sun, Jul 17, 2005 at 08:21:00PM +0200, Elimar Riesebieter wrote:
I don't see a gpl'd alternative to curl for internet streaming. I am
thinking about to build moc --without-curl then :(
or you could always contact the author and inform them of their
self-inflicted license violation. in my
On Sun, 17 Jul 2005 the mental interface of
sean finney told:
On Sun, Jul 17, 2005 at 08:21:00PM +0200, Elimar Riesebieter wrote:
I don't see a gpl'd alternative to curl for internet streaming. I am
thinking about to build moc --without-curl then :(
or you could always contact the author
On Sun, Jul 17, 2005 at 09:04:57PM +0200, Elimar Riesebieter wrote:
Why not building curl --without-sssl and --with-gnutls=/usr? Maybe a
NMU?
this is definitely NOT a reason to NMU libcurl. remember that it is
your package that is broken. of course you could still file a
wishlist bug against
On Sun, 17 Jul 2005 the mental interface of
sean finney told:
On Sun, Jul 17, 2005 at 08:21:00PM +0200, Elimar Riesebieter wrote:
I don't see a gpl'd alternative to curl for internet streaming. I am
thinking about to build moc --without-curl then :(
or you could always contact the author
On Sun, 17 Jul 2005, Elimar Riesebieter wrote:
apt-get remove --purge libssl0.9.7 gives me tons of packages. Just
an estimation: We need to repack half of all packages then?
NO.[1]
All that needs to happen is that GPLed packages without an OpenSSL
linking exception either need to:
1) Get a
40 matches
Mail list logo
