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
Task Type Bug Report
Category makepkg
Status Closed
Assigned To Allan McRae (Allan)
Architecture All
Severity Low
Priority Normal
Reported Version git
Due in Version 4.2.0
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Summary 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.
   force-binary-sigs.diff (0.5 KiB)
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
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...

Loading...