Richard Braakman wrote:
> On Fri, Apr 27, 2001 at 04:34:15PM -0400, Joey Hess wrote:
> > Richard Braakman wrote:
> > > We usually allow some time for license issues to be resolved. In the
> > > extreme case of KDE it was more than a year :)
> >
> > You forget: KDE was removed from the archive dur
On Fri, Apr 27, 2001 at 04:34:15PM -0400, Joey Hess wrote:
> Richard Braakman wrote:
> > We usually allow some time for license issues to be resolved. In the
> > extreme case of KDE it was more than a year :)
>
> You forget: KDE was removed from the archive during that time.
No, I'm specifically
Richard Braakman wrote:
> We usually allow some time for license issues to be resolved. In the
> extreme case of KDE it was more than a year :)
You forget: KDE was removed from the archive during that time.
--
see shy jo
> begin Sam Hartman quotation of Tue, Apr 24, 2001 at 03:54:38AM -0400:
>
> > We should also talk to the linux-kernel folks and strongly encourage
> > them to produce a DFSG free kernel, splitting out any non-free parts
> > if necessary.
>
> What's the deal with drivers/net/bsd_comp.c anyway? U
begin Sam Hartman quotation of Tue, Apr 24, 2001 at 03:54:38AM -0400:
> We should also talk to the linux-kernel folks and strongly encourage
> them to produce a DFSG free kernel, splitting out any non-free parts
> if necessary.
What's the deal with drivers/net/bsd_comp.c anyway? Unisys isn't ex
>> i wonder if it would be worth speaking with the people from keyspan/etc. and
>> explaining the problem to them? who knows - an appropriately worded message
>> (or 10) would probably convince them to release it under a less restrictive
>> license. the code itself isn't very useful is it? then aga
> "Richard" == Richard Braakman <[EMAIL PROTECTED]> writes:
Richard> If you wish to encourage dialog with the vendor, then by
Richard> all means start dialoguing :-) Nothing will happen unless
Richard> someone steps up to fix this, and the more voices the
Richard> better, I th
On Mon, Apr 23, 2001 at 10:04:06PM -0600, Walter Landry wrote:
> is DFSG compliant or GPL-compatible or not. This also means that
> Debian can't even distribute the original source tar-ball. Debian has
> no permission at all. If no one complains, I'll file bugs against
>
> kernel-source-2.4.0
>
On Tue, Apr 24, 2001 at 03:31:45PM +1000, Sam Johnston wrote:
> I'm usually a big fan of pedantic correctness, and yes, in retrospect having
> it in main is a cause for concern. My intention was to encourage dialog with
> the vendor rather than immediately removing it, not necessarily to encourage
> i wonder if it would be worth speaking with the people from keyspan/etc. and
> explaining the problem to them? who knows - an appropriately worded message
> (or 10) would probably convince them to release it under a less restrictive
> license. the code itself isn't very useful is it? then again i
From: [EMAIL PROTECTED]
Subject: Re: Copyright infringement in linux/drivers/usb/serial/keyspan*fw.h
Date: Mon, 23 Apr 2001 22:49:43 -0700
> On Mon, Apr 23, 2001 at 10:04:06PM -0600, Walter Landry wrote:
> > Adam J. Richter wrote:
> > Linus's Linux kernel releases from 2.3.5
On Mon, Apr 23, 2001 at 10:04:06PM -0600, Walter Landry wrote:
> Adam J. Richter wrote:
> Linus's Linux kernel releases from 2.3.50 through the latest
> test release (2.4.4-pre6) contain GPL-incompatible "firmware" images
> for "EZUSB" devices in linux/drivers/usb/serial/keyspan*fw.h, which
>
> Debian always follows the licenses, and that pedantic correctness is an
attractive factor for many of us.
I'm usually a big fan of pedantic correctness, and yes, in retrospect having
it in main is a cause for concern. My intention was to encourage dialog with
the vendor rather than immediately r
On Tue, Apr 24, 2001 at 02:13:48PM +1000, Sam Johnston wrote:
> i'd be inclined to leave the kernel source alone as if it's ok for AC then
> it should be ok for us too.
That has _never_ been Debian's policy.
> i don't think there's much risk in doing this as
> about the worst that is likely to
to go download a few bytes of
firmware from X, and recompile a module or the kernel itself).
- samj
-Original Message-
From: Walter Landry [mailto:[EMAIL PROTECTED]
Sent: Tuesday, 24 April 2001 2:04 PM
To: debian-legal@lists.debian.org
Subject: Re: Copyright infringement in
linux/drive
Adam J. Richter wrote:
Linus's Linux kernel releases from 2.3.50 through the latest
test release (2.4.4-pre6) contain GPL-incompatible "firmware" images
for "EZUSB" devices in linux/drivers/usb/serial/keyspan*fw.h, which
are #included into drivers which contain GPL'ed code, even when compil
16 matches
Mail list logo
