See also bug 1720690 and bug 1644241.

Created attachment 1588724 [details]
test.spec

I create a patch that change decisions in libsolv: https://github.com/rpm-software-management/dnf/pull/1474.

The problem is discussed in  https://github.com/openSUSE/libsolv/issues/287 and https://github.com/openSUSE/libsolv/issues/342.

There is also related bug: https://bugzilla.redhat.com/show_bug.cgi?id=1644241

Hmm,
for me this was a very useful feature to test changes in packages of mine without bumping rpm version, before i push changes to github or fedora git.
I use a local repo for this where i can rebuild packages with mock for testing commits.
Before dnf-4.2.8-2.fc30 i could simply use `dnf update` to install packages from my local repo to get changes without bumping package version.
Well, i agree that this behaviour can cause problems for other use cases.
But is there command line option to get this behaviour back?
Or can such a command line option be implemented?

Thanks

Any chance to answer to questions from a fedora maintainer before you cancel my needinfo request?

Sorry, I missed your question.
As far as your use case is concerned - do I understand your work-flow correctly?

1. build a package into your local repository
2. test it
3. fix the bugs without changing the nevra and go back to 1.

If that is the case, you should be able to use distrosync command with narrowing down the repositories to your local one:

# dnf distrosync --repoid=<id-of-the-local-repo>

(In reply to Marek Blaha from comment #24)
> Sorry, I missed your question.
> As far as your use case is concerned - do I understand your work-flow
> correctly?
> 
> 1. build a package into your local repository
> 2. test it
> 3. fix the bugs without changing the nevra and go back to 1.
> 
> If that is the case, you should be able to use distrosync command with
> narrowing down the repositories to your local one:
> 
> # dnf distrosync --repoid=<id-of-the-local-repo>

Thanks for answering.
I am using my fedora RPMs to work on commits or testing PRs for MATE destop. And we have a lot of changes.
My work flow works like this.
1. Using RPMS for MATE developer releases from my public copr repo https://copr.fedorainfracloud.org/coprs/raveit65/MATE-1.23.x/builds/ for my local installation
eg. caja-1.23.2-1.fc30
2. with a new commit or a PR for testing i bumped version to caja-1.23.2-2.fc30 in my local dnf repo. This version i am using in my installation and i don't downgrade to to version from public copr repo.
3. New commits from Mate i simply add to caja-1.23.2-2.fc30 without bumping the version, to avoid pumping version daily.

So, for me it was very comfortable to use previous dnf version which reinstall packages with different buildtime with the `dnf update` command.
I thought to myself what a nice and useful new feature from fedora. I don't like all new features from fedora after using it a long time, but this one was amazing :)

Well, not a big deal because i can use `dnf reinstall caja* ` to test new changes for this package from my local repo.
But maybe the feature which was removed with latest dnf can be implemented as config or command line option?

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:1823