You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The hotness hears about a new upstream release being discovered, it compares the version of it against what it thinks is in rawhide. It uses repoquery with this yum config to figure out what we currently have.
The metadata_expire part is set intentionally small, so that shortly after something gets built for rawhide, hotness will know about it and not file bugs by mistake. But, it's not working as expected. I'll release something mid-day and build it for rawhide, then 6 hours later anitya will run, notice the new upstream release, then hotness will run and not yet know about my new rawhide build.
To close this window, we can use the repo used internally by koji for buildroots (generated by kojira):
A new problem stemming from that, is that that repo doesn't have any SRPMs and the-new-hotness currently requires a source repo to do its check. So, we simply need to modify the repoquery code to allow it to check the binary repos instead, then we can change our production config to use this new more frequently updated repo.
The text was updated successfully, but these errors were encountered:
The hotness hears about a new upstream release being discovered, it compares the version of it against what it thinks is in rawhide. It uses
repoquery
with this yum config to figure out what we currently have.The
metadata_expire
part is set intentionally small, so that shortly after something gets built for rawhide, hotness will know about it and not file bugs by mistake. But, it's not working as expected. I'll release something mid-day and build it for rawhide, then 6 hours later anitya will run, notice the new upstream release, then hotness will run and not yet know about my new rawhide build.To close this window, we can use the repo used internally by koji for buildroots (generated by kojira):
https://kojipkgs.fedoraproject.org/repos/rawhide/latest/
A new problem stemming from that, is that that repo doesn't have any SRPMs and the-new-hotness currently requires a source repo to do its check. So, we simply need to modify the repoquery code to allow it to check the binary repos instead, then we can change our production config to use this new more frequently updated repo.
The text was updated successfully, but these errors were encountered: