This package is no longer being maintained

[GhostSquad57]

This .deb is no longer being maintained; Steam now runs fine on Debian Testing, (Jessie), without needing this package.

It's recommended that you uninstall "steam-debian" and install Valve's official installer

I thank all of you for your kind feedback! --GhostSquad57

[gheesh]

Thank you for the excellent work, you've allowed us to experience Steam months ahead!

[basvdheuvel]

The steam_latest.deb still doesn't install due to an unsatisfiable package (libc6).

[GhostSquad57]

@klaplong interesting... what version of Debian are you running? i.e. Stable, Testing.

[kirbyUK]

The Steam package still relies on jockey-common, is there any way around this?

[GhostSquad57]

@kirbyman62 you could still use my shell script to fix this problem; it downloads jockey-common and python-xkit from Ubuntu's mirrors and installs them.

wget http://mirror.pnl.gov/ubuntu//pool/main/x/x-kit/python-xkit_0.4.2.3build1_all.deb && sudo dpkg --install python-xkit_0.4.2.3build1_all.deb && rm python-xkit_0.4.2.3build1_all.deb wget http://mirror.pnl.gov/ubuntu//pool/main/j/jockey/jockey-common_0.9.7-0ubuntu7_all.deb && sudo dpkg --install jockey-common_0.9.7-0ubuntu7_all.deb && rm jockey-common_0.9.7-0ubuntu7_all.deb

[basvdheuvel]

@GhostSquad57 I'm running Debian Wheezy (not Testing anymore I believe?) 64-bit.

[GhostSquad57]

@klaplong That explains it. Newest version of libc6 was pushed to Testing and not Stable for obvious reasons.

If you would like to go back to Testing, you could open /etc/apt/sources.list and replace wheezy with testing

[basvdheuvel]

@GhostSquad57 Everything is already set to testing in mij sources.list. But I think the cause is that I haven't upgraded yet. I am upgrading now and think it will work.

[kirbyUK]

@GhostSquad57 That's solved it, thanks.

[GhostSquad57]

@klaplong Yep, that's probably it.

[habernir]

thanks for your work but not everyone using Debian Testing, (Jessie)

[tomasabril]

@habernir yep, im in wheezy stable and I use this package. It's working very well

[habernir]

you talk about the steam-debian or Valve's official?

[tomasabril]

this package steam-debian from GhostSquad57

[testian]

Too bad. Testing is too buggy for me.

I will keep using this package.

[habernir]

thanks for maintaining but why did you stop maintaining? Jessie its still in testing (not stable) and not everyone use testing channel

[GhostSquad57]

@habernir I'm considering installing Stable on a virtual machine and using that for testing my package. If everything goes well, I'll definitely start maintaining this package again.

[habernir]

thanks ,I thank you very much !!!!

[testian]

That would be really great. If you don't get it to work, can you provide a guide to maintain it?

And if we could have a repository, that would be great. (Alternatively I can take over that part) I'm a newbie regarding repositories, but it's very easy with reprepro, so if you pick my modified version of the steam-debian package: http://repository.violetsky.ch/steam/pool/main/s/steam/steam-debian_1.0.0.39-8-1_all.deb you will get the repository added.

Alternatively just add "deb http://repository.violetsky.ch/steam/ wheezy main" to your sources and add this key using apt-key add: http://repository.violetsky.ch/dimitri_nuescheler.asc

[GhostSquad57]

@testian Thank you very much for the repo, I've included your repo with the newest version of my deb (which should be uploaded shortly). My deb seems to run fine on Wheezy, so it looks like I'm maintaining this package again!

[GhostSquad57]

All right, new version is up!

[testian]

I think you incremented the version number part that I added. In my opinion you can remove that part and call your next version 1.0.0.39-9 (assuming there is no no release from valve until)

Thanks for leaving no man behind :-)

edit: and you can also call yourself Maintainer again :-)

[GhostSquad57]

@testian D'oh! I didn't realize all those silly mistakes I made, oh well, I'll fix it next release :-)

[GhostSquad57]

@testian After thinking about it for a bit, I think it would be better to keep the current naming scheme; since my deb now uses your repo, it would be best to keep the names the same in order to avoid conflict.