Re: yum not working ok on x86_64 ?

On Wed, 5 Jan 2005, Pasi Pirhonen wrote:

> On Tue, Jan 04, 2005 at 04:29:46PM -0500, David L. Parsley wrote:
> > On Tue, 2005-01-04 at 12:30, [email protected] wrote:
> > 
> > The 'Vendor' tag for wget is 'Pasi Pirhonen builds' != 'Tao Linux'
> > (Vendor for tao-release).  So, as far as 'protectbase' is concerned,
> > that package came from a 3rd-party repo.  Unfortunately, Pasi used
> > several different 'Vendor' strings while building, so regardless of the
> > the 'Vendor' used for tao-release, there are going to be packages that
> > aren't 'protected' by the patch.
> > 
> 
> Yeah. I didn't know that vendor would make any value in future, so
> there might be still many different vendor tags on x86-64. That
> protectbase-stuff apllies so only to ia32. David made it and it does
> aplly only on stuff David has compiled.
> 
> I've since used the vendor 'Tao Linux' tho, but that doesn't make
> initial stuff magically change, so protectbase is out of support on
> anything else than ia32.
> 
> If i would have thought something like that, i'd make it use 'source
> patch of the RPM' ie. repo it's coming from. I don't know if such info
> could be calculated from the info available, but that would have made
> it 'if it's from this URL, it's BASE'.
> 
> contrib etc. does anyway have different repo tags in yum.conf, so diff
> paths then.
> 
> But it's tool late for that too .....

Maybe there ought to be different protectbase methods available, like 
vendor, dist, packager, gpg or even a combination or list of each.

But given the fact that upstream does not agree with the patch, I can 
surely understand that no more effort is put in such functionality :/

My hope goes out to a smartpm for RHEL3, which already has such 
functionality as part of the tool.

--   dag wieers,  [email protected],  http://dag.wieers.com/   --
[all I want is a warm bed and a kind word and unlimited power]