Bug 1129229 - $releasever and $basearch in kickstart recognition
Summary: $releasever and $basearch in kickstart recognition
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 20
Hardware: Unspecified
OS: Linux
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2014-08-12 10:57 UTC by Frantisek Hanzlik
Modified: 2015-06-29 22:02 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2015-06-29 22:02:07 UTC

Attachments (Terms of Use)

Description Frantisek Hanzlik 2014-08-12 10:57:32 UTC
Description of problem:
Perhaps not bug, but feature request: F19 and F20 allow use $releasever and $basearch in 'url' keyword in kickstart. But it isn't possible use these substitutions in 'repo', 'nfs', '%include' and maybe others.
IMO this should be usefull allow use it there as well.

One other thing that would be useful would be the possibility of substitution for installation server. For example, basic frame of my typical kickstart file is:

nfs --server=MYSERVER --dir=/repos/fedora/20/i386/os
repo --name="moje" --baseurl=http://MYSERVER/fedoralinux/20/i386/moje  (several times)
%include http://MYSERVER/ks/20/_must-be     (several times)

I'd be happy if I were to write some as:
nfs --server=MYSERVER --dir=/repos/fedora/$releasever/$basearch/os
repo --name="moje" --baseurl=http://$BASESERVER/fedoralinux/$releasever/$basearch/moje  (several times)
%include http://$BASESERVER/$releasever/$basearch/_must-be     (several times)

(i.e., also substitute base repo server (MYSERVER here) to $BASESERVER in following 'repo' and '%include' keywords. Is would be usefull, when want install from several servers - then isn't necessary to manually change several URLs, change in base repo  would be sufficient)

Version-Release number of selected component (if applicable):
anaconda from F20

Comment 1 Fedora End Of Life 2015-05-29 12:37:02 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

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 20 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.

Comment 2 Fedora End Of Life 2015-06-29 22:02:07 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.

Note You need to log in before you can comment on or make changes to this bug.