Description of problem: The /etc/yum.repos.d/fedora-cisco-openh264.repo file contains the following entry in the [fedora-cisco-openh264] section: enabled_metadata=1 This parameter is not described in the dnf.conf man page. Version-Release number of selected component (if applicable): dnf-2.7.5-9.fc28.noarch How reproducible: Always Steps to Reproduce: 1. $ man dnf.conf 2. Search for "enabled_metadata" Actual results: Parameter is not described in the man page. Expected results: Parameter should be described in the man page.
Well this is a good point. The option enabled_metadata can be in .repo file, it parsed but used in dnf anywhere, because the behavior that can be triggered by the option is incompatible with dnf philosophy. Hope that you will understand.
I had to search online to find out more, and other users might have the same problem. Fedora uses this parameter in a repo that we ship in the default installation but it's not documented. That's why I consider this as a *UX (user expierence) bug* and, in my opinion, this ticket should be re-opened and fixed. Instead of having a mysterious parameter in the configs and provide no option for the user to find out what it does, we should do one of the following: 1) Do not use this parameter in any repo. 2) Document the parameter in the man page. The description can mention that dnf does not use this parameter, but other tools can use it to optionally retrieve the metadata from the repository to provide a list of its contents to the user.
Hello Marc, You stole my words. I wanted to suggest exactly these alternatives. The only source of information is : https://fedoraproject.org/wiki/Third_Party_Repository_Policy I will also be working on making a KCS for RH customers to have clearer understanding until map page is created. I hope to have a BZ open under RHEL product to have this propagated into RHEL as well. Regards, Pranav