Your message dated Sat, 29 Oct 2022 17:08:14 +0000
with message-id <e1oopje-00ftov...@fasolo.debian.org>
and subject line Bug#1019618: fixed in ruby-delayed-job 4.1.9-1.1
has caused the Debian Bug report #1019618,
regarding ruby-delayed-job: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed:   
   Failure/Error:
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.)


-- 
1019618: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019618
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-delayed-job
Version: 4.1.9-1
Severity: serious
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-delayed-job with ruby3.1 enabled, the build failed.

Relevant part of the build log (hopefully):
>      Failure/Error:
>        expect do
>          yaml = "--- !ruby/struct\nn: 1\n"
>          object = YAML.load(yaml)
>          expect(object).to be_kind_of(Struct)
>          expect(object.n).to eq(1)
>        end.not_to raise_error
> 
>        expected no Exception, got #<Psych::DisallowedClass: Tried to load 
> unspecified class: Struct> with backtrace:
>          # (eval):2:in `struct'
>          # ./spec/yaml_ext_spec.rb:28:in `block (3 levels) in <top 
> (required)>'
>          # ./spec/yaml_ext_spec.rb:26:in `block (2 levels) in <top 
> (required)>'
>      # ./spec/yaml_ext_spec.rb:26:in `block (2 levels) in <top (required)>'
> 
> Finished in 1.46 seconds (files took 0.9459 seconds to load)
> 177 examples, 1 failure
> 
> Failed examples:
> 
> rspec ./spec/yaml_ext_spec.rb:25 # YAML autoloads the class of an anonymous 
> struct
> 
> /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-delayed-job/ruby-delayed-job_4.1.9-1+rebuild1663007476_amd64-2022-09-12T18:31:17Z.build

To reproduce this, you need ruby-all-dev >= 1:3.0+2.  Depending on when you
read this, this might mean installing ruby-all-dev from experimental, or ir the
transition has alraedy started in unstable, a normal build on unstable should
do it.  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-delayed-job
Source-Version: 4.1.9-1.1
Done: Adrian Bunk <b...@debian.org>

We believe that the bug you reported is fixed in the latest version of
ruby-delayed-job, 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.
Adrian Bunk <b...@debian.org> (supplier of updated ruby-delayed-job 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: Sat, 15 Oct 2022 17:07:57 +0300
Source: ruby-delayed-job
Architecture: source
Version: 4.1.9-1.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Team 
<pkg-ruby-extras-maintain...@lists.alioth.debian.org>
Changed-By: Adrian Bunk <b...@debian.org>
Closes: 1019618
Changes:
 ruby-delayed-job (4.1.9-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Backport upstream fix for Ruby 3.1. (Closes: #1019618)
Checksums-Sha1:
 f6afe116b3ce499b97dff185818a93c9e81d316d 2192 ruby-delayed-job_4.1.9-1.1.dsc
 fb244cb92e8709f6f1a93cb0b8d74af7a820ec96 4336 
ruby-delayed-job_4.1.9-1.1.debian.tar.xz
Checksums-Sha256:
 dfeff954d06cc7ea8e82daf6d4bf5abc13545829aa5e9e6af49d2bb203004f2b 2192 
ruby-delayed-job_4.1.9-1.1.dsc
 9d3b4b78a21692e2c66ade2cca9d4adcea277a0bb15b9798388a8626de0cf5ff 4336 
ruby-delayed-job_4.1.9-1.1.debian.tar.xz
Files:
 ec983ab46fd8c1bbeea54564cd754a73 2192 ruby optional 
ruby-delayed-job_4.1.9-1.1.dsc
 b032ad5d9a2e964d87b0fe9dd71fdf0f 4336 ruby optional 
ruby-delayed-job_4.1.9-1.1.debian.tar.xz

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

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmNKv2cACgkQiNJCh6LY
mLEMxg/+LrutpNw8p3L6F/RjO29hooZ3tzvJ8quVlp591nhpp8Cd6Asyu2N64CmU
1KJej+GupuAo66yV0olYl8Cxmj2NmsajOxY2WMWbepGrGNgB9myXuJkVZJ6khcrq
SSR4WBMG+zTBxNSfmd0EOBbwZwwSdDEwfsJjGi5IoyGljXdriXYeiyGHkF4tLjpB
OUzkVvh9I15Ad/vScVG3zmYfouHOjR1lSluvEJkObIeTK/tI/CbJ1chaqPCDjcJv
5z77Pre4WGSTf0+DQn3OiAqPDVHbPq/z1NFvH6+HjvE5N//gPFH/8nWczueKtu/0
kXFNqqVPwbRJHsfcU2xv4ouIDTowLp0vpNsjG4xyJ3teoomke5o8w/5uSygDklOC
N5i/jdBF0JVmOXRv707nIDP/7vflLUHRe6rM7adJ73i9GY89yhXisH/VTFFX/AnM
G6ovfahGKs+BfSVFWYqg5xjvVSVRRsJHkRIyAELyNfkogjIKH5isvckcPb1Ykb1T
n6GgnMUgxh32ohh85NNhQcu4OAUGIpYcq8GWRAUs7jt4jhaM5rz+YvCvxr5+EbKM
fisPY0GgOBirCeb5xyQX252Yn2oyf6C5jMheyB0lbmzWEo8M6dG7L/HOx2dERb7b
2y9rbO8LAsSuhtRvn4paXlorZqddqGRKbwn6VUjkmeEkbEszEuo=
=9ypP
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to