Dne Tue, 9 Dec 2008 08:00:46 +0100 Salvatore Bonaccorso <carnil.debian@gmx.net> napsal(a): > Hi > > On Mon, Dec 08, 2008 at 10:29:15PM +0100, Salvatore Bonaccorso wrote: > > On Mon, Dec 08, 2008 at 03:06:00PM +0100, Michal Čihař wrote: > > > Dne Sun, 7 Dec 2008 19:25:47 +0100 > > > Salvatore Bonaccorso <salvatore.bonaccorso@gmail.com> napsal(a): > > > > > > > The package can be found on mentors.debian.net: > > > > - URL: http://mentors.debian.net/debian/pool/main/t/tuxcmd > > > > - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free > > > > - dget http://mentors.debian.net/debian/pool/main/t/tuxcmd/tuxcmd_0.6.50-1.dsc > > > > > > Why is it only arch: i386 amd64? > > > > > > Also debian/copyright lacks some information: > > > - translation copyrights are not included > > > - also some source files have more than one copyright holders > > [...] > > I fix this issues when preparing to upload a new version to check, > > following the proposal, thanks! The reason I used only arch i386 and > > amd64, was bit "stupid" as I was not sure if the package would also > > build cleanly under the other architectures. > > See the note of the Author on: > > https://bugzilla.redhat.com/show_bug.cgi?id=449367 > > Only a further note on this. tuxcmd uses some parts, which is not > available on all architectures. fp-compiler is only available for > amd64, arm, i386, powerpc and sparc. How should I handle this > correctly? GTK+ 2 units in same way also only for the above archs. > > Extend arch also for those archs and then try if tuxcmd will compile > also under those architectures? If build depends are not available, you don't care. Just make the package arch: all and builders will handle this. -- Michal Čihař | http://cihar.com | http://blog.cihar.com
Attachment:
signature.asc
Description: PGP signature