Pavel Raiskup
Pavel Raiskup
We plan to rework the dnf-plugins-core copr project into C++ (DNF5 work). We could work on this one after that.
Be careful about ipv6 arithmetics, we have /116 range, not yet fully working (see #3983).
https://pagure.io/fedora-infra/ansible/blob/ba209ee7df6f261469425cb40a656c9b40eca13e/f/roles/copr/backend/templates/provision/libvirt-new#_389-428
> Be careful about ipv6 arithmetics, By that I mean -- we need to re-assure that no pool (both on prod/stage) is taking the same statically allocated ipv6 address.
https://pagure.io/fedora-infra/ansible/blob/c0e5d61e0d163e14ee8af2d7d9c334c95ed4517d/f/roles/copr/backend/templates/provision/libvirt-new#_394-428
Could this be related to the Mock 6.6 release?
I'm not sure what do we do about this. Any proposals? On one hand this isn't a good packaging practice (that said, package builds should be as deterministic as possible,...
> what specifically isn't "good" here? Hello @pgnd, sorry for the delay. It's suboptimal for the package version to be that dynamic, as RPM returns a different NEVRA for every...
Thank you for the follow up on this, @pgnd > that a "Filename too long" error pops up Weird. Can you open a separate ticket for this, and link to...
Triage mtg: @xsuchy: A good addition would be an AI doing the tagging automatically per build history (dumped time/processor/memory consumption per recent tasks, etc...).