Your message dated Tue, 27 Dec 2022 19:05:35 +0000
with message-id <[email protected]>
and subject line Bug#1019640: fixed in ruby-mono-logger 1.1.1-2
has caused the Debian Bug report #1019640,
regarding ruby-mono-logger: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed:
/usr/share/rubygems-integration/all/gems/simplecov-0.21.2/lib/simplecov.rb:354:in
`start': coverage measurement is already setup (RuntimeError)
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 [email protected]
immediately.)
--
1019640: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019640
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: ruby-mono-logger
Version: 1.1.1-1
Severity: important
Justification: FTBFS
Tags: bookworm sid ftbfs
User: [email protected]
Usertags: ruby3.1
Hi,
We are about to start the ruby3.1 transition in unstable. While trying to
rebuild ruby-mono-logger with ruby3.1 enabled, the build failed.
Relevant part of the build log (hopefully):
> /usr/share/rubygems-integration/all/gems/simplecov-0.21.2/lib/simplecov.rb:354:in
> `start': coverage measurement is already setup (RuntimeError)
> from
> /usr/share/rubygems-integration/all/gems/simplecov-0.21.2/lib/simplecov.rb:354:in
> `start_coverage_with_criteria'
> from
> /usr/share/rubygems-integration/all/gems/simplecov-0.21.2/lib/simplecov.rb:343:in
> `start_coverage_measurement'
> from
> /usr/share/rubygems-integration/all/gems/simplecov-0.21.2/lib/simplecov.rb:59:in
> `start'
> from /usr/lib/ruby/vendor_ruby/coveralls.rb:74:in `start!'
> from /usr/lib/ruby/vendor_ruby/coveralls.rb:19:in `wear!'
> from /<<PKGBUILDDIR>>/test/mri_logger_test.rb:10:in `<top (required)>'
> from
> <internal:/usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb>:85:in
> `require'
> from
> <internal:/usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb>:85:in
> `require'
> from
> /usr/lib/ruby/gems/3.1.0/gems/rake-13.0.6/lib/rake/rake_test_loader.rb:21:in
> `block in <main>'
> from
> /usr/lib/ruby/gems/3.1.0/gems/rake-13.0.6/lib/rake/rake_test_loader.rb:6:in
> `select'
> from
> /usr/lib/ruby/gems/3.1.0/gems/rake-13.0.6/lib/rake/rake_test_loader.rb:6:in
> `<main>'
> [32m[Coveralls] Set up the SimpleCov formatter.[0m
> [32m[Coveralls] Using SimpleCov's default settings.[0m
> [33m[Coveralls] Outside the CI environment, not sending data.[0m
> rake aborted!
> Command failed with status (1): [ruby -w -I"test"
> /usr/lib/ruby/gems/3.1.0/gems/rake-13.0.6/lib/rake/rake_test_loader.rb
> "test/mri_logger_test.rb" -v]
>
> Tasks: TOP => default
> (See full trace by running task with --trace)
> ERROR: Test "ruby3.1" failed:
The full build log is available from:
https://people.debian.org/~terceiro/ruby3.1/17/ruby-mono-logger/ruby-mono-logger_1.1.1-1+rebuild1663007849_amd64-2022-09-12T18:37:30Z.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-mono-logger
Source-Version: 1.1.1-2
Done: Nilesh Patra <[email protected]>
We believe that the bug you reported is fixed in the latest version of
ruby-mono-logger, 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 [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Nilesh Patra <[email protected]> (supplier of updated ruby-mono-logger 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 [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Format: 1.8
Date: Wed, 28 Dec 2022 00:16:07 +0530
Source: ruby-mono-logger
Architecture: source
Version: 1.1.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Team
<[email protected]>
Changed-By: Nilesh Patra <[email protected]>
Closes: 1019640
Changes:
ruby-mono-logger (1.1.1-2) unstable; urgency=medium
.
* Team Upload.
* Add patch to fix ruby 3.1 FTBFS (Closes: #1019640)
Checksums-Sha1:
2cc6f5e1de6b798c65ea070ac23a2708fbfab170 1534 ruby-mono-logger_1.1.1-2.dsc
df8393678c48533e15d9abc39c3406225f678292 3340
ruby-mono-logger_1.1.1-2.debian.tar.xz
e94dc5c60c70e09bf06a85ad91c6424cb2c96396 9274
ruby-mono-logger_1.1.1-2_amd64.buildinfo
Checksums-Sha256:
20a21d58bee8d30d5c3a1ecc47e6afd5d5ee49455018305bf375668120008aaa 1534
ruby-mono-logger_1.1.1-2.dsc
67bfc8652ec7966524d387d90c9140d7c80ab285af690667c8648343afa89411 3340
ruby-mono-logger_1.1.1-2.debian.tar.xz
118e5dc70c303f8f87b3868f42dcab7e8cb45a0c2bce3b2c65465b23006fe0a8 9274
ruby-mono-logger_1.1.1-2_amd64.buildinfo
Files:
57159e73cf408fb83a5dc8d91b16d963 1534 ruby optional
ruby-mono-logger_1.1.1-2.dsc
2548ed99051fe6c2e2967ec4049e0ef4 3340 ruby optional
ruby-mono-logger_1.1.1-2.debian.tar.xz
885049837fd8e9ecd6715b98110c89ac 9274 ruby optional
ruby-mono-logger_1.1.1-2_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iHUEARYIAB0WIQSglbZu4JAkvuai8HIqJ5BL1yQ+2gUCY6s+PQAKCRAqJ5BL1yQ+
2hjrAQCUTsVo+LsAK6Ye3W02igIUSqBPHXF+E2eFqB1RmZjWKgD/ZVTHk3/xX/Rb
S6d6IbMibgse5uN2zHbEMfMohShR0Qg=
=I2n+
-----END PGP SIGNATURE-----
--- End Message ---
