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

Revert "Use focusbest: prefer latest deps versions over smaller transactions #1211

Merged
merged 1 commit into from
Jan 30, 2024

Conversation

kontura
Copy link
Contributor

@kontura kontura commented Jan 29, 2024

This reverts commit 2d9df1c.

The current behavior of SOLVER_FLAG_FOCUS_BEST turned out not be viable at this time, more details in: #1106

Depending on openSUSE/libsolv#549 we can either make the SOLVER_FLAG_FOCUS_BEST functionality configurable with a new option or use some different approach.

Closes #1106

@j-mracek
Copy link
Contributor

What about to make the flag optional? In past we've got several reports where users complained that transaction is performed with not latest packages. In case that I have a package foo and I want to upgrade or install it with all latest dependencies, such an option would be beneficial. This use case is applicable for containers (build and upgrade). What do you think?

@kontura
Copy link
Contributor Author

kontura commented Jan 29, 2024

What about to make the flag optional? In past we've got several reports where users complained that transaction is performed with not latest packages. In case that I have a package foo and I want to upgrade or install it with all latest dependencies, such an option would be beneficial. This use case is applicable for containers (build and upgrade). What do you think?

Yes as I wrote in the description I would first wait for the response from libsolv and depending on that we can either make it a new option or do something else.

But I think we should do this revert as soon as possible because the behavior is really not great.

@j-mracek j-mracek self-assigned this Jan 30, 2024
@@ -51,7 +51,7 @@ pkg_check_modules(LIBMODULEMD REQUIRED modulemd-2.0>=2.11.2)
list(APPEND LIBDNF5_PC_REQUIRES "${LIBMODULEMD_MODULE_NAME}")
target_link_libraries(libdnf5 PRIVATE ${LIBMODULEMD_LIBRARIES})

pkg_check_modules(LIBSOLV REQUIRED libsolv>=0.7.25)
pkg_check_modules(LIBSOLV REQUIRED libsolv>=0.7.21)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I do not recommend to lower a minimal version. It might happen that other recently introduced feature requires newer version then libsolv>=0.7.21 but at the time of introducing it the minimal require was libsolv>=0.7.25. Are you sure that this scenario is not applicable for this case?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am not 100% sure, I have dropped the change.

@j-mracek
Copy link
Contributor

LGTM

@kontura
Copy link
Contributor Author

kontura commented Jan 30, 2024

Here is a PR with ci tests update: rpm-software-management/ci-dnf-stack#1441

@j-mracek j-mracek added this pull request to the merge queue Jan 30, 2024
j-mracek pushed a commit to rpm-software-management/ci-dnf-stack that referenced this pull request Jan 30, 2024
Merged via the queue into rpm-software-management:main with commit 3ca5cf3 Jan 30, 2024
5 of 9 checks passed
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.

Unable to upgrade a single package unless --no-best is used
2 participants