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

Confusing error state reported by Koschei. #320

Open
ellert opened this issue Jun 23, 2020 · 0 comments
Open

Confusing error state reported by Koschei. #320

ellert opened this issue Jun 23, 2020 · 0 comments

Comments

@ellert
Copy link

ellert commented Jun 23, 2020

For several of my packages Koschei currently reports "No suitable SRPM was found", even though the current SRPM has been used by Koschei to perform test builds in the past.

Here is a list of my affected packages:
https://koschei.fedoraproject.org/package/arc-gui-clients?collection=f33
https://koschei.fedoraproject.org/package/globus-net-manager?collection=f33
https://koschei.fedoraproject.org/package/jargs?collection=f33
https://koschei.fedoraproject.org/package/R-qtl?collection=f32
https://koschei.fedoraproject.org/package/xrootd-ceph?collection=f33

I could imagine this happening if there was e.g. a temporary network issue and Koschei couldn't check if the SRPM was available, but in that case it shouldn't stay in this state for long. It looks like once it gets into this state it doesn't get out if it for days and weeks.

Looking around the Koschhei web UI, many other packages seems to be affected.

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