Re: new cogito package, OpenSSL license issue resolved
On Fri, 13 May 2005 23:44:05 -0600, Sebastian Kuzminsky wrote: I've updated the Cogito package to compile against the upstream-included GPL SHA1 implementation lifted from Mozilla, instead of the (possibly) GPL-incompatible OpenSSL code. Thanks to Florian Weimer and Anibal Monsalve Salazar for bringing this issue to my attention. I have a terrible head for this kind of legal stuff, can't we all just get the code? This is the last issue I know of keeping this package out of the Debian archives. Yay! There's still the manpage issue, but I expect it will be resolved upstream in the next few days. For people trying this out, Zach Brown wrote some excellent documentation [1]. It would be nice to see this end up in the debian packages. If you need a sponsor for this, let me know; I'd like to see it in debian sooner rather than later. [1] http://thread.gmane.org/gmane.comp.version-control.git/3338 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: new cogito package, OpenSSL license issue resolved
Andres Salomon [EMAIL PROTECTED] wrote: For people trying this out, Zach Brown wrote some excellent documentation [1]. It would be nice to see this end up in the debian packages. I'm hoping the upstream maintainer (Pasky) will pick up that patch. If he doesnt in the next several days, I'll consider adding Zack Brown's updated README alongside the official upstream README. If you need a sponsor for this, let me know; I'd like to see it in debian sooner rather than later. I appreciate the offer, but it's already in Sid! Anibal Monsalve Salazar is sponsoring it. Sid currently has version 0.10+20050513-2, but there's a newer version in the queue (0.10+20050515-2). -- Sebastian Kuzminsky Marie will know I'm headed south, so's to meet me by and by Townes Van Zandt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: new cogito package, OpenSSL license issue resolved
On Sat, May 14, 2005 at 08:19:38AM -0600, Sebastian Kuzminsky wrote: This is the last issue I know of keeping this package out of the Debian archives. Yay! There's still the manpage issue, but I expect it will be resolved upstream in the next few days. Any chance you can make the package use the included assemly sha1 implementation on powerpc? It's a notable difference and with that change I could switch from self-compiled cognito to the package. I've updated my Cogito source package (0.10+20050513-3) to use the ppc-sha1 on powerpc, but I dont have a powerpc machine to compile on, so I haven't tested it. It still uses mozilla-sha1 on all the other architectures. Works just fine. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: new cogito package, OpenSSL license issue resolved
On Fri, May 13, 2005 at 11:44:05PM -0600, Sebastian Kuzminsky wrote: I've updated the Cogito package to compile against the upstream-included GPL SHA1 implementation lifted from Mozilla, instead of the (possibly) GPL-incompatible OpenSSL code. Thanks to Florian Weimer and Anibal Monsalve Salazar for bringing this issue to my attention. I have a terrible head for this kind of legal stuff, can't we all just get the code? This is the last issue I know of keeping this package out of the Debian archives. Yay! There's still the manpage issue, but I expect it will be resolved upstream in the next few days. Any chance you can make the package use the included assemly sha1 implementation on powerpc? It's a notable difference and with that change I could switch from self-compiled cognito to the package. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: new cogito package, OpenSSL license issue resolved
Christoph Hellwig [EMAIL PROTECTED] wrote: On Fri, May 13, 2005 at 11:44:05PM -0600, Sebastian Kuzminsky wrote: I've updated the Cogito package to compile against the upstream-included GPL SHA1 implementation lifted from Mozilla, instead of the (possibly) GPL-incompatible OpenSSL code. Thanks to Florian Weimer and Anibal Monsalve Salazar for bringing this issue to my attention. I have a terrible head for this kind of legal stuff, can't we all just get the code? This is the last issue I know of keeping this package out of the Debian archives. Yay! There's still the manpage issue, but I expect it will be resolved upstream in the next few days. Any chance you can make the package use the included assemly sha1 implementation on powerpc? It's a notable difference and with that change I could switch from self-compiled cognito to the package. I've updated my Cogito source package (0.10+20050513-3) to use the ppc-sha1 on powerpc, but I dont have a powerpc machine to compile on, so I haven't tested it. It still uses mozilla-sha1 on all the other architectures. Please pull the sources via http or apt and let me know if it works! http://highlab.com/~seb/debian -or- # Seb's packages from highlab.com deb http://highlab.com/~seb/debian / deb-src http://highlab.com/~seb/debian / -- Sebastian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
new cogito package, OpenSSL license issue resolved
I've updated the Cogito package to compile against the upstream-included GPL SHA1 implementation lifted from Mozilla, instead of the (possibly) GPL-incompatible OpenSSL code. Thanks to Florian Weimer and Anibal Monsalve Salazar for bringing this issue to my attention. I have a terrible head for this kind of legal stuff, can't we all just get the code? This is the last issue I know of keeping this package out of the Debian archives. Yay! There's still the manpage issue, but I expect it will be resolved upstream in the next few days. The latest version (0.10+20050513-2) can be downloaded from here: http://highlab.com/~seb/debian Or apt-getted from here: # Seb's packages from highlab.com deb http://highlab.com/~seb/debian / deb-src http://highlab.com/~seb/debian / -- Sebastian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
