On Tue, Apr 18, 2017 at 02:01:04PM (+0200), Bastian Blank wrote: > 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
severity 860548 normal stop Hi Bastian, Sorry for the delay, and thanks for this bug-report, Just tested on a bar clean sandbox. root@1330b8e762bd:~# irb irb(main):001:0> require('rugged') => true irb(main):002:0> Rugged.features => [:threads, :ssh] # r10k.yaml git: provider: 'rugged' And indeed, r10k fails (with the non-default r10k provider 'rugged') with the error, "Method unimplemented in libgcrypt" According and quoting the upstream documentation: https://github.com/puppetlabs/r10k/blob/master/doc/git/providers.mkd#supported-transports-with-rugged « libssh2 on Debian and Ubuntu is compiled against libgcrypto instead of OpenSSL due to licensing reasons, and unfortunately libgcrypto does not support a number of required operations, including reading from a private key file. You will need to either use shellgit or recompile your own libssh2-1 package to use OpenSSL on these distributions. » 'licensing reasons' are tracked in the bug https://bugs.debian.org/668271 We take a look to change r10k hard-deps on rugged. Thanks Sebastien
signature.asc
Description: PGP signature