On 28/12/13 14:14, Philipp Kern wrote:
> On Sat, Dec 28, 2013 at 10:58:56AM +0000, Daniel Lintott wrote:
>>> On Wed, Oct 09, 2013 at 12:22:48PM +0100, Daniel Lintott wrote:
>>>> I have just taken over the maintenance of the dynamips package 
>>>> (http://packages.debian.org/sid/dynamips) and would like for this
>>>> to be Autobuilt as per bug #690097.
>>>> The dynamips package is licensed under GPL-2.0+, but contains
>>>> two binaries mips64_microcode and ppc32_microcode that have have
>>>> been included with dynamips since the it was first written.
>>> I'm confused. Those are not listed in debian/copyright. Why?
>> These aren't currently listed in debian/copyright as I've no more
>> information on the files.
>>
>> Both myself and upstream have been searching for some time now, to try
>> and uncover more details on these two files... but have been
>> unsuccessful.
>>
>> To quote a previous email that Andrew sent:
>>> The main and well-known issue with Dynamips is that it contains
>>> non-free microcode blobs, while the rest of the package is 
>>> buildable and is cross-platform.
>>
>> Is there a particular statement that would like to be seen in
>> debian/copyright regarding these files?
> 
> So those files are not even from the GPL-2.0+ source, even if not
> buildable in Debian itself? How do we know that we can distribute them?
> 

Sorry for the long delay in replying here.

I have been I contact with the upstream authors of dynamips and we can
now confirm that the microcode blobs were indeed created specifically
for the Dynamips project.

I have added the following comment to the copyright file:

> Comment: Dynamips includes 4 microcode blobs (2 in stable, 2 in
>  unstable) without source code present. Following discussions
>  with the upstream author we have confirmed that these files
>  were created specifically for the Dynamips project.   
>  From the upstream author: I confirmed that it's built 
>  specifically for dynamips while disassembling the microcode:
>   1) It relies on the custom device found in dev_remote.c
>   2) It assumes our hardcoded ("broken") behavior and doesn't 
>      set things that would be needed if the cpu/motherboard 
>      emulation was complete.

This copyright is not yet present in Debian, but is in the git repo [1],
ready for the next upload.

I hope that with this we can now get Dynamips enabled on the buildd's.

[1] http://anonscm.debian.org/gitweb/?p=users/dlintott-guest/dynamips.git

Regards,
-- 
Daniel Lintott
GPG Key: 4096R/5D73EC6E

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to