New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
pgpewrap hard-coded paths break things #1271
Comments
Thanks. I've corrected a handful of paths in:
The commit's in my 'devel/trivial' branch: e05e13a |
Is libexec the new standard everywhere? This issue still persists if I set the prefix on configure to anything other than the default. Is it possible to run the file through configure to procedurally give it the correct directory? $ mkdir tmp
$ ./configure --prefix=$PWD/tmp
...
$ make
...
$ make install
...
$ ls tmp/libexec/neomutt/
pgpewrap smime_keys
$ grep pgpewrap tmp/share/doc/neomutt/samples/gpg.rc
# set pgp_encrypt_only_command="/usr/libexec/neomutt/pgpewrap gpg-2comp -v --batch --output - --encrypt --textmode --armor --always-trust -- -r %r -- %f"
set pgp_encrypt_only_command="/usr/libexec/neomutt/pgpewrap gpg --batch --quiet --no-verbose --output - --textmode --armor --encrypt -- --recipient %r -- %f"
# set pgp_encrypt_sign_command="/usr/libexec/neomutt/pgpewrap gpg-2comp %?p?--passphrase-fd 0? -v --batch --output - --encrypt --sign %?a?-u %a? --armor --always-trust -- -r %r -- %f"
set pgp_encrypt_sign_command="/usr/libexec/neomutt/pgpewrap gpg %?p?--pinentry-mode loopback --passphrase-fd 0? --batch --quiet --no-verbose --textmode --output - %?a?--local-user %a? --armor --sign --encrypt -- --recipient %r -- %f" Incorrect directories here ^ |
You know, there is a guaranteed fix which is also the reason I've never seen this in spite of Neomutt being installed in /opt/local. All it takes is ignoring the immediate upstream and listening to their upstream with regards to the correct means of integrating GnuPG with Mutt and/or Neomutt. It really does “just work” and it's not that hard to install. … Oh come on, @flatcap, you already knew I'd notice sooner or later. 😉 |
I just updated, and I think this commit has broken some things for me. I tried to send an encrypted mail and got the following error.
I reverted I'm using neomutt-git on Arch, but AFAICT the package doesn't change much. |
line 31 is the problem, it's changing the libexec dir to something that hasn't been hardcoded in. |
Thanks @mjsir911, removing that line fixes it for me. |
This explains why we don't see the same sort of thing in the MacPorts version since it handles configuration slightly differently in the port file. It's mainly aimed at just rewriting the $PREFIX and/or $EPREFIX while honouring the existing directory structure of packages. |
Expected Behaviour
Following the useGPG tutorial, get a working gpg setup going
Actual Behaviour
Doesn't work because when copying and decompressing my system's gpgrc (located at
/usr/share/doc/neomutt-20180512/samples/gpg.rc.bz2
on gentoo), points at file/usr/lib/neomutt/pgpewrap
when it is actually located at/usr/libexec/neomutt/pgpewrap
I suspect there is a similar issue with the other files in
/usr/libexec/neomutt
, but I haven't confirmedSteps to Reproduce
Follow the instructions on useGPG on a system configured to point at any directory other than the default
/usr/lib/neomutt/pgpewrap
Write an email either encrypting or encrypting and signing
How often does this happen?
NeoMutt Version
Extra Info
Temporary fix
This is an easy fix locally on my machine, just replace the broken paths with the fixed ones.
The text was updated successfully, but these errors were encountered: