-
Notifications
You must be signed in to change notification settings - Fork 88
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
flatdeb-steam documentation to build sniper is out of date #737
Comments
Hello, Is there a specific reason you want to build a runtime yourself, vs using an official image? For more info about the Steam for Linux runtime, and how to obtain sdk and runtime builds, see https://gitlab.steamos.cloud/steamrt/steam-runtime-tools/-/blob/main/docs/slr-for-game-developers.md @smcv we should probably cleanup those scripts, retire the chroot stuff and the old runtimes that we don't support anymore .. |
It is technically possible to do your own builds of a sniper runtime, but I wouldn't recommend it. Because the container runtime is structured rather differently, they are done via a different set of scripts (https://gitlab.steamos.cloud/steamrt/flatdeb-steam, followed by populate-depot.py from the https://gitlab.steamos.cloud/steamrt/steam-runtime-tools repository). We've generally been avoiding adding new tooling to this particular git repo, because its git history is inconveniently large: at some point in the past a developer committed binary .deb files to it, and now those are permanently part of the history and can't be removed. flatdeb-steam and steam-runtime-tools don't have that problem. |
Some of the scripts in this repository are still necessary when used internally (in particular, we still use `build-runtime.py` to build official scout releases), but third-party developers shouldn't normally need to run them, and they are not the same scripts that we use to build the container-based runtimes. Resolves: ValveSoftware#737 Signed-off-by: Simon McVittie <smcv@collabora.com>
Resolves: ValveSoftware#737 Signed-off-by: Simon McVittie <smcv@collabora.com>
I made a start on this in #740. |
FYI, the problem indicated by this error message wasn't actually that you were trying to build a sniper runtime with the wrong scripts. Instead, the problem is that it's spelled (But if you'd spelled that option correctly, the result still wouldn't have been practically useful: there is no |
Some of the scripts in this repository are still necessary when used internally (in particular, we still use `build-runtime.py` to build official scout releases), but third-party developers shouldn't normally need to run them, and they are not the same scripts that we use to build the container-based runtimes. Resolves: #737 Signed-off-by: Simon McVittie <smcv@collabora.com>
Resolves: #737 Signed-off-by: Simon McVittie <smcv@collabora.com>
@smcv Here's my build command:
Here's the part of the log.
However, on my browser, the cert of |
@kisak-valve, please could you reopen this and change the title to something like "flatdeb-steam documentation to build sniper out of date"? |
Building runtimes with these tools, outside the CI infrastructure that produces official releases, is not something that is frequently done (you're perhaps the fourth or fifth person to have ever tried it!) so the readme probably doesn't have all the information that's needed.
You shouldn't need
Do you have the I think all the other errors you see are just a result of not being able to access the apt repository.
Your browser has its own list of trusted CA certificates, which is independent of the one used by tools like apt, so it's entirely possible to get a situation where your browser works but apt doesn't. |
Yes, I did installed the |
Hmm, I might see what's happening here. The final runtime includes Try adding command-line options:
and
[edited: (That's the same as the default, but with http instead of https. The result will still have secure integrity checking, using secure apt GPG signatures.) Official builds aren't affected by this because we don't actually build from |
Thanks!
This is what I have in my directory:
Here is the end of the log.
[Update] |
Thanks, that sounds good. So I think there are two things we need to fix: the bootstrap should be done over http rather than https to avoid the ca-certificates dependency (this might just be a matter of configuration in flatdeb-steam, or we might need a small amount of new code in flatdeb to separate the build-time apt sources from the final apt sources first), and
This warning is harmless: if we don't want to put any configuration in that directory (which we don't) then it doesn't matter that it doesn't exist. Possibly some part of flatdeb could avoid this warning by creating it as an empty directory. |
Thank you for your reply!
Thanks! [Update] |
Yes, that's the default location for output unless overridden by
The official depot published via Steampipe consists of the contents of the archive The CI that runs flatdeb and As I'm sure you've realized by now, none of this is something that end users or game developers would normally need to do, and the official releases published by Valve are the only thing that we can provide support for. |
Hi, I'm trying to build the sniper runtime with this script, but I got an error:
Then I found that the
args.suite
only acceptscout
,scout_beta
,heavy
andheavy_beta
.I wonder if Ii'm using the right script or not.
Thanks!
The text was updated successfully, but these errors were encountered: