Historical bug tracker for the Pacman package manager.
The pacman bug tracker has moved to gitlab:
https://gitlab.archlinux.org/pacman/pacman/-/issues
This tracker remains open for interaction with historical bugs during the transition period. Any new bugs reports will be closed without further action.
The pacman bug tracker has moved to gitlab:
https://gitlab.archlinux.org/pacman/pacman/-/issues
This tracker remains open for interaction with historical bugs during the transition period. Any new bugs reports will be closed without further action.
FS#38503 - makepkg creates unusable signatures depending on the user's gpg settings
Attached to Project:
Pacman
Opened by Lars Gustäbel (gustaebel) - Tuesday, 14 January 2014, 10:08 GMT
Last edited by Allan McRae (Allan) - Saturday, 08 February 2014, 12:09 GMT
Opened by Lars Gustäbel (gustaebel) - Tuesday, 14 January 2014, 10:08 GMT
Last edited by Allan McRae (Allan) - Saturday, 08 February 2014, 12:09 GMT
|
DetailsSummary and Info:
Depending on the "armor" setting in ~/.gnupg/gpg.conf makepkg creates either binary (.sig) or unusable ascii-armored (.asc) gpg signatures. As a fix, I propose that makepkg calls gpg using the "--no-armor" command line option. Steps to Reproduce: Add the "armor" option to ~/.gnupg/gpg.conf and create a package with "makepkg --sign". Instead of a .sig signature a .asc signature will be created. |
This task depends upon
Closed by Allan McRae (Allan)
Saturday, 08 February 2014, 12:09 GMT
Reason for closing: Fixed
Additional comments about closing: git commit 47a4741a
Saturday, 08 February 2014, 12:09 GMT
Reason for closing: Fixed
Additional comments about closing: git commit 47a4741a
Comment by Allan McRae (Allan) -
Thursday, 30 January 2014, 07:54 GMT
What name and email would you like on the git commit?
Comment by Lars Gustäbel (gustaebel) -
Sunday, 02 February 2014, 08:56 GMT
"Lars Gustäbel <lars@gustaebel.de>" is just fine...
force-binary-sigs.diff