Satadru Pramanik, DO, MPH, MEng
Satadru Pramanik, DO, MPH, MEng
> `crew update compatible` is used to refresh package information without a git pull. > > It looks like this PR breaks that functionality... If I'm missing an obvious rename...
> All crew update compatible does is run PackageUtils.compatible? on every package and save the result. No part of crew uses the result anymore, so we can safely remove it....
I guess you will also have to add in the essential packages code that creates `@device[:essential_deps]` I just dropped into `generate_compatible`... 🫣
I don't understand why using an array is bad? Isn't that simpler and cleaner?
Unit tests are failing.
Honestly I'd be happier with the array being put in another file and just read in, as opposed to putting a bunch of `deprecrated` or whatever calls in a script...
I do love that we are testing changes on i686 containers now. 😅
> oh also the yaml handoff has been broken for some time now it looks like-- the changed-files actions is not reporting the changed github workflows I think I fixed...
This is because we have been using a modified version of the ChromeOS system Glibc binaries to bootstrap our own Glibc binaries. It's a really annoying hack, but otherwise our...
> Is there any way to perhaps patch the binary? > > **EDIT: ** I noticed `--with-bugurl=https://github.com/chromebrew/chromebrew/issues/new` in glibc_build237.rb. Why doesn't that change the bug url? Because that is our...