Your message dated Mon, 12 May 2014 14:07:08 -0300
with message-id <[email protected]>
and subject line Re: Bug#746108: pry: FTBFS: ERROR: Test "ruby2.0" failed
has caused the Debian Bug report #746108,
regarding pry: FTBFS: ERROR: Test "ruby2.0" failed
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 [email protected]
immediately.)
--
746108: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746108
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: pry
Version: 0.9.12.6-1
Severity: serious
Tags: jessie sid
User: [email protected]
Usertags: qa-ftbfs-20140426 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully):
> Bacon::Error: "bigdecimal (1.2.0)\nio-console (0.4.2)\njson
> (1.7.7)\nmetaclass (0.0.4)\nminitest (4.3.2)\nmocha (1.0.0)\npsych
> (2.0.0)\nrake (0.9.6)\nrdoc (4.0.0)\nslop (3.4.7)\ntest-unit
> (2.0.0.0)\n".=~(/bacon \(/) failed
> /«PKGBUILDDIR»/spec/commands/gem_list_spec.rb:14:in `block (2 levels)
> in <top (required)>': gem-list - should work arglessly
> /«PKGBUILDDIR»/spec/commands/gem_list_spec.rb:11:in `block in <top
> (required)>'
> /«PKGBUILDDIR»/spec/commands/gem_list_spec.rb:3:in `<top (required)>'
>
> 980 tests, 1401 assertions, 1 failures, 0 errors
> debian/ruby-tests.rb:1:in `<main>': unhandled exception
> ERROR: Test "ruby2.0" failed:
The full build log is available from:
http://aws-logs.debian.net/ftbfs-logs/2014/04/26/pry_0.9.12.6-1_unstable.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
On Sun, Apr 27, 2014 at 02:19:16PM +0200, David Suárez wrote:
> Source: pry
> Version: 0.9.12.6-1
> Severity: serious
> Tags: jessie sid
> User: [email protected]
> Usertags: qa-ftbfs-20140426 qa-ftbfs
> Justification: FTBFS on amd64
>
> Hi,
>
> During a rebuild of all packages in sid, your package failed to build on
> amd64.
>
> Relevant part (hopefully):
> > Bacon::Error: "bigdecimal (1.2.0)\nio-console (0.4.2)\njson
> > (1.7.7)\nmetaclass (0.0.4)\nminitest (4.3.2)\nmocha (1.0.0)\npsych
> > (2.0.0)\nrake (0.9.6)\nrdoc (4.0.0)\nslop (3.4.7)\ntest-unit
> > (2.0.0.0)\n".=~(/bacon \(/) failed
> > /«PKGBUILDDIR»/spec/commands/gem_list_spec.rb:14:in `block (2 levels)
> > in <top (required)>': gem-list - should work arglessly
> > /«PKGBUILDDIR»/spec/commands/gem_list_spec.rb:11:in `block in <top
> > (required)>'
> > /«PKGBUILDDIR»/spec/commands/gem_list_spec.rb:3:in `<top (required)>'
> >
> > 980 tests, 1401 assertions, 1 failures, 0 errors
> > debian/ruby-tests.rb:1:in `<main>': unhandled exception
> > ERROR: Test "ruby2.0" failed:
This was caused by ruby-bacon only having gemspecs for 1.8 and 1.9.1. I
have uploaded a new version of ruby-bacon built against a recent
gem2deb.
After that, tests failed under ruby2.1 because ruby-slop didn't have 2.1
gemspecs. I uploaded a new upstream version for ruby-slow.
With these new ruby-bacon and ruby-slop, pry builds just fine.
--
Antonio Terceiro <[email protected]>
http://softwarelivre.org/terceiro
signature.asc
Description: Digital signature
--- End Message ---
