Overlap policy v20120615

Jan-Frode Myklebust janfrode at tanso.net
Fri Jun 15 22:04:56 UTC 2012


On Fri, Jun 15, 2012 at 03:29:49PM -0600, Kevin Fenzi wrote:
> 
> How do you handle issues between add-ons? 

I've never seen any.

> Even the base ones I see conflicting packages... do you have RHEL folks
> handle that and enable them as you like, or is there some kind of
> "Please dont enable foo and bar because they conflict" you look at?
> 
> > RHN-channels we currently use for RHEL6 is:
> > 
> > 	updates		
> > 	supplementary
> > 	optional
> > 	rhn-tools	-- some rhn client packages
> > 	rhevm-3		-- Red Hat Enterprise virtualization
> > 	jbappplatform-5 -- jboss packages needed for RHEV manager
> > 	sfs		-- xfs
> 
> I don't know off hand what is in those. 

Updated above.. 

> > On the upside, the new policy seems to allow including the whole
> > sfs-channel in epel, as it's only xfsdump, xfsprogs, xfsprogs-devel
> > and xfsprogs-qa-devel. ..
> 
> Does that include the kernel module as well? 

xfs.ko is included in the standard kernel package.

	$ rpm -qf /lib/modules/$(uname -r)/kernel/fs/xfs/xfs.ko
	kernel-2.6.32-220.7.1.el6.x86_64


  -jf




More information about the epel-devel-list mailing list