Your message dated Tue, 20 Dec 2022 21:08:35 +0100
with message-id <Y6IWQ2q+17b2S/r...@xanadu.blop.info>
and subject line Re: Bug#1011685: ruby-openid-connect: FTBFS: ERROR: Test
"ruby3.0" failed: Failure/Error:
has caused the Debian Bug report #1011685,
regarding ruby-openid-connect: FTBFS: ERROR: Test "ruby3.0" failed:
Failure/Error:
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.)
--
1011685: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011685
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-openid-connect
Version: 1.2.0-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220525 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> Failure/Error:
> expect do
> klass.decode self_issued, :self_issued
> end.not_to raise_error
>
> expected no Exception, got #<OpenSSL::PKey::PKeyError: rsa#set_key= is
> incompatible with OpenSSL 3.0> with backtrace:
> #
> /usr/share/rubygems-integration/all/gems/json-jwt-1.13.0/lib/json/jwk.rb:106:in
> `set_key'
> #
> /usr/share/rubygems-integration/all/gems/json-jwt-1.13.0/lib/json/jwk.rb:106:in
> `to_rsa_key'
> #
> /usr/share/rubygems-integration/all/gems/json-jwt-1.13.0/lib/json/jwk.rb:43:in
> `to_key'
> #
> /usr/share/rubygems-integration/all/gems/json-jwt-1.13.0/lib/json/jose.rb:27:in
> `with_jwk_support'
> #
> /usr/share/rubygems-integration/all/gems/json-jwt-1.13.0/lib/json/jws.rb:124:in
> `valid?'
> #
> /usr/share/rubygems-integration/all/gems/json-jwt-1.13.0/lib/json/jws.rb:26:in
> `verify!'
> # ./lib/openid_connect/response_object/id_token.rb:79:in
> `decode_self_issued'
> # ./lib/openid_connect/response_object/id_token.rb:68:in `decode'
> # ./spec/openid_connect/response_object/id_token_spec.rb:263:in
> `block (7 levels) in <top (required)>'
> # ./spec/openid_connect/response_object/id_token_spec.rb:262:in
> `block (6 levels) in <top (required)>'
> # ./spec/openid_connect/response_object/id_token_spec.rb:262:in `block
> (6 levels) in <top (required)>'
>
> Finished in 13.15 seconds (files took 1.19 seconds to load)
> 234 examples, 2 failures, 2 pending
>
> Failed examples:
>
> rspec ./spec/openid_connect/discovery/provider/config/response_spec.rb:98 #
> OpenIDConnect::Discovery::Provider::Config::Response#public_keys
> rspec ./spec/openid_connect/response_object/id_token_spec.rb:261 #
> OpenIDConnect::ResponseObject::IdToken.decode when self-issued when valid
> when key == :self_issued is expected not to raise Exception
>
> /usr/bin/ruby3.0
> -I/usr/share/rubygems-integration/all/gems/rspec-support-3.10.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/lib
> /usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/exe/rspec
> --pattern ./spec/\*\*/\*_spec.rb --format documentation failed
> ERROR: Test "ruby3.0" failed:
The full build log is available from:
http://qa-logs.debian.net/2022/05/25/ruby-openid-connect_1.2.0-2_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220525;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20220525&fusertaguser=lu...@debian.org&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 marking 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.
--- End Message ---
--- Begin Message ---
I cannot reproduce this anymore => closing
--- End Message ---
