Re: [AUH] [PATCH v2 1/2] upgrade-helper: add state module and --incremental mode

Alexander Kanavin <[email protected]>
Newsgroups org.yoctoproject.lists.yocto-patches
Message-ID <CANNYZj9X=Bd47XAP49w6hDqP6GVTMNWxE=Jc8WUV78bUdRCULg@mail.gmail.com>
On Wed, 3 Jun 2026 at 17:50, <[email protected]> wrote:
> Behavior:
> - Failed attempts are retried after retry_interval days (default 30).
> - Successful/already-current upgrades are suppressed for success_max_age
>   days (default 30).

I have realized that we also need to handle recipes with rapid-fire
releases, that would otherwise flood the mailing list with daily
updates (if AUH is run once a day, which is the goal). This typically
happens when:
- there are no release tags, the recipe just takes the latest commit,
and upstream adds commits frequently (for example, vulkan-samples)
- upstream does have release tags, but they're added often, e.g.
sbom-cve-check-* items add them once a day, and some python items are
also rather quite 'liberal' with tags

So I'd suggest:

retry_interval is renamed to retry_same_version_interval
retry_any_version_interval setting is introduced
retry_any_version_recipes setting is introduced, and is a list of recipes
_prune() is adjusted to first check if a recipe is in that list, and
if so, it's checked against retry_any_version_interval, and not any
other intervals, so that it's guaranteed to be skipped until that
interval elapses (and skip_reason() should consider that similarly)

Otherwise, I think this is more or less ready!

Alex
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.