Your message dated Mon, 28 Dec 2009 20:42:21 +0000
with message-id <1262032941.474098.2288.nullmai...@kmos.homeip.net>
and subject line Package w3c-linkchecker has been removed from Debian
has caused the Debian Bug report #553558,
regarding w3c-linkchecker: dir-or-file-in-var-www /var/www/w3c-linkchecker
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 ow...@bugs.debian.org
immediately.)
--
553558: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=553558
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: w3c-linkchecker
Version: 4.3-1
Severity: serious
User: lintian-ma...@debian.org
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 w3c-linkchecker depends on:
ii libconfig-general-perl 2.44-1 Generic Configuration Module
ii libhtml-parser-perl 3.62-1 collection of modules that parse H
ii libnet-ip-perl 1.25-2 Perl extension for manipulating IP
ii liburi-perl 1.37+dfsg-1 Manipulates and accesses URI strin
ii libwww-perl 5.833-1 Perl HTTP/WWW client/server librar
ii perl 5.10.1-6 Larry Wall's Practical Extraction
w3c-linkchecker recommends no packages.
Versions of packages w3c-linkchecker suggests:
ii libterm-readkey-perl 2.30-4 A perl module for simple terminal
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 4.3-1+rm
You filled the bug http://bugs.debian.org/553558 in Debian BTS
against the package w3c-linkchecker. I'm closing it at *unstable*, but it will
remain open for older distributions.
For more information about this package's removal, read
http://bugs.debian.org/553903. That bug might give the reasons why
this package was removed and suggestions of possible replacements.
Don't hesitate to reply to this mail if you have any question.
Thank you for your contribution to Debian.
--
Marco Rodrigues
--- End Message ---
