I'm now sure, that this bug is caused by changes between Ruby 1.8.7.72 and
1.8.7.174, which produce a problem with libparsetree-ruby. The latest
upstream version of libparsetree would help, but it would introduce a new
package.
Packaging sexp_processor, which was split off from ParseTree seems to
Lucas Nussbaum wrote:
> During a rebuild of all packages in sid, your package failed to build on
> amd64.
This somehow must be caused by changes in ruby1.8, because as far as I can
see, all other dependent packages haven't changed. For some reason now an
object id seems to appear in the parse tre
Package: libheckle-ruby
Version: 1.4.2-1
Severity: serious
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20090620 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part:
> make[1]: Entering directory
> `/bui
3 matches
Mail list logo
