SCIENTIFIC-LINUX-USERS Archives

March 2011

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Tim Edwards <[log in to unmask]>
Reply To:
Tim Edwards <[log in to unmask]>
Date:
Fri, 11 Mar 2011 10:15:19 +0100
Content-Type:
text/plain
Parts/Attachments:
text/plain (34 lines)
On 11/03/11 10:05, Andreas Petzold wrote:
> 	Hi,
> 
> in SL5 I replaced the stock yum repository files and /etc/yum.conf with files 
> customized for our site (local repo mirrors, special excludes etc.) with an 
> RPM with the following properties:
> 
> Requires:       redhat-release >=  %{version}
> Provides:       yum-conf
> Provides:       epel-release-5
> Obsoletes:      yum-conf
> Obsoletes:      yum-conf-epel
> Obsoletes:      epel-release
> 
> With this setup we were able to prevent updates from SL from clobbering our 
> repo setup. This worked fine, since the yum-conf package owns /etc/yum.conf on 
> SL5.
> 
> On SL6 however, yum.conf is owned by the yum package. It doesn't make sense 
> for us to rebuild that just to insert our own yum.conf. Of course, we will 
> have to change a few things to accomodate the new sl-release rpm, but that's 
> fine.
> 
> Any ideas?
> 
> 	Cheers,
> 
> 		Andreas

You're not the only one, I found this extremely irritating as we use
puppet to manage yum config.

Tim

ATOM RSS1 RSS2