-
Notifications
You must be signed in to change notification settings - Fork 123
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
Discover step fails if beakerlib library not found in the repo #397
Comments
This should be already fixed by #382. What version of |
|
The problem above is that the epel repository does not have a |
I did not even notice that. Shouldn't tmt look at the default branch instead of hard-coded master? |
ok, adding master branch moved me a bit forward
|
just for the record, previously I was using |
Ok, we should nicely handle when there are no fmf metadata in the library repository. Should be fixed by #399. |
If there's an existing repo on
github.com/beakerlib/<COMPONENT>
but the library is not there the discover step fails as git command cannot find the library there. This way it even does not try to satisfy the requirements from possibly enabled dnf repo.I.e. if I want to move one of the distribution libraries to github I will break the others.
The correct behaviour should be to continue and try to satisfy the library requirement in different execution phases.
The text was updated successfully, but these errors were encountered: