Pass Anitya

[mfocko]

Related to packit/packit-service#2068

[softwarefactory-project-zuul]

Build succeeded.
https://softwarefactory-project.io/zuul/t/packit-service/buildset/886ee36593e54d9c9f83d1c00764a097

✔️ pre-commit SUCCESS in 6m 25s

[softwarefactory-project-zuul]

Build succeeded.
https://softwarefactory-project.io/zuul/t/packit-service/buildset/c0ef93323e874c65ac840fbacffd574c

✔️ pre-commit SUCCESS in 9m 35s

[lbarcziova]

nicely factored out! 🚀

[lbarcziova]

how will this work if there are multiple new versions? Could you point me to the docs explaining these, e.g. "upstream_versions" vs "version" (and maybe add a comment with this link please)

[mfocko]

Very good question, open for discussion IMO 😂 docs

I think this applies mainly to the upstreams that keep multiple running branches (like kernel, maybe Java (? even though they have separate RPM packages for that)).

OTOH this is something that I can see used with CentOS specifically, because if there are multiple major/minor releases maintained, user should be able to specify some tag filtering in sense of “I want to follow this branch instead of the latest one”.

Given this example, these are the relevant fields:

• upstream_versions: which are apparently the newly detected versions
• stable_versions: duh…
• versions: all versions (including stable, newly detected and prereleases; literally all)
• old_version (not relevant, but worth mentioning): latest from version, CAN be prerelease

I think we'll need to adjust this in the Service…

[lbarcziova]

ok, got it, thanks for the explanation!

I think we'll need to adjust this in the Service

👍

[softwarefactory-project-zuul]

Build succeeded.
https://softwarefactory-project.io/zuul/t/packit-service/buildset/8fd4d0db3bf44cdbb3e7561491cd7d49

✔️ pre-commit SUCCESS in 1m 34s

[softwarefactory-project-zuul]

Build succeeded (gate pipeline).
https://softwarefactory-project.io/zuul/t/packit-service/buildset/b6be1f29f1d342a9a525b25de04d26d8

✔️ pre-commit SUCCESS in 1m 16s