This is because Metaproxy is running as a different user now -
and old lock files etc, previously created as "nobody" would cause
permission problems for CF.
Section: net
Architecture: any
Depends: ${shlibs:Depends}, libmetaproxy4 (= ${Source-Version})
+Conflicts: cf-engine (<= 2.12.5)
Description: Z39.50/SRU router (main executable)
This is a universal router, proxy and encapsulated metasearcher
for information retrieval protocols. It accepts, processes, interprets
Prefix: %{_prefix} /etc/metaproxy
BuildRequires: pkgconfig, libyaz4-devel >= 4.2.27, libyazpp4-devel >= 1.2.7
BuildRequires: libxslt-devel, boost-devel
+Conflicts: cf-engine <= 2.12.5
Packager: Adam Dickmeiss <adam@indexdata.dk>
URL: http://www.indexdata.com/metaproxy
Group: Applications/Internet