[Spacewalk-list] Switching from rhn-clone-errata to eva-direct-errata-sync

[Paul Robert Marino]

On Tue, Dec 18, 2012 at 2:10 AM, Pierre Casenove <pcasenove at gmail.com> wrote:
> Hello,
> I'm currently using rhn-clone-errate to sync RHN errata.
> But we've recently added centos distribution, so I need to create errata for
> centos as well.
> I've been looking at eva-direct-errata, which seems really interesting but I
> don't understand how it works.
> - How can I configure a proxy to connect to RHN?
Unfortunately I never put that in because I wasn't sure how to do that
with the RPC module I'm using but I may add it in the future

> - I have the following channels configured:
> 1 - CentOS 5 Base with Cent0S 5 Updates as child channel
> 2 - rhel 5 Server
> 3 - RHEL 5 Workstation
> 4 - CentOS 6 Base with CentOS 6 Updates as child channel
> 5 - RHEL 6 Server with RHEL 6 optionnal as child channel
> As I understand the script, I need to launch it 5 times, changing source
> channels, dest channels and "rewirtepackagereleasefrom/to". Is it correct?

Yes this is due to a bug in the spacewalk API,s
https://bugzilla.redhat.com/show_bug.cgi?id=834569
If the bug ever gets fixed I will release a version that can do it in
one round. I've already written a version in my non public git repo
but due to the spacewalk bug im not releasing it to the public yet

> - Is it possible to put some configuration directives (such as user/password
> information) in a config file?
No not yet but you can use environment variables they are documented
in the pod documentation
use perldoc /path/to/script or pod2txt, pod2man. pod2... to read the
documentation
I highly suggest using the environment variables for now so your
passwords don't show up in ps

>
> Thanks a lot for your help,
>
> Pierre
>
> _______________________________________________
> Spacewalk-list mailing list
> Spacewalk-list at redhat.com
> https://www.redhat.com/mailman/listinfo/spacewalk-list