I updated to the proposed version then applied the 2nd patch and it hasn't worked for me.
With the non patched version in my /var/squid/log/access.log the first entry after hitting the check button is:
1257825448.330 1 192.168.5.91 TCP_DENIED/407 1771 GET http://changelogs.ubuntu.com/meta-release - NONE/- text/html
no credentials passed to the proxy - as we would expect given explanations in this conversation.
However with the patch applied, it seems that there is no attempt made to download changelogs.ubuntu.com/meta-release, the first line in the access.log is:
1257825577.334 669 192.168.5.91 TCP_REFRESH_HIT/304 194 GET http://archive.ubuntu.com/ubuntu/dists/jaunty/Release.gpg kgnews DIRECT/91.189.88.134 -
My user is kgnews and so credentials are passed to the proxy. However there is no call made to changelogs.ubuntu.com and I am not presented with the button to "Upgrade", but am simply told my system is up to date.
I updated to the proposed version then applied the 2nd patch and it hasn't worked for me. log/access. log the first entry after hitting the check button is: changelogs. ubuntu. com/meta- release - NONE/- text/html
With the non patched version in my /var/squid/
1257825448.330 1 192.168.5.91 TCP_DENIED/407 1771 GET http://
no credentials passed to the proxy - as we would expect given explanations in this conversation.
However with the patch applied, it seems that there is no attempt made to download changelogs. ubuntu. com/meta- release, the first line in the access.log is: archive. ubuntu. com/ubuntu/ dists/jaunty/ Release. gpg kgnews DIRECT/ 91.189. 88.134 -
1257825577.334 669 192.168.5.91 TCP_REFRESH_HIT/304 194 GET http://
My user is kgnews and so credentials are passed to the proxy. However there is no call made to changelogs. ubuntu. com and I am not presented with the button to "Upgrade", but am simply told my system is up to date.