/usr/lib/update-notifier/package-data-downloader from update-notifier uses python urllib
It seems to be problems when using proxies. In addition, urllib doesn't supports https protocol.
https://docs.python.org/2/library/urllib.html#urllib-restrictions
Using a http proxy, adobe-flashplugin updates will work but not allways:
urllib.urlretrieve("http://archive.canonical.com/pool/partner/a/adobe-flashplugin/adobe-flashplugin_11.2.202.425.orig.tar.gz", "adobe-flashplugin.tar.gz")
Using a https proxy, pepflashpluguin updates will never work:
urllib.urlretrieve("https://dl-ssl.google.com/linux/chrome/deb/pool/main/g/google-chrome-stable/google-chrome-stable_39.0.2171.95-1_i386.deb", "google-chrome.deb")
So, scripts must be something like:
export http_proxy=http://192.168.0.1:3128 export https_proxy=https://192.168.0.1:3128 apt-get install -y flashplugin-installer apt-get install -y pepflashplugin-installer echo "" >> /etc/chromium-browser/default echo ". /usr/lib/pepflashplugin-installer/pepflashplayer.sh" >> /etc/chromium-browser/default echo "" >> /etc/chromium-browser/default unset http_proxy unset https_proxy apt-get --reinstall install -y flashplugin-installer apt-get --reinstall install -y pepflashplugin-installer
Of course, if yo do this, your corporative firewall/proxy must allow direct connections to archive.canonical.com (http) and dl-ssl.google.com (https).
In my opinion, update-notifier (and other applications using urllib) should avoid python urllib
There are many bugs related (in fact, they are duplicated):
https://bugs.launchpad.net/ubuntu/+source/anacron/+bug/1209146 https://bugs.launchpad.net/ubuntu/+source/flashplugin-nonfree/+bug/1098233 https://bugs.launchpad.net/ubuntu/+source/flashplugin-nonfree/+bug/1037662 https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1005837 https://bugs.launchpad.net/zc.buildout/+bug/484735
/usr/lib/ update- notifier/ package- data-downloader from update-notifier uses python urllib
It seems to be problems when using proxies. In addition, urllib doesn't supports https protocol.
https:/ /docs.python. org/2/library/ urllib. html#urllib- restrictions
Using a http proxy, adobe-flashplugin updates will work but not allways:
urllib. urlretrieve( "http:// archive. canonical. com/pool/ partner/ a/adobe- flashplugin/ adobe-flashplug in_11.2. 202.425. orig.tar. gz", "adobe- flashplugin. tar.gz" )
Using a https proxy, pepflashpluguin updates will never work:
urllib. urlretrieve( "https:/ /dl-ssl. google. com/linux/ chrome/ deb/pool/ main/g/ google- chrome- stable/ google- chrome- stable_ 39.0.2171. 95-1_i386. deb", "google- chrome. deb")
So, scripts must be something like:
export http_proxy=http:// 192.168. 0.1:3128 /192.168. 0.1:3128 installer installer browser/ default pepflashplugin- installer/ pepflashplayer. sh" >> /etc/chromium- browser/ default browser/ default installer installer
export https_proxy=https:/
apt-get install -y flashplugin-
apt-get install -y pepflashplugin-
echo "" >> /etc/chromium-
echo ". /usr/lib/
echo "" >> /etc/chromium-
unset http_proxy
unset https_proxy
apt-get --reinstall install -y flashplugin-
apt-get --reinstall install -y pepflashplugin-
Of course, if yo do this, your corporative firewall/proxy must allow direct connections to archive. canonical. com (http) and dl-ssl.google.com (https).
In my opinion, update-notifier (and other applications using urllib) should avoid python urllib
There are many bugs related (in fact, they are duplicated):
https:/ /bugs.launchpad .net/ubuntu/ +source/ anacron/ +bug/1209146 /bugs.launchpad .net/ubuntu/ +source/ flashplugin- nonfree/ +bug/1098233 /bugs.launchpad .net/ubuntu/ +source/ flashplugin- nonfree/ +bug/1037662 /bugs.launchpad .net/ubuntu/ +source/ update- notifier/ +bug/1005837 /bugs.launchpad .net/zc. buildout/ +bug/484735
https:/
https:/
https:/
https:/