Package Details: iozone 3_434-4

Git Clone URL: (read-only)
Package Base: iozone
Description: A filesystem benchmark tool
Upstream URL:
Licenses: custom
Submitter: sanerb
Maintainer: sanerb
Last Packager: sanerb
Votes: 13
Popularity: 0.184755
First Submitted: 2015-08-25 00:00
Last Updated: 2016-06-26 04:48

Dependencies (2)

Required by (0)

Sources (2)

Latest Comments

sanerb commented on 2016-08-26 16:24


hrmmmm. yeah it builds fine for me...

couple questions for you.

1.) are you using an AUR helper (apacman, yaourt, etc.)?

2.) are you able to download a clean copy of the snapshot, untar it, cd into it, run makepkg --check (or just download the iozone3_434.tar file manually), and do (as the same user you're building the package as):

gpg --verify iozone3_434.tar.sig iozone3_434.tar

- 1.) above is false, and the above command returns "gpg: Good signature from..." on the second line of output, then the issue is somewhere in your makepkg configuration.
- 1.) above is false and the above command returns a FAILURE, you may not have imported my key correctly ( )
- 1.) above is true, i'd start by checking your AUR helper's config. i know apacman supports importing keys automatically, i can't recall if yaourt does or not. they use their own user to build packages, from what i remember. i can try to get you more help once i know which helper you're using, if you are.

skrunc commented on 2016-08-26 16:01

Hi sanerb,

I've got a problem with building the version "iozone3_434". Error is
FAILED (unknown public key 8C004C2F93481F6B)
ERROR: One or more PGP signatures could not be verified!
I did add your key to my local keyring but this error still persists.

What am I missing out? Regards

sanerb commented on 2016-06-26 04:49


sorry for the delay- laptop crash, etc. should be back up and running now.

your fixes/cleanups look awesome. incorporated them and pushed.


Please note the following additions:

# Bug reports can be filed at
# News updates for packages can be followed at

(If you want an RSS-feed only pertaining to my AUR packages, you can subscribe to in your favourite RSS reader.)

Note that you should still use the AUR web interface for flagging packages as out-of-date if a new version is released; the aforementioned bug tracker is to aid in issues with building/packaging/the PKGBUILD formats/etc. specifically.


sanerb commented on 2016-06-03 19:29

thanks graysky; sorry for the delay in response. i should have this fixed this weekend with a bump

graysky commented on 2016-05-22 19:21

Thank you for maintaining. The package 3_434-2 does not provide the man page and others. I have proposed a change to the PKGBUILD that does: