Your message dated Mon, 29 Nov 2021 00:06:48 +0000
with message-id <e1mruc0-000esx...@fasolo.debian.org>
and subject line Bug#996116: fixed in r10k 3.7.0-2.1
has caused the Debian Bug report #996116,
regarding r10k: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed:
ArgumentError:
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.)
--
996116: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996116
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: r10k
Version: 3.7.0-2
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, r10k 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):
> ArgumentError:
> wrong number of arguments (given 2, expected 0..1)
> Shared Example Group: "a git working repository" called from
> ./spec/integration/git/rugged/working_repository_spec.rb:12
> #
> /usr/lib/x86_64-linux-gnu/rubygems-integration/3.0.0/gems/rugged-1.1.0/lib/rugged/repository.rb:257:in
> `fetch'
> #
> /usr/lib/x86_64-linux-gnu/rubygems-integration/3.0.0/gems/rugged-1.1.0/lib/rugged/repository.rb:257:in
> `fetch'
> # ./lib/r10k/git/rugged/working_repository.rb:96:in `block (2 levels)
> in fetch'
> # ./lib/r10k/git/rugged/base_repository.rb:67:in `with_repo'
> # ./lib/r10k/git/rugged/working_repository.rb:139:in `with_repo'
> # ./lib/r10k/git/rugged/working_repository.rb:96:in `block in fetch'
> # ./lib/r10k/git.rb:188:in `with_proxy'
> # ./lib/r10k/git/rugged/working_repository.rb:95:in `fetch'
> # ./spec/shared-examples/git/working_repository.rb:136:in `block (4
> levels) in <top (required)>'
>
> Finished in 3.67 seconds (files took 0.61891 seconds to load)
> 784 examples, 24 failures, 3 pending
>
> Failed examples:
>
> rspec './spec/integration/git/rugged/bare_repository_spec.rb[1:1:2:1]' #
> R10K::Git::Rugged::BareRepository behaves like a git repository listing tags
> lists all tags in alphabetical order
> rspec './spec/integration/git/rugged/bare_repository_spec.rb[1:1:3:1]' #
> R10K::Git::Rugged::BareRepository behaves like a git repository resolving
> refs can resolve branches
> rspec './spec/integration/git/rugged/bare_repository_spec.rb[1:1:3:2]' #
> R10K::Git::Rugged::BareRepository behaves like a git repository resolving
> refs can resolve tags
> rspec './spec/integration/git/rugged/bare_repository_spec.rb[1:1:3:3]' #
> R10K::Git::Rugged::BareRepository behaves like a git repository resolving
> refs can resolve commits
> rspec './spec/integration/git/rugged/bare_repository_spec.rb[1:1:3:4]' #
> R10K::Git::Rugged::BareRepository behaves like a git repository resolving
> refs returns nil when the object cannot be resolved
> rspec './spec/integration/git/rugged/bare_repository_spec.rb[1:2:1:1]' #
> R10K::Git::Rugged::BareRepository behaves like a git bare repository checking
> for the presence of the repo exists if the repo is present
> rspec './spec/integration/git/rugged/bare_repository_spec.rb[1:2:2:1]' #
> R10K::Git::Rugged::BareRepository behaves like a git bare repository cloning
> the repo creates the repo at the expected location
> rspec './spec/integration/git/rugged/bare_repository_spec.rb[1:2:2:2:1]' #
> R10K::Git::Rugged::BareRepository behaves like a git bare repository cloning
> the repo without a proxy does not change proxy ENV
> rspec './spec/integration/git/rugged/bare_repository_spec.rb[1:2:2:3:1]' #
> R10K::Git::Rugged::BareRepository behaves like a git bare repository cloning
> the repo with a proxy manages proxy-related ENV vars
> rspec './spec/integration/git/rugged/bare_repository_spec.rb[1:2:3:1]' #
> R10K::Git::Rugged::BareRepository behaves like a git bare repository updating
> the repo fetches objects from the remote
> rspec './spec/integration/git/rugged/bare_repository_spec.rb[1:2:3:2:1]' #
> R10K::Git::Rugged::BareRepository behaves like a git bare repository updating
> the repo without a proxy does not change proxy ENV
> rspec './spec/integration/git/rugged/bare_repository_spec.rb[1:2:3:3:1]' #
> R10K::Git::Rugged::BareRepository behaves like a git bare repository updating
> the repo with a proxy manages proxy-related ENV vars
> rspec './spec/integration/git/rugged/bare_repository_spec.rb[1:2:4:1]' #
> R10K::Git::Rugged::BareRepository behaves like a git bare repository listing
> branches lists all branches in alphabetical order
> rspec './spec/integration/git/rugged/bare_repository_spec.rb[1:2:5:1]' #
> R10K::Git::Rugged::BareRepository behaves like a git bare repository
> determining ref type can infer the type of a branch ref
> rspec './spec/integration/git/rugged/bare_repository_spec.rb[1:2:5:2]' #
> R10K::Git::Rugged::BareRepository behaves like a git bare repository
> determining ref type can infer the type of a tag ref
> rspec './spec/integration/git/rugged/bare_repository_spec.rb[1:2:5:3]' #
> R10K::Git::Rugged::BareRepository behaves like a git bare repository
> determining ref type can infer the type of a commit
> rspec './spec/integration/git/rugged/bare_repository_spec.rb[1:2:5:4]' #
> R10K::Git::Rugged::BareRepository behaves like a git bare repository
> determining ref type returns :unknown when the type cannot be inferred
> rspec './spec/integration/git/rugged/thin_repository_spec.rb[1:1:1:1]' #
> R10K::Git::Rugged::ThinRepository behaves like a git thin repository cloning
> creates a working copy of the repo
> rspec './spec/integration/git/rugged/thin_repository_spec.rb[1:1:1:2]' #
> R10K::Git::Rugged::ThinRepository behaves like a git thin repository cloning
> sets the remote origin url to the provided url
> rspec './spec/integration/git/rugged/thin_repository_spec.rb[1:1:1:3]' #
> R10K::Git::Rugged::ThinRepository behaves like a git thin repository cloning
> sets the remote cache url to the path to the cache repo
> rspec './spec/integration/git/rugged/thin_repository_spec.rb[1:1:1:4]' #
> R10K::Git::Rugged::ThinRepository behaves like a git thin repository cloning
> adds the cache repo to the alternates file
> rspec './spec/integration/git/rugged/working_repository_spec.rb[1:2:2:1]' #
> R10K::Git::Rugged::WorkingRepository behaves like a git working repository
> updating the repo fetches objects from the remote
> rspec './spec/integration/git/rugged/working_repository_spec.rb[1:2:2:2:1]' #
> R10K::Git::Rugged::WorkingRepository behaves like a git working repository
> updating the repo without a proxy does not change proxy ENV
> rspec './spec/integration/git/rugged/working_repository_spec.rb[1:2:2:3:1]' #
> R10K::Git::Rugged::WorkingRepository behaves like a git working repository
> updating the repo with a proxy manages proxy-related ENV vars
>
> /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 --exclude-pattern
> ./spec/unit/forge/module_release_spec.rb failed
> ERROR: Test "ruby3.0" failed:
The build full is available at
https://people.debian.org/~kanashiro/ruby3.0/round2/builds/3/r10k/r10k_3.7.0-2+rebuild1633374645_amd64.build.txt
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: r10k
Source-Version: 3.7.0-2.1
Done: Daniel Leidert <dleid...@debian.org>
We believe that the bug you reported is fixed in the latest version of
r10k, 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.
Daniel Leidert <dleid...@debian.org> (supplier of updated r10k 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, 27 Nov 2021 00:24:35 +0100
Source: r10k
Architecture: source
Version: 3.7.0-2.1
Distribution: unstable
Urgency: medium
Maintainer: Puppet Package Maintainers
<pkg-puppet-de...@lists.alioth.debian.org>
Changed-By: Daniel Leidert <dleid...@debian.org>
Closes: 996116
Changes:
r10k (3.7.0-2.1) unstable; urgency=medium
.
* Non-maintainer upload.
* d/patches/13_fix_ruby_30_kwargs.patch: Add patch.
- Fix Ruby 3.0 keywords argument handling (closes: #996116).
* d/patches/series: Add new patch.
Checksums-Sha1:
fcecae59810fe968c07774e140f7f5561003adc6 2307 r10k_3.7.0-2.1.dsc
2800b166ab154bea12238b5734303567a7235732 5728 r10k_3.7.0-2.1.debian.tar.xz
9769c40e1f7b950ce32de6a868d448ecf39c7b8c 10807 r10k_3.7.0-2.1_amd64.buildinfo
Checksums-Sha256:
3a89fecf95cdb944cc101221d3b3c6776e479a930836f66898bfab49821de12d 2307
r10k_3.7.0-2.1.dsc
853b28c66980fcd126825440015ba14dd26c5b9cca5384e13f4096c4ab642f6e 5728
r10k_3.7.0-2.1.debian.tar.xz
14c73921475898eeb415f3b6dafeecb3490f599c640203e9b2894c25d3168b70 10807
r10k_3.7.0-2.1_amd64.buildinfo
Files:
7208f28bd578e28ef849f8341c0d645b 2307 admin optional r10k_3.7.0-2.1.dsc
ae7c87f64352efcb874671f91a4483ad 5728 admin optional
r10k_3.7.0-2.1.debian.tar.xz
3a1f4ee44ee5305df984f74601210be3 10807 admin optional
r10k_3.7.0-2.1_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEvu1N7VVEpMA+KD3HS80FZ8KW0F0FAmGhbg4ACgkQS80FZ8KW
0F0m4Q/+ILIAHztCpodGz4nrm3wiowfSnBInJ2tfz2w2Rmc3Sg+zkc4cmHhLMHtB
R8tZG26hbr05HR6TJ/noCEunYEm91bi8pnEMKf2QiYP+Y2RnDIO4CDwYaZsuSEls
GBZHZJlFEO5x/ZGJqjOM+0zkA0rkJpaJffuaEb1viteUhRDgnTTlLbj6ioIiiMFH
zbtvmHT5Ttl1SEW1S0JFOY045F3srXBFfW3/wBSqsgkHJpLXL/gfumeObauYMAZ2
vYdPepSYkG1Zu8Vb7F28s64g36KwImz72arqQoFA4cqh5uys5woHu6sw1IuXLFKf
PgSSxqhEKmcMYaB8Fs6a72+U5yiiZCEd87wRRi2iQ9OCQJO1PTcXxtMnUVDC8hJY
HikmYOBhNruu9boJP/3oP1FIBKHqmhS4E/si0iE9o1zU3/AMvcP8tyCGBbuXKuEt
1k8b7pbeUGbIRjCpuh46Sf2F5jAQg+gj32OlCbmi5WMrgddaAKk1Dj802rPU284j
WkeENUrJzyKjOf6RrRCcgeXkhePAIrn2utOAD5EXYuw0sYKpzVanpcLm9gRlKy/I
lxvLe9PwF+s912WN63sEE3VlDojNlqatrbCh6tQWh8SQTMXfEso52gzrCXVsAiyE
qs1wIbtZ+agWb3L+vzKO9Nov5eevTKFdc2N5jahbgHHEPpipqik=
=8vMU
-----END PGP SIGNATURE-----
--- End Message ---
