Package Details: iozone 3.506-4

Git Clone URL: https://aur.archlinux.org/iozone.git (read-only, click to copy)
Package Base: iozone
Description: A filesystem benchmark tool
Upstream URL: http://www.iozone.org/
Licenses: custom
Submitter: sanerb
Maintainer: gilcu3
Last Packager: gilcu3
Votes: 28
Popularity: 0.000000
First Submitted: 2015-08-25 00:00 (UTC)
Last Updated: 2024-09-12 07:57 (UTC)

Dependencies (2)

Required by (0)

Sources (1)

Latest Comments

« First ‹ Previous 1 2 3

sanerb commented on 2018-07-08 00:13 (UTC)

@applebloom-

terribly sorry! you are correct.

package fixed and bumped to most recent release (3.482). thanks!

applebloom commented on 2018-07-07 20:02 (UTC)

The install file refers in a message to a file, Guidelines.doc (supposedly it should be in /usr/share/doc/iozone), that isn't installed (and is nowhere in the package).

sanerb commented on 2017-06-19 14:55 (UTC) (edited on 2017-09-01 22:56 (UTC) by sanerb)

# Bug reports can be filed at https://bugs.square-r00t.net/index.php?project=3 # News updates for packages can be followed at https://devblog.square-r00t.net (If you want an RSS-feed only pertaining to my AUR packages, you can subscribe to https://devblog.square-r00t.net/rss/?category=aur 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. GPG signature "errors" are explained here: https://devblog.square-r00t.net/articles/a-note-on-using-gpg-signatures-in-pkgbuilds Please read; it's not a bug. Thanks!

sanerb commented on 2016-08-26 16:24 (UTC) (edited on 2016-08-26 16:33 (UTC) by sanerb)

@skrunc- 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 if: - 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 ( https://devblog.square-r00t.net/articles/a-note-on-using-gpg-signatures-in-pkgbuilds ) - 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 (UTC) (edited on 2016-08-26 16:07 (UTC) by skrunc)

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 (UTC)

@graysky: 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 https://bugs.square-r00t.net/index.php?project=3 # News updates for packages can be followed at https://devblog.square-r00t.net (If you want an RSS-feed only pertaining to my AUR packages, you can subscribe to https://devblog.square-r00t.net/rss/?category=aur 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. Thanks!

sanerb commented on 2016-06-03 19:29 (UTC)

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 (UTC)

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: https://gist.github.com/graysky2/c9b9d9ca14e87fe4a4d091dfb1c4fffd

« First ‹ Previous 1 2 3