On Fri, Dec 14, 2007 at 01:38:48PM -0800, Ralph Shumaker wrote: > Chris Grau wrote: >> If I had some file in my directory, let's say >> packages.i.found.which.match.g++, and I ran an unescaped yum command: >> >> $ yum provides *g++ >> >> The command would then actually be, >> >> $ yum provides packages.i.found.which.match.g++ >> >> Which probably isn't what I want. >> > > This probably explains why after some usage, I start to have problems > with: yum update tre* tra* sel* per* ...
Yes.
> ?Would this be a simple matter of doing this: yum update 'tre* tra*
> sel* per* ...'
Close. You'll want to quote each individually.
$ yum update 'tre*' "tra*" sel\* per'*'
Otherwise, you're giving the whole string as a single argument and yum
will attempt to match a package to the glob 'tre* tra* sel* per*', which
I suppose could match to something, if you're (un)lucky. I deliberately
used different methods of escaping the glob wildcard, just to
demonstrate that there's more than one way to do it.
> It seems that over time, yum starts accumulating files that apparently
> start giving me false matches and then yum bombs. When this starts to
> happen, I always do a 'yum clean all'. I figure I should probably do
> that once in a while anyway, right?
Recent versions of yum automatically perform a clean on the packages and
headers at the end of execution, though I believe this can be disabled.
I tend to avoid a 'clean all' unless I have somehow screwed up yum's
metadata (which I did just last week on a RHEL box, actually...).
pgpz8qHToUqtq.pgp
Description: PGP signature
-- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
