Your message dated Tue, 19 Oct 2021 22:48:38 +0000
with message-id <e1mcxuq-000gj1...@fasolo.debian.org>
and subject line Bug#996218: fixed in ruby-enum 0.9.0+ds-1
has caused the Debian Bug report #996218,
regarding ruby-enum: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed:        
expected Ruby::Enum::Errors::UninitializedConstantError, got #<ArgumentError: 
wrong number of arguments (given 2, expected 0..1)> with backtrace:
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.)


-- 
996218: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996218
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-enum
Version: 0.7.2-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby3.0

Hi,

We are about to enable building against ruby3.0 on unstable. During a test
rebuild, ruby-enum was found to fail to build in that situation.

To reproduce this locally, you need to install ruby-all-dev from experimental
on an unstable system or build chroot.

Relevant part (hopefully):
>        expected Ruby::Enum::Errors::UninitializedConstantError, got 
> #<ArgumentError: wrong number of arguments (given 2, expected 0..1)> with 
> backtrace:
>          # 
> /usr/share/rubygems-integration/all/gems/i18n-1.8.10/lib/i18n.rb:196:in 
> `translate'
>          # ./lib/ruby-enum/errors/base.rb:40:in `translate'
>          # ./lib/ruby-enum/errors/base.rb:51:in `create_problem'
>          # ./lib/ruby-enum/errors/base.rb:19:in `compose_message'
>          # ./lib/ruby-enum/errors/uninitialized_constant_error.rb:6:in 
> `initialize'
>          # ./lib/ruby-enum/enum.rb:46:in `exception'
>          # ./lib/ruby-enum/enum.rb:46:in `raise'
>          # ./lib/ruby-enum/enum.rb:46:in `const_missing'
>          # ./spec/ruby-enum/enum_spec.rb:168:in `block (4 levels) in <top 
> (required)>'
>          # ./spec/ruby-enum/enum_spec.rb:168:in `block (3 levels) in <top 
> (required)>'
>      # ./spec/ruby-enum/enum_spec.rb:168:in `block (3 levels) in <top 
> (required)>'
> 
> Finished in 0.0624 seconds (files took 0.45851 seconds to load)
> 29 examples, 5 failures
> 
> Failed examples:
> 
> rspec ./spec/ruby-enum/enum_spec.rb:23 # Ruby::Enum raises 
> UninitializedConstantError on an invalid constant
> rspec ./spec/ruby-enum/enum_spec.rb:122 # Ruby::Enum on duplicate keys raises 
> DuplicateKeyError
> rspec ./spec/ruby-enum/enum_spec.rb:132 # Ruby::Enum on duplicate values 
> raises a DuplicateValueError
> rspec ./spec/ruby-enum/enum_spec.rb:145 # Ruby::Enum Given a class that has 
> not defined any enums is expected to raise 
> Ruby::Enum::Errors::UninitializedConstantError
> rspec ./spec/ruby-enum/enum_spec.rb:167 # Ruby::Enum Subclass behavior parent 
> class should not have enums defined in child classes
> 
> /usr/bin/ruby3.0 
> -I/usr/share/rubygems-integration/all/gems/rspec-support-3.9.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib
>  /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/exe/rspec 
> --pattern ./spec/\*\*/\*_spec.rb --format documentation failed
> ERROR: Test "ruby3.0" failed: 


The full build log is available at
https://people.debian.org/~kanashiro/ruby3.0/round2/builds/3/ruby-enum/ruby-enum_0.7.2-3+rebuild1633378915_amd64.build.txt

Attachment: signature.asc
Description: PGP signature


--- End Message ---
--- Begin Message ---
Source: ruby-enum
Source-Version: 0.9.0+ds-1
Done: Lucas Kanashiro <kanash...@debian.org>

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

