Algorithm negotiation fail #203
Comments
|
@daggerok This more recent issue could be: ymnk/jsch-agent-proxy#29 Unfortunately it seems that library isn't being maintained anymore, so not sure what to do about a fix. The original issue, we'd have to reproduce again and get a debug log of to see if there's more information. Side note, it didn't seem like the exceptions were showing up in the logs you posted. Did you redirect the error stream in as well? |
|
hm.. maybe I forgot redirect 2>&1... gradle --debug asciidoctor gitPublishPush > 0.3.0-out.log 2> 0.3.0-err.log gradle --debug asciidoctor gitPublishPush > 0.3.2-out.log 2> 0.3.2-err.log gradle --debug asciidoctor gitPublishPush > 0.4.0-rc.2-out.log 2> 0.4.0-rc.2-err.log regards |
|
Sorry, for the back and forth here, but looks like you'll need both |
|
Yeah, this looks like that jsch-agent-proxy issue I linked above. Not sure what can be done about that though, there doesn't seem to be much info. |
|
sad... |
|
one solution is to update manually jsch files in .gradle/caches/modules-2/files-2.1/com.jcraft/jsch to version 0.1.54 |
|
Not sure if it can help, but we can try force needed dependency like so: buildscript {
repositories {
maven {
url "https://plugins.gradle.org/m2/"
}
}
dependencies {
classpath "org.ajoberstar:gradle-git-publish:0.4.0-rc.2"
}
configurations.all {
resolutionStrategy {
force 'com.jcraft:jsch:0.1.54'
}
}
}
apply plugin: "org.ajoberstar.git-publish"at the moment I'm using old version which is only worked for me 0.2.2: plugins {
id "org.ajoberstar.git-publish" version "0.2.2"
}Regards, |
|
@gaborvass I definitely would suggest against modifying anything in the @daggerok Yeah, that should work for forcing a version, though this may be fixed by using 0.3.3 publish plugin (which uses jsch 0.1.54, transitively). That 0.4.0-rc.2 version is a mistaken release from a while back. I'll have to see if there's way to remove it from the plugin portal. |
|
Hello, @ajoberstar seems like root cause of problem is not with jsch 0.1.54 but something else... I just have tried this: buildscript {
repositories {
maven {
url "https://plugins.gradle.org/m2/"
}
}
dependencies {
classpath "org.ajoberstar:gradle-git-publish:0.3.2"
}
configurations.all {
resolutionStrategy {
force "com.jcraft:jsch:0.1.54"
}
}
}
plugins {
id "org.asciidoctor.convert" version "1.5.3"
}
apply plugin: "org.ajoberstar.git-publish"
// skip other stuff..and wasn't successful, as well as using version 0.3.3
yes you can ask remove it in this discussion: https://discuss.gradle.org/t/removing-an-accidentaly-published-plugin/11703 Update: ./gradlew :docs:dependencies
# ...
asciidoctor
+--- org.asciidoctor:asciidoctorj:1.5.5
| +--- org.jruby:jruby-complete:1.7.26
| \--- com.beust:jcommander:1.35
\--- org.asciidoctor:asciidoctorj-groovy-dsl:1.0.0.preview2
+--- org.codehaus.groovy:groovy-all:1.8.9
\--- org.asciidoctor:asciidoctorj:1.5.1 -> 1.5.5 (*)anyway, switching back to 0.2.2.... Regards, |
|
OK, I found another worked configuration, this time for 0.3.0 version: buildscript {
configurations.all {
resolutionStrategy {
force "com.jcraft:jsch:0.1.54"
}
}
}
plugins {
id "org.ajoberstar.git-publish" version "0.3.0"
}But not 0.3.2 nor 0.3.3 don't work. Hope this will help... Regards, |
|
The JSch stuff has been the cause of most of the issues over the history of grgit. I'm hoping that something like #206 will help here. It seems that JGit supports falling back to your system ssh or plink. I'm hoping that's more reliable. |
|
Closing, as the fix for #206, which will be the default in Grgit 3, should resolve this. |
|
I was having the same issue with Jsch when I have env variable for an ssh-agent that I have killed
Start another ssh-agent and set env var to new one solved the error |
|
What version of Grgit are you on? As of Grgit 3, I no longer include the JSch Agent Proxy. Most of the time you'll be using the native SSH on your machine rather than JSch. |
|
None, sorry to comment on closed issue. |
Copied from ajoberstar/gradle-git-publish#42 by @daggerok
and follow up:
The text was updated successfully, but these errors were encountered: