Bug 15782

Summary: get-skype failed during upgrade from mga4 to mga5 rc
Product: Mageia Reporter: Chris Denice <eatdirt>
Component: RPM PackagesAssignee: Sander Lepik <mageia>
Status: RESOLVED WORKSFORME QA Contact:
Severity: normal    
Priority: Normal CC: mageia
Version: Cauldron   
Target Milestone: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: MGA5TOO
Source RPM: get-skype-4.3.0.37-5.mga5.nonfree.src.rpm CVE:
Status comment:

Description Chris Denice 2015-04-27 18:38:15 CEST
During the upgrade from mga4 to mga5, get-skype package failed with some script errors:


--2015-04-27 17:16:04--  http://download.skype.com/linux/skype-4.3.0.37.tar.bz2
Resolving download.skype.com (download.skype.com)... failed: Name or service not known.
wget: unable to resolve host address 'download.skype.com'
%prein(get-skype-4.3.0.37-5.mga5.nonfree.noarch) scriptlet failed, exit status 1
get-skype-4.3.0.37-5.mga5.nonfree.noarch
get-skype-4.3.0.37-5.mga5.nonfree.noarch: install failed

The complete report is available there:
https://bugs.mageia.org/show_bug.cgi?id=15781

It is not clear to me what really happens, maybe a transient failure of the download.skype.com domain?

cheers,
chris.

Reproducible: 

Steps to Reproduce:
Comment 1 Sander Lepik 2015-04-28 19:47:24 CEST
Your network connection was probably down at that time. And this is something we can't avoid during upgrade.

CC: (none) => mageia

Comment 2 Chris Denice 2015-04-28 20:49:41 CEST
Since I was upgrading with a network install, I am pretty sure that my connection was up.

The pb may have been that the skype website was down. I think we should have a safety mechanism for this because we also do the same get-* with flash such that the reliability of the upgrade does no longer depend only on the availability of our servers but also to those third parties. Namely, upgrade will work only if downloader && mageia server && skype && flash are fine.

If we go like this, it is going to be a constant failure at some point :) That's why I was thinking the get-* could be moved to updates; then the system upgrade will no longer depends on them?
Comment 3 Sander Lepik 2015-04-30 18:58:17 CEST
Network install can break connection anyway, more often when you are using wifi. And the error says "unable to resolve host address" - this means that DNS was unavailable.
Samuel Verschelde 2015-06-06 17:11:33 CEST

Whiteboard: (none) => MGA5TOO

Samuel Verschelde 2015-06-06 17:11:50 CEST

Assignee: bugsquad => mageia

Comment 4 Sander Lepik 2015-06-06 18:40:12 CEST
AFAIK system upgrade also uses updates medias so it wouldn't help. And this problem is clearly about local connection issues.

I don't see that anything can be done here.

Status: NEW => RESOLVED
Resolution: (none) => WORKSFORME