Bug 28911 - Unable to install Skype
Summary: Unable to install Skype
Status: RESOLVED INVALID
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 8
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-05-13 07:02 CEST by Jan Pihlgren
Modified: 2021-05-13 12:06 CEST (History)
2 users (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments

Description Jan Pihlgren 2021-05-13 07:02:25 CEST
When Skype deliver it latest version off Skype (skypeforlinux-64.rpm) for installaton by rpm
I get an error that its missing libatomic or libatomic1

I think a solution is that mageia include either of this libs in Mageia repositories or made it possible to instal them manually.

Or that Mageia inclode  Skype as a instalable program.

Steps to Reproduce:
Download Skype for Linux
run skypeforlinux-64.rpm
Comment 1 sturmvogel 2021-05-13 10:05:33 CEST
libatomic1 is available in core repository. 
After installation of libatomic1 and gnome-keyring skype can be installed and starts successfull.

sudo rpm -ivh /home/ich/Desktop/daten/downloads/skypeforlinux-64.rpm
Warnung: /home/ich/Desktop/daten/downloads/skypeforlinux-64.rpm: Header V4 RSA/SHA256 Signature, Schlüssel-ID df7587c3: NOKEY
Wird überprüft …                  ################################# [100%]
Vorbereiten …                       ################################# [100%]
Aktualisierung/ Installation …
   1:skypeforlinux-8.71.0.36-1        ################################# [100%]
Redirecting to /bin/systemctl start atd.service

Status: NEW => UNCONFIRMED
Ever confirmed: 1 => 0

Comment 2 Sander Lepik 2021-05-13 10:24:07 CEST
I suggest urpmi instead of rpm -ivh as urpmi will resolve missing dependencies automatically.

CC: (none) => mageia

Comment 3 Jan Pihlgren 2021-05-13 11:24:00 CEST
Solved.
Thanks! ;)

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

Comment 4 Morgan Leijström 2021-05-13 12:06:17 CEST
It was never a bug :)

Resolution: FIXED => INVALID
CC: (none) => fri


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