Skip to content

Fix issue that prevented freight-cache from working with GnuPG 2.x #73

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.

Sign up for GitHub

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

Open
mattock wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Fix issue that prevented freight-cache from working with GnuPG 2.x #73

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -27,6 +27,10 @@ Build the cache of all the files needed to be accepted as a Debian archive:

freight cache

If your system has GnuPG 2.x make sure that a gpg-agent is running or the above
command will fail. Also make sure you have installed a pinentry package (e.g.
pinentry-curses) that suits your needs.

Serve `/var/cache/freight` via your favorite web server and install it as an APT source:

echo "deb http://example.com $(lsb_release -sc) main" | sudo tee /etc/apt/sources.list.d/example.list
Expand Down
7 changes: 7 additions & 0 deletions lib/freight/apt.sh
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -207,6 +207,13 @@ EOF

} >"$DISTCACHE/Release"

# Pinentry may fail on GnuPG 2.x without GPG_TTY, see
# https://github.com/freight-team/freight/issues/72
if GPG_TTY=$(tty)
then
export GPG_TTY
fi

# Sign the top-level `Release` file with `gpg`, for each key and
# concatenate signatures.
for GPGKEY in $GPG; do
Expand Down