Bug#734441: link to If
Package: apache2-doc Version: 2.4.6-3 Severity: wishlist File: /usr/share/doc/apache2-doc/manual/en/mod/mod_setenvif.html file:///usr/share/doc/apache2-doc/manual/en/mod/mod_setenvif.html mentions If twice, but does not link them to file:///usr/share/doc/apache2-doc/manual/en/mod/core.html#if -- To UNSUBSCRIBE, email to debian-apache-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87txdgnypf@jidanni.org
Bug#717610: a second run of aptitude safe-upgrade clears it
By the way, we here doing apt upgrades don't necessarily understand what apache2-maintscript-helper invoked from a modified environment. Please hint required arguments manually is all about. -- To UNSUBSCRIBE, email to debian-apache-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87bo5tfsdc@jidanni.org
Bug#711755: don't attempt to reload apache2 if it wasn't running before we started the upgrade
Package: apache2 Version: 2.4.4-6 Severity: minor I'm telling you guys, not everybody runs apache2 24/7/365 days a year, so please double check if it was running first (before the upgrade started) before causing these error messages during upgrades! ... Replacing config file /etc/phpmyadmin/config-db.php with new version dbconfig-common: flushing administrative password [FAIL] Reloading web server: apache2 failed! failed! invoke-rc.d: initscript apache2, action reload failed. Setting up dmsetup (2:1.02.77-2) ... update-initramfs: deferring update (trigger activated) Setting up libdevmapper1.02.1:i386 (2:1.02.77-2) ... ... Thanks! -- To UNSUBSCRIBE, email to debian-apache-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87bo7fea5r@jidanni.org
Re: [php-maint] Apache 2.4 MediaWiki Debian tips
It turns out one needs to install libapache2-mod-php5 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707759 -- To UNSUBSCRIBE, email to debian-apache-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87k3n6o0j7@jidanni.org
Re: Apache 2.4 MediaWiki Debian tips
Yes so I decided to reinstall from scratch and now index.php is being interpreted as plain text so I cannot figure out how to make it interpreted as PHP here with apache 2.4 in Debian and any searches just give advice for older versions of apache. -- To UNSUBSCRIBE, email to debian-apache-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87d2sz36js@jidanni.org
Bug#707317: httpd.conf deleted
Package: apache2 Version: 2.4.4-2 Severity: wishlist I would just like to note that during upgrade the user's httpd.conf is thrown away as if there is no danger he had customized it. Also whatever messages you were trying to tell the user upon apt-get upgrade flies off the screen and is not stored anywhere. -- To UNSUBSCRIBE, email to debian-apache-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87wqr9arxx@jidanni.org
Bug#665436: PHP no longer usable
Package: apache2
Version: 2.4.1-2
Severity: grave
# a2enmod php5
Enabling module php5.
To activate the new configuration, you need to run:
service apache2 restart
# service apache2 restart
apache2: Syntax error on line 161 of /etc/apache2/apache2.conf: Syntax error on
line 1 of /etc/apache2/mods-enabled/php5.load: Cannot load
/usr/lib/apache2/modules/libphp5.so into server:
/usr/lib/apache2/modules/libphp5.so: cannot open shared object file: No such
file or directory
Action 'configtest' failed.
The Apache error log may have more information.
# set libapache2-mod-php5
# aptitude install $@
The following NEW packages will be installed:
apache2-mpm-prefork{a} (D: libapache2-mod-php5, R: apache2-doc, R:
phpmyadmin, R: wdg-html-validator) (for )
apache2.2-bin{a} (D: apache2-mpm-prefork, D: apache2.2-common, R:
apache2-bin) (for libapache2-mod-php5)
apache2.2-common{a} (D: apache2-mpm-prefork, D: libapache2-mod-php5, R:
apache2, R: apache2-bin, R: apache2-data) (for libapache2-mod-php5)
libapache2-mod-php5
0 packages upgraded, 4 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/4,369 kB of archives. After unpacking 12.1 MB will be used.
The following packages have unmet dependencies:
apache2-data: Conflicts: apache2.2-common but 2.2.22-2 is to be installed.
apache2: Conflicts: apache2.2-common but 2.2.22-2 is to be installed.
apache2-bin: Conflicts: apache2.2-bin but 2.2.22-2 is to be installed.
Conflicts: apache2.2-common but 2.2.22-2 is to be installed.
The following actions will resolve these dependencies:
Remove the following packages:
1) apache2
2) apache2-bin
3) apache2-data
--
To UNSUBSCRIBE, email to debian-apache-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/87limqh5mn@jidanni.org
Bug#665330: test /etc/init.d/MyPackage start before shipping, please
I have an idea, all /etc/init.d/ script packages should test to see they actually can be started and stopped before their debs get shipped. Hmmm, and all bin/ programs should given a test run too... to at least see they can print --version without segfaulting etc. Hmmm, all even more important than piuparts. I mean it would avoid show stoppers of the first degree. AT == Arno Töll deb...@toell.net writes: AT On 24.03.2012 01:59, jida...@jidanni.org wrote: May I humbly request that your build scripts in the future take the automobile for a test drive (/etc/init.d/apache2 start at least) at the factory, before it reaches the dealership. AT And your point is? Our package worked just fine until someone else AT decided to break unrelated packages by uploading broken reverse AT dependencies exactly 8 days after uploading and building our package - AT or to put it with your words after it left the factory. -- To UNSUBSCRIBE, email to debian-apache-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87mx76wz4w.fsf...@jidanni.org
Bug#665330: test /etc/init.d/MyPackage start before shipping, please
It doesn't matter who is to blame. A simple /etc/init.d/... start test could catch such grave bugs before they hit the user. Who is to blame could be figured out internally. -- To UNSUBSCRIBE, email to debian-apache-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87iphuwwyn@jidanni.org
Bug#665330: symbol lookup error: /usr/sbin/apache2: undefined symbol: pcre_info
Package: apache2.2-common Version: 2.2.22-2 Severity: grave Starting web server: apache2/usr/sbin/apache2: symbol lookup error: /usr/sbin/apache2: undefined symbol: pcre_info Action 'start' failed. -- To UNSUBSCRIBE, email to debian-apache-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87limsq98u@jidanni.org
Bug#547263: insserv: warning: current start runlevel(s) (empty) of script `apache2'
Package: apache2.2-common Version: 2.2.13-2 Severity: wishlist Seen on upgrade: Setting up apache2.2-common (2.2.13-2) ... insserv: warning: current start runlevel(s) (empty) of script `apache2' overwrites defaults (2 3 4 5). insserv: warning: current stop runlevel(s) (0 1 2 3 4 5 6) of script `apache2' overwrites defaults (0 1 6) -- To UNSUBSCRIBE, email to debian-apache-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#351841: clean up apache cruft
OK, hope I don't break anything. # find /etc/apache /etc/apache /etc/apache/conf.d # rm -r /etc/apache -- To UNSUBSCRIBE, email to debian-apache-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#528424: mention what check_forensic does
Package: apache2-utils X-debbugs-cc: fabbi...@fabbione.net Version: 2.2.11-3 File: /usr/share/man/man8/check_forensic.8.gz Tags: patch I hope this is what check_forensic does. At least that is what the source code says it does. $ zdiff -u /usr/share/man/man8/check_forensic.8.gz /tmp/check_forensic.8.gz --- /dev/fd/5 2009-05-13 03:09:02.023252658 +0800 +++ - 2009-05-13 03:09:02.030996382 +0800 @@ -9,6 +9,8 @@ to extract mod_log_forensic output from apache, apache-ssl and apache-perl log files. .PP +It checks the forensic log for requests that did not complete +and outputs the request log for each one. .SH AUTHOR This manual page was written by Fabio M. Di Nitto fabbi...@fabbione.net, for the Debian GNU/Linux system -- To UNSUBSCRIBE, email to debian-apache-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#528425: mention help in both versions of the Usage statement
Package: apache2.2-common
Version: 2.2.11-3
Severity: minor
File: /usr/sbin/apache2ctl
Please make sure help is mentioned in both cases below, so that there
is no longer the two lines with just 0.
# for i in -- ''; do for c in wc 'grep -ic help'; do k=apache2ctl ${i}help
21|$c;echo \# $k; eval $k; done; done
# apache2ctl --help 21|wc
2 6 142
# apache2ctl --help 21|grep -ic help
0
# apache2ctl help 21|wc
23 1701347
# apache2ctl help 21|grep -ic help
0
--
To UNSUBSCRIBE, email to debian-apache-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#528425: mention help in both versions of the Usage statement
I really don't understand the usefulness of this. You have two different types of help output. Depending on which one a users triggers, he will never know about the other. On the man page you document a help command, but the Usage messages, both of them, make no mention of it. You must admit that is wrong. Currently one will get more help by giving 'zz' instead of --help. -- To UNSUBSCRIBE, email to debian-apache-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#457708: add example of fully qualified domain name
!Common Problems !=== ! !1) Error message Could not determine the server's fully qualified domain name, !using 127.0.0.1 for ServerName during start ! !This can usually be ignored but it means that Apache httpd was unable to obtain !a fully-qualified hostname by doing a reverse lookup on your server's IP !address. You may want to add the fully-qualified hostname to /etc/hosts . Which is a science in itself. So you might want to add an example. Else it is easy to affect a lot of other programs, who's names I forgot. Here's what worked for me: 127.0.0.1 jidanni2.jidanni.org localhost jidanni2 I tried to get them to add such an example to hosts(5), but they said no. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#486078: emacs' show-trailing-whitespace
Sorry, I didn't notice. Actually they're easy to spot using e.g., emacs' show-trailing-whitespace. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#457339: SetEnv vs. SetEnvif vs. php
I see 301s 403s 200s... in my twisted homebrew mediawiki .htaccess mess's logs that now slip from my brain as I moved on to a different project... -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#457708: eliminate startup warnings
Package: apache2 Version: 2.2.6-3 Severity: minor Instead of the user having to search Google for ways to fix # apache2ctl start apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.0.1 for ServerName Could we instead have a configuration item [ ]use ___ [ ]use 'localhost' [ ]use contents of today's /etc/hostname [ ]use contents of /etc/hostname as found upon each start OK, but maybe those aren't fully qualified domain names. Anyway, this message should at least be addressed in the Debian docs without the user needing to search the Internet for a solution. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
cleaner perl printenv
/usr/share/doc/apache2-doc/cgi-examples/printenv:
print Content-type: text/plain; charset=iso-8859-1\n\n;
charset assumptions?
But mainly, this can be simplified to:
for (sort keys %ENV) {
$val = $ENV{$_};
$val =~ s|\n|\\n|g;
$val =~ s||\\|g;
print $_=\${val}\\n;
}
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#457339: SetEnv vs. SetEnvif vs. php
Package: apache2.2-common Version: 2.2.6-3 I have discovered a bug in the Debian apache2 and/or php packages. Consider the following .htaccess file, #SetEnvif User-Agent . ban #SetEnv ban Order Allow,Deny Allow from all Deny from env=ban Looking in error.log, if you uncomment the first line, all you will see [Fri Dec 21 23:23:23 2007] [error] [client 127.0.0.1] client denied by server configuration: /var/lib/bla/ which is good. If instead you uncomment the second line, you get [Fri Dec 21 23:26:24 2007] [error] [client 127.0.0.1] client denied by server configuration: /var/lib/bla/index.html [Fri Dec 21 23:26:24 2007] [error] [client 127.0.0.1] client denied by server configuration: /var/lib/bla/index.cgi [Fri Dec 21 23:26:24 2007] [error] [client 127.0.0.1] client denied by server configuration: /var/lib/bla/index.pl meaning that somehow index.php was forgotten on the list of things to stop! Indeed, one scratches their head about why the effect is not the same as the first. Or http://localhost/manual/env.html should expound further the secrets involved. If so please reassign to apache2-doc. Thanks. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
