Bug 201646 - textproc/apache-solr: Missing bin files and directories (potentially revert to 4.x or create apache-solr4)
Summary: textproc/apache-solr: Missing bin files and directories (potentially revert t...
Status: Closed DUPLICATE of bug 201455
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: Normal Affects Many People
Assignee: Kurt Jaeger
URL:
Keywords: needs-patch, needs-qa
Depends on:
Blocks:
 
Reported: 2015-07-17 09:17 UTC by Fernando Herrero Carrón
Modified: 2015-08-03 17:14 UTC (History)
4 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Fernando Herrero Carrón 2015-07-17 09:17:25 UTC
The online documentation on running Solr (https://cwiki.apache.org/confluence/display/solr/Running+Solr) several script utilities that should be found under bin/ such as bin/solr or bin/post. Those scripts are indeed found in the source distfile but are not distributed with the port.
Comment 1 Paul Mather 2015-07-21 13:46:04 UTC
(In reply to elferdo from comment #0)

Also not installed with this port is the server/ directory from the distribution that the bin/ scripts use.

The upgrade of apache-solr to 5.2.1 appears not to take into account that it is a major upgrade of Solr and certain things that held for Solr 4 no longer hold for Solr 5.  As it stands, apache-solr is currently completely broken.

If the upgrade isn't going to be fixed, could we please revert it back to 4.10?  Right now, I'm having to "pkg lock" my installed apache-solr to prevent it from being upgraded.
Comment 2 Kubilay Kocak freebsd_committer freebsd_triage 2015-07-22 09:29:15 UTC
Thank you for your report(s)

textproc/apache-solr is currently unmaintained, so it's likely this issue won't progress quickly without proposed patches that a committer (potentially unfamiliar with solr/java etc) can review and commit.

I am cc'ing the maintainer of the apache-solr3 port in the hope that they may be able to provide something useful.

Along with patches I highly recommend thorough testing & QA, including attaching the following test output to this issue

 * portlint -AC
 * poudriere testport (or bulk -t)

See the following for more information and instructions:

https://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/testing.html

I also highly recommend someone put their hand up to maintain this port going forward. There are many resources available to assist people in ramping up as a new maintainer :)
Comment 3 Kurt Jaeger freebsd_committer freebsd_triage 2015-08-03 13:59:00 UTC
Sorry, @work
Comment 4 Kurt Jaeger freebsd_committer freebsd_triage 2015-08-03 17:14:06 UTC
The problems are my fault: At that time I had no test case, I now have one and
will work in PR201455 on that problem.

*** This bug has been marked as a duplicate of bug 201455 ***