Hi On Sun, Mar 15, 2009 at 09:03:03PM +0000, Debian Bug Tracking System wrote: > Processing commands for cont...@bugs.debian.org: > > > # It doesn't work. Binary for powerpc should probably get removed from the > > archive. > > severity 513891 serious > Bug#513891: tuxcmd: Does not run at all > Severity set to `serious' from `important'
I agree with you that tuxcmd in it's current shape should not be "released" for powerpc architecture (but works with i386 and amd64). So serious bug will prevent whole tuxcmd to migrate to testing right (future versions uploaded) What would be the best approach on your point of view for that? My sponsor suggested to me, to not restrict Architecture in debian/control, but at the moment there is no solution to have tuxcmd also working on powerpc architecture. I'm currently not able to solve this, and the Developer of tuxcmd sais that his effort to try support also powerpc architecture failed in past [1]. Any hint, how I should procede? A new version of the fpc will be released end of this week, and then tuxcmd should be retried to build whit the new fpc, but then I need some people with powerpc which could test that again [2]. Bests Salvatore [1] http://lists.debian.org/debian-mentors/2009/02/msg00095.html [2] http://bugs.debian.org/515035
signature.asc
Description: Digital signature
