Dear Maintainer,

While updating ruby-faraday to new upstream, rebuild of
ruby-puppet-forge fails
here is the log of the failed rebuild

┌──────────────────────────────────────────────────────────────────────────────┐
│ Install Rubygems integration
metadata                                        │
└──────────────────────────────────────────────────────────────────────────────┘

generating gemspec at
/<<PKGBUILDDIR>>/debian/ruby-puppet-forge/usr/share/rubygems-integration/all/specifications/puppet_forge-3.0.0.gemspec
dh_installchangelogs -pruby-puppet-forge /<<PKGBUILDDIR>>/CHANGELOG.md
upstream
/usr/bin/ruby3.0 /usr/bin/gem2deb-test-runner

┌──────────────────────────────────────────────────────────────────────────────┐
│ Checking Rubygems dependency resolution on
ruby3.0                           │
└──────────────────────────────────────────────────────────────────────────────┘

GEM_PATH=/<<PKGBUILDDIR>>/debian/ruby-puppet-forge/usr/share/rubygems-integration/all:/<<PKGBUILDDIR>>/debian/.debhelper/generated/_source/home/.local/share/gem/ruby/3.0.0:/var/lib/gems/3.0.0:/usr/local/lib/ruby/gems/3.0.0:/usr/lib/ruby/gems/3.0.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.0.0:/usr/share/rubygems-integration/3.0.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.0.0
ruby3.0 -e gem\ \"puppet_forge\"
/usr/lib/ruby/vendor_ruby/rubygems/specification.rb:2248:in
`raise_if_conflicts': Unable to activate faraday_middleware-1.0.0,
because faraday-2.7.1 conflicts with faraday (~> 1.0) (Gem::ConflictError)
     from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1379:in
`activate'
     from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1417:in
`block in activate_dependencies'
     from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1399:in `each'
     from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1399:in
`activate_dependencies'
     from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1381:in
`activate'
     from
/usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in `block
in gem'
     from
/usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in
`synchronize'
     from
/usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in `gem'
     from -e:1:in `<main>'
abbrev (default: 0.1.0)

On Tue, 29 Nov 2022 22:30:43 +0530 Vinay <vinaykeshava@disroot.org>  wrote:
 > ruby3.0 -e gem\ \"puppet_forge\"
 > /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:2248:in
 > `raise_if_conflicts': Unable to activate faraday_middleware-1.0.0,
 > because faraday-2.7.1 conflicts with faraday (~> 1.0)
(Gem::ConflictError)

Upstream now support faraday 2.0
https://github.com/puppetlabs/forge-ruby/commit/06102bc9478d9d19fbe12b505639fb253d29ba54

On Sun, 18 Jun 2023 15:51:36 +0530 Pirate Praveen  <praveen@onenetbeyond.org> wrote:
 > Upstream now support faraday 2.0
 >
https://github.com/puppetlabs/forge-ruby/commit/06102bc9478d9d19fbe12b505639fb253d29ba54

I'm planning to upload ruby-faraday 2.0 to unstable around 1st August.

Control: severity -1 serious
ruby-faraday 2.x is now uploaded to unstable.

close 1025078 5.0.3-1
thanks

With now both ruby-faraday and ruby-puppet-forge up to date in sid, this issue
is solved.