[Pkg-puppet-devel] Bug#918779: r10k: uninitialized constant Cri::Error

Nicolas Dandrimont olasd at debian.org
Fri Jan 11 14:47:51 GMT 2019


Package: r10k
Version: 2.6.3-1
Followup-For: Bug #918779

Control: severity -1 grave
Control: tags -1 + buster sid

Dear maintainer,

I'm bumping the severity of this bug as this makes the current combination of
r10k and ruby-cri versions in buster and sid unusable.

Thanks for maintaining r10k!
Nicolas

-- System Information:
Debian Release: buster/sid
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'unstable'), (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages r10k depends on:
ii  ruby                1:2.5.1
ii  ruby-colored        1.2-2
ii  ruby-cri            2.15.2-1
ii  ruby-gettext-setup  0.30-2
ii  ruby-log4r          1.1.10-4
ii  ruby-minitar        0.6.1-1
ii  ruby-multi-json     1.12.1-1
ii  ruby-puppet-forge   2.2.9-2
ii  ruby-rugged         0.27.4+ds-1

Versions of packages r10k recommends:
ii  git  1:2.20.1-1

r10k suggests no packages.

-- no debconf information



More information about the Pkg-puppet-devel mailing list