Re: [panc...@nopcode.org: License]

2011-10-27 Thread Ted Unangst
On Thu, Oct 27, 2011, pancake wrote:
 
 The problem I'm facing now is in libr/util/regex which is the imported
 version of OpenBSD's lib/libc/regex.
 
 The issue was reported by the Debian maintainer of r2 and it's a license
 issue.
 
 http://radare.org/cgi-bin/hg/radare2/file/41de633fa424/libr/util/regex
 
 If you look at the COPYRIGHT file you'll see that this BSD license
 includes the 4th clause which is GPL incompatible and therefore
 problematic for Debian to be packaged.

Uh, actually there are two licenses in that file.  The BSD license only
has 3 clauses.  The first license does have 4 clauses, but not all
licenses with 4 clauses are BSD licenses.  Did the debian dudes read the
license and decide it's incompatible, or is this all a misunderstanding
of what the license is?

You'd have to talk to Spencer about changing it, but I really doubt
that's necessary because that regex code was very widely copied.  I can
practically guarantee there are other programs in Debian using it too.

[Whatever it is you're building, why not just use the system regex code?
That seems more maintainable in the long run.]



Re: [panc...@nopcode.org: License]

2011-10-27 Thread Ingo Schwarze
Hi Pancake,

pancake wrote on Thu, Oct 27, 2011 at 06:03:13PM +0200:

 Sorry for the lag and the silence. I've been pretty busy and was
 unable to reply in this thread.

No problem with the delay, your time is your own to spend.

However, i'm not sure this discussion is apropriate on tech@.
You are not sending patches.
Next time, consider using misc@.

 There was a confussion with the bug report that I want to clarify.
 
 In radare2 I took libc/regex and usr.bin/file from the OpenBSD CVS.
 I was looking for some smart implementations of regex and magic to
 be used in my project and make it more portable. After a long
 evaluation I found that the OpenBSD ones was the shorter and nicer
 to maintain.

Well, that's a completely different question, not at all related
to file(1).

 During the merge process I found some C missuses which caused
 crashes and problems in file.. I already report them to Edd Barret.
 So I think they should be already fixed in mainstream.
 
 The problem I'm facing now is in libr/util/regex which is the
 imported version of OpenBSD's lib/libc/regex.
 
 The issue was reported by the Debian maintainer of r2 and it's a
 license issue.
 
http://radare.org/cgi-bin/hg/radare2/file/41de633fa424/libr/util/regex
 
 If you look at the COPYRIGHT file you'll see that this BSD license
 includes the 4th clause which is GPL incompatible and therefore
 problematic for Debian to be packaged.

I don't see the 4th Berkeley clause in there,
but i do see that it was removed 8 years ago:

  http://www.openbsd.org/cgi-bin/cvsweb/ \
src/lib/libc/regex/COPYRIGHT.diff?r1=1.2;r2=1.3

Once again, it seems unclear what you are talking about.

Maybe you are talking about something else, not the 4th Berkeley
clause?  If so, what exactly?

Yours,
  Ingo


 The thing is that there's no .c file in the same directory that
 contains such clause, all the code is under 2 or 3 bsd clauses which
 are ok for Debian.
 
 I want to clarify if this 4th clause is inherited to the C code or
 it's just a license bug or what.
 
 r2-0.8.8 release is locked by this issue, so it would be great if we
 can fix it asap.



Re: [panc...@nopcode.org: License]

2011-10-27 Thread pancake
Sorry for the lag and the silence. I've been pretty busy and was unable 
to reply in this thread.


There was a confussion with the bug report that I want to clarify.

In radare2 I took libc/regex and usr.bin/file from the OpenBSD CVS. I 
was looking for some smart implementations of regex and magic to be used 
in my project and make it more portable. After a long evaluation I found 
that the OpenBSD ones was the shorter and nicer to maintain.


During the merge process I found some C missuses which caused crashes 
and problems in file.. I already report them to Edd Barret. So I think 
they should be already fixed in mainstream.


The problem I'm facing now is in libr/util/regex which is the imported 
version of OpenBSD's lib/libc/regex.


The issue was reported by the Debian maintainer of r2 and it's a license 
issue.


   http://radare.org/cgi-bin/hg/radare2/file/41de633fa424/libr/util/regex

If you look at the COPYRIGHT file you'll see that this BSD license 
includes the 4th clause which is GPL incompatible and therefore 
problematic for Debian to be packaged.


The thing is that there's no .c file in the same directory that contains 
such clause, all the code is under 2 or 3 bsd clauses which are ok for 
Debian.


