Bug 27123 - steam does not install because libcurl4 is unsatisfied
Summary: steam does not install because libcurl4 is unsatisfied
Status: RESOLVED INVALID
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Rémi Verschelde
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-08-16 11:46 CEST by Jean Michel Varvou
Modified: 2020-08-18 06:54 CEST (History)
0 users

See Also:
Source RPM: steam-1.0.0.64-1.mga8.nonfree.src.rpm
CVE:
Status comment:


Attachments

Description Jean Michel Varvou 2020-08-16 11:46:35 CEST
Description of problem:
steam does not install because libcurl4 is unsatisfied

Version-Release number of selected component (if applicable):
steam-1.0.0.64-1.mga8.nonfree.x86_64

How reproducible: Always
Install steam

Steps to Reproduce:
1. urpmi steam
2. then you have :

root@DESKTOP~]# urpmi steam
Le paquetage demandé ne peut pas être installé :
steam-1.0.0.64-1.mga8.nonfree.x86_64 (car libcurl4 est non satisfait)
Désirez-vous tout de même continuer ? (O/n)
Comment 1 Lewis Smith 2020-08-17 21:28:54 CEST
Thank you for the report.
This looks a problem of nomenclature:

$ urpmq --requires steam | grep curl
libcurl4
$ urpmq --whatrequires libcurl4
Dim pecyn o'r enw libcurl4      [No pkg of this name]

$ urpmq -y curl
lib64curl4      [among many others]
$ urpmq --whatrequires lib64curl4 | grep steam
$

Assigning to Rémi as the steam maintainer.

Source RPM: (none) => steam-1.0.0.64-1.mga8.nonfree.src.rpm
Assignee: bugsquad => rverschelde
Hardware: All => x86_64

Comment 2 Rémi Verschelde 2020-08-18 00:10:17 CEST
Steam needs 32-bit dependencies, so you need to enable 32-bit repositories to install it.
Comment 3 Jean Michel Varvou 2020-08-18 06:54:21 CEST
Hello

Thank you for your response. I just realized that when installing mageia 8, only updates are active for 32-bit and 64-bit tainted repositories .

Anyway, it's a rookie mistake not to have checked that...

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


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