https://bugs.kde.org/show_bug.cgi?id=404104
Harald Sitter <sit...@kde.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|WAITINGFORINFO |NOT A BUG
--- Comment #6 from Harald Sitter <sit...@kde.org> ---
> From the log I would say that releaseme tries to clone the repo with an ssh
> url (g...@git.kde.org...) instead of using the anonymous url
> (git://anongit.kde.org).
This fails if the related users ssh key is not present.
This is expected. I do not quite recall why it uses writable urls but I know
that it was a specific choice. In any event to actually tag a release you need
write access, so it needs setting up one way or another.
As for your issue with actually getting the key found. Releaseme doesn't do
anything special there. It calls the git binary, whatever works with git when
you manually invoke it also works when it is run trough releaseme.
I am not entirely certain what you are trying to do but if it is signing
artifacts on a host that isn't localhost we had a long inspection of that issue
here https://markmail.org/message/jfzwohq25nxl7gzw it may be of some help.
--
You are receiving this mail because:
You are watching all bug changes.
