Use packit instead of rpm-gitoverlay to build nighly

[kontura]

This requires: drpm, libcomps, dnf-plugins-core, dnf-plugins-extras, microdnf - to setup packit

It also requires dnf5 change to get the right version for all packit builds.

There is also a libsolv workaround because it is missing a packit setup as well but I think it is unlikely libsolv upstream would accept it.

Finally all the builds will run in parallel now so we loose the requires relationship between components. This could cause problems when one package requires a new version of another. However I think the build should fail only once because in a second run the new dependency will be already built.
One possible proper (and easy but slower) solution could be to configure the github action to do only one build at the time in the specified order.

[mfocko]

LGTM

[mfocko]

I've noticed yesterday that we also have rpm-software-management/libsolv, given this I guess it's not used anymore? So should it be archived?

[kontura]

Unfortunately there is a couple (one really) of small patches we need in RHEL that libsolv upstream doesn't want. Specifically its computing hashes using OpenSSL instead of the libsolv custom algorithms.

We store this in the rpm-software-management/libsolv.

[mfocko]

Finally all the builds will run in parallel now so we loose the requires relationship between components. This could cause problems when one package requires a new version of another. However I think the build should fail only once because in a second run the new dependency will be already built.

Copr allows setting order of the builds, but IIRC
a) it requires build IDs, not components :/
b) Packit doesn't support this option yet :/

[mfocko]

Copr allows setting order of the builds, but IIRC
a) it requires build IDs, not components :/
b) Packit doesn't support this option yet :/

https://python-copr.readthedocs.io/en/latest/client_v3/build_options.html#:~:text=after_build_id,ID%20is%20processed

eh… I guess there should be an option in the GitHub Action to propagate the build ID out… though I think it would need to be parsed from the Packit output; and now that I think about it, it would be sequential anyways 🤔

[kontura]

Copr allows setting order of the builds, but IIRC
a) it requires build IDs, not components :/
b) Packit doesn't support this option yet :/

https://python-copr.readthedocs.io/en/latest/client_v3/build_options.html#:~:text=after_build_id,ID%20is%20processed

Oh yea, right, I think that is what rpm-gitoverlay uses.

eh… I guess there should be an option in the GitHub Action to propagate the build ID out… though I think it would need to be parsed from the Packit output; and now that I think about it, it would be sequential anyways 🤔

We probably could build something to have it in batches but indeed I don't think it is worth it. We can always add it later if it turns out to cause problems. Perhaps even Packit will add some support (packit/packit-service#2105) that could be used in this use case.