[Spacewalk-list] yet another errata clone script

[Velayutham, Prakash]

+1

Prakash

On Oct 15, 2012, at 9:30 AM, Hamilton, James wrote:

> Hi Franky,
> I'd be interested in trying this out.  
> Thanks
> Jim
> 
> 
> On Mon, 2012-10-15 at 15:17 +0200, Franky Van Liedekerke wrote:
>> Yet another errata clone script ... for CentOS and RedHat
>> 
>> Hi,
>> 
>> based on some existing scripts (eva_direct_sync.pl and
>> errata-import.pl), I've
>> created a new script. Reason for the rework:
>> - we have redhat and centos packages in spacewalk, both can have the
>> same
>>  package names, which would result in redhat packages being pushed in
>> centos
>>  channels because of the errata create (and thus everything fails)
>> - the XML file of errata-import.pl is ok, but updated by one person
>> and only
>>  for security errata (I think)
>> - errata-import.pl had good code, but no RHN integration, and is too
>> easy
>>  for missing packages (if 1 package from the errata is there, the
>> errata is
>>  created, while other packages might be missing)
>> - always different scripts were created/used for redhat and centos
>> errata
>> 
>> So, my script (well, combo of shell and perl) was born:
>> For CentOS:
>> - first some shell calls to get the latest announces from the centos
>> archive
>>  (but not by scraping the announces list, but getting digests, much
>> less
>>  traffic then)
>>  You can change the number of announces anyway you want by changing
>> the
>>  wget command to your liking
>> - then the perl script comes along, parsing the digest files and
>> looking in 1
>>  channel (yes, one) for package availability and creating the errata
>> there.
>>  It has optional integration with RHN for notes, description, topic
>> info, and
>>  CVE's and/or can use the OVAL file like the errata-import.pl script
>> does.
>>  The created errata gets a suffix based on the OS version and
>> architecture
>>  (e.g. ":C5-64" or "C6-32"), because the same errata can exist for
>> multiple
>>  OS versions and architectures (and creating the errata for more than
>> one
>>  base channel would result in packages being copied which is a mess
>> again).
>>  Also a proxy can be defined for spacewalk and or RHN servers
>> Or, for RedHat:
>> - log in to RHN, get the errata for the specified channel
>>  (possibility to define the date range)
>> - then follow the same logic as for CentOS
>> 
>> 
>> 
>> If anybody is interested, I'll put it on github or so ...
>> 
>> 
>> 
>> Franky
>> 
>> 
> 
> 
> _______________________________________________
> Spacewalk-list mailing list
> Spacewalk-list at redhat.com
> https://www.redhat.com/mailman/listinfo/spacewalk-list