[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#743338: marked as done (lighttpd: "Broken" migration to /var/www/html)

Your message dated Tue, 4 Dec 2018 08:58:30 +0100
with message-id <20181204075828.6qp7nemlbppfpxyr@laureti-dev>
and subject line Re: Bug#743338: lighttpd: "Broken" migration to /var/www/html
has caused the Debian Bug report #743338,
regarding lighttpd: "Broken" migration to /var/www/html
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 owner@bugs.debian.org
immediately.)


-- 
743338: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=743338
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: lighttpd
Version: 1.4.35-1
Severity: important

Hi!

Today I was seeing a lot of 404 errors in my lighttpd log.
All my files were perfectly under /var/www and I really couldn't find
anything wrong with them.

Then I saw that lighttpd was upgraded from 1.4.33-1+nmu2 to 1.4.35-1 and
in the changelog I saw "Change the default document root /var/www/html"
(it took a while to figure out and look at the changelog).

I see two problems here: it broke my server without any message (there
isn't a message in NEWS, for example) and the placeholder page gives a
wrong path too:

"The DocumentRoot, which is the directory under which all your HTML
files should exist, is set to /var/www."

I am also thinking if it should automatically change/update my
/etc/lighttpd/lighttpd.conf file to include the new path (like happened)
or if it should only use /var/www/html on new installs.

Thank you!

Best regards,
Nelson

-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (990, 'testing'), (100, 'experimental'), (100, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.13-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages lighttpd depends on:
ii  init-system-helpers         1.18
ii  libattr1                    1:2.4.47-1
ii  libbz2-1.0                  1.0.6-5
ii  libc6                       2.18-4
ii  libfam0                     2.7.0-17.1
ii  libldap-2.4-2               2.4.39-1
ii  libpcre3                    1:8.31-2
ii  libssl1.0.0                 1.0.1f-1
ii  libterm-readline-perl-perl  1.0303-1
ii  lsb-base                    4.1+Debian12
ii  mime-support                3.54
ii  perl                        5.18.2-2+b1
ii  systemd                     204-8
ii  zlib1g                      1:1.2.8.dfsg-1

Versions of packages lighttpd recommends:
ii  spawn-fcgi  1.6.3-1

Versions of packages lighttpd suggests:
ii  apache2-utils  2.4.7-1
ii  openssl        1.0.1f-1
pn  rrdtool        <none>

-- Configuration Files:
/etc/lighttpd/conf-available/10-dir-listing.conf changed [not included]

-- no debconf information

--- End Message ---
--- Begin Message --- 
On Tue, Apr 01, 2014 at 06:24:31PM -0300, Nelson A. de Oliveira wrote:
> Today I was seeing a lot of 404 errors in my lighttpd log.
> All my files were perfectly under /var/www and I really couldn't find
> anything wrong with them.
> 
> Then I saw that lighttpd was upgraded from 1.4.33-1+nmu2 to 1.4.35-1 and
> in the changelog I saw "Change the default document root /var/www/html"
> (it took a while to figure out and look at the changelog).
> 
> I see two problems here: it broke my server without any message (there
> isn't a message in NEWS, for example) and the placeholder page gives a
> wrong path too:

There still is no message in NEWS, but at this point in time, version
1.4.35-1 is older than Debian oldstable (jessie). I fear that it no
longer makes any sense to add these news. We missed the point where that
was useful unfortunately.

> "The DocumentRoot, which is the directory under which all your HTML
> files should exist, is set to /var/www."

This has been fixed (likely around 1.4.43 according to the git history).

> I am also thinking if it should automatically change/update my
> /etc/lighttpd/lighttpd.conf file to include the new path (like happened)
> or if it should only use /var/www/html on new installs.

That's a sane suggestion, but difficult to implement given Debian's
requirements on conffiles (as explained by Arno Töll). I fear that it is
no longer useful to implement this scheme as two Debian stable releases
have happend since and most users will already have endured the
resulting pain. It simply is no longer worth the effort and risk.

I don't see anything useful that can be done at this point for
addressing the reported problem. New installations (since jessie) will
not experience problems and old installations are very likely to have
run into the problem already. Therefore I am closing the bug. Please
reopen it, if you disagree.

Helmut

--- End Message ---
Reply to: