Scott,
I just added /opt/local/bin to the launchd job and it appears it has solved the problem.
My conclusion is that prior to the Monterey upgrade, gpg was on the existing path, for whatever reason. Configuration changes due to that upgrade caused it no longer to be on the configured path.
I have also confirmed that the --gpg-binary flag is not needed either and so have removed that.
Thanks for the simple solution!
Jeffrey
The launchd mechanism does not use the same PATH variable that your command line will. You need to set the PATH variable to add /usr/local/?? or wherever macports puts the gpg applications.
-Scott
Jeffrey,
Please reply-all so the mailing list benefits as well.
I ran the output through re and it matched as it should. I think the problem may be that it's not finding gpg. StackOverflow may be your best answer since it looks like the problem is in MacOS launchd. I personally use cron instead of launchd. Just never saw the need of such a needlessly complex interface.
...Ken Ken,
Thanks for your very quick response!
Here is the requested output:
iMac3:~ jas$ gpg --version gpg (GnuPG) 2.2.35 libgcrypt 1.10.1 Copyright (C) 2022 g10 Code GmbH This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law.
Home: /Users/jas/.gnupg Supported algorithms: Pubkey: RSA, ELG, DSA, ECDH, ECDSA, EDDSA Cipher: IDEA, 3DES, CAST5, BLOWFISH, AES, AES192, AES256, TWOFISH, CAMELLIA128, CAMELLIA192, CAMELLIA256 Hash: SHA1, RIPEMD160, SHA256, SHA384, SHA512, SHA224 Compression: Uncompressed, ZIP, ZLIB, BZIP2 iMac3:~ jas$
Jeffrey
Hi,
Could you run "$ gpg --version" and post its output? duplicity has to use this output, via regex, to check the version. Perhaps MacPort has modded the normal version lines.
...Ken
Ever since I upgraded to macOS Monterey, a launchd job that includes a call to duplicity will no longer work.
- The job is a php script.
- An example of the command is as follows:
env PASSPHRASE='************' /opt/local/bin/duplicity --gpg-binary /opt/local/bin/gpg --file-to-restore 20220805.s4.sql.rephunter.bz2 file:///Volumes/Backup1/RH-backup/20220805 /Volumes/Backup1/RH-backup/dbtemp/20220805.s4.sql.rephunter.bz2 >> /Users/jas/dbload.log 2>&1
- The script continues to work perfectly from the command line. My workaround is to run it from the command line.
- A possible difference with Monterey is that previously gpg could have been installed in a macOS-determined location. However with Monterey gpg was installed by MacPorts. So it might be in a different location. Or prior to Monterey it could have been in the same location; hard to tell now.
- Duplicity is throwing error output which includes the line "GPGError: failed to determine gnupg version of None from b''
- Searching on that error gives a page at https://bugs.launchpad.net/duplicity/+bug/1865427, where the suggestion is to add --gpg-binary with the path to gpg.
- I have added --gpg-binary /opt/local/bin/gpg but it does not help: the same error message is thrown.
Advice is appreciated.
Jeffrey _______________________________________________
Duplicity-talk mailing list
Duplicity-talk@nongnu.org
https://lists.nongnu.org/mailman/listinfo/duplicity-talk
_______________________________________________ Duplicity-talk mailing list Duplicity-talk@nongnu.orghttps://lists.nongnu.org/mailman/listinfo/duplicity-talk
_______________________________________________ Duplicity-talk mailing list Duplicity-talk@nongnu.orghttps://lists.nongnu.org/mailman/listinfo/duplicity-talk
|