Bug 1682446 - Issue with gpg vs gpg2 dependency
Summary: Issue with gpg vs gpg2 dependency
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: git-annex
Version: 29
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Ben Boeckel
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-02-25 18:19 UTC by dermungo
Modified: 2019-03-15 18:28 UTC (History)
3 users (show)

Fixed In Version: git-annex-6.20181011-2.fc28 git-annex-6.20181011-2.fc29
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-03-13 19:05:24 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description dermungo 2019-02-25 18:19:30 UTC
Description of problem:

git-annex needs gpg for some encrypted special remotes.

I encountered the issue using a  git-annex-remote-googledrive remote, but I suspect the issue is more general. Perhaps, as alluded to here, https://git-annex.branchable.com/bugs/git-annex_can__39__t_find_gpg_if_it__39__s_named_gpg2/ , it's something with the build system that should be configured with gpg2.



Version-Release number of selected component (if applicable):6.20181011


How reproducible:

Steps to Reproduce:
1. install git-annex
https://github.com/Lykos153/git-annex-remote-googledrive
2. install git-annex-remote-googledrive
3. clone repository 
4. enable special remote 
5. try to copy a test file to the special remote

Actual results:
```
git annex copy --to google text_upload.txt
copy text_upload.txt (to google...) 

  gpg: createProcess: runInteractiveProcess: exec: does not exist (No such file or directory)
failed
git-annex: copy: 1 failed
```

Expected results:
```
git annex copy --to google text_upload.txt
copy text_upload.txt (to google...) 
ok
(recording state in git...)
```

Additional info:
Installing gpg manually
```
dnf install gpg
```
fixes the problem

Comment 1 Elliott Sales de Andrade 2019-03-04 08:36:44 UTC
Neither gpg2 nor gpg are available during the build of git-annex, so it won't bake in either program, and fallback to plain gpg. The link above says git-annex will respect git config with higher priority, so you can do: git config [--global] gpg.program gpg2

Note that there's a Fedora 30 change to swap the binary names: https://fedoraproject.org/wiki/Changes/GnuPG2_as_default_GPG_implementation so this won't necessary in F30.

Comment 2 Fedora Update System 2019-03-04 11:10:48 UTC
git-annex-6.20181011-2.fc29 has been submitted as an update to Fedora 29. https://bodhi.fedoraproject.org/updates/FEDORA-2019-b42ce8382e

Comment 3 Fedora Update System 2019-03-04 11:11:03 UTC
git-annex-6.20181011-2.fc28 has been submitted as an update to Fedora 28. https://bodhi.fedoraproject.org/updates/FEDORA-2019-d144a962b8

Comment 4 Fedora Update System 2019-03-05 04:37:38 UTC
git-annex-6.20181011-2.fc28 has been pushed to the Fedora 28 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-d144a962b8

Comment 5 Fedora Update System 2019-03-05 14:43:57 UTC
git-annex-6.20181011-2.fc29 has been pushed to the Fedora 29 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-b42ce8382e

Comment 6 Fedora Update System 2019-03-13 19:05:24 UTC
git-annex-6.20181011-2.fc28 has been pushed to the Fedora 28 stable repository. If problems still persist, please make note of it in this bug report.

Comment 7 Fedora Update System 2019-03-15 18:28:44 UTC
git-annex-6.20181011-2.fc29 has been pushed to the Fedora 29 stable repository. If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.