Drop in configuration is affecting tests

[kontura]

Before drop in configuration was read or existed (for both dnf5 and dnf4) the tests were isolated from host system dnf configuration (present since f41) but now it is affecting them.

One issue this caused is workarounded in #1680.

However I worry this might cause more problems.

I think that ideally we should somehow disable it or make sure there is no extra configuration.

[ppisar]

This cannot be fixed in tests (unless you want to run everything in chroot). DNF4 and DNF5 code needs to support changing paths to user configuration and distribution configuration.

If main configuration file (dnf5 --config FILE) is processed first, then it can be a configuration option there. Otherwise, new command-line options for the programs are needed. Theoretically it could be new environment variables instead of the options.

As a weaker solution the options could at least disable processing those configurations instead of changing their locations.

[ppisar]

Or if we want to run all tests in chroot, then we can simply delete all files in the configuration directories inside the chroot.

[kontura]

Or if we want to run all tests in chroot, then we can simply delete all files in the configuration directories inside the chroot.

That is probably not an option, there are tests that are tagged @no_installroot.

[jrohel]

That is probably not an option, there are tests that are tagged @no_installroot.

Last week, I made two PRs related to this.

• The first one context config: Fix and extend support libdnf5 drop-in dirs and repository overrides libdnf#1710 fixes and extends support for drop-in dirs and repository overrides to be as compatible as possible with DNF5.
• The second one Context: Add tests for drop-in dirs, repository overrides, fix and add vars test #1678 addresses CI tests.
  • It backports the DNF5 tests for the old microdnf to verify that configuration reading is truly compatible.
  • Removes @no_installroot and @destructive from microdnf tests. - Initially, microdnf did not support installroot, so tests were marked with @no_installroot. However, I added installroot support to microdnf several years ago.