Bug 10202 - Skype 4.2 update
Summary: Skype 4.2 update
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Sander Lepik
QA Contact:
URL: http://blogs.skype.com/2013/05/20/sky...
Whiteboard:
Keywords: Triaged
: 10562 (view as bug list)
Depends on:
Blocks:
 
Reported: 2013-05-21 21:31 CEST by Alejandro Cobo
Modified: 2013-06-18 23:57 CEST (History)
1 user (show)

See Also:
Source RPM: get-skype-4.1.0.20-2.mga3.nonfree.noarch.rpm
CVE:
Status comment:


Attachments

Description Alejandro Cobo 2013-05-21 21:31:29 CEST
Microsoft has released Skype for Linux 4.2 update, which rolls in a bunch of bug-fixes.


Reproducible: 

Steps to Reproduce:
Manuel Hiebel 2013-05-21 22:37:30 CEST

Keywords: (none) => Triaged
Assignee: bugsquad => sander.lepik

Comment 1 Sander Lepik 2013-05-21 22:59:06 CEST
You can get it from here for now: https://www.dropbox.com/s/vnby05v0ob2hequ/get-skype-4.2.0.11-1.mga3.noarch.rpm

I'll submit it to cauldron when cauldron opens again. Not going to push it to Mageia 3 yet. No security fixes and it's a major version change. But you can get it from Mageia 4's repos (if it's submitted) as it's just a downloader.

Hardware: i586 => All
Version: 3 => Cauldron

Comment 2 Alejandro Cobo 2013-05-21 23:13:35 CEST
Ok. Thank you very much for the fast rebuild.
Comment 3 Sander Lepik 2013-05-26 10:05:27 CEST
It's now in cauldron. You can get it from here: http://distrib-coffee.ipsl.jussieu.fr/pub/linux/Mageia/distrib/cauldron/i586/media/nonfree/release/get-skype-4.2.0.11-1.mga4.nonfree.noarch.rpm

As it's just a downloader it will work for Mageia 3 too.

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

Comment 4 Alejandro Cobo 2013-05-26 10:15:03 CEST
Perfect. I can confirm it works in Mageia 2 too.
Comment 5 Sander Lepik 2013-06-18 23:57:02 CEST
*** Bug 10562 has been marked as a duplicate of this bug. ***

CC: (none) => ezequiel_partida


Note You need to log in before you can comment on or make changes to this bug.