Trouble with symlinked conffiles

[Jan-Pascal van Best]

Hi all,

I'm having a bit of trouble with bug# 515945. The bug is caused by this:

- solr-tomcat5.5 needs some tweaking of the tomcat5.5 configuration.
This configuration is placed in /etc/solr/tomcat.policy and symlinked to
/etc/tomcat5.5/policy.d/

- When tomcat5.5 and solr-tomcat5.5 are installed at the same time, the
following steps happen:
  - tomcat5.5 is unpacked
  - solr-tomcat5.5 is unpacked. /etc/solr/tomcat.policy is installed as
/etc/solr/tomcat.policy.dpkg-new. The symlink is installed (but for the
moment dangling)
  - tomcat5.5 is configured and started. This fails because of the
dangling symlink
  - solr-tomcat5.5 is not configured because of the previous error, so
the tomcat.policy.dpkg-new is not renamed to tomcat.policy and the
symlink stays dangling.

I've tried reversing the symlink (placing the actual conffile in
/etc/tomcat5.5/policy and symlinking to /etc/solr/), but this causes
similar problems when updating from the solr-tomcat5.5 version in Lenny.
And it feels wrong.

Does any of you have any ideas about:
- how to deal with packages placing configuration items into other
package's configuration directories properly?
- how to proceed in the case of solr, including providing a proper
upgrade path?

Thanks for any help,

Jan-Pascal


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 260 bytes
Desc: OpenPGP digital signature
Url : http://lists.alioth.debian.org/pipermail/pkg-java-maintainers/attachments/20090220/fade78b9/attachment.pgp