Description of problem: the system-config-kickstart gui fails to launch from either the gnome launcher or the command line Version-Release number of selected component (if applicable): 2.9.3-2 How reproducible: every time Steps to Reproduce: 1.install Fedora 23 x86_64 on generic platform 2.install system-config-kickstart 3.from the gnome menu search for kickstart and click the icon / run system-config-kickstart from the command line Actual results: no gui is launched / error is reported from the command line Traceback (most recent call last): File "/usr/bin/system-config-kickstart", line 88, in <module> import kickstartGui File "/usr/share/system-config-kickstart/kickstartGui.py", line 29, in <module> import basic File "/usr/share/system-config-kickstart/basic.py", line 39, in <module> from pykickstart.constants import * ImportError: No module named pykickstart.constants Expected results: system-config-kickstart gui is launched Additional info:
The Requires: are screwed up - you actually need the python-kickstart package installed. I'll make the change in the package here too. Please note that s-c-ks is kind of rotting at the moment. I really need to get to work on a much improved version. Thanks for the bug report.
Same issue and fix on Fedora 24.
Same issue and fix as well here on F24.
Thanks after installing python-kickstart package it's working fine
This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. 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 '23'. 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 23 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.
This issue has gotten worse on Fedora 25: $ sudo dnf install system-config-kickstart Last metadata expiration check: 0:03:11 ago on Tue Nov 29 14:21:25 2016. Error: nothing provides system-config-date needed by system-config-kickstart-2.9.3-3.fc24.noarch (try to add '--allowerasing' to command line to replace conflicting packages) (allowerasing doesn't change anything) The package now appears to be completely unusable.
(In reply to Jason Bradley Nance from comment #6) > This issue has gotten worse on Fedora 25: > > $ sudo dnf install system-config-kickstart > Last metadata expiration check: 0:03:11 ago on Tue Nov 29 14:21:25 2016. > Error: nothing provides system-config-date needed by > system-config-kickstart-2.9.3-3.fc24.noarch > (try to add '--allowerasing' to command line to replace conflicting packages) > > (allowerasing doesn't change anything) > > The package now appears to be completely unusable. Same issue I'm also on F25
Temporary workaround for Fedora 25: $ sudo dnf install https://kojipkgs.fedoraproject.org/packages/system-config-date/1.10.9/3.fc25/noarch/system-config-date-1.10.9-3.fc25.noarch.rpm python-kickstart system-config-kickstart
I am affected by this as well (Fedora 25 Workstation), and can confirm that Martin's workaround allowed me to install system-config-kickstart.
IMHO this bug should be closed as it was initially about a different issue in Fedora 23; bug #1406598 covers the broken dependency in Fedora 25.
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. 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 '25'. 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 25 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.
That's a different bug than the original, tracked in a different bug report. I'm going to close this one and consolidate the others. Thanks!