On Fri, Jul 10, 2009 at 16:28:12 +0100, something...@sodium.serveirc.com wrote:
So it turns out the main bug does not affect amd64 (or more generally,
roughly systems where (LONG_MAX2) = INT_MAX).
There are at least two bugs in the tag comparison:
- Assumes number equality is the same as
Public bug reported:
Please sync librspec-ruby 1.3.0-3 (universe) from Debian unstable (main)
as it fixes tests failures during build
Changelog entries since current maverick version 1.3.0-2:
librspec-ruby (1.3.0-3) unstable; urgency=low
* Added support for Ruby 1.9.2 which introduced some
Public bug reported:
Please sync libsexp-processor-ruby 3.0.4-2 (universe) from Debian
unstable (main) as it fixes tests failure problem during build
Changelog entries since current maverick version 3.0.4-1:
libsexp-processor-ruby (3.0.4-2) unstable; urgency=low
* Load tests with absolute
** Changed in: librspec-ruby (Ubuntu)
Importance: Undecided = Wishlist
** Changed in: librspec-ruby (Ubuntu)
Status: New = Fix Committed
--
Sync librspec-ruby 1.3.0-3 (universe) from Debian unstable (main)
https://bugs.launchpad.net/bugs/632900
You received this bug notification
This bug was fixed in the package librspec-ruby - 1.3.0-3
---
librspec-ruby (1.3.0-3) unstable; urgency=low
* Added support for Ruby 1.9.2 which introduced some breaking changes like no
'.' in the LOAD_PATH or requiring to pass blocks with a parameter to
instance_eval
Julien Cristau dijo [Wed, Sep 08, 2010 at 10:51:26AM +0200]:
On Fri, Jul 10, 2009 at 16:28:12 +0100, something...@sodium.serveirc.com
wrote:
So it turns out the main bug does not affect amd64 (or more generally,
roughly systems where (LONG_MAX2) = INT_MAX).
There are at least two
