Your message dated Thu, 24 Feb 2022 01:50:01 +0000
with message-id <e1nn3gb-000giq...@fasolo.debian.org>
and subject line Bug#1005426: fixed in ruby-jwt 2.3.0-1
has caused the Debian Bug report #1005426,
regarding ruby-jwt: FTBFS: ERROR: Test "ruby3.0" failed: Failure/Error:
raise JWT::RequiredDependencyError, "You currently have OpenSSL
#{OpenSSL::VERSION}. PS support requires >= 2.1"
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.)
--
1005426: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005426
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-jwt
Version: 2.2.2-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220212 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> Failure/Error: raise JWT::RequiredDependencyError, "You currently have
> OpenSSL #{OpenSSL::VERSION}. PS support requires >= 2.1"
>
> JWT::RequiredDependencyError:
> You currently have OpenSSL 3.0.0. PS support requires >= 2.1
> # ./lib/jwt/algos/ps.rb:35:in `require_openssl!'
> # ./lib/jwt/algos/ps.rb:11:in `sign'
> # ./lib/jwt/signature.rb:37:in `sign'
> # ./lib/jwt/encode.rb:57:in `encode_signature'
> # ./lib/jwt/encode.rb:34:in `encoded_signature'
> # ./lib/jwt/encode.rb:20:in `segments'
> # ./lib/jwt.rb:24:in `encode'
> # ./spec/jwt_spec.rb:225:in `block (4 levels) in <top (required)>'
>
> Finished in 0.80869 seconds (files took 0.13885 seconds to load)
> 160 examples, 13 failures
>
> Failed examples:
>
> rspec ./spec/integration/readme_examples_spec.rb:71 # README.md code test
> algorithm usage RSASSA-PSS
> rspec './spec/jwt_spec.rb[1:14:2]' # JWT alg: PS256 should decode a valid
> token
> rspec './spec/jwt_spec.rb[1:14:4]' # JWT alg: PS256 wrong key and verify =
> false should not raise JWT::DecodeError
> rspec './spec/jwt_spec.rb[1:14:3]' # JWT alg: PS256 wrong key should raise
> JWT::DecodeError
> rspec './spec/jwt_spec.rb[1:14:1]' # JWT alg: PS256 should generate a valid
> token
> rspec './spec/jwt_spec.rb[1:15:1]' # JWT alg: PS384 should generate a valid
> token
> rspec './spec/jwt_spec.rb[1:15:4]' # JWT alg: PS384 wrong key and verify =
> false should not raise JWT::DecodeError
> rspec './spec/jwt_spec.rb[1:15:2]' # JWT alg: PS384 should decode a valid
> token
> rspec './spec/jwt_spec.rb[1:15:3]' # JWT alg: PS384 wrong key should raise
> JWT::DecodeError
> rspec './spec/jwt_spec.rb[1:16:2]' # JWT alg: PS512 should decode a valid
> token
> rspec './spec/jwt_spec.rb[1:16:3]' # JWT alg: PS512 wrong key should raise
> JWT::DecodeError
> rspec './spec/jwt_spec.rb[1:16:1]' # JWT alg: PS512 should generate a valid
> token
> rspec './spec/jwt_spec.rb[1:16:4]' # JWT alg: PS512 wrong key and verify =
> false should not raise JWT::DecodeError
>
> Randomized with seed 63633
>
> /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 failed
> ERROR: Test "ruby3.0" failed:
The full build log is available from:
http://qa-logs.debian.net/2022/02/12/ruby-jwt_2.2.2-1_unstable.log
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 ---
Source: ruby-jwt
Source-Version: 2.3.0-1
Done: Antonio Terceiro <terce...@debian.org>
We believe that the bug you reported is fixed in the latest version of
ruby-jwt, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1005...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Antonio Terceiro <terce...@debian.org> (supplier of updated ruby-jwt package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Format: 1.8
Date: Wed, 23 Feb 2022 21:37:45 -0300
Source: ruby-jwt
Architecture: source
Version: 2.3.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Team
<pkg-ruby-extras-maintain...@lists.alioth.debian.org>
Changed-By: Antonio Terceiro <terce...@debian.org>
Closes: 1005426
Changes:
ruby-jwt (2.3.0-1) unstable; urgency=medium
.
* Team upload
.
[ Antonio Terceiro ]
* New upstream version 2.3.0
* Drop all patches (not needed anymore)
* Add upstream patch to fix openssl version check (Closes: #1005426)
* Build-Depends: add ruby-simplecov to avoid a patch
* Bump Standards-Version to 4.6.0; no changes needed
* debian/ruby-tests.rake: update from template
* debian/rules: update from template.
Install using rubygems layout
* debian/upstream/metadata: update from template
* debian/control: update from template
Checksums-Sha1:
642a3cb0db52ba71683a03dbbb24cdeff20e89de 2054 ruby-jwt_2.3.0-1.dsc
8446e093803dd0b1bbabd1a6b3d05f35e52b69ba 53312 ruby-jwt_2.3.0.orig.tar.gz
52551e5acb74cfa6ede85ea8b02a8bb55f28d456 4084 ruby-jwt_2.3.0-1.debian.tar.xz
0ccf100fcbad81c821a963229741c49cee50dab3 9663 ruby-jwt_2.3.0-1_amd64.buildinfo
Checksums-Sha256:
78cccfd597fa5d7e330063bfefece19dce03b89358134fcf09a4e01a9b6edd02 2054
ruby-jwt_2.3.0-1.dsc
159b45de990f589d38338e915a94ec1eb0de0d8bd25ca6acd5ad514baea411f0 53312
ruby-jwt_2.3.0.orig.tar.gz
1cc59095f1114ccf238533c100771ce4e3ba57a026e1db095af6fd19715e54cc 4084
ruby-jwt_2.3.0-1.debian.tar.xz
e90b0a8d45c3948d333784cbba97fc92914237cb98606706a4715994c5815a9e 9663
ruby-jwt_2.3.0-1_amd64.buildinfo
Files:
d96727fd0cd189be148d864a5b209d25 2054 ruby optional ruby-jwt_2.3.0-1.dsc
816555e818447e012f46590f0df659a5 53312 ruby optional ruby-jwt_2.3.0.orig.tar.gz
8b26d241c2a8047c3a88a7b58d190497 4084 ruby optional
ruby-jwt_2.3.0-1.debian.tar.xz
a5fb8c500bab8e7ae4048d0ac36a4b19 9663 ruby optional
ruby-jwt_2.3.0-1_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEEst7mYDbECCn80PEM/A2xu81GC94FAmIW3pgACgkQ/A2xu81G
C97Q+RAAzN9X75HxKTTxNGGgutA5cI5uXGBWePSSQzNcOuKHYaw+ITrPBjzNCN7G
gFRmAbXE9yM6Wrtjcq4brPNQCReiq/R3O7QlqRfbx+2sqkw8jM7/+Xe6g54SVXdQ
ZghMre/KUNB8T6DICDXvG2U+mEaewwHf3f4gbYKaQ30hUWaEcexv+OgDV6UjVNox
BIYpqtrz+T5MgyVVeUrzzkaukD6f/6c9FShWUu9zoKYNFPfSwzKqf3/G9kxrfwsZ
iET7qusX7yxW5kWwXDJIat9lmqD1GxsmIqbFAC1kriGcawqtIkG+HZFurUa+M0wg
cX2L2gN1RzpUjUCDoFm4klcvJBPzB/7ygzkK9hRR/9Ilw3JN8HUyUC0uaC/8S9NC
H6iYH+1acdkZIsc4MNsK9LvDDbhxnh70h+VEGN577j1QTurSaStGvmud9YMN/eMW
sAhJedR3nHnbLQeFnPN9x2RZjC7Q06r+AT6DjXK8qwAhRVIgs38QgejmVAv7bypK
4ZAS1e7Dv5fFTm1b3vUgt7xSSY8wAG3xnzZHsWi4UJLVJ1tCAQRxH7hWoZW6NnsE
9UjPY3fvxEVjBgQi7DhhLMmJ4d600Bfqg3EgOzz3YnZkXUHQT7kZMxcaOT0YpHb8
rg0x8xH2Qown+SGRZXTSZKc8cX4pfHjr/JSZ7kFLJO1XpiAY27E=
=R5DC
-----END PGP SIGNATURE-----
--- End Message ---
