Your message dated Mon, 09 Mar 2020 15:50:57 +0000
with message-id <e1jbkgd-000inj...@fasolo.debian.org>
and subject line Bug#953199: fixed in r10k 3.4.0-1
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.0-1
Done: Georg Faerber <ge...@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.
Georg Faerber <ge...@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: SHA256

Format: 1.8
Date: Mon, 09 Mar 2020 15:24:40 +0000
Source: r10k
Architecture: source
Version: 3.4.0-1
Distribution: unstable
Urgency: medium
Maintainer: Puppet Package Maintainers 
<pkg-puppet-de...@lists.alioth.debian.org>
Changed-By: Georg Faerber <ge...@debian.org>
Closes: 953199
Changes:
 r10k (3.4.0-1) unstable; urgency=medium
 .
   * New upstream version 3.4.0. (Closes: #953199)
   * d/control:
     + Rely on debhelper-compat and bump compat level to 12
     + Bump Standards-Version to 4.5.0 (no changes needed)
     + Run wrap-and-sort -abt
     + Add myself as Uploader
     + Depend on ruby-colored2, instead of ruby-colored
   * d/compat:
     - Drop, obsolete
   * d/manpages:
     + Drop obsolete manpages
     + Run wrap-and-sort -abt
   * d/patches: Refresh for new release
   * d/r10k.docs: Run wrap-and-sort -abt
   * d/salsa-ci.yml: Add to enable CI
Checksums-Sha1:
 1c7caec013643c0d4be794d18d3705657bac6494 1694 r10k_3.4.0-1.dsc
 c3557efd2ffc6f5c9fa0082482601aad78c2e0ea 211789 r10k_3.4.0.orig.tar.gz
 455aaadb88fb861c58abdaf7738b59a79c7160a6 4992 r10k_3.4.0-1.debian.tar.xz
 2f4f908e9a952c67377a8c8910f5ecbcb2b7c680 9969 r10k_3.4.0-1_amd64.buildinfo
Checksums-Sha256:
 604a68109554aa4c0b20b40916ec7181235802b2ee7983e2f864f9b3984bc657 1694 
r10k_3.4.0-1.dsc
 6981db22047375e24c0d0bec9b074a22d194706ee452e3ab5014c50f328749aa 211789 
r10k_3.4.0.orig.tar.gz
 0ef13019e70721253ebbf7a43278f17f4e3b60ea35f2240f92ae91b45925bf1f 4992 
r10k_3.4.0-1.debian.tar.xz
 31ff4b99cf52370ee04b8a918bfbbcb3f25c437694256b6f85243a2a63506af2 9969 
r10k_3.4.0-1_amd64.buildinfo
Files:
 40a72fce19aa3040e52dec894748639e 1694 admin optional r10k_3.4.0-1.dsc
 8e8a2b5cde75821c624d252947607af4 211789 admin optional r10k_3.4.0.orig.tar.gz
 9f233a9ff4a88e19daffaf9733e66c7d 4992 admin optional r10k_3.4.0-1.debian.tar.xz
 58b76b7e7fd846f3372c8ea228ad5ab8 9969 admin optional 
r10k_3.4.0-1_amd64.buildinfo

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

iHUEARYIAB0WIQTEfr/MTlfp/DLKNABGG+5dJAqekQUCXmZg6AAKCRBGG+5dJAqe
kT84AP4pz/KbBDvmcVAoDyhT183KEECVbXfXGW19Di7F5tb3xAEA35qGlQ3k8t33
T2ZuW2/LXKtEnRjLRcqyVRsVKWk2ogc=
=jBLM
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to