Spec URL: <http://zarb.org/~david/hamcrest.spec> SRPM URL: <http://zarb.org/~david/hamcrest-1.1-2.jpp5.src.rpm> Description : Provides a library of matcher objects (also known as constraints or predicates) allowing 'match' rules to be defined declaratively, to be used in other frameworks. Typical scenarios include testing frameworks, mocking libraries and UI validation rules.
This package is required by junit4 4.4 and later.
I'll take this one.
Created attachment 321455 [details] build log
I can't build this in mock (fedora-devel-i386), please see attached build.log.
Naming: OK Licensing: OK No inclusion of pre-built binaries or libraries: OK Filesystem layout: OK No Packager, Vendor tag: OK Summary tag not ending with a period: OK Source tag: OK (md5sum matches) Buildroot tag: OK %install begins with removing buildroot: OK Changelog: OK Jar file naming: OK Directory structure: OK BuildRequires and Requires: OK
Running rpmlint against the mock built rpms: rpmlint /var/lib/mock/fedora-development-i386/result/*rpm hamcrest.i386: W: non-conffile-in-etc /etc/maven/fragments/hamcrest hamcrest-demo.i386: W: no-documentation rpm -qp --provides hamcrest-1.1-5.1.fc10.i386.rpm all-1.1.jar.so hamcrest = 0:1.1-5.1.fc10 hamcrest(x86-32) = 0:1.1-5.1.fc10 Is the Provides for all-1.1.jar.so correct?
hamcrest.i386: W: non-conffile-in-etc This is a bug in maven, as this file is not really a config file. hamcrest-demo.i386: W: no-documentation The demo depends on the main package, which contains the license. Otherwise, there is no other documentation. The all-1.1.jar.so was added automatically. It seems kind of weird.
Links for the spec file and SRPM that builds successfully: http://zarb.org/~david/hamcrest.spec http://zarb.org/~david/hamcrest-1.1-5.1.jpp5.src.rpm APPROVED
New Package CVS Request ======================= Package Name: hamcrest Short Description: Hamcrest matcher object framework Owners: dwalluck Branches: F-10 InitialCC:
CVS Done