steam depends on libpulse0 (>= 1:0.99.1)

steamclosed wontfix

ValveSoftware/steam-for-linux#49 · opened 2012-12-20 by trancee · updated 2012-12-20 · 4 comments · github

Ttrancee 2012-12-20 github

System:    Host: SUISSE Kernel: 3.6.0-10.dmz.1-liquorix-amd64 x86_64 (64 bit) Desktop: MATE 1.4.0  Distro: LinuxMint 1 debian
Machine:   System: LENOVO (portable) product: 4384GFG version: ThinkPad T510 serial: R996WEV 
           Mobo: LENOVO model: 4384GFG serial: 1ZJ9X0BD144 Bios: LENOVO version: 6MET81WW (1.41 ) date: 10/26/2010
CPU:       Dual core Intel Core i7 CPU M 620 (-HT-MCP-) clocked at 1199.00 MHz 
Graphics:  Card-1: Intel Core Processor Integrated Graphics Controller 
           Card-2: NVIDIA GT218 [NVS 3100M] 
           X.org: 1.12.4 drivers: intel (unloaded: fbdev,vesa) tty size: 143x37 Advanced Data: N/A for root 
Network:   Card-1: Intel Centrino Ultimate-N 6300 driver: iwlwifi 
           Card-2: Intel 82577LM Gigabit Network Connection driver: e1000e 
Drives:    HDD Total Size: 502.1GB (11.5% used)
Info:      Processes: 239 Uptime: 1:09 Memory: 1547.5/5759.0MB Client: Shell inxi: 1.8.20

As you can see from my report above, I have Linux Mint LMDE installed. Since I updated to the latest Update Pack 6, I was finally able to successfully install Steam. There was only one dependency which Steam said was not met:

 steam depends on libpulse0 (>= 1:0.99.1); however:
  Version of libpulse0:i386 on system is 2.0-6.

If I ignore this error and force the install, Steam works as expected. Maybe something about that dependency is not configured right, as it says >= 0.99.1 and I have 2.0-6 which is clearly newer.

I installed the latest Steam binary (1.0.0.17).

?ghost 2012-12-20 github

Your using Linux Mint... Steam for Linux is Officially Support only on Ubuntu 12.04 LTS which has the proper dependencies.

Bugs seem invalid.

KKarolS 2012-12-20 github

According to Debian versioning scheme, 1:0.99.1 > 2.0-6

Ttrancee 2012-12-20 github

I know that Linux Mint is not officially supported, but anyway, it runs if you ignore this dependency issue. I also upgraded to the latest experimental libpulse0 2.1-2 and it still gave me that error. What's up with this different versioning scheme? To me, it looks more like a policy issue not a technical issue.

Ssk1p 2012-12-20 github

@trancee have a look at the Debian Policy Manual. "It is provided to allow mistakes in the version numbers of older versions of a package, and also a package's previous version numbering schemes, to be left behind."

Nothing extracted yet.