Your message dated Mon, 16 Mar 2020 10:51:04 +0000
with message-id <e1jdnkq-000ixn...@fasolo.debian.org>
and subject line Bug#953199: fixed in r10k 3.4.1-3
has caused the Debian Bug report #953199,
regarding r10k: autopkgtest needs update for new version of ruby-puppet-forge: 
strict undeclared dependency
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.)


-- 
953199: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953199
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: r10k
Version: 3.1.0-1
Severity: serious
Tags: sid bullseye
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:ruby-puppet-forge

[X-Debbugs-CC: debian...@lists.debian.org,
ruby-puppet-fo...@packages.debian.org]

Dear maintainers,

With a recent upload of ruby-puppet-forge the autopkgtest of r10k fails
in testing when that autopkgtest is run with the binary packages of
ruby-puppet-forge from unstable. It passes when run with only packages
from testing. In tabular form:
                       pass            fail
ruby-puppet-forge      from testing    2.3.2-1
r10k                   from testing    3.1.0-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-puppet-forge
to testing [1]. Of course, ruby-puppet-forge shouldn't just break your
autopkgtest (or even worse, your package), but it seems to me that the
change in ruby-puppet-forge 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-puppet-forge 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-puppet-forge

https://ci.debian.net/data/autopkgtest/testing/amd64/r/r10k/4452690/log.gz

fatal: not a git repository (or any of the parent directories): .git
GEM_PATH= ruby2.5 -e gem\ \"r10k\"
/usr/lib/ruby/2.5.0/rubygems/dependency.rb:312:in `to_specs': Could not
find 'puppet_forge' (~> 2.2.8) - did find: [puppet_forge-2.3.2]
(Gem::MissingSpecVersionError)
Checked in
'GEM_PATH=/home/debci/.gem/ruby/2.5.0:/var/lib/gems/2.5.0:/usr/lib/ruby/gems/2.5.0:/usr/share/rubygems-integration/2.5.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.5.0',
execute `gem env` for more information
        from /usr/lib/ruby/2.5.0/rubygems/specification.rb:1469:in `block in
activate_dependencies'
        from /usr/lib/ruby/2.5.0/rubygems/specification.rb:1458:in `each'
        from /usr/lib/ruby/2.5.0/rubygems/specification.rb:1458:in
`activate_dependencies'
        from /usr/lib/ruby/2.5.0/rubygems/specification.rb:1440:in `activate'
        from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_gem.rb:68:in `block
in gem'
        from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_gem.rb:67:in
`synchronize'
        from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_gem.rb:67:in `gem'
        from -e:1:in `<main>'

Attachment: signature.asc
Description: OpenPGP digital signature


--- End Message ---
--- Begin Message ---
Source: r10k
Source-Version: 3.4.1-3
Done: Sebastien Badia <sba...@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 953...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sebastien Badia <sba...@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: Mon, 16 Mar 2020 00:13:10 +0100
Source: r10k
Architecture: source
Version: 3.4.1-3
Distribution: unstable
Urgency: medium
Maintainer: Puppet Package Maintainers 
<pkg-puppet-de...@lists.alioth.debian.org>
Changed-By: Sebastien Badia <sba...@debian.org>
Closes: 953199
Changes:
 r10k (3.4.1-3) unstable; urgency=medium
 .
   * d/control: Fix puppet-forge version (Closes: #953199)
Checksums-Sha1:
 d5e48ff27865fcf73c3305ec5bbbaa4c7689fd0d 2299 r10k_3.4.1-3.dsc
 f696a8e4e8e372d681316557b802dfe822d021d4 5172 r10k_3.4.1-3.debian.tar.xz
 ac16571884ecbe7789cf78334fe9df580e95fea0 12933 r10k_3.4.1-3_source.buildinfo
Checksums-Sha256:
 966587ae2166137dd4a4d28cf2eba646980201265b9cdac57cef32df512815d5 2299 
r10k_3.4.1-3.dsc
 94709efb5e832c066876c458b88fddd2de1641b6af1c6c9905e10937b8ec9890 5172 
r10k_3.4.1-3.debian.tar.xz
 4f87d14f2501a0ab5270348617f834bafa670222aa3578ce29e39ffe74a6665c 12933 
r10k_3.4.1-3_source.buildinfo
Files:
 ac44a3906ba454b4c1004ad96b6614ce 2299 admin optional r10k_3.4.1-3.dsc
 b3da2dcb1e1873b588cbdfa46bcbf2c0 5172 admin optional r10k_3.4.1-3.debian.tar.xz
 490ac2782c735a8023504bfcdaf83244 12933 admin optional 
r10k_3.4.1-3_source.buildinfo

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEfkPprL9yerPPCIUzhxbORhSkUtgFAl5vVicACgkQhxbORhSk
Uti7Gg/+MCu+PP/jvqsR30fKl8bTbaT2fVJ5qb4D7x0d/Ps4fPkLjnW9hF63le8P
nLdBmP0VgD3DbpR4yxpHFuBGSHyALAwQCHqWnwMtqEAqcxHsXsTRWeFb5ez6Xptg
h+7dN8H32yWPuDgYjE3F14NZe0HlMUvkqGKIF9OsXv53C3k0H/zswCyVXoKUu0mE
evVeuxHNyAknjV/Vq3PdM29oINGuFsFyJ1i+sMJfOg1dOFTVDiADsRVtH9zemGyc
Rc26oSClAksGaX+gjqrOm0/4WeIwvFTqQ+/O2lBCgK5UgRao0OZ3dCreTMovfauI
AUiB9Vs/hpM6SKFTJPpaEhDiZjODu42KEoq256mtNyuHqZcxpdPq/fFS+Xc91tmc
GrNK9i9Fjc7rDM5xKt79WJw6k1loacN6AL8OnBs8bLQ66VYtqDGDKGRIy4WpXYEy
myG1Y/KaVURWwptWkmwzH8X58P9b1g0VRcyGRJoQwHBuUk9EM50CJR/4Jsw9P37/
LiLuwEuz2t1JOLCj/xsWMoW3g6Sr6Hdck00kxChZA+WT4rMZZ7ROie0fp9dEMnd6
eI5ST2FsvZFm3Z0iYagKJAT2y0+Q7uXzQMbFD/QL0WqrNGtR8YrCWRbi8nNP3JsV
RmU6reVuMSVoNKBXrnD9XLoru6Oj++xK9/+rFtw5sAwLNROinMI=
=sO19
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to