gopass: update to 1.12.0.

[dshynkev]

General

• This is a new package and it conforms to the quality requirements

Have the results of the proposed changes been tested?

• I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
• I generally don't use the affected packages but briefly tested this PR

[dshynkev]

One thing of note: this version changed the way the gpg binary is selected. They assume gpg points to the version of GPG the user uses, but on Void it points to GPG v1, which is probably not what most use.

One must export GOPASS_GPG_BINARY=$(which gpg2) for it to keep working with GPG v2.

Should I note this in a post-install message?

[ericonr]

I'd use /usr/bin/gpg2 directly instead of which.

You could also open an RFC for dropping old GPG, if you think it's feasible.

[dshynkev]

It should be possible. A few of current gnupg revdeps definitely support gnupg2.

I'll file an RFC, but perhaps for now a post-install message is best?
It might take a while to phase out v1 if at least one of its revdeps really requires it.

I could also patch gopass if that's more appropriate. Sorry, not sure about the Void packaging etiquette.

[dshynkev]

I've tentatively added a message.

[ericonr]

It might take a while to phase out v1 if at least one of its revdeps really requires it.

Fair enough :)

Ideally, we want to make the package with as little friction as possible. If Void still defaulting to gnupg 1 makes it an issue (assuming most users do actually use gnupg2 instead), we can consider patching, IMO. I'm tagging @fnogcps so they can leave their thoughts here.

[ahesford]

Upstream is doing this wrong. GPG2 provides gpgconf to provide a machine-readable way to discover the path to the gpg binary. If gpgconf is available, you query that for the full path to the gpg executable, which in Void returns /usr/bin/gpg2. If gpgconf is not available, then you fall back to looking for gpg in the path.

[ericonr]

@dshynkev see #28217 :)

[ahesford]

FYI, upstream is considering properly looking for the gpg2 binary. Might want to keep an eye on that PR and, if it's accepted, backport the patch for this release if they don't cut a new release.

[dshynkev]

Thanks for reporting it to them!

[ahesford]

gopasspw/gopass@2b2c605

[dshynkev]

The next version got tagged. Didn't want to carry a non-trivial patch (just that commit alone didn't work) when release was imminent, and so finally we're here. Sorry about the delay!