[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

How handle Architecture when package is restricted/limited to only some archs?


tuxcmd is currently by upsteam "restricted" to the Architectures i386
and x86_64. [1]. As suggested in a previous thread I had put 
	Architecture: any

in the control file, and now I'm having the following situation: On
powerpc all Build-Depends are satisfied, and also the package get's
build, but tuxcmd will not work at all on this architecture.

Are there any policy about that, if I should explicitely list only
i386, amd64 and source there? I have not found a hint on that on
policy 5.6.8, it says there that "Specifying a list of architectures
indicates that the source will build an architecture-dependent
package, and will only work correctly on the listed architectures." So
I assume I should switch to listing the supported archs?

Thanks in advance
Kind regards

[1] https://bugzilla.redhat.com/show_bug.cgi?id=449367

  oo|  Debian GNU/Linux -- The power of freedom ---------------------- 
 /`'\  GPG key ID: 0x518DA394        http://arda.homelinux.org/~salvi/
(\_;/) Fingerprint: 346C D422 1366 FA52 D898  5666 BD45 6753 518D A394

Attachment: signature.asc
Description: Digital signature

Reply to: