Your message dated Wed, 02 Mar 2016 08:25:28 +0000
with message-id
<1456907128.1398342.537103850.2d896...@webmail.messagingengine.com>
and subject line Closing dupes of #816482
has caused the Debian Bug report #816483,
regarding ruby-acts-as-list: FTBFS: `require': cannot load such file --
bundler/setup (LoadError)
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.)
--
816483: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816483
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: ruby-acts-as-list
Version: 0.7.2-3
Severity: serious
Justification: fails to build from source
User: [email protected]
Usertags: ftbfs
X-Debbugs-Cc: [email protected]
Dear Maintainer,
ruby-acts-as-list fails to build from source in unstable/amd64:
[..]
RUBYLIB=/home/lamby/temp/cdt.20160302081131.nOph1DEzhc/ruby-acts-as-list-0.7.2/debian/ruby-acts-as-list/usr/lib/ruby/vendor_ruby:.
GEM_PATH=debian/ruby-acts-as-list/usr/share/rubygems-integration/all:/home/lamby/.gem/ruby/2.2.0:/var/lib/gems/2.2.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.2.0:/usr/share/rubygems-integration/2.2.0:/usr/share/rubygems-integration/2.2:/usr/share/rubygems-integration/all
ruby2.2 -ryaml -e YAML.load_file\(\"debian/ruby-test-files.yaml\"\).each\ \{\
\|f\|\ require\ f\ \}
/usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in `require':
cannot load such file -- bundler/setup (LoadError)
from /usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in
`require'
from
/home/lamby/temp/cdt.20160302081131.nOph1DEzhc/ruby-acts-as-list-0.7.2/test/helper.rb:2:in
`<top (required)>'
from /usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in
`require'
from /usr/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in
`require'
from -e:1:in `block in <main>'
from -e:1:in `each'
from -e:1:in `<main>'
WARNING: Test "ruby2.2" failed, but ignoring this test result.
/usr/bin/ruby2.3 /usr/bin/gem2deb-test-runner
┌──────────────────────────────────────────────────────────────────────────────â”
│ Run tests for ruby2.3 from debian/ruby-test-files.yaml
│
└──────────────────────────────────────────────────────────────────────────────┘
RUBYLIB=/home/lamby/temp/cdt.20160302081131.nOph1DEzhc/ruby-acts-as-list-0.7.2/debian/ruby-acts-as-list/usr/lib/ruby/vendor_ruby:.
GEM_PATH=debian/ruby-acts-as-list/usr/share/rubygems-integration/all:/home/lamby/.gem/ruby/2.3.0:/var/lib/gems/2.3.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.3.0:/usr/share/rubygems-integration/2.3.0:/usr/share/rubygems-integration/all
ruby2.3 -ryaml -e YAML.load_file\(\"debian/ruby-test-files.yaml\"\).each\ \{\
\|f\|\ require\ f\ \}
/usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require':
cannot load such file -- bundler/setup (LoadError)
from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in
`require'
from
/home/lamby/temp/cdt.20160302081131.nOph1DEzhc/ruby-acts-as-list-0.7.2/test/helper.rb:2:in
`<top (required)>'
from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in
`require'
from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in
`require'
from -e:1:in `block in <main>'
from -e:1:in `each'
from -e:1:in `<main>'
ERROR: Test "ruby2.3" failed. Exiting.
dh_auto_install: dh_ruby --install
/home/lamby/temp/cdt.20160302081131.nOph1DEzhc/ruby-acts-as-list-0.7.2/debian/ruby-acts-as-list
returned exit code 1
debian/rules:16: recipe for target 'binary' failed
make: *** [binary] Error 1
[..]
The full build log is attached.
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` [email protected] / chris-lamb.co.uk
`-
--- End Message ---
--- Begin Message ---
Argh, so sorry. If my mail client disconnects from the internet, it will send
multiple copies for some bizarre reason. :(
--- End Message ---