I want to clarify if this 4th clause is inherited to the C code or it's 
just a license bug or what.


r2-0.8.8 release is locked by this issue, so it would be great if we can 
fix it asap.


Thanks

--pancake



Help with Port(s)?

2011-10-27 Thread cody chandler
Hello,

  I'm interested in helping with port(s).  I'm new and have a lot to learn
but if someone would not mind teaching I'd like to help!

Thank you
Cody



Re: Help with Port(s)?

2011-10-27 Thread Gonzalo L. R.
first of all you need to read:

http://www.openbsd.org/faq/

and then send the mail to the correct list, ports@


On Thu, 27 Oct 2011 15:10:54 -0400, cody chandler
cody.a.chand...@gmail.com wrote:
 Hello,
 
   I'm interested in helping with port(s).  I'm new and have a lot to
learn
 but if someone would not mind teaching I'd like to help!
 
 Thank you
 Cody

-- 
Sending from my computer



Re: Help with Port(s)?

2011-10-27 Thread Darrin Chandler
On Thu, Oct 27, 2011 at 03:10:54PM -0400, cody chandler wrote:
   I'm interested in helping with port(s).  I'm new and have a lot to learn
 but if someone would not mind teaching I'd like to help!

See http://www.openbsd.org/faq/ports/index.html for starters.

-- 
http://code.phxbsd.com/



Asesoramiento impositivo - contable - laboral - societario

2011-10-27 Thread ESTUDIO CONTABLE IMPOSITIVO

(This safeguard is not inserted when using the registered version)
jkdldcknlkdsncqldsnlcnlqSC
(This safeguard is not inserted when using the registered version)



new uftdi(4) device

2011-10-27 Thread Mark Peoples
i needed to test my sirius tuner w windows, and in doing so, the driver did 
some wonky shit and upgraded the pid i suppose? anyways, this makes the device 
get correctly attached as uftdi(4) while also allowing the old pid to work as 
well

sorting looks dicked up, but so is what the driver did

Index: usbdevs
===
RCS file: /cvs/src/sys/dev/usb/usbdevs,v
retrieving revision 1.560
diff -u usbdevs
--- usbdevs 20 Oct 2011 16:35:52 -  1.560
+++ usbdevs 28 Oct 2011 01:06:21 -
@@ -1578,6 +1578,7 @@
 product FTDI FT4232H   0x6011  FT4232H
 product FTDI PS2KBDMS  0x8371  PS/2 Keyboard/Mouse
 product FTDI SERIAL_8U100AX0x8372  Serial
+product FTDI MJS_SIRIUS_PC_2   0x9379  MJS Sirius To PC Interface
 product FTDI OPENRD0x9e90  OpenRD JTAGKey
 product FTDI CANDAPTER 0x9f80  CANdapter
 product FTDI NXTCAM0xabb8  Mindstorms NXTCam
@@ -1599,7 +1600,7 @@
 product FTDI ASK_RDR4X7_6  0xc995  ASK RDR 4X7
 product FTDI ASK_RDR4X7_7  0xc996  ASK RDR 4X7
 product FTDI ASK_RDR4X7_8  0xc997  ASK RDR 4X7
-product FTDI MJS_SIRIUS_PC 0xca81  MJS Sirius To PC Interface
+product FTDI MJS_SIRIUS_PC_1   0xca81  MJS Sirius To PC Interface
 product FTDI CHAMELEON 0xcaa0  5Chameleon
 product FTDI OPENPORT_13M  0xcc48  OpenPort 1.3 Mitsubishi
 product FTDI OPENPORT_13S  0xcc49  OpenPort 1.3 Subaru



Enlace Convocatoria para operadores telefonicos y data entry

2011-10-27 Thread Novedades Feedback
Mail para ser visto con conexion, si no puede verlo, click aqui

[IMAGE]

FeedBack

[IMAGE]

FeedBack

Feedback, comunicacion en serio

[IMAGE]

[IMAGE]

bl

Agencia de Prensa y Noticias, servicio de Mailing y Publicidad
email: veron...@agenciafeedback.com.ar | website:
www.agenciafeedback.com.ar

bt

Si usted no esta interesado en recibir mas informacion proporcionada por
Feedback, Agencia de Prensa, envCenos un e-mail indicando en el asunto la
palabra Eliminar a prensafeedb...@gmail.com y sera dado de baja
automaticamente. Para subscribirse o por algun tercero que desee hacerlo,
tambien envienos a la misma direccion de email resaltando en el asunto la
palabra Registro. Nuevamente disculpe por las molestias que le pudimos
haber ocasionado.