Package: r10k Version: 2.5.0-1 Severity: grave The rugged provider, as provided by ruby-rugged in Debian, does neither support HTTPS, nor SSH. As this is a hard dependency, I think it is safe to assume it should work.
As long as rugged is in this state, I don't think a dependency with all the problems is in order. Output: | ERROR -> Failed to authenticate SSH session: Unable to extract public key from private key file: Method unimplemented in libgcrypt backend at HOME/.r10k/git/ssh---...@gitlab-bla-blub.git | ERROR -> Failed to resolve address for https: Name or service not known at HOME/.r10k/git/https---github.com-foo-bar.git Bastian -- System Information: Debian Release: 9.0 APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages r10k depends on: ii ruby 1:2.3.3 ii ruby-colored 1.2-2 ii ruby-cri 2.7.0-2 ii ruby-gettext-setup 0.7-1 ii ruby-log4r 1.1.10-4 ii ruby-minitar 0.5.4-3.1 ii ruby-multi-json 1.11.2-3 ii ruby-puppet-forge 2.2.2-2 ii ruby-rugged 0.24.0+ds1-2 ii ruby-semantic-puppet 0.1.4-2 Versions of packages r10k recommends: ii git 1:2.11.0-2 r10k suggests no packages. -- no debconf information
