Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Pull from different rawhide repo. #16

Closed
ralphbean opened this issue Feb 22, 2015 · 0 comments
Closed

Pull from different rawhide repo. #16

ralphbean opened this issue Feb 22, 2015 · 0 comments

Comments

@ralphbean
Copy link
Contributor

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant