Re: Please give back ruby1.9/1.9.0.2-9 on hppa and alpha

2009-02-09 Thread dann frazier
On Mon, Feb 09, 2009 at 06:20:41PM +0100, Lucas Nussbaum wrote: > On 09/02/09 at 16:33 +0100, Adeodato Sim? wrote: > > * dann frazier [Mon, 09 Feb 2009 08:26:40 -0700]: > > > > > On Mon, Feb 09, 2009 at 02:25:10PM +0100, Adeodato Sim?? wrote: > > > > Please upload a manual build this time. If you'

Re: Please give back ruby1.9/1.9.0.2-9 on hppa and alpha

2009-02-09 Thread Lucas Nussbaum
On 09/02/09 at 16:33 +0100, Adeodato Simó wrote: > * dann frazier [Mon, 09 Feb 2009 08:26:40 -0700]: > > > On Mon, Feb 09, 2009 at 02:25:10PM +0100, Adeodato Sim?? wrote: > > > Please upload a manual build this time. If you're in a position to do > > > the same for hppa, please do that as well, el

Re: Please give back ruby1.9/1.9.0.2-9 on hppa and alpha

2009-02-09 Thread dann frazier
On Mon, Feb 09, 2009 at 02:25:10PM +0100, Adeodato Sim?? wrote: > * Lucas Nussbaum [Thu, 05 Feb 2009 14:43:40 +0100]: > > > On 05/02/09 at 14:12 +0100, Adeodato Sim?? wrote: > > > * Lucas Nussbaum [Mon, 02 Feb 2009 19:04:48 +0100]: > > > > > On alpha, there's a segfault during the build. Manual b

Re: Please give back ruby1.9/1.9.0.2-9 on hppa and alpha

2009-02-09 Thread Adeodato Simó
* dann frazier [Mon, 09 Feb 2009 08:26:40 -0700]: > On Mon, Feb 09, 2009 at 02:25:10PM +0100, Adeodato Sim?? wrote: > > Please upload a manual build this time. If you're in a position to do > > the same for hppa, please do that as well, else we'll migrate ruby1.9 -9 > > without hppa. > > Please r

Re: Please give back ruby1.9/1.9.0.2-9 on hppa and alpha

2009-02-09 Thread Adeodato Simó
* Lucas Nussbaum [Thu, 05 Feb 2009 14:43:40 +0100]: > On 05/02/09 at 14:12 +0100, Adeodato Simó wrote: > > * Lucas Nussbaum [Mon, 02 Feb 2009 19:04:48 +0100]: > > > On alpha, there's a segfault during the build. Manual builds on porter > > > machines do work, though. > > Failed again with the sa

Re: Please give back ruby1.9/1.9.0.2-9 on hppa and alpha

2009-02-06 Thread dann frazier
On Thu, Feb 05, 2009 at 04:51:15PM -0700, dann frazier wrote: > On Thu, Feb 05, 2009 at 09:00:43PM +0100, Helge Deller wrote: > > dann frazier wrote: > > > On Mon, Feb 02, 2009 at 07:04:48PM +0100, Lucas Nussbaum wrote: > > >> ruby1.9 still fails to build on hppa and alpha. > > >> > > >> On hppa, i

Re: Please give back ruby1.9/1.9.0.2-9 on hppa and alpha

2009-02-05 Thread dann frazier
On Thu, Feb 05, 2009 at 09:00:43PM +0100, Helge Deller wrote: > dann frazier wrote: > > On Mon, Feb 02, 2009 at 07:04:48PM +0100, Lucas Nussbaum wrote: > >> ruby1.9 still fails to build on hppa and alpha. > >> > >> On hppa, it's caused by a kernel bug, which was partially fixed (at > >> least the k

Re: Please give back ruby1.9/1.9.0.2-9 on hppa and alpha

2009-02-05 Thread Helge Deller
dann frazier wrote: > On Mon, Feb 02, 2009 at 07:04:48PM +0100, Lucas Nussbaum wrote: >> ruby1.9 still fails to build on hppa and alpha. >> >> On hppa, it's caused by a kernel bug, which was partially fixed (at >> least the kernel doesn't panic() anymore). Since the issue is related to >> threading

Re: Please give back ruby1.9/1.9.0.2-9 on hppa and alpha

2009-02-05 Thread Lucas Nussbaum
On 05/02/09 at 14:12 +0100, Adeodato Simó wrote: > * Lucas Nussbaum [Mon, 02 Feb 2009 19:04:48 +0100]: > > > On alpha, there's a segfault during the build. Manual builds on porter > > machines do work, though. > > Failed again with the same exact segfault. Do you want me to upload a manual build

Re: Please give back ruby1.9/1.9.0.2-9 on hppa and alpha

2009-02-05 Thread Adeodato Simó
* Lucas Nussbaum [Mon, 02 Feb 2009 19:04:48 +0100]: > On alpha, there's a segfault during the build. Manual builds on porter > machines do work, though. Failed again with the same exact segfault. -- Adeodato Simó dato at net.com.org.es Debian Developer

Re: Please give back ruby1.9/1.9.0.2-9 on hppa and alpha

2009-02-02 Thread dann frazier
On Mon, Feb 02, 2009 at 07:04:48PM +0100, Lucas Nussbaum wrote: > Hi, hey Lucas! > ruby1.9 still fails to build on hppa and alpha. > > On hppa, it's caused by a kernel bug, which was partially fixed (at > least the kernel doesn't panic() anymore). Since the issue is related to > threading, it is