Bug#228791: apache: modules-config name and/or location too general

severity 228791 wishlist tags 228781 wontfix stop quit Hi Jeroen, On Tue, 20 Jan 2004, Jeroen van Wolffelaar wrote: Since shortishly, apache uses /usr/sbin/modules-config for providing an interface to update the available and loaded modules in apache. First, the name seems a bit general to

Bug#228667: apache: fails to start after fresh install

Hi Russel, please keep the bug in CC. Can you send me your modules.conf? Thanks Fabio On Tue, 20 Jan 2004, Russell Hires wrote: Only apache. How does php4 work w/ apache? Russell -- Our mission: make IPv6 the default IP protocol We are on a mission from God - Elwood Blues

Bug#228840: apache2-prefork-dev has identity crisis

Package: apache2-prefork-dev Version: 2.0.48-4 Severity: normal lucifer:~/build/php4/4.3.5/php-4.3.5RC1/ /usr/bin/apxs2 -q MPM_NAME worker lucifer:~/build/php4/4.3.5/php-4.3.5RC1/ dpkg -S /usr/bin/apxs2 apache2-prefork-dev: /usr/bin/apxs2 'nuff said. This is breaking PHP builds, forcing

Bug#227232: apache: Overwrites own modules.conf on upgrade

On Tue, 20 Jan 2004, Jeroen van Wolffelaar wrote: I'm now going to clean up the mess and restore config from backup, and I will check out the postinst afterwards, if I find more problems, or a patch for this, I will add to this report and/or open another one. No need to. I know where

Processed: tagging the right bug

Processing commands for [EMAIL PROTECTED]: tags 228791 wontfix Bug#228791: apache: modules-config name and/or location too general There were no tags set. Tags added: wontfix tags 228781 - wontfix Bug#228781: unmet dependecies Tags were: wontfix Tags removed: wontfix stop Stopping processing

Re: Processed: tagging the right bug

Ops.. sorry.. thanks for fixing it. Fabio On Wed, 21 Jan 2004, Debian Bug Tracking System wrote: Processing commands for [EMAIL PROTECTED]: tags 228791 wontfix Bug#228791: apache: modules-config name and/or location too general There were no tags set. Tags added: wontfix tags 228781

Bug#228667: apache: fails to start after fresh install

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 # Autogenerated file - do not edit! # This file is maintained by the apache package. # To update it, run the command: #/usr/sbin/modules-config apache ClearModuleList AddModule mod_so.c AddModule mod_macro.c LoadModule config_log_module

Processed: your mail

Processing commands for [EMAIL PROTECTED]: severity 228033 normal Bug#228033: apache does not start Severity set to `normal'. severity 228667 normal Bug#228667: apache: fails to start after fresh install Severity set to `normal'. merge 228033 228667 Bug#228033: apache does not start

Re: Perfect webdesign

Hello: We are proud to offer you high quality custom web design, logo and stationery design, e-commerce and custom programming. Please, check our portfolio at http://www.luxwebdev.com/portfolioweb.html What can we do for your business? - Unique custom high quality design - Unique logo design

Bug#227357: /usr/lib/apache/1.3/mod_log_config.so undefined symbol: ap_popenf_ex (from log rotate?); but it obviously can...

tags 227357 pending stop quit Ok found the problem and fixed for the next upload. You should never seen this message again (also from now). According to my tests it happens only when upgrading from woody (1.3.26) and testing (1.3.27) where one of the mantainer scripts was broken. The problem is

Processed: Re: Bug#227357: /usr/lib/apache/1.3/mod_log_config.so undefined symbol: ap_popenf_ex (from log rotate?); but it obviously can...

Processing commands for [EMAIL PROTECTED]: tags 227357 pending Bug#227357: /usr/lib/apache/1.3/mod_log_config.so undefined symbol: ap_popenf_ex (from log rotate?); but it obviously can... There were no tags set. Tags added: pending stop Stopping processing here. Please contact me if you need

Bug#228946: apache: apache 1.3.29.0.1-3 conflicts with libapache-mod-perl 1.27, causing coredumps

Package: apache Version: 1.3.29.0.1-3 Severity: normal I upgraded apache to 1.3.29.0.1-3 yesterday; no conflict was noted with the given version of libapache-mod-perl. After upgrading apache, however, it (and apache-ssl) both coredumped when run; backtrace below: #0 0x403f0fe2 in

Bug#228946: apache: apache 1.3.29.0.1-3 conflicts with libapache-mod-perl 1.27, causing coredumps

tags 228946 + pending stop quit Hi, for some reason this bit was lost around apache 1.3.27. the fix is ready to be uploaded. Thanks Fabio On Wed, 21 Jan 2004 [EMAIL PROTECTED] wrote: Package: apache Version: 1.3.29.0.1-3 Severity: normal I upgraded apache to 1.3.29.0.1-3

Processed: submitter

Processing commands for [EMAIL PROTECTED]: submitter 228946 ! Bug#228946: apache: apache 1.3.29.0.1-3 conflicts with libapache-mod-perl 1.27, causing coredumps Changed Bug submitter from [EMAIL PROTECTED] to Paul Walker [EMAIL PROTECTED]. -- Stopping processing here. Please contact me if

Processed: Re: Bug#228946: apache: apache 1.3.29.0.1-3 conflicts with libapache-mod-perl 1.27, causing coredumps

Processing commands for [EMAIL PROTECTED]: tags 228946 + pending Bug#228946: apache: apache 1.3.29.0.1-3 conflicts with libapache-mod-perl 1.27, causing coredumps There were no tags set. Tags added: pending stop Stopping processing here. Please contact me if you need assistance. Debian bug

Re: Re: conf.d usage

Michael Loftis wrote: Putting a file in a conf.d is equivalent to writing those directives in the httpd.conf file. There are no restrictions. A follow-up question, as a package maintainer: if my package wants to install a snippet of config (or a symlink) into conf.d and the file already exists

Re: Re: conf.d usage

Hi Frederic, On Thu, 22 Jan 2004, Frederic Schutz wrote: Michael Loftis wrote: Putting a file in a conf.d is equivalent to writing those directives in the httpd.conf file. There are no restrictions. A follow-up question, as a package maintainer: if my package wants to install a