From: [email protected]

Package: spikeproxy
Version: 1.4.7-7
Severity: serious
Justification: Policy 9.1.1



-- System Information:
Debian Release: 3.1
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.7
Locale: LANG=C, LC_CTYPE=C

Versions of packages spikeproxy depends on:
ii python 2.3.4-1 An interactive high-level object-o ii python-pyopenssl 0.6-1 Python wrapper around the OpenSSL

-- no debconf information


It appears spikeproxy stores it's variable data (user-generated via
browsing) in /usr/share/spikeproxy/spikeProxyUI, which is in clear
violation of FHS and Debian Policy. Quote from version 2.2 of FHS:

[snip]
4.11 /usr/share : Architecture-independent data

4.11.1 Purpose

The /usr/share hierarchy is for all read-only architecture independent
data files.
[/snip]

"read-only" means no variable data belongs in /usr/share. It should
live somewhere under /var.

I know this is how the author probably set up his package, but to bring
it in line with Debian Policy, it will need some sanity patches and
directory changes.

thanks,
tim


--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

--- SoupGate-Win32 v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)