Fedora Account System
Red Hat Associate
Red Hat Customer
package: snake-server - 0.9-0.5git.el5.noarch from epel-testing unresolved deps: pykickstart >= 0:1.1 pykickstart-0.43 seems to be the one available in RHEL5. Can this version of snake be made to work with that? Or could an update be requested of the package in RHEL5?
The snake base package (client) is intended for any distro release ... while the snake-server package requires pykickstart >= 1.1. To resolve the deps I can: 1. Drop the version requirement and add a note into the README that execution will require an updated pykickstart 2. We backport the pykickstart changes into RHEL5 3. We backport the pykickstart changes into EPEL5 (I think this goes against EPEL policy) 4. Special case the .spec file so that only the base snake package is built on EPEL4 and EPEL5. The least messy approach seems to be #1. #4 seems ideal but may not be appropriate in a spec file? Any thoughts?
1 violates the rule of least surprise. 4 might be an option until 2 is accomplished.
clumens: What are your thoughts about option#2 ... I imagine that would be rather difficult given it's a big version bump.
We can't put the latest pykickstart in RHEL5 without making significant changes to anaconda and system-config-kickstart. I'd rather not do that.
Thanks Chris! option#4 it is...
Fixed in snake-0.10-0.4git.el5. The snake-server sub-package will no longer be built. Detail for Job ID 38066 (snake): -------------------------------------------------------------------------------- Source: snake-0_10-0_4git_el5 Target: fedora-5-epel Submitter: jlaska Status: needsign/ Archjobs: noarch: ppc2.fedora.redhat.com done/done
38066 (snake): Build on target fedora-5-epel succeeded. Build logs may be found at http://buildsys.fedoraproject.org/logs/fedora-5-epel/38066-snake-0.10-0.4git.el5/
This build was just pushed out... shall we go ahead and close this now? Thanks for the prompt attention here.
This issue has been fixed in snake >= snake-0.10-0.4git