[Frank Küster]
> Any news on this? A patch maybe or a tip how you intend to solve it,
> so that someone else can start testing, and NMU in case you won't
> find time?
My work in progress can be seen at:
svn diff -c303 svn://svn.debian.org/pkg-apache/branches/etch-apache2
I still have to do s
Peter Samuelson <[EMAIL PROTECTED]> wrote:
> I think I've fixed this for the next upload (to be done in the next day
> or two - I'm away from home but I'll still try), and I consider it a
> release-critical upgrade issue, so I hope the release managers will
> allow it into etch.
Any news on this?
# this is a sarge upgrade issue that I think should be RC
severity 407171 serious
thanks
[Per Olofsson]
> I upgraded from sarge and Apache's proxy stopped working. The reason
> was that mod_proxy_http wasn't loaded, but this was in no way obvious
> since that module was not required in sarge.
We
Package: apache2
Version: 2.2.3-3.2
Severity: important
Hi,
I upgraded from sarge and Apache's proxy stopped working. The reason
was that mod_proxy_http wasn't loaded, but this was in no way obvious
since that module was not required in sarge.
I think this should at least be noted in NEWS.Debian
4 matches
Mail list logo
