Source: ruby-warden
Version: 1.2.3-1
Severity: serious
Justification: fails to build from source
Tags: sid stretch
User: [email protected]
Usertags: ftbfs
X-Debbugs-CC: [email protected]
Dear Maintainer,
The package fails to build:
Failures:
1) Warden::Config should allow to silence missing strategies
Failure/Error: @config.silence_missing_strategies?.should be_true
expected true to respond to `true?` or perhaps you meant `be true` or
`be_truthy`
# ./spec/warden/config_spec.rb:29:in `block (2 levels) in <top (required)>'
2) standard authentication hooks after_set_user should allow me to add an
after_set_user hook
Failure/Error: RAM._after_set_user.should have(1).item
NoMethodError:
undefined method `have' for
#<RSpec::ExampleGroups::StandardAuthenticationHooks::AfterSetUser:0x000000019b89c0>
# ./spec/warden/hooks_spec.rb:24:in `block (3 levels) in <top (required)>'
3) standard authentication hooks after_set_user should allow me to add
multiple after_set_user hooks
Failure/Error: RAM._after_set_user.should have(2).items
NoMethodError:
undefined method `have' for
#<RSpec::ExampleGroups::StandardAuthenticationHooks::AfterSetUser:0x000000019b6ee0>
# ./spec/warden/hooks_spec.rb:30:in `block (3 levels) in <top (required)>'
4) standard authentication hooks after_set_user after_authentication should
allow me to log out a user in an after_set_user block
Failure/Error: env['warden'].authenticated?.should be_false
expected false to respond to `false?` or perhaps you meant `be false` or
`be_falsey`
# ./spec/warden/hooks_spec.rb:130:in `block (4 levels) in <top (required)>'
...
215 examples, 14 failures
Full build log:
https://reproducible.debian.net/rb-pkg/unstable/amd64/ruby-warden.html
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.19.0-23-generic (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
