Am 16.06.2012 14:16, schrieb Julien Cristau: > On Sat, Jun 16, 2012 at 14:11:34 +0200, Tobias Hansen wrote: > >> Am 16.06.2012 13:49, schrieb Julien Cristau: >>> On Wed, Jun 13, 2012 at 09:28:25 +0200, Tobias Hansen wrote: >>> >>>> allegro4.4 is now a migration candidate and I didn't get access >>>> to a porterbox yet. Can we continue the transition? >>>> >>> I don't think so. Either that FTBFS gets fixed, or the transition >>> gets reverted, AFAICT. >>> >>> Cheers, Julien >> >> Even if allegro4.2 has the same bug? The last time it was built on >> ia64 was a year ago with gcc 4.4.5 and since the changes between >> allegro4.2 and allegro4.4 are not that big, chances are that >> allegro4.2 doesn't built there anymore either. >> > hmm, no, in that case if the bug can't get fixed we'd have to remove all > allegro reverse dependencies on ia64.
How do we find out? Would you issue a rebuild of allegro4.2 on ia64? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org