Your message dated Sun, 13 Nov 2022 23:07:12 +0000 with message-id <e1oum4g-007svq...@fasolo.debian.org> and subject line Bug#1019674: fixed in ruby-vcr 6.0.0+really5.0.0-4 has caused the Debian Bug report #1019674, regarding ruby-vcr: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: test failures 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.) -- 1019674: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019674 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Source: ruby-vcr Version: 6.0.0+really5.0.0-3 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-vcr with ruby3.1 enabled, the build failed. Relevant part of the build log (hopefully): > /<<PKGBUILDDIR>>/lib/vcr/library_hooks/webmock.rb:36:in `block in > global_hook_disabled_requests': wrong number of arguments (given 1, expected > 0) (ArgumentError) > /usr/bin/ruby3.1 > -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.1" failed: The full build log is available from: https://people.debian.org/~terceiro/ruby3.1/17/ruby-vcr/ruby-vcr_6.0.0+really5.0.0-3+rebuild1663008290_amd64-2022-09-12T18:44:51Z.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
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---Source: ruby-vcr Source-Version: 6.0.0+really5.0.0-4 Done: Cédric Boutillier <bou...@debian.org> We believe that the bug you reported is fixed in the latest version of ruby-vcr, 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-vcr 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: Sun, 13 Nov 2022 23:31:11 +0100 Source: ruby-vcr Architecture: source Version: 6.0.0+really5.0.0-4 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: 1018882 1019674 Changes: ruby-vcr (6.0.0+really5.0.0-4) unstable; urgency=medium . * Team upload * Import upstream commits to make VCR::Cassette::Migrator compatible with newer psych (Closes: #1019674) * Disable shared example for tests failing on ipv6-only machines (Closes: #1018882) Checksums-Sha1: a5b93b433473138f29fd2344af1db7ac54a8adc9 1722 ruby-vcr_6.0.0+really5.0.0-4.dsc 363fd4129ef0fdd6dc37f9b9ae2392c9a033ea57 147602 ruby-vcr_6.0.0+really5.0.0.orig.tar.gz ba18fe042373baf32e27902132e55061a4dc8b3e 7520 ruby-vcr_6.0.0+really5.0.0-4.debian.tar.xz 130453772582f5833d2fc6e21c5beb01e7bde7fb 11043 ruby-vcr_6.0.0+really5.0.0-4_amd64.buildinfo Checksums-Sha256: 6ad65737a2b3c601c22106f77c4b768dff38d18af588f874a940a16cd9bafe05 1722 ruby-vcr_6.0.0+really5.0.0-4.dsc a1d54ee3df0f7d29e641fd45d6e7ee1c0b606e17d3ec45c0377bd70b3e211565 147602 ruby-vcr_6.0.0+really5.0.0.orig.tar.gz c4dbc9aabc08c59e102aa5e5883db3266af7f776602d6d176a7bef13851d1e42 7520 ruby-vcr_6.0.0+really5.0.0-4.debian.tar.xz 353b3dd25842ddef7952bbd50f8f403e4fc7e0327d2bd01ca8a9fc2f4af24472 11043 ruby-vcr_6.0.0+really5.0.0-4_amd64.buildinfo Files: cfd9733b74f4678c735391bd9c0f9230 1722 ruby optional ruby-vcr_6.0.0+really5.0.0-4.dsc 36ac0193516f201510db562d084f6a34 147602 ruby optional ruby-vcr_6.0.0+really5.0.0.orig.tar.gz 881ea9f2d9dc214f8eda5bc9122bbb95 7520 ruby optional ruby-vcr_6.0.0+really5.0.0-4.debian.tar.xz 75bb055f75ccc37239ba90b6168c5a33 11043 ruby optional ruby-vcr_6.0.0+really5.0.0-4_amd64.buildinfo -----BEGIN PGP SIGNATURE----- iHUEARYKAB0WIQSEz/3CFSD4gwbsKdFSaZq2P58rwwUCY3F1rwAKCRBSaZq2P58r wyIJAPwIGZQf8pnFLuNHoJwq11Vein14XxvblDpJRuWbiyVniQD/S2+JouQhLsHq 3NuldqDjda5/b8uRB6fM9TZ26UQBdgE= =5CHT -----END PGP SIGNATURE-----
--- End Message ---
