Description of problem: Note that by downloading the Adobe Flash Player you indicate your acceptance of the EULA, available at http://www.adobe.com/products/eulas/players/flash/ Downloading from http://fpdownload.macromedia.com/get/flashplayer/pdc/11.1.102.55/flash-plugin-11.1.102.55-release.x86_64.rpm: curl: (6) Couldn't resolve host 'fpdownload.macromedia.com' Downloading from http://linuxdownload.adobe.com/linux/x86_64/flash-plugin-11.1.102.55-release.x86_64.rpm: curl: (6) Couldn't resolve host 'linuxdownload.adobe.com' Error: Unable to download Flash Player. This is likely due to this package being too old. Please file a bug report at https://bugs.mageia.org so that the package gets updated. Thank you. In the meantime, you can download Flash Player manually from http://get.adobe.com/flashplayer/ erreur: %pre(flash-player-plugin-11.1.102.55-1.mga2.nonfree.x86_64) scriptlet failed, exit status 1 erreur: install: échec du scriptlet %pre (2), on saute flash-player-plugin-11.1.102.55-1.mga2.nonfree [root@localhost ~]# Version-Release number of selected component (if applicable): flash-player-plugin-11.1.102.55-1.mga2.nonfree.x86_64 How reproducible: each upgrade Steps to Reproduce: 1.urpmi --auto-update 2. 3.
Was the network connection available ? Or do you use a proxy or something like that ? As you can see flash-player-plugin download the rpm from the adobe website, and if you have exotic network sometime it don't work see bug 3044
Keywords: (none) => NEEDINFOSource RPM: flash-plugin-11.1.102.55-release.x86_64.rpm => flash-player-plugin
Thanks for the reply. The network was avalaible: it is during update and there is no problem with other rpm. No proxy, ADSL box connected with ethernet. Every time, I update there is the same problem. If I use MCC, the update fails silently. If I try to open the link from Konsole (by right click, open the link), the result is : Not Found The requested URL /linux/x86_64/flash-plugin-11.1.102.55-release.x86_64.rpm: was not found on this server. Content of the Firefox address bar: http://linuxdownload.adobe.com/linux/x86_64/flash-plugin-11.1.102.55-release.x86_64.rpm: If I suppress the ":" from the address bar, the download can be done. When I try from Konsole, it seems that the ":" are included in the hyperlink (underlined). Downloading from http://fpdownload.macromedia.com/get/flashplayer/pdc/11.1.102.55/flash-plugin-11.1.102.55-release.x86_64.rpm:
it should work http://svnweb.mageia.org/packages/cauldron/flash-player-plugin/current/SPECS/flash-player-plugin.spec?view=markup 257 echo "Downloading from $URL:" 258 curl --connect-timeout 20 -m 10800 -L "$URL" > "%file"
Assignee: bugsquad => anssi.hannula
What happens when you run: curl --connect-timeout 20 -m 10800 -L "http://fpdownload.macromedia.com/get/flashplayer/pdc/11.1.102.55/flash-plugin-11.1.102.55-release.x86_64.rpm" > /dev/null as root user in a terminal?
Status: NEW => ASSIGNED
Here is the result: [root@localhost ~]# curl --connect-timeout 20 -m 10800 -L "http://fpdownload.macromedia.com/get/flashplayer/pdc/11.1.102.55/flash-plugin-11.1.102.55-release.x86_64.rpm" > /dev/null curl: (6) Couldn't resolve host 'fpdownload.macromedia.com' [root@localhost ~]# Nota: I have often to try twice in Firefox to launch Google because the first time, Firefox can't find the serveur at the address "www.google.fr". Philippe
That's clearly due to a DNS error of some sort, likely a transient one if it works fine the second time. It's probably not a bad idea to add a "--retry 3" to the curl command-line to let it try a few times to download the file before giving up.
CC: (none) => dan
Philippe, what happens when you run that command in command line multiple times?
If I try multiple times, it's OK the second time. [philippe@localhost ~]$ su - Mot de passe : [root@localhost ~]# curl --connect-timeout 20 -m 10800 -L "http://fpdownload.macromedia.com/get/flashplayer/pdc/11.1.102.55/flash-plugin-11.1.102.55-release.x86_64.rpm" > /dev/null curl: (6) Couldn't resolve host 'fpdownload.macromedia.com' [root@localhost ~]# curl --connect-timeout 20 -m 10800 -L "http://fpdownload.macromedia.com/get/flashplayer/pdc/11.1.102.55/flash-plugin-11.1.102.55-release.x86_64.rpm" > /dev/null % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 14 6870k 14 1023k 0 0 1076k 0 0:00:06 --:--:-- 0:00:06 34 6870k 34 2353k 0 0 1219k 0 0:00:05 0:00:01 0:00:04 55 6870k 55 3826k 0 0 1306k 0 0:00:05 0:00:02 0:00:03 75 6870k 75 5211k 0 0 1326k 0 0:00:05 0:00:03 0:00:02 100 6870k 100 6870k 0 0 1401k 0 0:00:04 0:00:04 --:--:-- 1417k [root@localhost ~]# Have you any idea why I have this problem? My network configuration is : -DHCP -DNS given by DHCP server The rest is default configuration. Thanks for your help.
Such a DNS error could be due to having one or more nonfunctional nameservers upstream combined with a local caching nameserver. The local cache requests a DNS lookup but curl aborts before the response finally comes in. By the time it's retried, the response has been received and in the local caching nameserver so it's available immidiately. Does it work successfully if you add "--retry 3" or if you increase the timeout "--connect-timeout 30"?
It doesn't work in any case. [root@localhost ~]# curl --retry 3 --connect-timeout 30 -m 10800 -L "http://fpdownload.macromedia.com/get/flashplayer/pdc/11.1.102.55/flash-plugin-11.1.102.55-release.x86_64.rpm" > /dev/null curl: (6) Couldn't resolve host 'fpdownload.macromedia.com' [root@localhost ~]# The mageia1 installed on this desktop has no problem.
curl has a bug that prevented it from retrying in the case of DNS problems. That bug has been fixed upstream and will be in the next curl release. That command you used in #c10 should work using the next release of curl (7.24.0). But, you should really fix your DNS so this workaround isn't necessary :-)
I have fixed the DNS to the value given by ISP website and it's OK. The question is why, with the DNS given by the ADSL box, it's OK for Mageia1 and not for cauldron. Thanks for the help.
The problem was due to DNS not to the package.
Status: ASSIGNED => RESOLVEDResolution: (none) => FIXED
I still think it would be wise to add --retry 3 to work around this kind of problem, and other temporary network problems, in the future.