Hi @Razaloc. Thanks for your PR.

I'm waiting for a coreos member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

I'm still testing it. It also fix a small format typo I found at line 1443

/ok-to-test

Do you have more background on this PR? I think having this option could make sense, though we should probably instead just enhance the global pkg_entries array or so to make it available in all the relevant commands.

As we wanted to handle pinning and unpinning pkgs to versions I think the idea was to undo the overrides at upgrade.

Let's hold this until we finalize the design in #1265.
/hold

@Razaloc: PR needs rebase.

@Razaloc: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Full PR test history. Your PR dashboard.