From a8a3cf4247fe374855e1ee292eb2b4bda835f690 Mon Sep 17 00:00:00 2001 From: Jaroslav Mracek Date: Wed, 3 Jul 2019 12:37:57 +0200 Subject: [PATCH] Revert consequences of Fail-Safe mechanism --- dnf/db/group.py | 2 +- doc/modularity.rst | 3 +-- 2 files changed, 2 insertions(+), 3 deletions(-) diff --git a/dnf/db/group.py b/dnf/db/group.py index 5082c7b..065d362 100644 --- a/dnf/db/group.py +++ b/dnf/db/group.py @@ -331,7 +331,7 @@ class RPMTransaction(object): else: raise RuntimeError("TransactionItemAction not handled: %s" % tsi.action) if modular_problems: - raise dnf.exceptions.Error(_("No available modular metadata for modular package")) + logger.critical(_("No available modular metadata for modular package")) return ts diff --git a/doc/modularity.rst b/doc/modularity.rst index 83b1227..a5d0975 100644 --- a/doc/modularity.rst +++ b/doc/modularity.rst @@ -99,5 +99,4 @@ Orphaned modular packages ========================= All packages that are built as a part of a module have ``%{modularitylabel}`` RPM header set. If such package becomes part of RPM transaction and cannot be associated with any available -modulemd, DNF prevents from getting it on the system (package is available, but cannot be -installed, upgraded, etc.) +modulemd, DNF logs the issue as critical problem. -- libgit2 0.27.8