[Bug 226110] Merge Review: lucene

[bugzilla at redhat.com]

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.


https://bugzilla.redhat.com/show_bug.cgi?id=226110

Alexander Kurtakov <akurtako at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |akurtako at redhat.com

--- Comment #2 from Alexander Kurtakov <akurtako at redhat.com> 2010-10-13 02:25:18 EDT ---
> lucene.noarch: W: file-not-utf8 /usr/share/doc/lucene-2.4.1/CHANGES.txt
Fixed.
> lucene.src:40: W: mixed-use-of-spaces-and-tabs (spaces: line 31, tab:line 40)
Fixed.

> lucene-contrib.noarch: W: no-documentation
Fixed.
> lucene-contrib.noarch: W: class-path-in-manifest
> /usr/share/java/lucene-contrib/lucene-lucli-2.4.1.jar
> needs to be fixed
Fixed.
> 
> lucene-demo.noarch: W: no-documentation
Nothing to do.
> 
> lucene-javadoc.noarch: W: dangerous-command-in-%post rm
> lucene-javadoc.noarch: W: dangerous-command-in-%postun rm
Fixed
> 
> [!]  Buildroot is correct
> (%{_tmppath}/%{name}-%{version}-%{release}-root-%(%{__id_u} -n))
Removed. We don't need it in F-15

> [!]  All independent sub-packages have license of their own
> subpackages should have LICENSE.txt of their own
Fixed.


> [!]  Package requires other packages for directories it uses.
> Package is missing Requires on Java/jpackage-utils
Fixed
> 
> [!]  Permissions on files are set properly.
> use defattr(-,root,root,-) in files section
Fixed.

> [!]  Packages have proper BuildRequires/Requires on jpackage-utils
Fixed.
> [!]  Javadoc subpackages have Require: jpackage-utils
Fixed.

> [!]  Latest version is packaged.
> Latest version is 3.0.2 (2.9.3 in 2.x line)
We can't build it now until we migrate eclipse.

Koji build:
http://koji.fedoraproject.org/koji/buildinfo?buildID=200237

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.