Source: ruby-warden
Version: 1.2.8-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: [email protected]
Usertags: ftbfs-20250128 ftbfs-trixie

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
>      Failure/Error: app = setup_rack(app, :session => 
> Rack::Session::Pool).to_app
> 
>      NameError:
>        uninitialized constant Rack::Session
>      # ./spec/warden/proxy_spec.rb:253:in `block (3 levels) in <top 
> (required)>'
> 
> Finished in 0.21056 seconds (files took 0.24876 seconds to load)
> 224 examples, 2 failures, 1 pending
> 
> Failed examples:
> 
> rspec ./spec/warden/proxy_spec.rb:204 # Warden::Proxy authentication should 
> renew session when user is set
> rspec ./spec/warden/proxy_spec.rb:243 # Warden::Proxy authentication should 
> not renew session when user is fetch
> 
> /usr/bin/ruby3.3 
> -I/usr/share/rubygems-integration/all/gems/rspec-support-3.13.1/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.13.0/lib
>  /usr/share/rubygems-integration/all/gems/rspec-core-3.13.0/exe/rspec 
> --pattern ./spec/\*\*/\*_spec.rb failed
> mv ./.gem2deb.Gemfile.lock Gemfile.lock
> ERROR: Test "ruby3.3" failed: 


The full build log is available from:
http://qa-logs.debian.net/2025/01/28/ruby-warden_1.2.8-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20250128;[email protected]
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20250128&[email protected]&allbugs=1&cseverity=1&ctags=1&caffected=1#results

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!

If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.

Reply via email to