kolage

This should be already addressed in dnf5. Closing this one.

Hi, sorry but we're decided to rather not merge such a change that could potentially change the existing behavior for API users.

Closing as Perl bindings are available in dnf5 and are compiled by default.

In dnf5 this issue is already covered [here](https://github.com/rpm-software-management/dnf5/issues/1031). Closing this one.

@abitrolly Hello, thanks for your PR and sorry for the late response, but the build is failing. Are you still planning to work on this?

Hello Stefan, I was trying to replicate the issue, but I was not successful. When I have the `git` package available for upgrade in the `updates` repository and I execute:...

> Could it be that the package we want to update is dependent of another package which although already installed the repo from which it comes is disabled in our...

@chenhaixing123 Thanks for submitting this one, it seems that it pointed me to the exact point of the problem here. I've prepared a [follow-up PR](https://github.com/rpm-software-management/dnf/pull/2048) for that. Let's wait for...

> Thank you for reviewing the PR. I'm still a little confused. If the merge action is to reinstall, do we execute the rollback command to reinstall or do nothing?...

I've prepared another PR to fix the issue already in the library code: - https://github.com/rpm-software-management/libdnf/pull/1644.