Arch Linux User Repository

upstream updated, package updated, it indeed does now build correctly.

per upstream, build has been fixed and new version (3.484) should be up within the next 24 hours.

@deep_thought -

got your out-of-date notification. unfortunately, 3.483 gives the following error during build:

cc -c -O3 -Dunix -Dlinux -DHAVE_ANSIC_C -DASYNC_IO \
-D_LARGEFILE64_SOURCE -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector-strong -fno-plt libasync.c  -o libasync.o 
libasync.c:1173:1: error: conflicting types for ‘async_write_no_copy’
 async_write_no_copy(struct cache *gc,long long fd,char *buffer,long long size,long long offset,long long depth,char *free_addr)
 ^~~~~~~~~~~~~~~~~~~
libasync.c:225:8: note: previous declaration of ‘async_write_no_copy’ was here
 size_t async_write_no_copy(struct cache *gc,long long fd,char *buffer,long long size,off64_t offset,long long depth,char *free_addr);
        ^~~~~~~~~~~~~~~~~~~
make: *** [makefile:1026: iozone_linux-AMD64.o] Error 1

so i'll need to pass it upstream. no 3.483 for now, i'm afraid.

@applebloom-

terribly sorry! you are correct.

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

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).

# 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!

@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.

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

@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!

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