| Summary: | tarme with ruby 2.5 issue | ||
|---|---|---|---|
| Product: | [Developer tools] releaseme | Reporter: | Ralf Habacker <ralf.habacker> |
| Component: | general | Assignee: | Harald Sitter <sitter> |
| Status: | RESOLVED NOT A BUG | ||
| Severity: | normal | ||
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Bug Depends on: | |||
| Bug Blocks: | 373932 | ||
| Attachments: | releaseme log file | ||
|
Description
Ralf Habacker
2019-02-08 16:53:21 UTC
Can't reproduce. I just installed Leap 15, installed git and ruby, and it works fine. what's the output with `export RELEASEME_DEBUG=5` Git commit ebf62e9ed303a7f65cd062cd67ebfdbea7acc80f by Harald Sitter. Committed on 08/05/2019 at 12:26. Pushed by sitter into branch 'master'. fail more obviously when clones go wrong previously we'd eat the output and then stumble over the directory not existing. since that makes it hard to figure out the clone has failed instead raise the output as error might be the underlying problem of M +5 -2 lib/releaseme/git.rb M +10 -0 test/git_test.rb https://commits.kde.org/releaseme/ebf62e9ed303a7f65cd062cd67ebfdbea7acc80f Created attachment 119917 [details] releaseme log file https://bugs.kde.org/show_bug.cgi?id=404104#add_comment(In reply to Harald Sitter from comment #1) > what's the output with `export RELEASEME_DEBUG=5` see appended file I initial recognized the issue with releaseme version from Oct 11 2018 and updating to git master gives some more informations about the issue, which persists. From the log I would say that releaseme tries to clone the repo with an ssh url (git@git.kde.org...) instead of using the anonymous url (git://anongit.kde.org). This fails if the related users ssh key is not present. (In reply to Ralf Habacker from comment #4) > From the log I would say that releaseme tries to clone the repo with an ssh > url (git@git.kde.org...) instead of using the anonymous url > (git://anongit.kde.org). > This fails if the related users ssh key is not present. Loading an ssh private key with ssh-agent does not solve the issue as assumed by me - releaseme ignores ssh-agent completly. > From the log I would say that releaseme tries to clone the repo with an ssh url (git@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. |