Bug 1149029 - no way to get location of kickstart file in %post% or %pre% scripts
Summary: no way to get location of kickstart file in %post% or %pre% scripts
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: pykickstart
Version: 20
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Chris Lumens
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-10-03 00:54 UTC by Be
Modified: 2015-06-29 22:46 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-06-29 22:46:49 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
patch for parser.py in pykickstart (1.13 KB, patch)
2014-10-03 10:26 UTC, Be
no flags Details | Diff
patch for creator.py in python-imgcreate (286 bytes, patch)
2014-10-03 10:27 UTC, Be
no flags Details | Diff

Description Be 2014-10-03 00:54:40 UTC
Description of problem:
There is no way to get the location of the kickstart file passed to livecd-creator in the %post% or %pre% scripts. The scripts are run from livecd-creator's cache directory, which may not have any relationship to the path of the kickstart file. It would be helpful if an environment variable, such as KICSTART_FILE, that identified the location of the kickstart file was passed to the scripts.

The most obvious use case for this would be to copy the kickstart file into the ISO image being created by livecd-creator. Another use case would be distributing an archive including a kickstart file and other files to be copied into an ISO image to build an ISO image of a Fedora Remix with livecd-creator. Similarly, this would allow Fedora Remix (and official Fedora Spin) live CD ISO images to be fully reproducible with livecd-creator by including the kickstart file in the ISO image and copying customized files from the old ISO image (by locating them relative to the kickstart file) into the new one.

Version-Release number of selected component (if applicable):
20

How reproducible:
always

Comment 1 Be 2014-10-03 10:26:19 UTC
Created attachment 943689 [details]
patch for parser.py in pykickstart

for /usr/lib/python2.7/site-packages/pykickstart/parser.py

Comment 2 Be 2014-10-03 10:27:44 UTC
Created attachment 943691 [details]
patch for creator.py in python-imgcreate

for /usr/lib/python2.7/site-packages/imgcreate/creator.py

Comment 3 Fedora End Of Life 2015-05-29 13:01:06 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 4 Fedora End Of Life 2015-06-29 22:46:49 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
bug.

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.