Bug#497270: Reviewing data in the debian-cd packages
Daniel's helpful bug (#497270) points out that we have embedded copies
of isolinux in the debian-cd package. It's prompted me to look for
other embedded data, and I've found the following list:
tack:~/debian/debian-cd/debian-cd$ find . -type f | xargs file | \
grep -v text | grep -v -e \.png -e \.jpg -e \.gif | \
awk '{print $1}'
./data/etch/sbm.bin.gz:
./data/etch/isolinux.bin:
./data/cts_amiga_info.tar.gz:
./data/macinstall-cd.tar.gz:
./data/lenny/sbm.bin.gz:
./data/lenny/vesamenu.c32:
./data/lenny/isolinux.bin:
./data/sarge/sbm.bin.gz:
./data/sarge/isolinux.bin:
Of those:
* isolinux.bin and vesamenu.c32 come from the syslinux package
* sbm.bin.gz comes from the sbm package
I can add code to extract the appropriate binaries from each package
at CD build time, in much the same way as we use debootstrap from the
archive. It'll slow things down a little, but that's not as important
as following licensing.
There's another implication, though... Normal weekly builds will
automatically pick up the appropriate source as part of the source
CD/DVD builds, so they're OK. However, more painfully, the current
daily netinst/businesscard builds don't produce source images. If
things change quickly in the syslinux/sbm packages there is a chance
that the source for the exact versions used in the daily images may
not remain on the mirrors. To be totally safe, we'll need to track
versions of packages that go into the daily images (both packages and
the used binary files) and archive those too. Yay.
Other files (hence the cc: to the m68k folks):
* cts_amiga_info.tar.gz
* macinstall-cd.tar.gz
are both provided to boot m68k machines, and they each contain binary
files (icons and boot files, AFAICS). I have no idea how those files
are generated, nor what the licensing situation is for them. Can you
help out please?
--
Steve McIntyre, Cambridge, UK.[EMAIL PROTECTED]
...In the UNIX world, people tend to interpret `non-technical user'
as meaning someone who's only ever written one device driver. -- Daniel Pead
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#497270: Reviewing data in the debian-cd packages
On Thu, Sep 11, 2008 at 12:37:22AM +0100, Steve McIntyre wrote: Daniel's helpful bug (#497270) points out that we have embedded copies of isolinux in the debian-cd package. It's prompted me to look for other embedded data, and I've found the following list: Other files (hence the cc: to the m68k folks): * cts_amiga_info.tar.gz * macinstall-cd.tar.gz are both provided to boot m68k machines, and they each contain binary files (icons and boot files, AFAICS). I have no idea how those files are generated, nor what the licensing situation is for them. Can you help out please? Wow I never caught that those files were in debian-cd. macinstall-cd.tar.gz contains an old version of Penguin, the mac bootloader, which is packaged in contrib (19-3). I'm pretty sure I used the penguin package when I was working on debian-cd for etch. The source for penguin 17 is at http://ftp.mac.linux-m68k.org/pub/linux-mac68k/penguin/. I'll have to let Christian answer for the licensing of cts_amiga_info.tar.gz. The rest of the amiga icons are in the d-i repo. If these have clear licensing (I'm pretty sure they do) then we should probably move them there too. As I recall they were created either by or for Christian to use with debian-cd. I don't believe they have a source form. They probably shouldn't be living in tar archives anyway. :) Thanks, Stephen -- Stephen R. Marenka If life's not fun, you're not doing it right! [EMAIL PROTECTED] signature.asc Description: Digital signature
Bug#497270: Reviewing data in the debian-cd packages
On Wed, 10 Sep 2008, Stephen R Marenka wrote: On Thu, Sep 11, 2008 at 12:37:22AM +0100, Steve McIntyre wrote: Daniel's helpful bug (#497270) points out that we have embedded copies of isolinux in the debian-cd package. It's prompted me to look for other embedded data, and I've found the following list: Other files (hence the cc: to the m68k folks): * cts_amiga_info.tar.gz * macinstall-cd.tar.gz are both provided to boot m68k machines, and they each contain binary files (icons and boot files, AFAICS). I have no idea how those files are generated, nor what the licensing situation is for them. Can you help out please? Wow I never caught that those files were in debian-cd. macinstall-cd.tar.gz contains an old version of Penguin, the mac bootloader, which is packaged in contrib (19-3). I'm pretty sure I used the penguin package when I was working on debian-cd for etch. The source for penguin 17 is at http://ftp.mac.linux-m68k.org/pub/linux-mac68k/penguin/. The current version is 19, and both the repo and the download are found on sourceforge. http://sourceforge.net/projects/linux-mac68k As to how it is generated, Penguin is a MacOS application and it is built under MacOS. Likewise BootX, the oldworld powermac bootloader. Neither can be built with Linux. Finn I'll have to let Christian answer for the licensing of cts_amiga_info.tar.gz. The rest of the amiga icons are in the d-i repo. If these have clear licensing (I'm pretty sure they do) then we should probably move them there too. As I recall they were created either by or for Christian to use with debian-cd. I don't believe they have a source form. They probably shouldn't be living in tar archives anyway. :) Thanks, Stephen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#497270: Reviewing data in the debian-cd packages
Hi, I'll have to let Christian answer for the licensing of cts_amiga_info.tar.gz. The rest of the amiga icons are in the d-i repo. If these have clear licensing (I'm pretty sure they do) then we should probably move them there too. As I recall they were created either by or for Christian to use with debian-cd. I don't believe they have a source form. IIRC the initial .info files (icon data needed by AmigaOS in order to start particular install shell scripts) were created by Frank Neumann. The others are by Christian. All were intended for distribution with the install CDs (but Christian should perhaps confirm that). My impression was that these files are created by some sort of resource editor which is part of AmigaOS, so there's no source (though the file format should not be too difficult to reverse engineer). They probably shouldn't be living in tar archives anyway. :) Perhaps not - there may be special permissions required for these files to be properly recognized, though (at least that's the case for start scripts). Christian has written a boot script that can fall back to a known good kernel on unsuccessful boot, maybe that can be added to whatever package gets to provide the icon files as well? Michael -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
