Hi Thibaut, > In the rules file for astromenace data, you list fonts in > /usr/share/fonts/truetype/ttf-liberation/, but the files there are > symlinks to files in /usr/share/fonts/truetype/liberation/. The symlinks > are provided by a compatility package which is not listed in your > build-dependencies, so building fails in a clean chroot. Can you fix that?
Thanks, I will fix it ASAP. > There is a more serious problem. You copy font files which end-up > (AFAIU) in gamedata.vfs. You therefore need to abide by the > redistribution terms of the license of those fonts. The Debian way of > insuring that in a generic manner (for DFSG-free material) would be to > list the font packages in Built-Using. This ensures that the user can > get the source for whatever ended-up in the binary package. > > The problem here is that astromenace-data is not in main but in > non-free. I'm not sure that the Built-Using mechanism is sufficient to > ensure that the source package for the fonts remain in the archive. Can > you check that on -devel or -legal? Ok, I will ask more opinions from team members and then ask people from other mailing lists if necessary. > Else I see two solutions: > > - copy (part of) the font source packages in astromenace-data (I didn't > check: if the ttf files are their own source, you only need to copy them > and amend debian/copyright); This is bad solution. I prefer do not do such things. > - pack gamedata.vfs on the end-user system to avoid redistribution. This is sane solution. And it is very easy to do. I will do this if other variants fail. Best regards, Boris -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1305171365073...@web22e.yandex.ru