Your message dated Wed, 29 Dec 2021 01:22:56 +0200
with message-id <20211228232256.GA6914@localhost>
and subject line Re: Bug#1000773: ruby-gitlab-sidekiq-fetcher: autopkgtest
needs update for new version of ruby-sidekiq: Could not find 'sidekiq' (>= 5, <
6.1)
has caused the Debian Bug report #1000773,
regarding ruby-gitlab-sidekiq-fetcher: autopkgtest needs update for new version
of ruby-sidekiq: Could not find 'sidekiq' (>= 5, < 6.1)
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.)
--
1000773: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000773
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-gitlab-sidekiq-fetcher
Version: 0.6.1-1
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:ruby-sidekiq
[X-Debbugs-CC: debian...@lists.debian.org, ruby-side...@packages.debian.org]
Dear maintainer(s),
With a recent upload of ruby-sidekiq the autopkgtest of
ruby-gitlab-sidekiq-fetcher fails in testing when that autopkgtest is
run with the binary packages of ruby-sidekiq from unstable. It passes
when run with only packages from testing. In tabular form:
pass fail
ruby-sidekiq from testing 6.3.1+dfsg-1
ruby-gitlab-sidekiq-fetcher from testing 0.6.1-1
all others from testing from testing
I copied some of the output at the bottom of this report.
Currently this regression is blocking the migration of ruby-sidekiq to
testing [1]. Of course, ruby-sidekiq shouldn't just break your
autopkgtest (or even worse, your package), but it seems to me that the
change in ruby-sidekiq 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-sidekiq 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-sidekiq
https://ci.debian.net/data/autopkgtest/testing/amd64/r/ruby-gitlab-sidekiq-fetcher/17076745/log.gz
┌──────────────────────────────────────────────────────────────────────────────┐
│ Checking Rubygems dependency resolution on ruby2.7
│
└──────────────────────────────────────────────────────────────────────────────┘
GEM_PATH= ruby2.7 -e gem\ \"gitlab-sidekiq-fetcher\"
/usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1404:in `rescue in
block in activate_dependencies': Could not find 'sidekiq' (>= 5, < 6.1)
among 61 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-sidekiq-fetcher-0.6.1.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 'sidekiq' (>= 5, < 6.1) - did find: [sidekiq-6.3.1]
(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>'
benchmark (default: 0.1.0)
bigdecimal (default: 2.0.0)
bundler (default: 2.1.4)
cgi (default: 0.1.0)
connection_pool (2.2.5)
csv (default: 3.1.2)
date (default: 3.0.0)
dbm (default: 1.1.0)
delegate (default: 0.1.0)
did_you_mean (default: 1.4.0)
etc (default: 1.1.0)
fcntl (default: 1.0.0)
fiddle (default: 1.0.0)
fileutils (default: 1.4.1)
forwardable (default: 1.3.1)
gdbm (default: 2.1.0)
getoptlong (default: 0.1.0)
gitlab-sidekiq-fetcher (0.6.1)
io-console (default: 0.5.6)
ipaddr (default: 1.2.2)
irb (default: 1.2.6)
json (default: 2.3.0)
logger (default: 1.4.2)
matrix (default: 0.2.0)
minitest (5.13.0)
mutex_m (default: 0.1.0)
net-pop (default: 0.1.0)
net-smtp (default: 0.1.0)
net-telnet (0.1.1)
observer (default: 0.1.0)
open3 (default: 0.1.0)
openssl (default: 2.1.2)
ostruct (default: 0.2.0)
power_assert (1.1.7)
prime (default: 0.1.1)
pstore (default: 0.1.0)
psych (default: 3.1.0)
racc (default: 1.4.16)
rack (2.1.4)
rake (13.0.3)
rdoc (default: 6.2.1.1)
readline (default: 0.0.2)
readline-ext (default: 0.1.0)
redis (4.2.5)
reline (default: 0.1.5)
rexml (default: 3.2.3.1)
rss (default: 0.2.8)
rubygems-update (3.2.27)
sdbm (default: 1.0.0)
sidekiq (6.3.1)
singleton (default: 0.1.0)
stringio (default: 0.1.0)
strscan (default: 1.0.3)
test-unit (3.3.9)
timeout (default: 0.1.0)
tracer (default: 0.1.0)
uri (default: 0.10.0)
webrick (default: 1.6.1)
xmlrpc (0.3.2)
yaml (default: 0.1.0)
zlib (default: 1.1.0)
autopkgtest [00:11:46]: test gem2deb-test-runner
OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Version: 0.8.0-1
On Sun, Nov 28, 2021 at 09:01:53PM +0100, Paul Gevers wrote:
> Source: ruby-gitlab-sidekiq-fetcher
> Version: 0.6.1-1
> Severity: serious
> Tags: sid bookworm
> User: debian...@lists.debian.org
> Usertags: needs-update
> Control: affects -1 src:ruby-sidekiq
>
> [X-Debbugs-CC: debian...@lists.debian.org, ruby-side...@packages.debian.org]
>
> Dear maintainer(s),
>
> With a recent upload of ruby-sidekiq the autopkgtest of
> ruby-gitlab-sidekiq-fetcher fails in testing when that autopkgtest is run
> with the binary packages of ruby-sidekiq from unstable. It passes when run
> with only packages from testing. In tabular form:
>
> pass fail
> ruby-sidekiq from testing 6.3.1+dfsg-1
> ruby-gitlab-sidekiq-fetcher from testing 0.6.1-1
> all others from testing from testing
>...
This was fixed in 0.8.0-1:
https://ci.debian.net/packages/r/ruby-gitlab-sidekiq-fetcher/unstable/amd64/
cu
Adrian
--- End Message ---
