If you use multiarch (and you probably do if you use Steam) there should be no problem.
But if you don't tell us what is the dpkg's error, we won't be able to help you.
Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230
STEAAAAAAM!!!!
-
gradinaruvasile
- Posts: 935
- Joined: 2010-01-31 22:03
- Location: Cluj, Romania
- Contact:
Re: STEAAAAAAM!!!!
The .deb in question is Ubuntu specific. Very Ubuntu specific. The biggest issue is that it requires a specific libc (2.15), which is different than the one used in Debian (2.13).
Nonetheless, it can be run on Debian. I do.
Here is a nice description of the ins and outs of this issue:
http://aspensmonster.com/2012/12/07/ste ... ng-wheezy/
Now, i was lazy and didnt fiddle with the recreation of the .deb + installing dependencies, just extracted the executable and lib files from it, downloaded the Ubuntu libc deb (the only real "dependency"), extracted it, made a wrapper script that preloades the Ubuntu libc then launched the steam script from the extracted location.
This first executable that is contained in the installer .deb in fact just activates the install sequence (it needs 2 additional files that are located in the lib folder of the deb file) downloads Steam and installs it in the home folder.
All subsequent actions launch the real Steam executable from the steam folder. So the installer .deb isnt needed for Steam updates and such (it is needed for proxying the launch of the real steam though), those are handled by Steam itself internally after launch.
Nonetheless, it can be run on Debian. I do.
Here is a nice description of the ins and outs of this issue:
http://aspensmonster.com/2012/12/07/ste ... ng-wheezy/
Now, i was lazy and didnt fiddle with the recreation of the .deb + installing dependencies, just extracted the executable and lib files from it, downloaded the Ubuntu libc deb (the only real "dependency"), extracted it, made a wrapper script that preloades the Ubuntu libc then launched the steam script from the extracted location.
This first executable that is contained in the installer .deb in fact just activates the install sequence (it needs 2 additional files that are located in the lib folder of the deb file) downloads Steam and installs it in the home folder.
All subsequent actions launch the real Steam executable from the steam folder. So the installer .deb isnt needed for Steam updates and such (it is needed for proxying the launch of the real steam though), those are handled by Steam itself internally after launch.