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 ow...@bugs.debian.org immediately.) -- 743338: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=743338 Debian Bug Tracking System Contact ow...@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 libattr11: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 libpcre31:8.31-2 ii libssl1.0.0 1.0.1f-1 ii libterm-readline-perl-perl 1.0303-1 ii lsb-base4.1+Debian12 ii mime-support3.54 ii perl5.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 openssl1.0.1f-1 pn rrdtool -- 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.
Processed: Re: Bug#760423: lighttpd: systemd service does not automatically create /var/run/lighttpd
Processing control commands: > tags -1 + moreinfo unreproducible Bug #760423 [lighttpd] lighttpd: systemd service does not automatically create /var/run/lighttpd Added tag(s) unreproducible and moreinfo. -- 760423: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760423 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#760423: lighttpd: systemd service does not automatically create /var/run/lighttpd
Control: tags -1 + moreinfo unreproducible On Wed, Sep 03, 2014 at 11:30:58PM +0100, Ximin Luo wrote: > Package: lighttpd > Version: 1.4.35-3 > Severity: important > > Dear Maintainer, > > When switching to systemd, the directory /var/run/lighttpd is not > automatically > created (and chown www-data), causing the resulting service to fail. I am unable to reproduce the reported failure (using version 1.4.49-2) nor see how that could happen for you. In 1.4.30-1, support for systemd was added to lighttpd and that support includes /usr/lib/tmpfiles.d/lighttpd.tmpfile.conf which is supposed to create that directory. dh_installinit invokes this during postinst and systemd runs it during boot. There should be no way for it to go missing. > A workaround is to manually create the directory with the right ownership, but > I have not verified if this persists across restarts. Did the issue only happen on initial installation? Possibly the dh_installinit only later gained the ability to run systemd-tmpfiles during postinst? Can you reproduce the issue at all? If no, please close the bug. Helmut
Bug#866737: duplicate of 913249
Control: forcemerge 913249 -1 These reports about missing Term/ReadLine.pm are duplicates of #913249, which was fixed with the recent upload. Thus closing via forcemerge. Helmut
Processed: duplicate of 913249
Processing control commands:
> forcemerge 913249 -1
Bug #913249 {Done: Ximin Luo } [lighttpd] lighttpd: Can't
locate Term/ReadLine.pm in @INC
Bug #913249 {Done: Ximin Luo } [lighttpd] lighttpd: Can't
locate Term/ReadLine.pm in @INC
Marked as found in versions lighttpd/1.4.45-1.
Added tag(s) patch.
Bug #866737 [lighttpd] Enable Mod command fails on Stretch
Severity set to 'serious' from 'normal'
Severity set to 'serious' from 'normal'
Marked Bug as done
Marked Bug as done
Marked as fixed in versions lighttpd/1.4.49-2.
Marked as fixed in versions lighttpd/1.4.49-2.
Marked as found in versions lighttpd/1.4.49-1.1.
Marked as found in versions lighttpd/1.4.49-1.1.
Bug #887450 {Done: Ximin Luo } [lighttpd] lighttpd
missing dependency on perl5 for mod scripts
Merged 866737 887450 913249
--
866737: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866737
887450: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887450
913249: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913249
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: tagging lighttpd bugs
Processing commands for cont...@bugs.debian.org: > # the report has a link to the relevant upstream commit > tags 913528 + fixed-upstream Bug #913528 [src:lighttpd] lighttpd: CVE-2018-19052 Added tag(s) fixed-upstream. > # title says 1.4.49, but that's in sid > retitle 879496 new upstream release 1.4.52 available Bug #879496 [lighttpd] New upstream release 1.4.49 available Changed Bug title to 'new upstream release 1.4.52 available' from 'New upstream release 1.4.49 available'. > # the report has a link to the relevant upstream commit > tags 904741 + fixed-upstream Bug #904741 [lighttpd] lighttpd: create-mime.assign.pl skips mime types with capital letters Added tag(s) fixed-upstream. > # running lighttpd as another user is a new feature, not a bug > severity 715205 wishlist Bug #715205 [lighttpd] [lighttpd]: Running lighttpd as another user Severity set to 'wishlist' from 'normal' > End of message, stopping processing here. Please contact me if you need assistance. -- 715205: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=715205 879496: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879496 904741: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904741 913528: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913528 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#915545: aptsh FTCBFS: does not pass --host to ./configure
Source: aptsh
Version: 0.0.8
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap
aptsh fails to cross build from source, because it does not pass --host
to ./configure. The easiest way of doing so is letting dh_auto_configure
do it. The attached patch does that and makes aptsh cross buildable.
Please consider applying it.
Helmut
diff --minimal -Nru aptsh-0.0.8/debian/changelog
aptsh-0.0.8+nmu1/debian/changelog
--- aptsh-0.0.8/debian/changelog2016-12-18 22:40:11.0 +0100
+++ aptsh-0.0.8+nmu1/debian/changelog 2018-12-04 06:21:49.0 +0100
@@ -1,3 +1,10 @@
+aptsh (0.0.8+nmu1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Fix FTCBFS: Let dh_auto_configure pass --host to ./configure. (Closes: #-1)
+
+ -- Helmut Grohne Tue, 04 Dec 2018 06:21:49 +0100
+
aptsh (0.0.8) unstable; urgency=medium
* QA upload
diff --minimal -Nru aptsh-0.0.8/debian/rules aptsh-0.0.8+nmu1/debian/rules
--- aptsh-0.0.8/debian/rules2007-04-09 16:30:38.0 +0200
+++ aptsh-0.0.8+nmu1/debian/rules 2018-12-04 06:21:49.0 +0100
@@ -10,7 +10,7 @@
config.status: configure
dh_testdir
- CFLAGS="$(CFLAGS)" ./configure --prefix=/usr
--mandir=\$${prefix}/share/man --infodir=\$${prefix}/share/info
+ CFLAGS="$(CFLAGS)" dh_auto_configure --
'--libexecdir=$${prefix}/lib/aptsh'
build: build-stamp
@@ -43,12 +43,6 @@
dh_installdirs
$(MAKE) install DESTDIR=$(CURDIR)/debian/aptsh
-
- mkdir -p $(CURDIR)/debian/aptsh/usr/lib/aptsh/
- mv $(CURDIR)/debian/aptsh/usr/libexec/aptsh_ls
$(CURDIR)/debian/aptsh/usr/lib/aptsh/
- mv $(CURDIR)/debian/aptsh/usr/libexec/aptsh_rls
$(CURDIR)/debian/aptsh/usr/lib/aptsh/
- mv $(CURDIR)/debian/aptsh/usr/libexec/aptsh_printer
$(CURDIR)/debian/aptsh/usr/lib/aptsh/
- rm -rf $(CURDIR)/debian/aptsh/usr/libexec
binary-indep: build install
Bug#915558: idesk FTCBFS: uses the wrong pkg-config
Source: idesk Version: 0.7.5-6 Tags: patch upstream User: helm...@debian.org Usertags: rebootstrap idesk fails to cross build from source, because it uses the build architecture pkg-config. The cause is using AC_PATH_PROG for finding pkg-config. It is much better to simply use PKG_CHECK_MODULES. Unfortunately, that macro doesn't work, because it is wrongly used in configure.in inside an if rather than AS_IF. The attached patch fixes that and makes idesk cross buildable. Please consider applying it. Helmut --- idesk-0.7.5.orig/acinclude.m4 +++ idesk-0.7.5/acinclude.m4 @@ -181,16 +181,7 @@ PKG_CONFIG=$xft_prefix/bin/pkg-config fi fi - -AC_PATH_PROG(PKG_CONFIG, pkg-config, no) -if test "x$PKG_CONFIG" = "xno" ; then - ifelse([$2], , :, [$2]) -else - XFT_CFLAGS=`$PKG_CONFIG $xftconf_args --cflags xft` - XFT_LIBS=`$PKG_CONFIG $xftconf_args --libs xft` - ifelse([$1], , :, [$1]) -fi - +PKG_CHECK_MODULES([XFT],[xft],[$1],[$2]) ]) # AM_PATH_XFT(default-value, [ACTION-IF-FOUND [, ACTION-IF-NOT-FOUND]]]) --- idesk-0.7.5.orig/configure.in +++ idesk-0.7.5/configure.in @@ -116,13 +116,13 @@ AC_ARG_ENABLE( libsn, [ --enable-libsninclude code for LIBSN [default=no]]) -if test -n "$enable_libsn"; then +AS_IF([test -n "$enable_libsn"],[ PKG_CHECK_MODULES(LIBSN, libstartup-notification-1.0 >= 0.5) AC_MSG_RESULT([yes]) STARTUP="-DHAVE_STARTUP_NOTIFICATION -DSN_API_NOT_YET_FROZEN=1", -else +],[ AC_MSG_RESULT([no]) -fi +]) AM_CONDITIONAL(HAVE_STARTUP_NOTIFICATION, test x$LIBSN = xtrue) AC_SUBST(STARTUP)
Processed: Re: nvi: large tabstop causes segmentation fault
Processing control commands: > tag -1 + moreinfo unreproducible Bug #735673 [nvi] nvi: large tabstop causes segmentation fault Added tag(s) unreproducible and moreinfo. -- 735673: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=735673 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processing of nvi_1.81.6-15_source.changes
nvi_1.81.6-15_source.changes uploaded successfully to localhost along with the files: nvi_1.81.6-15.dsc nvi_1.81.6-15.debian.tar.xz nvi_1.81.6-15_amd64.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
