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
Investigate whether we can mitigate libmodulemd / metadata version compatibility issues in the future #2718
Comments
Action item: talk to ppisar, amatej There is a |
Another option: drop libmodulemd entirely perhaps |
If we go this route, we might need to identify some product/downstream issues to be written for packaging/build teams. |
Merged
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We currently have the issue that because our module yaml snippets go through libmodulemd before being saved, we are at the mercy of what libmodulemd does with them. In the past we have seen that when when individual modules contain metadata that the version of libmodulemd in question does not support, it silently?!? ignores the module during processing. This causes problems when creating associations between those modules and RPM packages.
We should investigate whether there are any better methods of storing this data such that the failures are not silent, or if we can make sure the correct thing happens independently of libmodulemd.
The text was updated successfully, but these errors were encountered: