Bug#635126: status of ruby 1.9.1 wrt porting
On 29/08/11 at 23:48 +0200, Lucas Nussbaum wrote:
> Hi,
>
> Ruby 1.9.3 is going to be released in september, and is a candidate for
> the default ruby version in wheezy. A snapshot is available in
> experimental. Now is an ideal time to work on porting issues and get the
> fixes integrated upstream. Ruby has a fairly large test suite, which
> makes finding problems easy, but exercises the threading library in
> interesting ways.
>
> Most of the issues are reproducible by re-building the Debian package.
> Use make && make test to get a shorter build.
>
> Here is the current complete list of issues I'm aware of. My time will
> be very limited in the coming weeks, but I will try my best to provide
> help.
Hi,
I've uploaded a new version of ruby1.9.1. It's still a pre-release
snapshot of 1.9.3, and there's no real clear plan from upstream for the
final release.
> [armel,sparc] FTBFS due to miscompilation with -ftree-sra (inc. in -O3).
> See http://bugs.debian.org/635126.
> Currently worked-around by using -fno-tree-sra.
> Other packages might be affected.
> -> FIXED from ruby1.9.1's POV, but you really want to look at this
> for other packages.
No progress on #635126, but does not affect Ruby anymore.
> [armel] I've just seen that now that this one is fixed, the test suite
> segfaults.
> See
> https://buildd.debian.org/status/fetch.php?pkg=ruby1.9.1&arch=armel&ver=1.9.3~preview1%2Bsvn33077-1&stamp=1314634969
> search for 'TestFiber#test_many_fibers'.
> 'make test-all' to reproduce. Failures during test-all are currently not
> fatal. The remaining ones needs more investigation, but I don't think
> that they are arch-specific. I'd like to make test-all failures fatal at
> some point.
Builds fine now, I don't know if it's just luck.
> [sparc] continuations are completely broken.
> See http://redmine.ruby-lang.org/issues/5244 (minimal test case
> included)
There has been some discussions on the upstream bug, but no solution
yet.
> [ia64] crashes during test suite, linked to continuations according to
> backtrace.
> See http://redmine.ruby-lang.org/issues/5246. 'make test' to reproduce.
> Might be related to the sparc problem above.
No progress on the upstream bug.
> [kfreebsd] waitpid from threads problem
> http://redmine.ruby-lang.org/issues/5239
> http://bugs.debian.org/639658
> Will add a patch in test suite runner to work-around this
> -> FIXED from ruby1.9.1's POV.
The patch won't be merged upstream, but we can carry it in the Debian
package.
> [kfreebsd] mmap() with MAP_STACK requires non-null first arg
> http://redmine.ruby-lang.org/issues/5241
> http://www.FreeBSD.org/cgi/query-pr.cgi?pr=158755
> patch will be applied upstream, added to Debian package in the meantime
> -> FIXED from ruby1.9.1's POV.
patch merged upstream, removed from Debian package.
> [kfreebsd] thread-related hangs
> http://redmine.ruby-lang.org/issues/5240
> bisected the upstream commit.
> Petr Salinger working on a fix, see
> http://lists.debian.org/debian-bsd/2011/08/msg00180.html
progress on the upstream bug, no solution yet.
I'm planning to upload 1.9.3 to unstable as soon as it is released. This
release is much better than 1.9.2 (that we currently have in unstable and
testing). Also, it is likely that 1.9.3 ends up being the default Ruby
release in wheezy.
At this point, Ruby 1.9.3 is not in a releasable state on:
- ia64
- sparc
- kfreebsd-*
On those architectures, it's still possible to disable the test suite, to
allow (partially broken) packages to be built.
Lucas
Reply to: