Your message dated Sun, 29 Jan 2023 04:18:28 +0200
with message-id <Y9XXdPM4ciNW1pRL@localhost>
and subject line Fixed since 0.25.0-1
has caused the Debian Bug report #995359,
regarding ruby-gitlab-labkit: autopkgtest needs update for new version of
ruby-jaeger-client: Could not find 'jaeger-client' (~> 0.10)
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 [email protected]
immediately.)
--
995359: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995359
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: ruby-gitlab-labkit
Version: 0.12.2-1
Severity: serious
X-Debbugs-CC: [email protected], [email protected]
Tags: sid bookworm
User: [email protected]
Usertags: needs-update
Control: affects -1 src:ruby-jaeger-client
Dear maintainer(s),
With a recent upload of ruby-jaeger-client the autopkgtest of
ruby-gitlab-labkit fails in testing when that autopkgtest is run with
the binary packages of ruby-jaeger-client from unstable. It passes when
run with only packages from testing. In tabular form:
pass fail
ruby-jaeger-client from testing 1.1.0-2
ruby-gitlab-labkit from testing 0.12.2-1
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-jaeger-client.
Currently this regression is blocking the migration of
ruby-jaeger-client to testing [1]. Of course, ruby-jaeger-client
shouldn't just break your autopkgtest (or even worse, your package), but
it seems to me that the change in ruby-jaeger-client 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-jaeger-client 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
[1] https://qa.debian.org/excuses.php?package=ruby-jaeger-client
https://ci.debian.net/data/autopkgtest/testing/amd64/r/ruby-gitlab-labkit/15624242/log.gz
┌──────────────────────────────────────────────────────────────────────────────┐
│ Checking Rubygems dependency resolution on ruby2.7
│
└──────────────────────────────────────────────────────────────────────────────┘
GEM_PATH= ruby2.7 -e gem\ \"gitlab-labkit\"
/usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1404:in `rescue in
block in activate_dependencies': Could not find 'jaeger-client' (~>
0.10) among 98 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/gitlab-labkit-0.12.2.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 'jaeger-client' (~> 0.10) - did find:
[jaeger-client-1.1.0] (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>'
OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Version: 0.25.0-1
This is fixed since 0.25.0-1:
https://ci.debian.net/packages/r/ruby-gitlab-labkit/unstable/amd64/
cu
Adrian
--- End Message ---
