Your message dated Wed, 30 Nov 2022 15:09:48 +0000
with message-id <e1p0oia-00dqsf...@fasolo.debian.org>
and subject line Bug#1019637: fixed in ruby-memoizable 0.4.2-3
has caused the Debian Bug report #1019637,
regarding ruby-memoizable: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed:
Failure/Error: expect { subject }.to raise_error(NameError, 'No method bar is
memoized')
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.)
--
1019637: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019637
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-memoizable
Version: 0.4.2-2
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-memoizable with ruby3.1 enabled, the build failed.
Relevant part of the build log (hopefully):
> Failure/Error: expect { subject }.to raise_error(NameError, 'No method
> bar is memoized')
>
> expected NameError with "No method bar is memoized", got #<NameError:
> No method bar is memoized
>
> fail NameError, "No method #{name} is memoized"
> ^^^^> with backtrace:
> # ./lib/memoizable/memory.rb:30:in `block in []'
> # ./lib/memoizable/memory.rb:29:in `[]'
> # ./lib/memoizable/module_methods.rb:81:in
> `unmemoized_instance_method'
> #
> ./spec/unit/memoizable/module_methods/unmemoized_instance_method_spec.rb:6:in
> `block (2 levels) in <top (required)>'
> #
> ./spec/unit/memoizable/module_methods/unmemoized_instance_method_spec.rb:40:in
> `block (4 levels) in <top (required)>'
> #
> ./spec/unit/memoizable/module_methods/unmemoized_instance_method_spec.rb:40:in
> `block (3 levels) in <top (required)>'
> #
> ./spec/unit/memoizable/module_methods/unmemoized_instance_method_spec.rb:40:in
> `block (3 levels) in <top (required)>'
>
> Finished in 0.04572 seconds (files took 0.11871 seconds to load)
> 68 examples, 1 failure
>
> Failed examples:
>
> rspec
> ./spec/unit/memoizable/module_methods/unmemoized_instance_method_spec.rb:39 #
> Memoizable::ModuleMethods#unmemoized_instance_method when the method was not
> memoized raises an exception
>
> /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
> ./spec/integration/serializable_spec.rb
> ./spec/shared/call_super_shared_spec.rb
> ./spec/unit/memoizable/class_methods/included_spec.rb
> ./spec/unit/memoizable/instance_methods/freeze_spec.rb
> ./spec/unit/memoizable/instance_methods/memoize_spec.rb
> ./spec/unit/memoizable/memory_spec.rb
> ./spec/unit/memoizable/method_builder/call_spec.rb
> ./spec/unit/memoizable/method_builder/class_methods/new_spec.rb
> ./spec/unit/memoizable/method_builder/original_method_spec.rb
> ./spec/unit/memoizable/module_methods/included_spec.rb
> ./spec/unit/memoizable/module_methods/memoize_spec.rb
> ./spec/unit/memoizable/module_methods/memoized_predicate_spec.rb
> ./spec/unit/memoizable/module_methods/unmemoized_instance_method_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-memoizable/ruby-memoizable_0.4.2-2+rebuild1663007825_amd64-2022-09-12T18:37:06Z.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-memoizable
Source-Version: 0.4.2-3
Done: Cédric Boutillier <bou...@debian.org>
We believe that the bug you reported is fixed in the latest version of
ruby-memoizable, 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-memoizable
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 15:34:40 +0100
Source: ruby-memoizable
Architecture: source
Version: 0.4.2-3
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: 1019637
Changes:
ruby-memoizable (0.4.2-3) unstable; urgency=medium
.
* Team upload
.
[ Debian Janitor ]
* Set field Upstream-Contact in debian/copyright.
* Remove obsolete fields Contact, Name from debian/upstream/metadata
(already present in machine-readable debian/copyright).
* Update watch file format version to 4.
* Bump debhelper from old 12 to 13.
* Update standards version to 4.5.1, no changes needed.
.
[ Cédric Boutillier ]
* Bump Standards-Version to 4.6.1 (no changes needed)
* Disable error highlight with ruby3.1 in tests (Closes: #1019637)
Checksums-Sha1:
fd49d74a68649abe99f90ed711dc834e5dc760dd 1471 ruby-memoizable_0.4.2-3.dsc
ccd7f0f81ab7b84489601cbee9c3f782bc0ca5f2 10426
ruby-memoizable_0.4.2.orig.tar.gz
f37222025567bea0902a69f4910983a5edb6d884 3136
ruby-memoizable_0.4.2-3.debian.tar.xz
665fddbb2894b37d45a3ab1ebb038b2d4d5d0696 9296
ruby-memoizable_0.4.2-3_amd64.buildinfo
Checksums-Sha256:
d36509c858702bc3d91e75936f0f4d1e8fe4ae9dd01d56fba1aa59621762a376 1471
ruby-memoizable_0.4.2-3.dsc
534ef0e11a693ed15e1fd473fc556946e756f77d0ed1b83615ed5372313eba9e 10426
ruby-memoizable_0.4.2.orig.tar.gz
5abace1a92746ab7c8da06dc59c918c93f61310437877b11d748bc85960727cf 3136
ruby-memoizable_0.4.2-3.debian.tar.xz
1873cbec895bc281dacec853509d29f4ec9e3c1b5e80ad0b90499934757cbd72 9296
ruby-memoizable_0.4.2-3_amd64.buildinfo
Files:
6b6bd706df1c48c9e638a8a1d66c6370 1471 ruby optional ruby-memoizable_0.4.2-3.dsc
83bfe25ae96eec665717fa207720e998 10426 ruby optional
ruby-memoizable_0.4.2.orig.tar.gz
05170dfeb70be87641a91df20d3f71d8 3136 ruby optional
ruby-memoizable_0.4.2-3.debian.tar.xz
e878fa12a25975475b6c81aef79f0831 9296 ruby optional
ruby-memoizable_0.4.2-3_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iHUEARYKAB0WIQSEz/3CFSD4gwbsKdFSaZq2P58rwwUCY4dqqAAKCRBSaZq2P58r
wyIhAP9N0bEtSMncd3pHytiJ7B+Af9rop61jVJFiQYK74aJyowEAm+yQ2AsoqArs
20sWtvck8pXxJROqSCzvrOXYqLZK4Qs=
=FWUG
-----END PGP SIGNATURE-----
--- End Message ---
