Red Hat Bugzilla – Bug 1007034
more friendly handling of answer file
Last modified: 2015-02-17 12:09:03 EST
At one point I had to kill the running packstack. When I re-ran it I thought it would pick up from where it left off, instead it started over. I should have re-run it with the previous answer file. In the test day instructions this is documented (and I suppose elsewhere) but I either didn't read it or remember it.
If packstack completes without being interrupted it will inform you about the presence of the answer file, but in this case it did not exit normally and hence there was no message concerning the answer file.
When packstack first starts up it should check for the presence of an answer file and if it exists offer to run using that file. There should also probably be a command line option to control this behaviour.
As it turns out I was never able to get a successfully installed system, I'm not sure if it because I ran packstack multiple time with and without different answer files or because of some other problem, but I think if I hadn't made the initial mistake of running packstack again without the prior answer file things might well have gone much better.
This is just a "don't shoot yourself in the foot" suggestion where the tool can help you do the right thing.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
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.