The master himself! Thanks for the quick reply. Since it's COTS, I cannot provide the RPM. The vendor appears to offer an RPM as an afterthought; their principal market is Windows. I've patched our createrepo to relax this behavior with a command line option. Would this be useful to others? Jack -----Original Message----- From: yum-bounces@xxxxxxxxxxxxxxxxx [mailto:yum-bounces@xxxxxxxxxxxxxxxxx] On Behalf Of Seth Vidal Sent: Thursday, February 25, 2010 3:15 PM To: Yellowdog Updater, Modified Subject: Re: createrep question On Thu, 25 Feb 2010, Kidwell,jr, Jack wrote: > > Hello, > > > > After several googles, I turn to you. Forgive my poor google skills if this is a FAQ. > > > > I have a COTS RPM that is invisible to yum, and I think the cause is > the arch property. While the arch tag is properly set in the COTS RPM, createrepo always chooses “src”, ignoring the vendor’s arch tag. > > > > Looking in createrepo/ dumpMetadata.py I see this: > > > > > > def arch(self): > > if self.tagByName('sourcepackage') == 1 or not self.tagByName('sourcerpm'): > > return 'src' > > else: > > return self.tagByName('arch') > > > > > > The COTS RPM does not set tag SOURCERPM, so createrepo returns ‘src’. > > > > What’s the rationalization for this rule? I need to make a case with the vendor. B/c that's how you can detect a sourcerpm. How is the pkg being made such that it does not have sourcerpm tag? Can you provide a link to this pkg? -sv _______________________________________________ Yum mailing list Yum@xxxxxxxxxxxxxxxxx http://lists.baseurl.org/mailman/listinfo/yum
