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

[Pierre Casenove]

Hello,
I still have one problem.
I want to use options --rewritepackagereleasefrom=el5
--rewritepackagereleaseto=el5.centos for centos errata sync.
When I try to sync errata RHSA-2013:0128, I get the following error:

checking if RHSA-2013:0128 exists on the destination host
Geting details for COS5X64SA-2013:0128
getting RHSA-2013:0128 from the source
Geting details for RHSA-2013:0128
getting details for package ricci
Can't use string ("bugzilla_url") as a HASH ref while "strict refs" in use
at /usr/local/sbin/eva-direct-errata-sync.pl line 492.

Thanks in advance,

Pierre


2013/1/10 Paul Robert Marino <prmarino1 at gmail.com>

> On Thu, Jan 10, 2013 at 1:48 AM, Pierre Casenove <pcasenove at gmail.com>
> wrote:
> > Hello Paul.
> > First, thanks a lot for this hint, now it works... but with a little
> twist:
> > as I'm setting environment variables, I use proxy to connect to RHN AND
> to
> > my local spacewalk server...
> > How could I unset PROXY variables for Spacewalk, and not for RHN?
> I haven't looked into it yet but I think this is a limitation LWP
> inherits from one of it many dependencies. It will take time for me to
> investigate it there is a workaround but your solution using HTTP for
> the local connection and HTTPS to rhn may be the only practical
> workaround right now.
> > By the way, great script, it works like a charm (except this proxy
> setting!)
> >
> > I still have three questions:
> > - For Centos, I have a base channel named Centos 6 Base and a child
> channel
> > for the updates. Can your script find packages in both?
> yes it can
> > - For RHEL channels: Do i have to call the script twice to get erratas
> from
> > RHEL 6 Server channels and RHEL 6 Optionnal channel, or does your script
> > automatically find everything when calling it and specifying the rhel 6
> > server channel?
> No it will scan all channels on the source you have access to under
> the base channel
>
> > - I'm planning to call the script once a day, with the
> "startfromprevious"
> > option. Imagine the following case, which happens quite frequently:
> RedHat
> > publishes a RHSA with the associated packages on day 1. The next night,
> I'm
> > going the download the package and create the errata for RHEL. But  from
> > centos, it happens that the packages are not yet available (they are
> > published a few days after). Your script will skip the errata creation
> for
> > centos... but even when the package will be available, the errata will
> never
> > be re-created, as it starts with the last launch date. How can I address
> > this?
> I usually use startfromprevious with month with scientific linux and
> year with Centos because it doesn't take that much longer and resolves
> this for both distros
>
> >
> > Thanks in advance,
> >
> > Pierre
> >
> >
> >
> > 2013/1/4 Paul Robert Marino <prmarino1 at gmail.com>
> >>
> >> perl-Crypt-SSLeay
> >
> >
> >
> >
> > _______________________________________________
> > Spacewalk-list mailing list
> > Spacewalk-list at redhat.com
> > https://www.redhat.com/mailman/listinfo/spacewalk-list
>
> _______________________________________________
> Spacewalk-list mailing list
> Spacewalk-list at redhat.com
> https://www.redhat.com/mailman/listinfo/spacewalk-list
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/spacewalk-list/attachments/20130114/eb983bdd/attachment.htm>