Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at
Bug 1761518 - dnf.conf.Conf strict option is not honored
Summary: dnf.conf.Conf strict option is not honored
Alias: None
Product: Fedora
Classification: Fedora
Component: dnf
Version: 32
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Marek Blaha
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2019-10-14 14:50 UTC by Jiri Konecny
Modified: 2020-05-01 04:04 UTC (History)
9 users (show)

Fixed In Version: dnf-4.2.21-1.fc32
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2020-05-01 04:04:36 UTC
Type: Bug

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1642013 0 unspecified CLOSED kickstart installation aborted because of conflicting packages, there should be an option to ignore conflicting packages 2022-05-16 11:32:56 UTC

Internal Links: 1642013

Description Jiri Konecny 2019-10-14 14:50:03 UTC
Description of problem:

The `strict` configuration option should skip all packages with the conflicting content. This option works correctly if set by the `install_specs()` method but this value is also contained in the `dnf.conf.Conf` but it's ignored there. For our use-case it would be easier to just set the global configuration.

Please tell me if the global configuration should work or if I should use the `install_spec()` method instead.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
If you really need the reproducer please ask for it but in this case I think it will be much easier for you to create it than for me.

Actual results:
If the `dnf.conf.Conf.strict` option is set to False it will still abort the installation when conflicting packages are used.  

Expected results:
If the `dnf.conf.Conf.strict` option is set to True it should skip packages conflicting with other packages.

Additional info:
Based on the documentation this may not be supported because it's part of the Repo only configuration. However, this option is part of the global configuration already and second I think there is a use-case for the global settings.

Comment 1 Marek Blaha 2019-10-15 06:35:23 UTC
The documentation is wrong here - the `strict` option is the global one, not repo only. This will be fixed.

Is it possible for you to call the install_specs() with the `strict` argument correctly set from the configuration?
i.e.: base.install_specs(the_specs, strict=base.conf.strict)

Comment 2 Marek Blaha 2019-10-15 07:32:28 UTC
PR for the documentation change:

Comment 3 Jiri Konecny 2019-10-15 11:14:15 UTC
Thanks for the documentation change.

Yes, it is possible to make a temporal workaround like that.

Comment 4 Marek Blaha 2019-10-16 08:39:40 UTC
I'm sorry but we can't do this change of the behaviour in the current version of the API. But we will keep it in mind for the future versions.

Comment 5 Ben Cotton 2020-02-11 17:51:22 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 32 development cycle.
Changing version to 32.

Comment 6 Fedora Update System 2020-04-09 10:56:41 UTC
FEDORA-2020-68aa5586ed has been submitted as an update to Fedora 32.

Comment 7 Fedora Update System 2020-04-09 18:40:11 UTC
FEDORA-2020-68aa5586ed has been pushed to the Fedora 32 testing repository.
In short time you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-68aa5586ed`
You can provide feedback for this update here:

See also for more information on how to test updates.

Comment 8 Fedora Update System 2020-05-01 04:04:36 UTC
FEDORA-2020-68aa5586ed has been pushed to the Fedora 32 stable repository.
If problem still persists, please make note of it in this bug report.

Note You need to log in before you can comment on or make changes to this bug.