Your message dated Wed, 30 Nov 2022 13:50:58 +0000
with message-id <e1p0nui-00ciks...@fasolo.debian.org>
and subject line Bug#1019664: fixed in ruby-rspec 3.10.0c1e1m2s3-2
has caused the Debian Bug report #1019664,
regarding ruby-rspec: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed:      
Failure/Error: DEFAULT_FAILURE_NOTIFIER = lambda { |failure, _opts| raise 
failure }
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.)


-- 
1019664: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019664
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-rspec
Version: 3.10.0c1e1m2s3-1
Severity: important
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby3.1

Hi,

We are about to start the ruby3.1 transition in unstable. While trying to
rebuild ruby-rspec with ruby3.1 enabled, the build failed.

Relevant part of the build log (hopefully):
>      Failure/Error: DEFAULT_FAILURE_NOTIFIER = lambda { |failure, _opts| 
> raise failure }
>        expected /received: 0 times/ but nothing was raised
>      # ./spec/rspec/support/deprecation_helpers_spec.rb:66:in `block (4 
> levels) in <top (required)>'
>      # ./spec/rspec/support/deprecation_helpers_spec.rb:65:in `block (3 
> levels) in <top (required)>'
> 
>   2) RSpec::Support::ShellOut can shell out to ruby with the current load path
>      # Need to investigate why this is failing -- see 
> https://travis-ci.org/rspec/rspec-core/jobs/60327106 and 
> https://travis-ci.org/rspec/rspec-support/jobs/60296920 for examples
>      # ./spec/rspec/support/spec/shell_out_spec.rb:22
> 
> Finished in 0.7821 seconds (files took 0.18394 seconds to load)
> 553 examples, 0 failures, 2 pending
> 
> Randomized with seed 24209
> 
> cd -
> Failed: rspec-core, rspec-expectations
> ERROR: Test "ruby3.1" failed: 


The full build log is available from:
https://people.debian.org/~terceiro/ruby3.1/17/ruby-rspec/ruby-rspec_3.10.0c1e1m2s3-1+rebuild1663008138_amd64-2022-09-12T18:42:19Z.build

To reproduce this, you need to install ruby-all-dev >= 1:3.0+2. Depending on
when you try this, it might mean installing ruby-all-dev from experimental, or
if the transition has already started, a normal build on unstable will be
enough.  If you fail to reproduce, please provide a build log and diff it with
mine so that we can identify if something relevant changed in the meantime.

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

Attachment: signature.asc
Description: PGP signature


--- End Message ---
--- Begin Message ---
Source: ruby-rspec
Source-Version: 3.10.0c1e1m2s3-2
Done: Cédric Boutillier <bou...@debian.org>

We believe that the bug you reported is fixed in the latest version of
ruby-rspec, 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 1019...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Cédric Boutillier <bou...@debian.org> (supplier of updated ruby-rspec 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: SHA512

Format: 1.8
Date: Wed, 30 Nov 2022 14:27:18 +0100
Source: ruby-rspec
Architecture: source
Version: 3.10.0c1e1m2s3-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Team 
<pkg-ruby-extras-maintain...@lists.alioth.debian.org>
Changed-By: Cédric Boutillier <bou...@debian.org>
Closes: 1019664
Changes:
 ruby-rspec (3.10.0c1e1m2s3-2) unstable; urgency=medium
 .
   * Bump Standards-Version to 4.6.1 (no changes needed)
   * Bump debhelper compatibility level to 13
   * Fix test failures with ruby3.1
     - Disable error highlighting with ruby3.1 when running tests
       with --disable-error_highlight ruby option
       (Closes: #1019664)
     - Add patch to call correct interpreter in rspec-support 'shell out' specs
Checksums-Sha1:
 f117db6bedefbe7bd12536b8af4a6c9819b8abe5 1886 ruby-rspec_3.10.0c1e1m2s3-2.dsc
 015dd69bb12fbd1d15469f4af6104fd552d2cc6a 882578 
ruby-rspec_3.10.0c1e1m2s3.orig.tar.gz
 5e2a7010852726a57c7407fb2bed9b740d21622a 12016 
ruby-rspec_3.10.0c1e1m2s3-2.debian.tar.xz
 205ceae0b172f73e00cadebfbe253f8912b7c829 11405 
ruby-rspec_3.10.0c1e1m2s3-2_amd64.buildinfo
Checksums-Sha256:
 0ab358e8a17464f0dfa98f4a9622a324354271c8a76419ec179d24600ba6be20 1886 
ruby-rspec_3.10.0c1e1m2s3-2.dsc
 f84788d1311439b0aab489a2d456abf52f6aeec10530ae9abd92cfbe6534afc3 882578 
ruby-rspec_3.10.0c1e1m2s3.orig.tar.gz
 d0c9a4020d6d30b0f1403d1047bb9706c3e2bf8abd5f29e42db29d5fd12e2a36 12016 
ruby-rspec_3.10.0c1e1m2s3-2.debian.tar.xz
 1f17a93ff8026ac20a8bab27d24385dc378f695df33f4144697dbb65ae899141 11405 
ruby-rspec_3.10.0c1e1m2s3-2_amd64.buildinfo
Files:
 20e04c88c12b2bcf5b78552b6da87daa 1886 ruby optional 
ruby-rspec_3.10.0c1e1m2s3-2.dsc
 822b0c00a3dc9dda691cbb0b28b9e081 882578 ruby optional 
ruby-rspec_3.10.0c1e1m2s3.orig.tar.gz
 ebfa150cdad12932feb515c0b0708342 12016 ruby optional 
ruby-rspec_3.10.0c1e1m2s3-2.debian.tar.xz
 912255115a4a2bc8346a38d7cc899367 11405 ruby optional 
ruby-rspec_3.10.0c1e1m2s3-2_amd64.buildinfo

-----BEGIN PGP SIGNATURE-----

iHUEARYKAB0WIQSEz/3CFSD4gwbsKdFSaZq2P58rwwUCY4dcPwAKCRBSaZq2P58r
w6kgAQDZHDqJVmHjoOC3giMYxB1j1tsx0gIMt51OXOQgv8L6cgD/U1AKnbfj++Dx
iCTJYbvXXjr892NBiti5Cz9ycE021gc=
=aT0w
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to