Your message dated Sun, 24 Jan 2010 11:28:19 +0100
with message-id <[email protected]>
and subject line Package removed from Debian unstable
has caused the Debian Bug report #553543,
regarding libroxen-diary: dir-or-file-in-var-www /var/www/diary/
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
553543: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=553543
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: libroxen-diary
Version: 0.9-8.1
Severity: serious
User: [email protected]
Usertags: dir-or-file-in-var-www

Debian packages should not install files under /var/www. This is not
one of the /var directories in the File Hierarchy Standard and is
under the control of the local administrator. Packages should not
assume that it is the document root for a web server; it is very
common for users to change the default document root and packages
should not assume that users will keep any particular setting. 

Packages that want to make files available via an installed web server
should instead put instructions for the local administrator in a
README.Debian file and ideally include configuration fragments for
common web servers such as Apache.

As an exception, packages are permitted to create the /var/www
directory due to its past history as the default document root, but
should at most copy over a default file in postinst for a new install.

Refer to Filesystem Hierarchy Standard (The /var Hierarchy) for
details.

One solution that works is to put configuration files into
/etc/<package_name>, put static content, if any, into
/usr/{share,lib}/<package_name>, then create /var/lib/<package name>
as home for the package, and symlink the files from /etc and /usr/
into the /var/lib/<package_name>. Then create a simple set of
configuration snippets for popular web servers (for example, files one
may link into /etc/apache2/conf.d) and put them into
/etc/<package_name>. This way user modifiable files stil live in /etc,
and a simple operation can make the package go live.

Filed as serious, since this is a violation of the FHS (which is part
of policy), and also since a package with these files will currently
get this package rejected. See
  http://lists.debian.org/debian-devel-announce/2009/10/msg00004.html
for details. This means the package has been deemed too buggy to be in
Debian.

manoj


-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'oldstable'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.31.4-anzu-2 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages libroxen-diary depends on:
pn  roxen | roxen2 | caudium      <none>     (no description available)

libroxen-diary recommends no packages.

libroxen-diary suggests no packages.



--- End Message ---
--- Begin Message ---
Version: 0.9-8.1+rm

Package removed from Debian unstable: http://bugs.debian.org/566416

-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi


--- End Message ---

Reply via email to