Re: mpm-itk as separate package
Am Sonntag, 4. August 2013, 18:13:32 schrieb Steinar H. Gunderson: > On Sun, Aug 04, 2013 at 10:21:59AM +, Jean-Michel Vourgère wrote: > > Right now, apache2.preinst check for an installed apache2-mpm-* > > package and creates a /etc/apache2/.apache2_mpm_selected > > temporary file with the information. > > > > apache2.postinst reads that file in enable_default_mpm() and > > enable the correct mpm. The temp file is then deleted. > > Does this properly account for the fact that mpm-itk >= 2.4.4-02 is > a module, not an MPM, and thus needs prefork to work? No, it does not, yet. We still have the older version that is a real MPM in the apache2 package. So there is some upgrade logic to do in that regard. Actually I had forgotten about that when I wrote my initial mail. But there is no great hurry about the separate mpm-itk package. -- 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/1771539.r0vVNC9bTs@k
Re: mpm-itk as separate package
On Sun, Aug 04, 2013 at 10:21:59AM +, Jean-Michel Vourgère wrote: > Right now, apache2.preinst check for an installed apache2-mpm-* package and > creates a /etc/apache2/.apache2_mpm_selected temporary file with the > information. > > apache2.postinst reads that file in enable_default_mpm() and enable the > correct > mpm. The temp file is then deleted. Does this properly account for the fact that mpm-itk >= 2.4.4-02 is a module, not an MPM, and thus needs prefork to work? /* Steinar */ -- Homepage: http://www.sesse.net/ -- 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/20130804161332.ga19...@uio.no
Bug#296493: apache2ctl -t should warn about non-initial #
On 4 Aug 2013, at 6:50 AM, Jean-Michel Vourgère wrote: > Kevin Bullock wrote: >> (...) I therefore >> suggest that 'apache2ctl -t' warn the user about the mid-line comment which >> could be an error. (...) > > Stefan Fritsch wrote: >> The documentation states: "Comments may not be included on a line >> after a configuration directive. " >> >> '#' signs are considered normal characters inside a directive, so a >> warning would not be appropriate either. But I agree that >> DirectoryIndex is not behaving correctly here. > > It's actually used in default configuration: > $ grep -e '^[[:space:]]*[^#[:space:]].*#' /etc/apache2/*/* > /etc/apache2/mods-available/autoindex.conf: IndexIgnore .??* *~ *# RCS CVS > *,v *,t > /etc/apache2/mods-enabled/autoindex.conf: IndexIgnore .??* *~ *# RCS CVS > *,v *,t > > > Would checking only in DirectoryIndex for a local-url starting by # make > sense? > Should that bug be tagged wontfix? Or retitled as suggested? > The original request doesn't make much sense, as it would always generate > false > positives. (Wow, I hadn't thought about this bug in... about eight years.) It would seem that Apache is treating the #index.php as a partial URL, that is a bare page fragment, and thus re-expanding the URL internally to itself... and thus hitting the redirect limit. Does a bare fragment ever make sense as a DirectoryIndex target? If not, then mod_dir should be squawking about this at the start, and 'apache2ctl -t' should warn about it (just in DirectoryIndex directives). I haven't checked to see if the bug is still present in the 2.4 series. pacem in terris / мир / शान्ति / سَلاَم / 平和 Kevin R. Bullock -- 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/129dea20-66c3-4c17-83b3-79985dfea...@umn.edu
Bug#296493: apache2ctl -t should warn about non-initial #
Kevin Bullock wrote: > (...) I therefore > suggest that 'apache2ctl -t' warn the user about the mid-line comment which > could be an error. (...) Stefan Fritsch wrote: > The documentation states: "Comments may not be included on a line > after a configuration directive. " > > '#' signs are considered normal characters inside a directive, so a > warning would not be appropriate either. But I agree that > DirectoryIndex is not behaving correctly here. It's actually used in default configuration: $ grep -e '^[[:space:]]*[^#[:space:]].*#' /etc/apache2/*/* /etc/apache2/mods-available/autoindex.conf: IndexIgnore .??* *~ *# RCS CVS *,v *,t /etc/apache2/mods-enabled/autoindex.conf: IndexIgnore .??* *~ *# RCS CVS *,v *,t Would checking only in DirectoryIndex for a local-url starting by # make sense? Should that bug be tagged wontfix? Or retitled as suggested? The original request doesn't make much sense, as it would always generate false positives. -- 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/201308041150.39391.jmv_...@nirgal.com
Re: mpm-itk as separate package
On Sunday 04 August 2013 10:07:35 Steinar H. Gunderson wrote: > How are > upgrades from 2.2.x handled -- do they automatically load prefork in addition > to the mpm_itk module? Will a separate package need to duplicate this > logic? Arno will make the full answer I guess. Just an appetizer: Right now, apache2.preinst check for an installed apache2-mpm-* package and creates a /etc/apache2/.apache2_mpm_selected temporary file with the information. apache2.postinst reads that file in enable_default_mpm() and enable the correct mpm. The temp file is then deleted. -- 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/201308041022.32525.jmv_...@nirgal.com
Re: mpm-itk as separate package
On Sun, Aug 04, 2013 at 10:51:42AM +0200, Stefan Fritsch wrote: > I intend to include the open_htaccess hook in the next upload. When > you want to move mpm-itk back into a separate source package, just say > say so and we will remove it from apache2. This sounds good. I don't have the time to do it right now, but in the coming weeks and months, I'll hopefully get to this point. :-) It would be great if I could get some help working out the details of migration, though. How are upgrades from 2.2.x handled -- do they automatically load prefork in addition to the mpm_itk module? Will a separate package need to duplicate this logic? /* Steinar */ -- Homepage: http://www.sesse.net/ -- 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/20130804100731.gb5...@uio.no
mpm-itk as separate package
Hi Steinar, I intend to include the open_htaccess hook in the next upload. When you want to move mpm-itk back into a separate source package, just say say so and we will remove it from apache2. Cheers, Stefan -- Weitergeleitete Nachricht -- Betreff: [apache2] branch master updated (466d636 -> a49d341) Datum: Sonntag, 4. August 2013, 08:39:20 Von: Stefan Fritsch An: pkg-apache-comm...@lists.alioth.debian.org This is an automated email from the git hooks/post-receive script. sf pushed a change to branch master in repository apache2. from 466d636 Mark apache2-data as Multi-Arch: foreign new a49d341 Backport open_htaccess hook The 1 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference. -- 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/2666239.lVqgcdxgVD@k
Processed: tagging 718677, tagging 718650
Processing commands for cont...@bugs.debian.org: > tags 718677 + pending Bug #718677 [apache2] apache2.conf comment: Isn't LogLevel better explained as severity then number of messages? Added tag(s) pending. > tags 718650 + pending Bug #718650 [apache2] [apache2] Shipped ports.conf refers to old path for 000-default configuration Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 718650: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=718650 718677: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=718677 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- 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/handler.s.c.137560646419530.transcr...@bugs.debian.org
Bug#718677: apache2.conf comment: Isn't LogLevel better explained as severity then number of messages?
Package: apache2
Version: 2.4.6-2
Severity: minor
Tags: patch
File: /etc/apache2/apache2.conf
--- /etc/apache2/apache2.conf 2013-07-21 19:47:15.0 +0300
+++ apache2.conf2013-08-04 04:09:18.0 +0300
@@ -128,7 +128,7 @@ HostnameLookups Off
ErrorLog ${APACHE_LOG_DIR}/error.log
#
-# LogLevel: Control the number of messages logged to the error_log.
+# LogLevel: Control the severity of events logged to the error_log.
# Available values: trace8, ..., trace1, debug, info, notice, warn,
# error, crit, alert, emerg.
# It is also possible to configure the log level for particular modules, e.g.
--
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/20130804081118.gc5...@nt1.in
