Description of problem:
Some clients of yum generate their own .repo files. Yum has certain requirements for the format of the .repo files, in particular, for the format of the section name in a .repo file.
If the check for correct id format were exposed in a separate method the client code could call the method to verify correctness while writing the .repo file.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
It might be helpful to expose the whole chunk of code in getReposFromConfig that checks for proper format of a .repo file in a separate method so that a client could immediately read and verify the file after having written it and manage errors appropriately.
it would be best if the code that checks the format were factored out of the yum package, so that the user didn't have to load that package in order to verify that the repo files they were constructing were correctly formatted. (The client code probably wants to avoid the side-effects of loading the yum package when generating a .repo file).
I'm reassigning this to dnf, this has a bigger priority there, as we are in a process of defining dnf's API. This will not have a priority in yum itself, maybe as a backport from dnf.
Hi there, thanks for the report. We'll try to provide the requested function when we define the API. Leaving this a low prio thing until then.
Radek, please add a function like that to dnf.utils and document it as an API call.
The function called "repo_id_invalid" added by b81bdf1654cfa4174a9629547d8a5e3bca2e9759 on master.
dnf-0.4.10-1.fc20 has been submitted as an update for Fedora 20.
* should fix your issue,
* was pushed to the Fedora 20 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing dnf-0.4.10-1.fc20'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
dnf-0.4.10-1.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.