Your message dated Thu, 20 Nov 2014 22:38:33 +0100
with message-id <5192114.3rvSZcCLhs@sephirot>
and subject line pry: FTBFS in jessie: ERROR: Test "ruby2.1" failed:
Bacon::Error: /\* $/.===("[1] pry(main)* ") failed
has caused the Debian Bug report #768723,
regarding pry: FTBFS in jessie: ERROR: Test "ruby2.1" failed: Bacon::Error: /\*
$/.===("[1] pry(main)* ") 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 ow...@bugs.debian.org
immediately.)
--
768723: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768723
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pry
Version: 0.10.1-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20141108 qa-ftbfs
Justification: FTBFS in jessie on amd64
Hi,
During a rebuild of all packages in jessie (in a jessie chroot, not a
sid chroot), your package failed to build on amd64.
Relevant part (hopefully):
> Bacon::Error: /\* $/.===("[1] pry(main)* ") failed
> /«PKGBUILDDIR»/spec/spec_helpers/repl_tester.rb:75:in `prompt':
> eval_string and binding_stack - should immediately evaluate eval_string after
> cmd if complete
> /«PKGBUILDDIR»/spec/pry_repl_spec.rb:93:in `block (4 levels) in <top
> (required)>'
> /«PKGBUILDDIR»/spec/spec_helpers/repl_tester.rb:36:in `instance_eval'
> /«PKGBUILDDIR»/spec/spec_helpers/repl_tester.rb:36:in `block in start'
> /«PKGBUILDDIR»/spec/spec_helpers/mock_pry.rb:24:in `redirect_pry_io'
> /«PKGBUILDDIR»/spec/spec_helpers/repl_tester.rb:34:in `start'
> /«PKGBUILDDIR»/spec/pry_repl_spec.rb:90:in `block (3 levels) in <top
> (required)>'
> /«PKGBUILDDIR»/spec/pry_repl_spec.rb:81:in `block (2 levels) in <top
> (required)>'
> /«PKGBUILDDIR»/spec/pry_repl_spec.rb:30:in `block in <top (required)>'
> /«PKGBUILDDIR»/spec/pry_repl_spec.rb:3:in `<top (required)>'
>
> 1110 tests, 1628 assertions, 1 failures, 0 errors
> debian/ruby-tests.rb:1:in `<main>': unhandled exception
> ERROR: Test "ruby2.1" failed:
The full build log is available from:
http://aws-logs.debian.net/ftbfs-logs/2014/11/08/pry_0.10.1-1_jessie.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 ---
Hi,
Now builds fine:
Extract from build log (command: sbuild -n -A -s --force-orig-source --apt-
update -d jessie -v pry_0.10.1-1):
> sbuild (Debian sbuild) 0.63.2 (18 Aug 2012) on ip-XXX.XXX.XXX.XXX.us-
west-2.compute.internal
[ ... ]
> Rewriting shebang line of /«PKGBUILDDIR»/debian/pry/usr/bin/pry
> Running tests for ruby2.1 using debian/ruby-tests.rb...
> Ruby v2.1.4 (ruby), Pry v0.10.1, method_source v0.8.2, CodeRay v1.1.0, Slop
v3.6.0
>
......................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................
> 1110 tests, 1630 assertions, 0 failures, 0 errors
> generating gemspec at ${target}
> debian/pry/usr/lib/ruby/vendor_ruby/pry/commands/install_command.rb:
require 'rubygems/dependency_installer' unless defined?
Gem::DependencyInstaller
> debian/pry/usr/lib/ruby/vendor_ruby/pry/commands/gem_install.rb:
require 'rubygems/dependency_installer' unless defined?
Gem::DependencyInstaller
> debian/pry/usr/lib/ruby/vendor_ruby/pry/rubygem.rb: require 'rubygems'
> Found some 'require rubygems' without overrides (see above).
> WARNING: Test "require-rubygems" failed, but ignoring this test result.
I'll reopen it, if it fails again on next rebuilds.
--
David
--- End Message ---
