Christian Hofstaedtler <z...@debian.org> writes: > During a test rebuild your package failed to build. The test rebuild > was done using sbuild, in unstable.
> The build produced this output: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > util/network/client.....FAILED 21-22 > util/network/server.....ok > util/tokens.............FAILED 10 > util/vector.............ok > util/xmalloc............skipped (xmalloc tests only run for maintainer) > util/xwrite.............ok Hm. Those are timing-sensitive tests that can fail on extremely slow systems, but I did have them tweaked so that they pass on all of Debian's buildds. > I notice that this also uses an obsolete version of Ruby (1.9). Please > update your package to use either the meta package (ruby) or ruby2.1. Yeah, I was getting ready to make that change. (There's no way for this package to use the metapackage.) It currently builds against 1.9 and 2.0; I'll change that to build against 2.0 and 2.1 and upload without any changes to the tests and see if the buildds are still happy. If so, I think the FTBFS is spurious. I've been monitoring the progress on the Ruby migration and thought I had a bit of grace period before that became urgent, and was trying to get a new release out, but I'll go ahead and do the packaging changes now and worry about that later. Thanks for the report! -- Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/> -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
