Your message dated Tue, 27 Feb 2018 23:19:24 +0530
with message-id <492922ac-bfe3-5bf5-27d1-cbad672bc...@autistici.org>
and subject line Re: ruby-dalli: FTBFS on ruby2.5: "File does not exist:"
has caused the Debian Bug report #888120,
regarding ruby-dalli: FTBFS on ruby2.5: "File does not exist:"
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.)
--
888120: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888120
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-dalli
Version: 2.7.4-1
Severity: important
User: debian-r...@lists.debian.org
Usertags: ruby2.5
Dear Maintainer,
This package fails to build against ruby2.5. Soon, there will
be a transition to ruby2.5, and this package will FTBFS in sid.
There may be some details on the wiki about common problems:
https://wiki.debian.org/Teams/Ruby/Ruby25Transition
I have no idea what's going on here, maybe a gem2deb problem causing it
to not be happy building twice in a row?
Build log excerpt:
...
Finished in 13.066640s, 0.0765 runs/s, 0.0765 assertions/s.
1 runs, 1 assertions, 0 failures, 0 errors, 0 skips
/usr/bin/ruby2.5 /usr/bin/gem2deb-test-runner
┌──────────────────────────────────────────────────────────────────────────────┐
│ Checking Rubygems dependency resolution on ruby2.5 │
└──────────────────────────────────────────────────────────────────────────────┘
GEM_PATH=debian/ruby-dalli/usr/share/rubygems-integration/all:/root/.gem/ruby/2.5.0:/var/lib/gems/2.5.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.5.0:/usr/share/rubygems-integration/2.5.0:/usr/share/rubygems-integration/all
ruby2.5 -e gem\ \"dalli\"
┌──────────────────────────────────────────────────────────────────────────────┐
│ Run tests for ruby2.5 from debian/ruby-tests.rake │
└──────────────────────────────────────────────────────────────────────────────┘
RUBYLIB=/build/ruby-dalli-2.7.4/debian/ruby-dalli/usr/lib/ruby/vendor_ruby:.
GEM_PATH=debian/ruby-dalli/usr/share/rubygems-integration/all:/root/.gem/ruby/2.5.0:/var/lib/gems/2.5.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.5.0:/usr/share/rubygems-integration/2.5.0:/usr/share/rubygems-integration/all
ruby2.5 -S rake -f debian/ruby-tests.rake
/usr/bin/ruby2.5 -w -I"test"
"/usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb" "test/benchmark_test.rb" -v
/build/ruby-dalli-2.7.4/test/helper.rb:13: warning: already initialized
constant WANT_RAILS_VERSION
/build/ruby-dalli-2.7.4/test/helper.rb:13: warning: previous definition of
WANT_RAILS_VERSION was here
/build/ruby-dalli-2.7.4/test/helper.rb:13: warning: already initialized
constant WANT_RAILS_VERSION
/build/ruby-dalli-2.7.4/test/helper.rb:13: warning: previous definition of
WANT_RAILS_VERSION was here
/build/ruby-dalli-2.7.4/test/helper.rb:13: warning: already initialized
constant WANT_RAILS_VERSION
/build/ruby-dalli-2.7.4/test/helper.rb:13: warning: previous definition of
WANT_RAILS_VERSION was here
File does not exist:
rake aborted!
Command failed with status (1): [ruby -w -I"test"
"/usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb" "test/benchmark_test.rb"
-v]
Tasks: TOP => default
(See full trace by running task with --trace)
ERROR: Test "ruby2.5" failed. Exiting.
dh_auto_install: dh_ruby --install /build/ruby-dalli-2.7.4/debian/ruby-dalli
returned exit code 1
debian/rules:6: recipe for target 'binary' failed
make: *** [binary] Error 1
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
Full build log:
https://rbuild.fau.xxx/2018-01-23/ruby-dalli.log
Please fix it!
Cheers,
Chris.
--- End Message ---
--- Begin Message ---
Hi,
Looking at https://ci.debian.net/packages/r/ruby-dalli/unstable/amd64/ ,
it seems the FTBFS was a transient one. Hence closing this issue. If
this happens repeatedly, we shall tackle it.
Regards
Balasankar C
signature.asc
Description: OpenPGP digital signature
--- End Message ---
