Description of problem:
The following kickstart directive used to work with Fedora17, but fails now with 18.
repo --name="RPM Fusion for Fedora 18 - Free" --baseurl=http://download1.rpmfusion.org/free/fedora/development/18/x86_64/os/
Any --name parameter which includes a space will fail.
Work around is to replace spaces with _.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install with kickstart and include repo --name="one two" --url=http://valid/repo
2. include package which is only in repo
Install will complain that package is not available.
Install will install package from additional repo with spaces in it.
Looks like this problem lies within yum, not anaconda. I'm no yum expert, but it looks like the getGroups function in yumRepo.py might be the culprit; reassigning to the appropriate component.
I'll also attach packaging.log from when I reproduced this following the steps in the original post.
Created attachment 661030 [details]
*** Bug 886868 has been marked as a duplicate of this bug. ***
This is *still* broken in the latest Fedora 19 build.
While repository NAME can contain spaces in Yum, the repo ID can not(*). Also, the ID is mandatory, and NAME is optional. I guess kickstart breaks these rules (probably setting the ID to be equal to NAME). Is there an --id option to set the repo ID explicitly?
IMO, this is a bug in kickstart.. It should use the specified repo ID, or auto-generate a valid one (eg ks001, ks002 etc). Have no idea why this worked in F17 (the repo ID check is from year 2008).
(*)Allowed repo ID chars are ascii letters, numbers, and "-_.:".
Here is a link to the kickstart repo command
The argument is called --name but the description says "the repoid".
This is confusing. :-)
At a minimum the doc should be updated with a list of acceptable chars, or maybe automatically replace spaces with _?
Discussed at 2013-06-12 blocker review meeting: http://meetbot.fedoraproject.org/fedora-blocker-review/2013-06-12/f19final-blocker-review-5.2013-06-12-16.01.log.txt . This was rejected as a blocker bug as it doesn't really violate any release criteria and is easy enough to work around, but accepted as a freeze exception issue: it seems like improvements could be made to this anaconda-side if the anaconda team felt it was appropriate, like converting spaces to underscores in the repo ID, or just failing with a more useful error message. So we're re-assigning to anaconda for their decision: if they think the code is fine and the docs should just be updated, that's of course up to them, but we're giving them the option of putting a reasonable code fix in.
This message is a notice that Fedora 19 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 19. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 19 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.