SOLR 1.4 debian packaging

[Thomas Koch <th...@koch.ro>]

@solr-dev: Could sbd. from upstream help us out with a working tomcat.policy 
for solr? For now I just granted all permissions to solr.

Hi Jan-Pascal (et al),

I've uploaded the current state of my packaging effort of SOLR 1.4 to
http://github.com/thkoch2001/pkg-debian-solr
(This is a new repository and not compatible with the one found at the same 
place until today)

I still have some things, where I'm stuck, listed in debian/TODO, for your 
convenience copied here:

- Review web.xml.
- enable junit tests on build?
- Build javadocs?
- Decide, where dist/apache-solr-dataimporthandler-1.4.0.jar should go:
  - /usr/share/solr/WEB-INF/lib/
  - /usr/share/java
  Or should maybe all jars go to /usr/share/java and be symlinked?
- Review debian/tomcat.policy
- Delete obsolete topgit branches from 1.3

And I forgot one todo issue in the file: - test with Jetty

About GIT and topgit:

- upstream tarballs are available from the git repository with pristine-tar

- the git setup is the default one proposed by git-buildpackage. So git-
  buildpackage should work on this repository without any configuration

- patches are managed with topgit according to this workflow:
  http://lists.alioth.debian.org/pipermail/vcs-pkg-discuss/2009-
December/000688.html

Best regards,

Thomas Koch, http://www.koch.ro

Re: SOLR 1.4 debian packaging

[Shalin Shekhar Mangar <sh...@gmail.com>]

On Tue, Dec 22, 2009 at 4:15 AM, Chris Hostetter
<ho...@fucit.org>wrote:

>
> : @solr-dev: Could sbd. from upstream help us out with a working
> tomcat.policy
> : for solr? For now I just granted all permissions to solr.
>
>  * solr needs read for the conf directory.
>
>
With the new Java based replication in Solr 1.4, people who need
configuration replication need read/write access for the conf directory.


-- 
Regards,
Shalin Shekhar Mangar.

Re: SOLR 1.4 debian packaging

[Erik Hatcher <er...@gmail.com>]

Also, Solr's DataImportHandler needs write to a .properties files in  
conf/

	Erik


On Dec 21, 2009, at 5:45 PM, Chris Hostetter wrote:

>
> : @solr-dev: Could sbd. from upstream help us out with a working  
> tomcat.policy
> : for solr? For now I just granted all permissions to solr.
>
> I'm not very familiar with tomcat security policy declarations, but in
> general...
>
> * solr needs read/write to whatever is configured to be the data  
> dir(s)
>
> * if you want support for persistant core admin changes, then solr  
> needs
> read/write to the solr home dir, and the solr.xml file in that  
> directory.
>
> * solr needs read for the conf directory.
>
> * if you want config file replication, then solr needs write access to
> the conf directory (on slave machine)
>
>
> ...if it were me: i'd just use a full read/write policy for some top
> level "solr" directory, and then keep everything in there, but it  
> depends
> on how "generic" you are devising the packages.
>
>
> -Hoss
>

Re: SOLR 1.4 debian packaging

[Chris Hostetter <ho...@fucit.org>]

: @solr-dev: Could sbd. from upstream help us out with a working tomcat.policy 
: for solr? For now I just granted all permissions to solr.

I'm not very familiar with tomcat security policy declarations, but in 
general...

 * solr needs read/write to whatever is configured to be the data dir(s)

 * if you want support for persistant core admin changes, then solr needs 
read/write to the solr home dir, and the solr.xml file in that directory.

 * solr needs read for the conf directory.

 * if you want config file replication, then solr needs write access to 
the conf directory (on slave machine)


...if it were me: i'd just use a full read/write policy for some top 
level "solr" directory, and then keep everything in there, but it depends 
on how "generic" you are devising the packages.


-Hoss