Bug#175351: apache2-common: The problem persists with 2.0.52-1
Thijs Kinkhorst wrote: The problem persists with 2.0.52-1. The URIs mentioned above are still current. Thank you for your help in testing this problem. I'm working through the (rather long) list of Apache2 bugs. Could you try it again one more time with current Apache 2.2.3 ? That would really help. Sorry for the very long delay in my replying. I managed to upgrade my Apache to 2.2 only yesterday. Yes, the bug seems to still exist, which is consistent with the bug still being considered open by upstream. Julian. signature.asc Description: This is a digitally signed message part.
Processed: [bts-link] source package apache2
Processing commands for [EMAIL PROTECTED]: # # bts-link upstream status pull for source package apache2 # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user [EMAIL PROTECTED] Setting user to [EMAIL PROTECTED] (was [EMAIL PROTECTED]). # remote status report for #453630 # * http://issues.apache.org/bugzilla/show_bug.cgi?id=40910 # * remote status changed: (?) - RESOLVED # * remote resolution changed: (?) - FIXED # * closed upstream tags 453630 + fixed-upstream Bug#453630: apache2: Major host parsing error in Proxy balancer:/.. section Tags were: etch Tags added: fixed-upstream usertags 453630 + status-RESOLVED resolution-FIXED Bug#453630: apache2: Major host parsing error in Proxy balancer:/.. section There were no usertags set. Usertags are now: status-RESOLVED resolution-FIXED. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
[bts-link] source package apache2
# # bts-link upstream status pull for source package apache2 # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user [EMAIL PROTECTED] # remote status report for #453630 # * http://issues.apache.org/bugzilla/show_bug.cgi?id=40910 # * remote status changed: (?) - RESOLVED # * remote resolution changed: (?) - FIXED # * closed upstream tags 453630 + fixed-upstream usertags 453630 + status-RESOLVED resolution-FIXED thanks
