severity 298052 normal thanks On Sun, Mar 06, 2005 at 03:33:36PM +0100, [EMAIL PROTECTED] wrote: > Quoting Steve Langasek <[EMAIL PROTECTED]>:
> > On Fri, Mar 04, 2005 at 11:52:36AM +0100, Nicolas Champenois wrote: > > > Package: libapache2-mod-php4 > > > Version: 4:4.3.10-8 > > > Severity: grave > > > Justification: renders package unusable > > > After a dist-upgrade today a few functions of php didn't work anymore. I > > > found the following entry for memory_limit in apache2/php.ini : > > > memory_limit = 242424242424242424242424242424242424242424242424 of > > > memory a script may consume (8MB) > > > It works after commenting out this line > > > Of course, this line causes a parse error when starting apache. > > Are you suggesting that the line causing this parse error was somehow the > > fault of the libapache2-mod-php4 package? > I don't know if this is really the fault of this package or else, all I know > is > that right after a dist-upgrade the memory limit line has been modified to > this > incorrect value... > How do you think this can happen ? I have no idea, but I don't see anything at all in the code from the packages in question that would have caused your php.ini to be munged in this way. This strange line must have come from somewhere else. Causing apache2 to fail to start due to a config file parsing error is a bug, but not a grave one. -- Steve Langasek postmodern programmer
signature.asc
Description: Digital signature
