From: "Michael Schwendt" <mschwendt(a)gmail.com>
On Thu, 12 Nov 2015 06:38:41 -0500 (EST), Honza Šilhan wrote:
> "rpm -Uvh …" ~ "dnf install" - only difference is that dnf
install can
> do downgrades too if you specify the version of the package
So, if you run "dnf install *.rpm" and one of the local .rpm files is
older than what is installed, you cannot use that command because it
would want to perform a downgrade?
If you don't want the downgrade to be applied you should exclude that package
from cmdline (-x) or from the folder beforehand.
From: "Reindl Harald" <h.reindl(a)thelounge.net>
would not be a topic if DNF would not be completly broken for "dnf
update *.rpm", in F22 it works sometimes while in F23 it is just
unuseable 99.9% of the time
That's an important information, it would be great if you would cooperate
mentioning it in your bug report and attaching the debugdata as was requested
for each system. DNF versions are the same for F22 and F23 so I guess that would
be a a different packaging of the local packages - we will know from the debugdata.
From: "Michael Schwendt" <mschwendt(a)gmail.com>
If an _upgrade_ introduces new sub-packages or new dependencies, you
need a method that can install those new packages *and* update older
installed ones at the same time. Running "rpm -U *.rpm" is like asking
RPM to "upgrade the installation to the packages specified by *.rpm",
which may involve replacing older installed ones as well as adding new
packages to the installation.
I was suggesting that it would be possible to extend `strict` configuration option
for updates. That means with `dnf update *.rpm --strict=0` you would achieve what you
have said in this paragraph.
Honza