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

Don't use libdnf5 as a dependency #132

Merged
merged 1 commit into from
Jun 15, 2023
Merged

Conversation

jan-kolarik
Copy link
Member

We need to restrict the version of libdnf dependency to not use the libdnf >= 5.0.0 with different API. Unfortunately, the dnf5 package providing such a libdnf was already released, so it is not enough just to change the provide in the dnf5 package.

We need to restrict the version of `libdnf` dependency to not use the `libdnf >= 5.0.0` with different API. Unfortunately, the `dnf5` package providing such a `libdnf` was already released, so it is not enough just to change the provide in the `dnf5` package.
@j-mracek
Copy link
Contributor

I have nothing against to merge the PR, but if I am not mistaken the issue was resolved by rpm-software-management/dnf5#601.

@jan-kolarik
Copy link
Member Author

I have nothing against to merge the PR, but if I am not mistaken the issue was resolved by rpm-software-management/dnf5#601.

Unfortunately it's not enough as microdnf picks the older available dnf5 package from the repository which is still providing the libdnf f.e. in version 5.0.13.

@j-mracek
Copy link
Contributor

Correct

@j-mracek
Copy link
Contributor

LGTM

@j-mracek j-mracek merged commit a600c62 into master Jun 15, 2023
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

Successfully merging this pull request may close these issues.

2 participants