[DRE-maint] Bug#995354: ruby-async-http: autopkgtest needs update for new version of ruby-protocol-http: Could not find 'protocol-http' (~> 0.20.0)

[Paul Gevers]

Source: ruby-async-http
Version: 0.52.5-1
Severity: serious
X-Debbugs-CC: debian-ci at lists.debian.org, ruby-protocol-http at packages.debian.org, ruby-protocol-http at packages.debian.org
Tags: sid bookworm
User: debian-ci at lists.debian.org
Usertags: needs-update
Control: affects -1 src:ruby-protocol-http src:ruby-protocol-http1

Dear maintainer(s),

With a recent upload of ruby-protocol-http the autopkgtest of
ruby-async-http fails in testing when that autopkgtest is run with the
binary packages of ruby-protocol-http from unstable. It passes when run
with only packages from testing. In tabular form:

                       pass            fail
ruby-protocol-http     from testing    0.22.5-1
ruby-async-http        from testing    0.52.5-1
versioned deps [0]     from testing    from unstable
all others             from testing    from testing

I copied some of the output at the bottom of this report. It looks to me
that you have to make your package compatible with the next version of
ruby-protocol-http

Currently this regression is blocking the migration of
ruby-protocol-http to testing [1]. Of course, ruby-protocol-http
shouldn't just break your autopkgtest (or even worse, your package), but
it seems to me that the change in ruby-protocol-http was intended and
your package needs to update to the new situation.

If this is a real problem in your package (and not only in your
autopkgtest), the right binary package(s) from ruby-protocol-http should
really add a versioned Breaks on the unfixed version of (one of your)
package(s). Note: the Breaks is nice even if the issue is only in the
autopkgtest as it helps the migration software to figure out the right
versions to combine in the tests.

More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[0] You can see what packages were added from the second line of the log
file quoted below. The migration software adds source package from
unstable to the list if they are needed to install packages from
ruby-protocol-http/0.22.5-1. I.e. due to versioned dependencies or
breaks/conflicts.
[1] https://qa.debian.org/excuses.php?package=ruby-protocol-http

https://ci.debian.net/data/autopkgtest/testing/amd64/r/ruby-async-http/15624245/log.gz
autopkgtest [00:17:44]: test gem2deb-test-runner: [-----------------------

┌──────────────────────────────────────────────────────────────────────────────┐
│ Checking Rubygems dependency resolution on ruby2.7
       │
└──────────────────────────────────────────────────────────────────────────────┘

GEM_PATH= ruby2.7 -e gem\ \"async-http\"
/usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1404:in `rescue in
block in activate_dependencies': Could not find 'protocol-http' (~>
0.20.0) among 69 total gem(s) (Gem::MissingSpecError)
Checked in
'GEM_PATH=/home/debci/.local/share/gem/ruby/2.7.0:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0'
at:
/usr/share/rubygems-integration/all/specifications/async-http-0.52.5.gemspec,
execute `gem env` for more information
	from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1401:in `block
in activate_dependencies'
	from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in `each'
	from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in
`activate_dependencies'
	from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1372: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>'
/usr/lib/ruby/vendor_ruby/rubygems/dependency.rb:313:in `to_specs':
Could not find 'protocol-http' (~> 0.20.0) - did find:
[protocol-http-0.22.5] (Gem::MissingSpecVersionError)
Checked in
'GEM_PATH=/home/debci/.local/share/gem/ruby/2.7.0:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0'
, execute `gem env` for more information
	from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1402:in `block
in activate_dependencies'
	from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in `each'
	from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in
`activate_dependencies'
	from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1372: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>'





-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature
Type: application/pgp-signature
Size: 495 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-ruby-extras-maintainers/attachments/20210930/9a9c0a05/attachment-0002.sig>