"gouttegd (Damien Goutte-Gattat)" <noreply@dev.gnupg.org> writes:

I've just pushed the two fixes. `GNUPGHOME` is now set to the tests directory when running the tests and `gpg-connect-agent` is now looked for in `PATH` at runtime.

When the tests are run, Scute now contacts the agent intended for the tests instead of any agent running on behalf of the Jenkins user. And so the tests pass or skip appropriately.

I've just pushed the two fixes. GNUPGHOME is now set to the tests directory when running the tests and gpg-connect-agent is now looked for in PATH at runtime.

All build artifacts are accessible

I see several problems here:

All build artifacts are accessible, e.g.: https://jenkins.gnupg.org/job/scute/ws/XTARGET/native/obj/tests/test-suite.log

OK, I pushed my fix into master.

The canonical repo is git://git.gnupg.org . We have not yet mirrored it at dev.gnupg.org.

Since there is no news for the last two weeks, I am wondering: am I the one blocking the situation here? Are you waiting for me to do something to make progress?

Yes, I am ready to accept write access to the Scute repository.

Justus, please apply the patches.

I think the best method to make sure Scute can always find the socket is to use gpg-connect-agent to ask for the socket: we call gpg-connect-agent 'GETINFO socket_name' /bye and read the reply.

This is ambiguous and the email is not mentioned. Given how old this is and
Niibe's opinion, I'm closing this issue.

I maintain scute in Debian. It works for me for years.
I suspect it was build time issue.

1.4.0 works, indeed. I didn't realize that was the latest version. The web page
is woefully out-of-date, but following the ftp link got me what I needed.

Scute 1.2.0 is very old. It should be fixed in 1.4.0.

Marcus, can you please look at it?