FS#43199 - [pkgbuild-introspection] mkaurball fails to verify kernel sigs

Attached to Project: Community Packages
Opened by John (graysky) - Monday, 22 December 2014, 18:45 GMT
Last edited by Dave Reisner (falconindy) - Monday, 22 December 2014, 19:02 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Seems as though mkaurball fails when trying to verify sig files for [core]/linux since those sigs are for the tar ball (not xz) and patch (not xz) respectfully. This means that any AUR kernel PKGBUILD will also fail if it is in sync with the official ARCH PKGBUILD.

Additional info:
* package version(s) 6-1

Steps to reproduce:

Run on linux in trunk:
% mkaurball :(
==> Making package: linux 3.18.1-1 (Mon Dec 22 13:44:13 EST 2014)
==> Retrieving sources...
-> Found linux-3.18.tar.xz
-> Found linux-3.18.tar.sign
-> Found patch-3.18.1.xz
-> Found patch-3.18.1.sign
-> Found config
-> Found config.x86_64
-> Found linux.preset
-> Found change-default-console-loglevel.patch
==> Validating source files with sha256sums...
linux-3.18.tar.xz ... Passed
linux-3.18.tar.sign ... Skipped
patch-3.18.1.xz ... Passed
patch-3.18.1.sign ... Skipped
config ... Passed
config.x86_64 ... Passed
linux.preset ... Passed
change-default-console-loglevel.patch ... Passed
==> Verifying source file signatures with gpg...
linux-3.18.tar ... SOURCE FILE NOT FOUND
patch-3.18.1 ... SOURCE FILE NOT FOUND
==> ERROR: One or more PGP signatures could not be verified!
ERROR: makepkg exited non-zero
This task depends upon

Closed by  Dave Reisner (falconindy)
Monday, 22 December 2014, 19:02 GMT
Reason for closing:  Not a bug
Additional comments about closing:  Verification of kernel.org's GPG signatures requires makepkg from pacman-4.2
Comment by Dave Reisner (falconindy) - Monday, 22 December 2014, 18:53 GMT
Not a mkaurball bug. Your pacman (makepkg) is too old to support this.
Comment by John (graysky) - Monday, 22 December 2014, 18:54 GMT
Thanks Dave. I will wait for the 4.2.x series to hit [core] and request that this ticket gets closed.

Loading...