+1 for the script +10000 for including it in Spacewalk My only comment is that the RHEL to local channel mappings also be in the config file. This is where a standard for RHEL channels in spacewalk would be good. Generally I just remove the 'rh' from the channel label. So 'rhel-x86_64-server-5' becomes 'el-x86_64-server-5'. An exception is 'rhn-tools-rhel-x86_64-server-5' which I change to 'sw-tools-rhel-x86_64-server-5'. Its a bit annoying that we have to do this...
CC 2010/3/18 Andy Speagle <[email protected]>: > Hi Team, > > I've been piddling with this script for a while now. I've put some > finer touches on it and I'm wondering if it can be considered for > inclusion with the other community contributed scripts. > > This recent version (0.5) includes code from Colin Coe (thanks!) which > adds support for HTTP proxies. Additionally I've moved server, user and > password config information to a config file. This has the side effect > of significantly changing the command-line options, so care needs to be > taken if a user upgrades to this version. > > Basically, this script is responsible for connecting to RHN via ye olde > API, exporting errata and importing them into Spacewalk. It's written > in Python and seems to do the trick well enough. It's self-commented > within and SHOULD be easy enough for folks to follow. > > I've attached the script for review and inclusion. > > Thanks, > -- > Andy Speagle > > "THE Student" - UCATS > Wichita State University > > O: 316.978.3869 > C: 316.617.2431 > > > _______________________________________________ > Spacewalk-devel mailing list > [email protected] > https://www.redhat.com/mailman/listinfo/spacewalk-devel > -- RHCE#805007969328369 _______________________________________________ Spacewalk-devel mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-devel
