The `color` option value wasn't passed in `dnf-automatic` usage so far.
In the standard `dnf` command, the `Term` object is created before parsing the entire configuration, including command-line parameters. The `Term` is reinitialized within `Cli.configure` if the `color` option value was changed. In `dnf-automatic`, where configuration is processed in a single place, we can directly pass the value from the configuration.
Print better error message when the package specified in the argument is installed but is not available in the currently enabled repositories.
Resolves: https://issues.redhat.com/browse/RHEL-7018
Instead, hardcode the protection of dnf in libdnf. This way, DNF 5 will
be able to uninstall DNF 4.
= changelog =
msg: Allow dnf to be removed by DNF 5
type: enhancement
When a new group is being installed or an installed group is upgraded, do not mark the packages within the group as 'not installed' directly. Instead, check the actual package state in the database to determine if it was already installed by another group.
= changelog =
msg: comps: Fix removing packages belonging to another installed group
type: bugfix
resolves: https://bugzilla.redhat.com/show_bug.cgi?id=2066638
It was replace by RPM transaction item return code and it only prints
a message to terminal. It was not remove to keep compatibility of
outputs, but it does nothing.
https://bugzilla.redhat.com/show_bug.cgi?id=1908253
Add the ability to use STARTTLS/TLS for sending e-mail via the `email`
emitter.
The `email_tls` option supports three settings: ``starttls``, used to
switch to TLS on plaintext ports like 25 or 587 and ``yes``, used to
wrap the entire connection in TLS, usually on port 465. Any other
setting (``off`` by default) will use plain unencrypted SMTP.
Note: this depends on #1956 .
= changelog =
msg: Add `email_tls` option to DNF Automatic
type: enhancement
resolves: #1954
We are using the `rpm.blockSignals()` around RPM transactions to prevent interrupting them from outside. With rpm < 4.18.0, unblocking signals via this API caused termination on `SIGPIPE` signal which is unwanted as we have an overridden handler for this signal in DNF. With rpm >= 4.18.0 this is not happening anymore, therefore bumping the version.
Prevent signals to interrupt the processing of the RPM transaction inside the DNF.
This was originally committed in db833ff, but reverted later in 969781d as the provided API wasn't available on some systems rebasing from upstream which is not the case anymore.
Resolves https://issues.redhat.com/browse/RHEL-1235.
This reverts commit 352b174a0b.
adding the condition %{witout dnf5_obsoletes_dnf} to keep the
unprotected directive for chroots that build dnf with rpm
option with=dnf5_obsoletes_dnf
This change makes it resilient in some corner cases, such as if the user
has installed an old version of libdnf5 that doesn't provide
/etc/dnf/dnf.conf.
This patch adds documentation for the symbols shown in the "Action(s)"
and "Altered" columns of `dnf history list`
The "Action(s)" column abbreviates the names of transaction actions when
there was more than one action, e.g. a transaction that both installs
and upgrades packages would be displayed as "I, U".
The "Altered" column prints some extra symbols when something unusual
happened with the transaction, like if any warnings were printed or if
it completed with a non-zero status.
Some language was taken from the yum man pages:
https://github.com/rpm-software-management/yum/blob/master/docs/yum.8.
It appears we no longer use the "P" or "s" symbols.
Resolves https://bugzilla.redhat.com/show_bug.cgi?id=2172067
(RhBug:2172067)
= changelog =
msg: Document the symbols in the output of `dnf history list`
type: bugfix
resolves: https://bugzilla.redhat.com/show_bug.cgi?id=2172067
Move command provides to python3-dnf
In fedora distribution there are two packages that depends on those
provides therefor the movement of those provide to real provider should
help with transition to dnf5 or at least it allows to use the old dnf4
after obsolete of dnf package.
Jan Kolarik