On Fri, Dec 07, 2012 at 10:21:57PM +0100, Stephan Schreiber wrote:
I took a look at this a few weeks ago.
The problem is the code in the cont.c file which implements continuations.
A thread saves its own stack and its thread context itself while it
is running. The ruby programmers believe
Control: tag 653582 wheezy-ignore
Control: tag 593141 wheezy-ignore
On Sat, Dec 8, 2012 at 11:11:56 -0300, Antonio Terceiro wrote:
On Fri, Dec 07, 2012 at 10:21:57PM +0100, Stephan Schreiber wrote:
For now I'd prefer the 'wheezy-ignore' rather than removing the ia64
ruby package.
Looks
Processing control commands:
tag 653582 wheezy-ignore
Bug #653582 [ruby1.9.1] Segfaults when running ruby-hpricot's test suite on ia64
Added tag(s) wheezy-ignore.
tag 593141 wheezy-ignore
Bug #593141 [src:ruby1.9.1] ruby1.9.1: FTBFS on ia64: test suite segfaults
Added tag(s) wheezy-ignore.
--
Processing control commands:
tag 653582 wheezy-ignore
Bug #653582 [ruby1.9.1] Segfaults when running ruby-hpricot's test suite on ia64
Ignoring request to alter tags of bug #653582 to the same tags previously set
tag 593141 wheezy-ignore
Bug #593141 [src:ruby1.9.1] ruby1.9.1: FTBFS on ia64:
I took a look at this a few weeks ago.
The problem is the code in the cont.c file which implements continuations.
A thread saves its own stack and its thread context itself while it is
running. The ruby programmers believe that that the saved info can be
used by another thread to switch
On Mon, 16 Jan 2012 21:20:07 +0100
Lucas Nussbaum lu...@debian.org wrote:
Dear release team, at some point before the wheezy release, we need to
decide what to do with Ruby 1.9.X on ia64. It has been broken for
months, and hasn't seen any activity in Debian (#539141) or upstream
On Thu, Dec 6, 2012 at 10:22:00 +0100, Michael Stapelberg wrote:
On Mon, 16 Jan 2012 21:20:07 +0100
Lucas Nussbaum lu...@debian.org wrote:
Dear release team, at some point before the wheezy release, we need to
decide what to do with Ruby 1.9.X on ia64. It has been broken for
months, and
Michael Stapelberg dijo [Thu, Dec 06, 2012 at 10:22:00AM +0100]:
On Mon, 16 Jan 2012 21:20:07 +0100
Lucas Nussbaum lu...@debian.org wrote:
Dear release team, at some point before the wheezy release, we need to
decide what to do with Ruby 1.9.X on ia64. It has been broken for
months, and
What is broken about it? Has anyone estimated how much effort it would take
to fix? Are we talking needing assembly language bindings or just some dumb
SIGBUS error?
Patrick Baggett
On Thu, Dec 6, 2012 at 11:37 AM, Gunnar Wolf gw...@gwolf.org wrote:
Michael Stapelberg dijo [Thu, Dec 06, 2012
On Thu, Dec 06, 2012 at 06:13:31PM +0100, Julien Cristau wrote:
On Thu, Dec 6, 2012 at 10:22:00 +0100, Michael Stapelberg wrote:
On Mon, 16 Jan 2012 21:20:07 +0100
Lucas Nussbaum lu...@debian.org wrote:
Dear release team, at some point before the wheezy release, we need to
decide
On Mon, Sep 03, 2012 at 09:51:28PM +0200, Lucas Nussbaum wrote:
On 16/01/12 at 21:20 +0100, Lucas Nussbaum wrote:
ruby1.9.1 is known to be broken on ia64 (see #593141). It currently
builds only because the test suite is disabled on that architecture, but
the fact that other Ruby packages
On Mon, Sep 3, 2012 at 21:51:28 +0200, Lucas Nussbaum wrote:
On 16/01/12 at 21:20 +0100, Lucas Nussbaum wrote:
ruby1.9.1 is known to be broken on ia64 (see #593141). It currently
builds only because the test suite is disabled on that architecture, but
the fact that other Ruby packages
On 16/01/12 at 21:20 +0100, Lucas Nussbaum wrote:
ruby1.9.1 is known to be broken on ia64 (see #593141). It currently
builds only because the test suite is disabled on that architecture, but
the fact that other Ruby packages fail to build on ia64 doesn't surprise
me.
Dear release team, at
13 matches
Mail list logo