Stefan Fritsch wrote:
Version: 2.2.3-4
This bug has been fixed long ago (don't know when exactly, but 2.2.3-4
is definitely fixed)
How about The o+rx on the directory isn't necessary and should thus be
dropped.?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of
Package: apache2
Version: 2.2.3-4
Severity: normal
Hi,
Upstream has released 2.2.4 almost five months ago. Could you package it please?
Olaf
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (500, 'testing'), (1, 'unstable')
Architecture: i386 (i686)
Kernel:
Peter Samuelson wrote:
[Olaf van der Spek]
But where does it check whether the service is supposed to run in the
current runlevel? I didn't see that check in the script itself.
It doesn't. No init script does. That is the job of invoke-rc.d.
invoke-rc.d decides whether to run the script
Peter Samuelson wrote:
[Olaf van der Spek]
invoke-rc.d decides whether to run the script or not, based on the
current runlevel. invoke-rc.d always runs a script for 'reload' or
'force-reload' even if the runlevel doesn't include the service, but
the same is _not_ true for 'start' or 'restart
processing:
apache2-common
E: Sub-process /usr/bin/dpkg returned an error code (1)
[EMAIL PROTECTED]:~#
--
Olaf van der Spek
http://xccu.sf.net/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
* Now talking in #debian-apache
* Topic is ' Welcome to #debian-apache - discussions about the packaging
of 2.x in Debian | For support please visit #apache on Freenode |
apache2.2 hosted on svn.debian.org | APR/APU 1.2.7 uploaded to unstable '
* Set by thom on Fri Jul 21 22:23:03
XTF Hi,
XTF
Thom May wrote:
Please stop abusing the BTS with irrelevancies.
-Thom
Could you start using the BTS with relevancies in return?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Yesterday it happened again: :(
/etc/cron.daily/logrotate:
grep: /etc/apache2/conf.d/[^.#]*: No such file or directory
(98)Address already in use: make_sock: could not bind to address [::]:443
no listening sockets available, shutting down
Unable to open logs
error: error running shared postrotate
Thom May wrote:
* Olaf van der Spek ([EMAIL PROTECTED]) wrote :
What's the name of those packages?
I don't think the bug tracking system is a suitable place to teach you how
to use apt.
You're right.
What about Apache 2.2 itself?
--
Olaf van der Spek
http://xccu.sf.net/
--
To UNSUBSCRIBE
Thom May wrote:
* Olaf van der Spek ([EMAIL PROTECTED]) wrote :
Hi Adam,
We're well aware of this, and are actually planning to have a small
gathering in the new year to polish up the apr1.0/apache2.2 packaging
and get it into the archive.
What's the status of 2.2?
APR/APU 1.2
This morning the server died during a logrotate. I think this is the
same bug.
I think there's a race condition.
/etc/cron.daily/logrotate:
grep: /etc/apache2/conf.d/[^.#]*: No such file or directory
[Sun Feb 26 06:25:48 2006] [warn] module proxy_http_module is already
loaded, skipping
[Sun
Hi Adam,
We're well aware of this, and are actually planning to have a small
gathering in the new year to polish up the apr1.0/apache2.2 packaging
and get it into the archive.
What's the status of 2.2?
--
Olaf van der Spek
http://xccu.sf.net/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED
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?
I've been waiting for 1 year
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 don't dig into the other 4
Fabio Massimo Di Nitto wrote:
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
Fabio Massimo Di Nitto wrote:
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
Adam Conrad wrote:
Olaf van der Spek wrote:
Do you mind if a NMU is done to fix this issue?
Isn't it traditional to submit patches before an NMU? How do you propose
Yes, it is. I was only asking if you'd mind. :)
to fix it? The only real way to fix it is to move the config out
Hi,
Do you mind if a NMU is done to fix this issue?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Hi Debian developers,
Does any of you know about the status of Apache2?
I've send the message below to listed email address and I've asked at
IRC but I haven't received any response.
Hi Apache2 maintainers,
I've noticed there are a lot of bugs, see
On 1/21/06, Jeroen Massar [EMAIL PROTECTED] wrote:
Olaf van der Spek wrote:
Hi Debian developers,
Does any of you know about the status of Apache2?
It works flawlessly on several places where I have deployed it.
I've send the message below to listed email address and I've asked
| Why doesn't any one give any update information on this bug ?
Because it hasn't been discussed?
Why has it not been discussed?
| I even don't know if it's accepted/rejected.
I think it should be rejected, since it's just a way for you to
(mis)configure your server. Don't do that,
On 1/21/06, Jeroen Massar [EMAIL PROTECTED] wrote:
Olaf van der Spek wrote:
On 1/21/06, Jeroen Massar [EMAIL PROTECTED] wrote:
Olaf van der Spek wrote:
[..]
A lot of those bugs are quite old and some appear to be trivial to
fix, but they don't have a single response from you.
Could you
Package: apache2
Version: 2.0.55-3
Severity: wishlist
Hi,
Could you include a default deflate.conf containing the following line:
AddOutputFilterByType DEFLATE text/html text/plain text/xml
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (500,
Hi Apache2 maintainers,
I've noticed there are a lot of bugs, see
http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=apache2
http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=apache2-common
A lot of those bugs are quite old and some appear to be trivial to
fix, but they don't have a single response
Hi,
Any updates?
--
Olaf van der Spek
http://xccu.sf.net/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
On 11/25/05, Adam Conrad [EMAIL PROTECTED] wrote:
Olaf van der Spek wrote:
Hi Apache2 maintainers,
Could you tell me why this bug has not been fixed yet?
It most likely will be in my next upload.
Thanks.
Do you know already how it will be fixed?
Package: apache2
Version: 2.0.54-5
Severity: normal
Hi,
Could you move the /server-info and /server-status configuration to
mods-available?
This would clean up apache2.conf and cause less issues with conf file updates.
Olaf
-- System Information:
Debian Release: testing/unstable
APT prefers
Package: apache2
Version: 2.0.54-4
Severity: normal
Hi,
After I installed this security upgrade, Apache2 couldn't restart anymore.
Setting up libapache2-mod-php4 (4.3.10-16) ...
Forcing reload of web server: Apache2(98)Address already in use: make_sock:
could not bind to address [::]:443
no
Adam Conrad wrote:
Olaf van der Spek wrote:
Package: apache2
Version: 2.0.54-4
Severity: normal
# invoke-rc.d apache2 start
Starting web server: Apache2(98)Address already in use: make_sock: could not
bind to address [::]:443
no listening sockets available, shutting down
Unable to open logs
http://issues.apache.org/bugzilla/show_bug.cgi?id=35310
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Hi everyone,
Just wondering about this bug report:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=267477
It's about the setup of SSL in Apache 2.
Will this be fixed before Sarge or will people have trouble setting up
SSL for the next two years?
--
Olaf van der Spek
http://xccu.sf.net
--
Olaf van der Spek
http://xccu.sf.net/
mkdir --mode=750 --parents /var/log/apache2/ssl apache2-ssl-certificate
a2enmod ssl a2ensite ssl invoke-rc.d apache2 reload
/etc/apache2/sites-available/ssl:
Listen 443
NameVirtualHost *:443
VirtualHost *:443
ServerName localhost
Debian Bug Tracking System wrote:
This is an automatic notification regarding your Bug report
#291856: Duplicate Alias /icons/ /usr/share/apache2/icons/,
which was filed against the apache2 package.
It has been closed by one of the developers, namely
Adam Conrad [EMAIL PROTECTED].
Their
Florian Weimer wrote:
* Olaf van der Spek:
Instead of just an easy way to enable SSL/TLS, I'd like to see it
enabled by default. :)
This would be a questionable change because it unnecessarily exposes
more program code to potential attacks.
That's true, I guess being able to enable
* Olaf van der Spek ([EMAIL PROTECTED]) wrote :
Thom May wrote:
* Olaf van der Spek ([EMAIL PROTECTED]) wrote :
Hi,
Instead of just an easy way to enable SSL/TLS, I'd like to see it
enabled by default. :)
Anyway:
Step 3 and 4 can be replaced by running
/usr/sbin/apache2-ssl-certificate
* Olaf van der Spek ([EMAIL PROTECTED]) wrote :
Generating an ssl cert during install, and setting up apache to use it.
See the many archived bugs from the time.
If we can sensibly use debconf to ask the questions, then i may
reinstate
something like this post sarge.
I'll try.
But would
Thom May wrote:
* Olaf van der Spek ([EMAIL PROTECTED]) wrote :
Hi,
Instead of just an easy way to enable SSL/TLS, I'd like to see it
enabled by default. :)
Anyway:
Step 3 and 4 can be replaced by running /usr/sbin/apache2-ssl-certificate
In step 5 you can use
SSLCertificateFile /etc/apache2/ssl
Hi,
Instead of just an easy way to enable SSL/TLS, I'd like to see it
enabled by default. :)
Anyway:
Step 3 and 4 can be replaced by running /usr/sbin/apache2-ssl-certificate
In step 5 you can use
SSLCertificateFile /etc/apache2/ssl/apache.pem
and SSLCertificateKeyFile isn't needed.
--
Olaf van
Package: apache2-common
Version: 2.0.49-1
The conf file for this server contains the following line:
AddType application/x-tar .tgz
Shouldn't this be application/x-gzip instead?
Because the format of the content is gzip, not tar. Only after ungzip,
it becomes tar.
39 matches
Mail list logo
