Can https://github.com/coq/coq/pull/15271 be backported to v8.9--v8.14? It's a small change, and not having it continues to cause build issues on coq-performance-tests CI (which builds plots for old versions of Coq). I'm fine with it only being on the dev branch (happy to have the CI use the dev branch for old versions of Coq). (If it's okay to backport, I can even prepare the backporting PRs myself.)
I guess that'd be fine @Jason Gross
Probably you will have to prepare the backporting PRs and also merge them yourself because retired RMs might not want to do it. You will need to use the dev/merge-pr.sh script for this. Note that you may encounter CI issues on older branches since we don't maintain them, so we don't know if something non-reproducible broke.
Created https://github.com/coq/coq/pull/16231, https://github.com/coq/coq/pull/16232, https://github.com/coq/coq/pull/16233, https://github.com/coq/coq/pull/16234, https://github.com/coq/coq/pull/16235, https://github.com/coq/coq/pull/16236, https://github.com/coq/coq/pull/16238. Do I need to get approvals, tag specific RMs, etc?
(Is there a list of RMs somewhere?)
No, there's no process for backporting to older branches.
@Jason Gross you may want to consider submitting patches to the official opam Coq packages as an alternative
then there is a "process" of sorts, i.e., it might be merged by OCaml opam repo maintainers and may reach places like the Coq Platform
Is there a way to fix
ERROR: Job failed: failed to pull image "registry.gitlab.com/coq/coq:bionic_coq-V2020-11-26-V93" with specified policies [always]: Error response from daemon: manifest for registry.gitlab.com/coq/coq:bionic_coq-V2020-11-26-V93 not found: manifest unknown: manifest unknown (manager.go:203:0s)
I pushed a commit that should fix it
Thanks! Is there a similar fix for https://github.com/coq/coq/pull/16231? (just put v8.14 in the same place?)
well only in the yml for 8.14 since CACHEKEY handling was simplified a bit
Last updated: Dec 01 2023 at 07:01 UTC