Debian distribution maintenance software
pp.
Lucas Kanashiro <kanash...@debian.org> (supplier of updated ruby-enum 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, 19 Oct 2021 19:01:56 -0300
Source: ruby-enum
Architecture: source
Version: 0.9.0+ds-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Team 
<pkg-ruby-extras-maintain...@lists.alioth.debian.org>
Changed-By: Lucas Kanashiro <kanash...@debian.org>
Closes: 996218
Changes:
 ruby-enum (0.9.0+ds-1) unstable; urgency=medium
 .
   * Team upload.
   * Exclude the coverage directory
   * New upstream version 0.9.0 (Closes: #996218)
   * Add patch to not require simplecov to run tests
   * Declare compliance with Debian Policy 4.6.0
   * d/watch: add mangling option for the ds in the package version
Checksums-Sha1:
 a8f17bf540de4ae716ec919b485fc401de6f3ad7 2059 ruby-enum_0.9.0+ds-1.dsc
 809a6ed1d9cd7ac9a4944ba9b00ddbcb347e65df 21240 ruby-enum_0.9.0+ds.orig.tar.xz
 3a0445dd964f21bdad4c0d223b2bcfc4dffb0035 2876 
ruby-enum_0.9.0+ds-1.debian.tar.xz
Checksums-Sha256:
 d5303e34dcb76af95f9219d4b387256998b54e1f39d59668462a2aa8c9ff94d4 2059 
ruby-enum_0.9.0+ds-1.dsc
 92aa3c0cad6312fbcbbd8e83900b52b3be948ab62f3ebdac597c91c1d6c2e7db 21240 
ruby-enum_0.9.0+ds.orig.tar.xz
 3479c0ae572c36c00cd72aa9ef22854c6e192ae247e965608a36e9b15e2a30c9 2876 
ruby-enum_0.9.0+ds-1.debian.tar.xz
Files:
 da846e7f43e4a0c9333a8d2997b1e21d 2059 ruby optional ruby-enum_0.9.0+ds-1.dsc
 aeb5438b0af2b2b5c33aaeb2176439c2 21240 ruby optional 
ruby-enum_0.9.0+ds.orig.tar.xz
 291593748a147d1b2083693908f1b157 2876 ruby optional 
ruby-enum_0.9.0+ds-1.debian.tar.xz

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

iQJJBAEBCAAzFiEEjtbD+LrJ23/BMKhw+COicpiDyXwFAmFvRdwVHGthbmFzaGly
b0BkZWJpYW4ub3JnAAoJEPgjonKYg8l8pLsP/1mtShYf8coEBC+2+i1r2EyPL4Qy
l7/PxfhWf74JRa6bVG3vlxwXqQ7SKt5L4HuV+cOs53GCjOSsJv62VChxgumnvIM+
4/ag+fK5KmWTpa4hy/T82UcyMuMzk7U2np/aU1ydqX/wEhdIZ/b7lckheMQkd0Xp
jI+VG9u90H7dVJPzWd1IuOWigwFZiegF15yA07Ilq1bpV5nFRJGA9BT2IrEr7xmo
fTWtijplcpg3QKN/q+8QIVOczU/QUWQx3/IHlmOM/oi+oHsB+aPPC5ZkUADtFSLs
kXkDHhhCrGxbOnD9uZ82j6gAbDJc0/3pV4cfBbjT37yFq8IelnLldRvGLiwwbDFG
WSNpFLjnV98/hMmQA0U5jbyp8XDZHbafAhlApuMZWjhKnt8qtXljpIRacioNN7Pt
XAb8Od28MeZGBeud2+P+nFRyJl9pW30BVFed8qpih083GlcvyxXoM99uQiF2Tb9G
tWs06b/jq5P7EBBpMsEEzgOb7x/shU94j0guSvngIoH5rVxuh5VHXr5OxZm5n08p
roQxzKscGwF1MM6bkn5bzmWE+N5U4zSo2EMJT1aHs2dXO3qSmHwYN+Uga33urtJy
YlFwwWvdBHOtxlfGGnSjVA8mwyKOMxspQJxyVgCH7uVO4BCUD2O6O8wbpE/t4qd+
aGLtKYTKykaS2bxH
=Cfy/
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to