Your message dated Tue, 03 Jan 2023 07:15:44 +0000
with message-id <e1pcbws-00dczm...@fasolo.debian.org>
and subject line Bug#1027073: fixed in ruby-gh 0.18.0-5
has caused the Debian Bug report #1027073,
regarding ruby-gh: FTBFS with ruby-rspec 3.12: ERROR: Test "ruby3.1" failed:
Failure/Error: expect { subject['/x'] }.to
raise_error(GH::Error(:response_status => 500))
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.)
--
1027073: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027073
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-gh
Version: 0.18.0-4
Severity: important
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby-rspec-3.12
Hi,
I'm about to upload ruby-rspec 3.12. During a test rebuild with that version,
ruby-gh failed to build.
Relevant part of the build log (hopefully):
> Failure/Error: expect { subject['/x'] }.to
> raise_error(GH::Error(:response_status => 500))
>
> expected #<Module:0x00007fc649c453f8>, got
> #<RSpec::Mocks::MockExpectationError: #<GH::Remote: https://api.github.com>
> received :http with unexp...ken", {"Authorization"=>"Basic Zm9vOmJhcg==",
> :body=>"{\"access_token\": \"baz\"}"}) (options hash)> with backtrace:
> # ./lib/gh/token_check.rb:28:in `http'
> # ./lib/gh/token_check.rb:21:in `check_token'
> # ./lib/gh/token_check.rb:27:in `http'
> # ./lib/gh/remote.rb:66:in `fetch_resource'
> # ./lib/gh/wrapper.rb:82:in `[]'
> # ./spec/token_check_spec.rb:25:in `block (3 levels) in <top
> (required)>'
> # ./spec/token_check_spec.rb:25:in `block (2 levels) in <top
> (required)>'
> # ./spec/token_check_spec.rb:25:in `block (2 levels) in <top (required)>'
>
> Deprecation Warnings:
>
> Using `should_receive` from rspec-mocks' old `:should` syntax without
> explicitly enabling the syntax is deprecated. Use the new `:expect` syntax or
> explicitly enable `:should` instead. Called from
> /<<PKGBUILDDIR>>/spec/custom_limit_spec.rb:17:in `block (2 levels) in <top
> (required)>'.
>
> Using `should` from rspec-expectations' old `:should` syntax without
> explicitly enabling the syntax is deprecated. Use the new `:expect` syntax or
> explicitly enable `:should` with `config.expect_with(:rspec) { |c| c.syntax =
> :should }` instead. Called from /<<PKGBUILDDIR>>/spec/cache_spec.rb:7:in
> `block (2 levels) in <top (required)>'.
>
>
> If you need more of the backtrace for any of these deprecations to
> identify where to make the necessary changes, you can configure
> `config.raise_errors_for_deprecations!`, and it will turn the
> deprecation warnings into errors, giving you the full backtrace.
>
> 2 deprecation warnings total
>
> Finished in 1 second (files took 0.46356 seconds to load)
> 115 examples, 2 failures, 9 pending
>
> Failed examples:
>
> rspec ./spec/token_check_spec.rb:10 # GH::TokenCheck adds client_id and
> client_secret to a request
> rspec ./spec/token_check_spec.rb:19 # GH::TokenCheck does not swallow other
> status codes
>
> /usr/bin/ruby3.1
> -I/usr/share/rubygems-integration/all/gems/rspec-support-3.12.0/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.12.0/lib
> /usr/share/rubygems-integration/all/gems/rspec-core-3.12.0/exe/rspec
> --pattern ./spec/\*\*/\*_spec.rb --format documentation failed
> ERROR: Test "ruby3.1" failed:
The full build log is attached.
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
ruby-gh.log.gz
Description: application/gzip
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: ruby-gh
Source-Version: 0.18.0-5
Done: HIGUCHI Daisuke (VDR dai) <d...@debian.org>
We believe that the bug you reported is fixed in the latest version of
ruby-gh, 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 1027...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
HIGUCHI Daisuke (VDR dai) <d...@debian.org> (supplier of updated ruby-gh
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: Tue, 03 Jan 2023 15:25:21 +0900
Source: ruby-gh
Architecture: source
Version: 0.18.0-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Team
<pkg-ruby-extras-maintain...@lists.alioth.debian.org>
Changed-By: HIGUCHI Daisuke (VDR dai) <d...@debian.org>
Closes: 1027073
Changes:
ruby-gh (0.18.0-5) unstable; urgency=medium
.
* Team upload.
.
[ HIGUCHI Daisuke (VDR dai) ]
* fix FTBFS with ruby-rspec-3.12 (Closes: #1027073)
* Drop XS-Ruby-Version and XB-Ruby-Version.
* Bump Standards-Version to 4.6.1
Checksums-Sha1:
2d5a05965fb671a710b1fb822d977472191224cc 2158 ruby-gh_0.18.0-5.dsc
afb620d1d5894db9deeb8cfd1530973a775a2a90 3808 ruby-gh_0.18.0-5.debian.tar.xz
Checksums-Sha256:
dc0bb6d52cc35da86498c1823d3b039c66f836ee572793990aba4599ef6106cf 2158
ruby-gh_0.18.0-5.dsc
07937d53f1a362b69635ffe39f3d29681b01d0b3a90685ef05c7428b29ae56da 3808
ruby-gh_0.18.0-5.debian.tar.xz
Files:
11fdee5192756583da680ae18968b8f1 2158 ruby optional ruby-gh_0.18.0-5.dsc
52871e513fc050a689a048c589c291d1 3808 ruby optional
ruby-gh_0.18.0-5.debian.tar.xz
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEECynYjkLmt2W42OpQeDlhndQ5Zo4FAmOzzRMACgkQeDlhndQ5
Zo5WsA//aFXyWC1XzbsA8C1a4qKtCiZ/JDsZWeSmt9Zjfo4dqpmhqKvYISqdruK0
m7YijiHkTges5kywOvMtkjZEa3SlPUVD35jupK/nz6xhwC25I90MiWPcQ7HzOLRl
vQHyRwON4u1Ae0hwUvcAZkhJ3S9V4+EKokkhhxClSpfgN3o8H7ZbbRK5JpTMIBM3
7qbgPvloZ+iE4mLOhkKz1/YyE3K+XQD6H/BU3T/EZFLqDpEuSKNHk1lwCIh9kWia
qjqXtzNbGQMrruEKgsQvoGnlvTo/dAixGj3wdcIcf1CoOwLI1Xt+ZaIN4/ozuV8r
E+Go0adxidm5pF3VUAitElzMAabRQXtKiNhVwiMlL3XwNu9XXpzvZjaZ1uhDhBqZ
UgtVlDatVOX3+q2H1fZDSSxbol1XOhga7ATR7QhobeylpkwEQoJBczAPI/w+fqz4
IDY3I01YVJ1R+0536rGMlBenw0iH7j6y05+xqyOWGaSrCOpR6dYrHwxJMIIcQOXO
VCsTNSa+n9ZCCE6mOkz2GOmbYqNWM/dxVmooN3tQH8DzfutGUgrnm2prE5ZcxOiu
bVpZ10K/ij4HdzBiC9ubLoLnm6eXNIUFhE1xKIm37jaWPv0CRhWO6TJ3a4D5wRPG
N9nxzUjCx4kUSRFxoZhTcrprD+8My8JMcaFtQLNK9kfb/mz0RWM=
=rHjS
-----END PGP SIGNATURE-----
--- End Message ---
