Processing commands for [EMAIL PROTECTED]:
> # sarge upgrade issue, I think it is RC
> severity 396782 serious
Bug#396782: apache2.2-common: Upgrade adds "default" virtual host; breaks
existing config
Severity set to `serious' from `important'
> thanks
Stopping processing here.
Please contact m
# sarge upgrade issue, I think it is RC
severity 396782 serious
thanks
I hope I've fixed this for the next upload, targetted for etch, as I
believe it should be RC. I'm teaching the apache2.2-common postinst
how to recognise an upgrade from sarge versus a new install. I hope to
have the time an
# 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
Processing commands for [EMAIL PROTECTED]:
> # this is a sarge upgrade issue that I think should be RC
> severity 407171 serious
Bug#407171: proxy stops working after upgrading from sarge
Severity set to `serious' from `important'
> thanks
Stopping processing here.
Please contact me if you need
4 matches
Mail list logo