On 13 July 2014 at 04:28, Cyril Brulebois wrote: | Control: severity -1 serious | | Dirk Eddelbuettel <e...@debian.org> (2012-04-01): | > I also ran this by upstream, given that there were some changes to the | > .C() interface in R lately. But upstream couldn't tickle anything | > here either, so I suspect this is s390 / s390x specific. | | In the meanwhile, a successful build happened, so the s390x FTBFS is now | a regression, meaning your package can't migrate. Adjusting severity | accordingly. | | Build history on s390x: | https://buildd.debian.org/status/logs.php?pkg=rggobi&arch=s390x | | (Long story short, 1 single successful build: 2.1.19-2)
Could we just exclude s390x for builds of rggobi? There is little that I can point Michael (upstream; already CC'ed) to. The package fails after successfully compiling and linking when trying to load; that usually means an x11 issue of some sort. Could be a font metric; I have no idea. ggobi (the binary) and rggobi (the R package using it) are pretty stable; it would be a shame to loose either (or just rggobi) from the release over this. But if that were the worst case I could live with that too. This is a somewhat tangential package, and if there are users on s390x they can also install it from CRAN ... Dirk -- http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
