Bug#398058: nhfsstone: software is non-free
Package: nhfsstone Version: 1:1.0.10-4 Severity: serious Package copyright claims that all the software is under GPL, however, utils/nhfsstone/DISCLAIMER, as referenced by utils/nhfsstone/README, states: --- You may copy Legato nhfsstone source, object code and related documentation as necessary, but are not authorized to license it to anyone else. Legato nhfsstone may be modified only for the purpose of porting. If the basic algorithms are changed the resulting program may not be called nhfsstone. --- The choice of words seems unfortunate, as it makes this non-free. The intent seems to have been to just say that modified versions should be called something else. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#398058: nhfsstone: software is non-free
Processing commands for [EMAIL PROTECTED]: tags 398058 etch-ignore Bug#398058: nhfsstone: software is non-free There were no tags set. Tags added: etch-ignore thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#398058: nhfsstone: software is non-free
tags 398058 etch-ignore thanks On Sat, Nov 11, 2006 at 05:49:03PM +0200, Teemu Hukkanen wrote: Package: nhfsstone Version: 1:1.0.10-4 Severity: serious Package copyright claims that all the software is under GPL, however, utils/nhfsstone/DISCLAIMER, as referenced by utils/nhfsstone/README, states: --- You may copy Legato nhfsstone source, object code and related documentation as necessary, but are not authorized to license it to anyone else. Legato nhfsstone may be modified only for the purpose of porting. If the basic algorithms are changed the resulting program may not be called nhfsstone. --- Given the blanket notice in the package that it's available under the GPL, it's entirely possible that README and DISCLAIMER are historical statements that simply haven't been updated correctly. As such, I'm granting an etch-ignore exception on this bug to give the maintainer time to react and resolve this without risk of the package being pulled from the release without due cause. Thanks, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
