qyliss changed the topic of #spectrum to: A compartmentalized operating system | https://spectrum-os.org/ | Logs: https://logs.spectrum-os.org/spectrum/
<qyliss> hyperfekt: Is it not just that you look at https://chromium.googlesource.com/chromiumos/manifest-versions/+/master/paladin/buildspecs/80/12625.0.0-rc2.xml#65 rather than the corresponding one for Chromium?
<qyliss> hyperfekt: Are you sure they actually have release versions, as opposed to a rolling release?
<qyliss> hyperfekt: oh, crosvm also has tags with names like "release-R79-12607.B"
<qyliss> That looks promising
<qyliss> There's only one of those for each number after R
<qyliss> So I'm gonna assume it's those
<MichaelRaskin> I think with CrosVM being specifically targeted towards Crom{ium,e}OS, whatever Chromebooks ship can be considered a release
<qyliss> In my tree, unless I hear any reason to do anything better, I'm gonna go with the release tags
<qyliss> They look like the right thing
<MichaelRaskin> Hope .B is not «beta»
<hyperfekt> qyliss: well, you get a ref for a version then but it won't be a stable one
<qyliss> hyperfekt: the git tags are presumably stable
<qyliss> MichaelRaskin: I suspect it's "build'
<MichaelRaskin> I _hope_ so
<hyperfekt> and i wasn't able to find out what the git tag actually means, that's a presumption one could make but i didn't feel confident to
<hyperfekt> my best current guess is to look at the omahaproxy, look for the latest stable version, look for that in the buildspecs
<MichaelRaskin> Does the revision in the latest OS release correspond to a tag in CrosVM?
<qyliss> MichaelRaskin: good question
<qyliss> Oh I UNDERSTAND IT
<qyliss> I think
<qyliss> "12607.B" is "buildspec 12607"
<MichaelRaskin> We are losing qyliss, understanding what the hell is Google doing is not a good sign
<qyliss> Now, since there's only one tag per release number, that buildspec is not for disambiguation I think, but so that you can easily tell which buildspec is which release
<qyliss> This is corroborated by the fact that V 80, which is not out yet, but does have builds, doesn't have a corresponding tag.
<MichaelRaskin> It's a foreign key to some huge SVN repo!
<qyliss> release-R79-12607.B is cfb7db44eb9e5a0bca9a22bfb985252ef74ab251
<MichaelRaskin> Ah cool
<qyliss> So hyperfekt, it's the tags you want to use
<hyperfekt> so the latest stable build currently released to a device is 77.0.3865.105
<qyliss> hyperfekt: that web page doesn't load for me
<hyperfekt> you sure? it takes a loong while
<qyliss> 500 from the API
<qyliss> or the CSV url or whatever
<qyliss> Okay I can load it with curl
<hyperfekt> lmao that have python script to find a buildspec for a version
<qyliss> hyperfekt: you mean they have one?
<hyperfekt> oh i was looking at chromium versions not cros versions, just got up, still a bit slow
<hyperfekt> okay so the release-R77-12371.B tag is the latest stable
<hyperfekt> i guess we would check for the current stable chromium version, find out its tag and that should do the job, theoretically
<qyliss> That should be easy enough to script
<MichaelRaskin> And what is the status of R79 then?
<hyperfekt> which is a sensible setup for the chromium repo to have but them having that was not an assumption i was willing to make
<qyliss> MichaelRaskin: R79 is dev channel
<MichaelRaskin> Ah
<MichaelRaskin> So there will be another, later R79?
<qyliss> guessing so
<hyperfekt> yeah, i presume the latest build in a major version is the relase in a channel attached to that version, and they just keep piling builds on top
<qyliss> But we can at least write a script to get the tag version from a stable version
<qyliss> hyperfekt: how do you feel about a patch to your PR to finish it up?
<hyperfekt> the other thing to do is to make the patch applied to crosvm pretty
<hyperfekt> as in compile time instead of run time env var
<hyperfekt> if you wanna do the updater i'll look into how that is done in rust
<hyperfekt> you found an api to get the major version of the stable channel yet? i don't wanna tie it to chromium getting updated or the maintainer having to enter it manually
<qyliss> hyperfekt: yeah, that site you linked is I assume specific to Chromium OS
<qyliss> Since it's called cros- whatever
<hyperfekt> okay so we filter that csv by stable, sort, use that as tag
<hyperfekt> that's cleaner than looking for a tag for a major version in the repo anyway
<qyliss> Yeah
<qyliss> lmao the CSV is malformed
<qyliss> Acer Chromebook 15 (CB5-571, C910) is a field
<qyliss> they don't quote it
<hyperfekt> that's why i was looking for an API, this site doesn't seem to be meant for actual consumption lol
<qyliss> But this works well enough
<qyliss> hyperfekt: they link to the CSV!!
<qyliss> So it must be meant for consumption of some sort
<MichaelRaskin> Well, CSV that doesn't even load every time…
<hyperfekt> ^ this :/
<MichaelRaskin> Well-formedness of the _last_ field in CSV is not _that_ relevant
<hyperfekt> but it speaks to the care taken to provide that interface and thus the likelihood of it breaking on us
<qyliss> I doubt it's gonna break
<qyliss> It's at least going to be stably broken
<qyliss> And if it breaks, that's not a huge deal
<qyliss> We can find some new way
<MichaelRaskin> I also think that care to follow output format spec and care to update when upstream behaviour changes are completely unrelated, so we have no idea if something is going to break
MichaelRaskin has quit [Quit: MichaelRaskin]
<hyperfekt> ugh anyone here already know how gerrit works? i'm not so keen on submitting this patch lol
<qyliss> I've used gerrit before
<Shell> iirc you push things to refs/for/<branch> and it creates a branch/gerrit page with your commits?
<qyliss> And there's usually a wrapper to do it for you in Google's repo
pie_ has joined #spectrum
<hyperfekt> pushed the crosvm pr with the nicer patch
<qyliss> nice
<qyliss> I'm learning how updateScript works
<qyliss> But this is basically working
<qyliss> Will be with you in an our or so
<qyliss> *hour
<hyperfekt> there's some optional dependencies missing which are listed in https://chromium.googlesource.com/chromiumos/platform/crosvm/+/refs/heads/release-R77-12371.B/docker/Dockerfile but this should be enough to get a vm to boot
<qyliss> Ah shit
<qyliss> These things in the repo are branches, not tags
<qyliss> sad :(
<qyliss> So I guess I need to check in that other repo
<qyliss> I've asked about version numbers in #chromium-os but it seems to be pretty inactive going by the logs
<qyliss> My new plan is that I'll find the Chromium version number that's stable, then just pick the latest buildspec
<qyliss> I suspect we don't actually have access to whatever is in 12371.75.0
<qyliss> I suspect that is "75 proprietary google patches on top of 12371"
<qyliss> it means "tip of tree build 12371, branch build 75, branch branch build 0"
<qyliss> "branch branches" seem to be for device specific stuff I think? Going by the release Matrix.
<qyliss> hyperfekt: shall I send you the patch so you can apply it to your PR?
<hyperfekt> qyliss: sure, good opportunity to learn squashing
<qyliss> email address?
<hyperfekt> in query :)
pie_ has quit [Ping timeout: 240 seconds]
tilpner has quit [Quit: tilpner]
tilpner has joined #spectrum
tilpner has quit [Quit: tilpner]
tilpner has joined #spectrum