Launchpad itself

euca-blobs providing binaries without source

Asked by Kasimir Gabert

The package euca-blobs provides a download of binaries which it does not provide the source to.

Specifically, in their download there is a file win-grub.img which is a binary compilation of [it seems to be] GRUB. No mention is given of how to create this binary file, and the sources are not provided.

I feel that this file should either be explained or removed from the .tar.gz upload. I have tried contacting the author about this but my comment on his blog was rejected, and my question on euca-blobs expired.

Question information

Language:
English Edit question
Status:
Solved
For:
Launchpad itself Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Curtis Hovey (sinzui) said : 		#1

I sent a message to https://launchpad.net/~andrew-fulcher about the issue using the Contact this user feature. If he does not respond, I think we need to disable his if he is inviolation of GPL2

Revision history for this message
Andrew Fulcher (andrew-fulcher) said : 		#2

I've sent Curtis an e-mail directly about this. Essentially, though, I'd be delighted to make the download compliant, but need advice and/or help to do this. The image file is just /boot/grub from a standard Jaunty install, with configuration applied to menu.lst

And, Kasimir, I can't see any sign of your comment on my blog, so guess it must have been rejected automatically by wordpress for some reason. I'd missed the question on the euca-blobs 'Answers' tab, so apologies for this.

Revision history for this message
Kasimir Gabert (kasimir-g) said : 		#3

Hello Andrew,

Thank you for the work you have done for euca-blobs! It is quite helpful.

I'm not a lawyer or familiar exactly with how to satisfy the GPL2, but I figure that providing a script (or even a text file) that creates (or explains how to create) the win-grub.img file would be sufficient.

Thank you for your response,
Kasimir

Revision history for this message
Tim Penhey (thumper) said : 		#4

It seems like this is now resolved.