Skip to content

Conversation

@jrohel
Copy link
Contributor

@jrohel jrohel commented Jan 6, 2026

  • Add documentation for the plugin_conf_dir configuration option which supports a list of directories for loading libdnf5 plugin configuration files.
  • Fix pluginconfpath and pluginpath option descriptions. The options support only a single directory, not a list of directories.
  • Added details about .conf file extension requirement and plugin loading conditions.

jrohel added 2 commits January 6, 2026 11:47
The options pluginconfpath and pluginpath support only a single
directory, not a list of directories.
Added details about .conf file extension requirement and plugin loading
conditions.
Add documentation for the new plugin_conf_dir configuration option
which supports a list of directories for loading libdnf5 plugin
configuration files.
@jrohel jrohel requested a review from a team as a code owner January 6, 2026 13:34
@jrohel jrohel requested review from m-blaha and removed request for a team January 6, 2026 13:34
@m-blaha
Copy link
Member

m-blaha commented Jan 6, 2026

There seem to be problems with building dnf5 on rawhide. I guess swig 4.4 behaves differently?
Also tests

Failing scenarios:
  dnf/upgrade-from-vendor.feature:67  Upgrade vendorpkg from "Second Vendor" and upgrade dependencies and install new dependency from any repos
  dnf/upgrade-from-vendor.feature:91  Upgrade vendorpkg from "Second Vendor", don't change vendor for upgraded dependencies and install new dependency from any repos

seem to be flaky - they depend on the order of elements in rpm transaction.

But these issues are not caused by this PR.

@ppisar
Copy link
Contributor

ppisar commented Jan 6, 2026

If you mean the array offset warning-as-an-error in Ruby bindings, it could be triggered by GCC 16 which is now in Fedora 44.

@m-blaha
Copy link
Member

m-blaha commented Jan 7, 2026

Or gcc, thanks! I did not look into it too closely since the failures are definitely not caused by documentation enhancements :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants