severity 270459 minor
tag 270459 woody
stop
On Tue, 7 Sep 2004, LANTek wrote:
But if ServerType standalone it's all right
how to launch apache-ssl from inetd?
apache and inetd are usually a very very bad combination. It is highly
unsuggested. Also there are much more recent versions of
On Tue, 7 Sep 2004, Ian Eure wrote:
Is there some definitive resource which documents these effects? I'd like to
know what I run the risk of breaking by forcing Apache to use my locale.
Check the BTS for archived apache bugs. some of them were reporting
problems when LANG != C. I am not sure
On Wed, 8 Sep 2004, Gabor FUNK wrote:
Current testing, upg. to apache 1.3.31-5 rendered php4
not working by installing a clear modules.conf over the
one which contained a modules.conf with a line:
loadmodule php4_module ...
Happened on two systems.
G.
php4 has been broken for a few days.
On Sat, 4 Sep 2004, Jonathan Ah Kit wrote:
Fabio Massimo Di Nitto wrote:
Setting up libapache-mod-php4 (4.3.8-9) ...
Error: mod_macro.so does not have a corresponding .info file.
apache-common does not ship mod_macro.so or the info file. mod_macro is
compiled in.
Please check /usr/lib
On Sun, 12 Sep 2004, Jeroen van Wolffelaar wrote:
Package: apache
Version: 1.3.31-6
While upgrading apache in a chroot, I noticed that:
(a) there are two lines trying to stop apache, and not one:
Preparing to replace apache 1.3.31-3 (using .../apache_1.3.31-6_i386.deb) ...
Stopping web
On Tue, 14 Sep 2004, Mike McKay wrote:
Hi, I am getting the following error whenever I try and do pretty much
anything (installing Squirrelmail) via apt now:
Error: libmod_mono.so does not have a corresponding .info file.
The above errors might cause apache to not work properly or start
On Wed, 15 Sep 2004, cwinl-debian-apache wrote:
hi,all:
I put some DVD image files(each more than 4GB) into an apache's directory.
but i found that file size is xxxMB when i open that dir in IE browser .
why?
is it apache's bug?
No it's a limitation. You need apache2 for LFS.
Fabio
--
tag 272069 wontfix
severity 272069 wishlist
stop
On Fri, 17 Sep 2004, Gerfried Fuchs wrote:
Package: apache
Version: 1.3.31-6
Severity: important
#269009's usage of www-browser instead of lynx raised a new problem: Not
all www-browser alternatives do support -dump.
This is a browser
On Thu, 16 Sep 2004, Matt Zimmerman wrote:
Maintainers, please raise the severity of this bug and contact the security
team if this is an urgent issue.
Please can we have at least the CAN number and reference? Joey has been
keeping track of this iirc.
Fabio
--
user fajita: step one
fajita
reassign 272463 libapache-mod-php4
stop
--
user fajita: step one
fajita Whatever the problem, step one is always to look in the error log.
user fajita: step two
fajita When in danger or in doubt, step two is to scream and shout.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Adam Morley wrote:
| Hi,
|
| I sent this to debian-user, but haven't heard anything. I didn't know
if I should submit it as a bug, or send it here first --- sorry if I'm
doing it the wrong way. Please point me to the right place otherwise.
|
|
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hideki Yamane wrote:
| Hi,
|
|
| Yes, stability is most important thing in stable release.
|
| I would ask you that it needs to be built on all woody arch means
| it needs more time to be checked because changed source should be
| able to be built
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
This is offtopic for the bug.
Hideki Yamane wrote:
| Hi,
|
| Fri, 05 Nov 2004 09:32:59 +0100, Fabio Massimo Di Nitto
| Re: Bug#279753: apache: execute arbitrary code via SSI issue
(CAN-2004-0940)
|
| Is that review process on public or closed
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Helge Kreutzmann wrote:
| Hello,
| On Fri, Nov 05, 2004 at 06:18:12AM -0800, Debian Bug Tracking System wrote:
|
|Thanks for reporting this twice already. Please before filing bugs you are
welcome to check both
|debian-apache mailing lists and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
tag 280206 moreinfo
thanks
Peter Bredlöv wrote:
| Package: apache
| Version: 1.3.31-7
| Severity: important
|
| I recently upgraded from 1.3.31-6 to 1.3.31-7. After this, apache wont start
| any more unless I disable the log files I have for my around
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Giacomo A. Catenazzi wrote:
| Fabio Massimo Di Nitto wrote:
|
|
| Can you please attach the configuration files? What modules are you
| using?
|
| Fabio
|
|
| SSLNoV2
|
Can you please try to comment this out?
Thanks
Fabio
- --
Self-Service law
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Peter Bredlöv wrote:
| I installed apache, apache-common and apache-utils, but the same error comes
up;
|
| [Wed Nov 10 01:55:34 2004] [warn] make_sock: problem listening on port 443,
filedescriptor (1128)
larger than FD_SETSIZE (1024) found, you
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jakob Goldbach wrote:
| Package: apache
| Version: 1.3.31-7
|
| configure fails for apache when you have to many Include files.
|
| I have a config file for each virtual host - and include them with
| Include /etc/apache/vhosts/*.conf
|
|
|
Perhaps you
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
reassign 280871 libmm11
reassign 280233 libmm11
merge 280871 280233
severity 280871 grave
severity 280233 grave
tag 280233 woody
tag 280871 woody
stop
Hi Mark,
the last libmm11 stable update breaks apache badly.
I received already other reports
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Peter Bredlöv wrote:
| Ok, I understand.
|
| A little googling shows that many people have tried adding CFLAGS, but in
lots of cases they
werent being used. I guess they didn't add them in the right spot, or something
else over-wrote the
change.
|
|
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Alexis Sukrieh wrote:
| Hello there.
|
| I'm maintaining an unofficial package, apache-lingerd [1].
| It's a new flavour of the official Debian apache source tree.
|
| As it won't be included in Debian, and as some users requested me
| to maintain the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
severity 286604 important
reassign 286604 php4
thanks
PaulWB wrote:
|
|
| package: apache
| version: 1.3.33-2
| severity: critical
|
|
| A module or package has been upgraded recently and is creating large
| problems for apache
if a module has been
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jan Minar wrote:
| On Wed, Dec 22, 2004 at 09:57:13AM +0100, Fabio Massimo Di Nitto wrote:
|
|tag 286740 - security
|thanks
|
|Jan Minar wrote:
|| Package: apache
|| Version: 1.3.33-2
|| Severity: minor
|| Tags: security
||
|| Hi.
||
|| /var/log/apache
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[EMAIL PROTECTED] wrote:
| On Wed, Dec 22, 2004 at 11:44:54AM +0100, Fabio Massimo Di Nitto wrote:
|
| |There is no point in such operation. If a user have a local account
| |it also has at least a few other thousands options to make a DoS on
| apache
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[EMAIL PROTECTED] wrote:
| Ce jour Wed, 22 Dec 2004, Fabio Massimo Di Nitto a dit:
|
|
|-BEGIN PGP SIGNED MESSAGE-
|Hash: SHA1
|
|[EMAIL PROTECTED] wrote:
|| On Wed, Dec 22, 2004 at 11:44:54AM +0100, Fabio Massimo Di Nitto wrote:
||
|
|
| it's
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Jon,
Jon Dowland wrote:
| Package: apache
| Version: 1.3.33-2
| Severity: serious
| Justification: no longer builds from source
|
| Hi, I'm sorry to be filing this as I'm finding it hard to believe that
| this could be a problem for anyone but me.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jon Dowland wrote:
|This is my best guess atm.. otherwise would it be possible for you to test
|the same
|in a fresh sarge/sid chroot? that would really help to isolate the problem
|between your installed system and my build-test env.
|
|
| I'd be
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mathieu Jondet wrote:
| Hi,
| i've just run a apt-get dist-upgrade on my machine on debian/testing,
| everything went well except for the mod_perl upgrade, here are the
| information:
|
| mathieu:/home/mathieu# apt-get dist-upgrade
| Reading Package
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jon Dowland wrote:
| On Thu, Dec 23, 2004 at 01:18:06PM +0100, Fabio Massimo Di Nitto wrote:
|
|
|I know for sure that configure explicitly requires bash, did you replace
|/bin/bash with another
|shell? Can you verify the bash md5sum?
|
|
| ~$ md5sum
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
tag 288627 woody
severity 288627 minor
tag 288625 woody
severity 288625 minor
stop
George Georgalis wrote:
| Package: apache-ssl
| Version: 1.3.26.1+1.48-0woody3
|
| see: 288625
| http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=+288625
|
| This will
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ben Low wrote:
| Package: apache-common
| Version: 1.3.33-2
| Severity: normal
|
|
| It seems that mod_proxy is not (no longer) provided?
|
dpkg -c /mirrors/debian.org/pool/main/a/apache/apache-common_1.3.33-2_i386.deb
|grep proxy
- -rw-r--r--
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bjørn Mork wrote:
| Package: apache-ssl
| Version: 1.3.33-3
| Severity: important
|
| When I just upgraded apache-ssl, the postinst script did these modifications
| without asking me:
This is sounds quite impossible because apache uses debconf via ucf
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bjørn Mork wrote:
| Fabio Massimo Di Nitto [EMAIL PROTECTED] writes:
|
|
|Bjørn Mork wrote:
|| Package: apache-ssl
|| Version: 1.3.33-3
|| Severity: important
||
|| When I just upgraded apache-ssl, the postinst script did these modifications
|| without
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bjørn Mork wrote:
| Fabio Massimo Di Nitto [EMAIL PROTECTED] writes:
|
|Bjørn Mork wrote:
|
|| Anything else I should check?
|
|If you can efford to do a test break it would be great if you can rever the
changes
|to the old config and do:
|
|dpkg
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bjørn Mork wrote:
| Fabio Massimo Di Nitto [EMAIL PROTECTED] writes:
|
|
|Ah hold on.. one more test please.. i forgot about the md5sum check.
|
|Put the old config in place and edit (very carefully!) /var/lib/ucf/hashfile
|with the proper md5sum
Hi Simon,
clearly you did not read entirely the error message in the first
place since for that error you are not supposed to open bugs against
apache. info files as shipped by the mentioned modules, in this case
mod_tsunami, mod_accouting and mod_dynvhost. Please file bugs against
them.
Hi Marc,
On Thu, 18 Dec 2003, [utf-8] Marc Dequènes wrote:
can you send me your config files please?? I have been trying to
reproduce this problem with no success.
Sorry for the lag.
Attached is my httpd.conf with the problem.
Look at line 204-205, the include for modules was
Hi Holger,
please next time check the BTS. This bug has been fixed already in
-4 (actually in incoming).
Please check http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=237151 for a
teporary workaround.
Fabio
On Thu, 11 Mar 2004, Holger Müller wrote:
Package: apache-ssl
Version:
On Sat, 3 Apr 2004, Matt Zimmerman wrote:
On Sun, Apr 04, 2004 at 02:02:42AM +0200, Bill Allombert wrote:
Package: apache
Version: 1.3.29.0.2-4
Severity: important
Hello Debian Apache maintainers,
During the latest woody to sid upgrade test I performed (under
user-mode-linux,
On Tue, 6 Apr 2004, Kai Hendry wrote:
Package: apache
Version: 1.3.29.0.2-4
Severity: normal
I am trying to set apache to have liberal umask setting, to ensure www-data
user does not write something with incorrect permissions.
So I'm putting umask 002 in /etc/init.d/apache, but I see
It is already fixed in incoming.
On Mon, 3 May 2004, Fionn Behrens wrote:
Package: apache
Version: 1.3.29.0.1-5
Followup-For: Bug #247140
I basically ran into the same problem: trying to install the latest apache, my
perl appeared to be too old but installing a new one would mean its too
Hi Philipp,
On Sat, 31 Jul 2004, Philipp Bliedung wrote:
Package: apache-common
Version: 1.3.31-2
Severity: serious
Justification: apache-modconf doesn't accept correct syntax
*** Please type your report below this line ***
apache-common: apache-modconf doesn't accept correct syntax.
On Mon, 6 Sep 2004, Marc Haber wrote:
Package: apache
Version: 1.3.29.0.2-5
Severity: minor
httpd.conf says:
# Please keep this LoadModule: line here, it is needed for installation.
Include /etc/apache/modules.conf
Shouldn't it say Please keep this Include line here?
No. This is correct
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
severity 304785 wishlist
stop
Piotr Roszatycki wrote:
Package: apache
Version: 1.3.33-4
Severity: important
Please convert
Include /etc/apache/conf.d
to the:
Include /etc/apache/conf.d/*.conf
The files in this directory are handled
David N. Welton wrote:
Olaf van der Spek wrote:
Hi,
Do you mind if a NMU is done to fix this issue?
No, go ahead - thanks!
Perhaps waiting an answer from the maintainer would be better.
As Adam already said it is in his tree/queue for the next upload.
Thanks
Fabio
--
To UNSUBSCRIBE,
Olaf van der Spek wrote:
Fabio Massimo Di Nitto wrote:
David N. Welton wrote:
Olaf van der Spek wrote:
Hi,
Do you mind if a NMU is done to fix this issue?
No, go ahead - thanks!
Perhaps waiting an answer from the maintainer would be better.
Aren't you one of the maintainers?
Yes
David N. Welton wrote:
Fabio Massimo Di Nitto wrote:
David N. Welton wrote:
Olaf van der Spek wrote:
Hi,
Do you mind if a NMU is done to fix this issue?
No, go ahead - thanks!
Perhaps waiting an answer from the maintainer would be better.
As Adam already said it is in his tree/queue
Olaf van der Spek wrote:
There are five maintainers listed in the maintainers field. Are you
saying that none of them had time to post a reply that none of them have
time to work on most of the bugs for the past/next year?
Since i don't dig into the other 4 maintainer private lifes and I can
Olaf van der Spek wrote:
Fabio Massimo Di Nitto wrote:
Olaf van der Spek wrote:
There are five maintainers listed in the maintainers field. Are you
saying that none of them had time to post a reply that none of them
have time to work on most of the bugs for the past/next year?
Since i
Roberto Pariset wrote:
Package: apr-util
Version: 1.2.2-3
Severity: important
Justification: fails to build from source
Hi,
apr-util seems to FTBFS on everything but i386 because dependencies
cannot be satisfied: E: Couldn't find package libapr1-dev.
Maybe you should replace libapr1-dev with
Toni Mueller wrote:
Hello,
I'd say that making a LAMP package that includes a lot of PHP stuff
and not much else is sort of hijacking a good name for a bad purpose.
If anything, packages like
lamp-python (best language)
lamp-perl (original definition of LAMP)
lamp-php
(in
Thom May wrote:
I don't see there's any benefit in doing this _at all_, to be honest. It'll
just turn into a whine fest when people don't get exactly what they want
installed, and it then just becomes an unmaintainable mess.
-Thom
That's exactly why i don't want it in apache, and somebody can
201 - 252 of 252 matches
Mail list logo
