Re: [Spacewalk-devel] Spacewalk client yum repo
On Thu, 19 Nov 2009 14:40:18 +0100 Jan Pazdziora wrote: > On Thu, Nov 19, 2009 at 02:13:08PM +0100, Jan Blazek wrote: > > > > I have an idea how to do this. If we don't want to split koji tags > > (which I think would be an overhead) we need to specify somewhere > > the lists of packages which would go to which repository. I'd > > prefer to use comps files as these lists. We take a similar > > approach for Satellite where there are two separate comps files for > > Satellite and EmbededDB. > > > > Next step would be to force mash to take into account only those > > packages specified in comps. This would need to patch mash to add > > this feature. > > > > How do you like this idea? > > While it would certainly be interesting to have this feature, patching > the mash, getting it upstream, etc. seems like bringing unnecessary > delay. Can you use the same mash config which is used now for the > Spacewalk server repo, have that setup, and only then start working on > patching mash to support comps, and once we get the new mash in EPEL > or whatever is running on koji.rhndev.redhat.com, convert the current > config to comps? > > I definitely prefer having the yum repo available today without comps > over having it in two weeks with comps. > > Thank you, > OK. I'll work on a workaround for now and then take a look on patching mash. -- Jan Blazek Release Engineering, Red Hat ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
Re: [Spacewalk-devel] Spacewalk client yum repo
On Thu, Nov 19, 2009 at 02:13:08PM +0100, Jan Blazek wrote: > > I have an idea how to do this. If we don't want to split koji tags > (which I think would be an overhead) we need to specify somewhere the > lists of packages which would go to which repository. I'd prefer to use > comps files as these lists. We take a similar approach for Satellite > where there are two separate comps files for Satellite and EmbededDB. > > Next step would be to force mash to take into account only those > packages specified in comps. This would need to patch mash to add this > feature. > > How do you like this idea? While it would certainly be interesting to have this feature, patching the mash, getting it upstream, etc. seems like bringing unnecessary delay. Can you use the same mash config which is used now for the Spacewalk server repo, have that setup, and only then start working on patching mash to support comps, and once we get the new mash in EPEL or whatever is running on koji.rhndev.redhat.com, convert the current config to comps? I definitely prefer having the yum repo available today without comps over having it in two weeks with comps. Thank you, -- Jan Pazdziora Senior Software Engineer, Satellite Engineering, Red Hat ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
Re: [Spacewalk-devel] Spacewalk client yum repo
On Wed, 18 Nov 2009 14:47:23 +0100 Jan Pazdziora wrote: > On Mon, Sep 07, 2009 at 09:46:07AM +0200, Miroslav Suchý wrote: > > Please create Spacewalk client yum repo in koji.rhndev.redhat.com and > move the following packages from the Spacewalk server yum repo to it: > > > rhcfg* > > rhn-custom-info > > osad > > rhn-applet-actions > > rhn-custom-info > > rhn-kickstart* > > rhn-virtualization* > > spacewalk-koan > > rhnlib > > rhnmd > > rhnsd > > rhn-check > > rhn-setup > > yum-rhn-plugin > > koan > > spacewalk-certs-tools > > spacewalk-koan > > Thank you, Hi, I have an idea how to do this. If we don't want to split koji tags (which I think would be an overhead) we need to specify somewhere the lists of packages which would go to which repository. I'd prefer to use comps files as these lists. We take a similar approach for Satellite where there are two separate comps files for Satellite and EmbededDB. Next step would be to force mash to take into account only those packages specified in comps. This would need to patch mash to add this feature. How do you like this idea? Another question is where to store the comps files? I'd prefer to use http://cvs.devel.redhat.com/cgi-bin/cvsweb.cgi/comps/?cvsroot=RH-Devel for consistency with another products. Thanks for any comments. Jan -- Jan Blazek Release Engineering, Red Hat ___ Spacewalk-devel mailing list Spacewalk-devel@redhat.com https://www.redhat.com/mailman/listinfo/spacewalk-devel
