Your message dated Tue, 18 May 2010 21:18:02 +0200
with message-id <20100518191802.ga29...@xanadu.blop.info>
and subject line Re: Bug#565765: ruby1.9.1: FTBFS on sparc
has caused the Debian Bug report #565765,
regarding ruby1.9.1: FTBFS on sparc
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
565765: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=565765
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:ruby1.9.1
Version: 1.9.1.378-1
Severity: serious

Hi,

ruby1.9.1 FTBFS on sparc with the following error:
> make[2]: Leaving directory
> `/build/buildd-ruby1.9.1_1.9.1.378-1-sparc-KMvrBv/ruby1.9.1-1.9.1.378'
> compiling bigdecimal
> Aborted
> make[1]: *** [mkmain.sh] Error 134
> make: *** [debian/stamp-makefile-build] Error 2
> dpkg-buildpackage: error: debian/rules build gave error exit status 2

Also, we have #545345 (ruby1.9.1: test suite fails on sparc). For which
upstream said (in the redmine bug) that Sparc is no supported.

Sparc porters, could you help us investigate this?

This is extremely worrying, because we still need to transition all ruby
1.9.0 packages to 1.9.1 (so we can drop 1.9.0) before the squeeze
release. Not releasing ruby1.9.1 on sparc isn't really an option because
of all the reverse-dependencies.
-- 
| Lucas Nussbaum
| lu...@lucas-nussbaum.net   http://www.lucas-nussbaum.net/ |
| jabber: lu...@nussbaum.fr             GPG: 1024D/023B3F4F |



--- End Message ---
--- Begin Message ---
Version: 1.9.1.378-3

Miraculously, it was built fine on schroeder.
-- 
| Lucas Nussbaum
| lu...@lucas-nussbaum.net   http://www.lucas-nussbaum.net/ |
| jabber: lu...@nussbaum.fr             GPG: 1024D/023B3F4F |


--- End Message ---

Reply via email to