I am trying things like "yum provides alsamixer" on centox 5.2 i386 and x86_64 also "yum provides vi" "yum provides gvimdiff" "yum provides dumpiso" "yum provides uname"
All of these return "no matches found"
is something broke???
These are just examples. I was trying to do "yum provides xf86Modes.h" it returns no matches also.
Jerry
On Wednesday, August 27, 2008 at 8:49 PM, Jerry Geis wrote:
I am trying things like "yum provides alsamixer" on centox 5.2 i386 and x86_64 also "yum provides vi" "yum provides gvimdiff" "yum provides dumpiso" "yum provides uname"
All of these return "no matches found"
is something broke???
Include the path:
# yum provides uname No Matches found
# which uname /bin/uname
# yum provides /bin/uname coreutils.x86_64 : The GNU core utilities...
Steve
Include the path:
Doesn't that defeat the purpose? My favourite use of the "whatprovides" feature of yum is could find things that aren't on my system. I'd prefer not to go on a wild path chase. :)
This looks like a bug to me.
On CentOS 5.1 (yum 3.0.5):
# yum provides uname | awk '/i386|noarch/ {print $1}' uucp.i386 man-pages-de.noarch man-pages-de.noarch bash.i386 kdevelop.i386 kdevelop.i386 kdevelop.i386 man-pages-ja.noarch man-pages-ja.noarch man-pages-ko.noarch man-pages-ko.noarch coreutils.i386 coreutils.i386 python-tools.i386 man-pages-fr.noarch man-pages-es.noarch kdewebdev.i386 man-pages-ru.noarch man-pages-cs.noarch epic.i386 man-pages.noarch man-pages.noarch man-pages.noarch man-pages-it.noarch inn.i386 man-pages-pl.noarch man-pages-pl.noarch man-pages.noarch bash.i386 coreutils.i386
on CentOS 5.2 (yum 3.2.8), No Matches found
On Thu, 2008-08-28 at 13:50 +1200, Spiro Harvey, Knossos Networks Ltd wrote:
Include the path:
Doesn't that defeat the purpose? My favourite use of the "whatprovides" feature of yum is could find things that aren't on my system. I'd prefer not to go on a wild path chase. :)
This looks like a bug to me.
On CentOS 5.1 (yum 3.0.5):
# yum provides uname | awk '/i386|noarch/ {print $1}' uucp.i386 ... coreutils.i386
on CentOS 5.2 (yum 3.2.8), No Matches found
That's not a bug, that's a “feature”. :-D
Historically, “yum provides” dumped the kitchen sink on you and you had to wade through the debris to find what you wanted.
Looks like the new “feature” went a bit too far the other way.
Steve
Spiro Harvey, Knossos Networks Ltd wrote:
Steve Tindall wrote:
Looks like the new “feature� went a bit too far the other way.
Roger that.
From too much to not enough. We must bring balance back to the force.
Wildcards do good balancing >:)
yum provides "*uucp"
Cheers,
Ralph
Jerry Geis wrote:
I am trying things like "yum provides alsamixer" on centox 5.2 i386 and x86_64 also "yum provides vi" "yum provides gvimdiff" "yum provides dumpiso" "yum provides uname"
All of these return "no matches found"
is something broke???
These are just examples. I was trying to do "yum provides xf86Modes.h" it returns no matches also.
Jerry _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
For files try
yum provides '*/vi' etc...
I think this is new behavior for yum
Tony Schreiner
Tony Schreiner wrote:
Jerry Geis wrote:
I am trying things like "yum provides alsamixer" on centox 5.2 i386 and x86_64 also "yum provides vi" "yum provides gvimdiff" "yum provides dumpiso" "yum provides uname"
All of these return "no matches found"
is something broke???
These are just examples. I was trying to do "yum provides xf86Modes.h" it returns no matches also.
Jerry _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
For files try
yum provides '*/vi' etc...
I think this is new behavior for yum
Tony Schreiner _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
I recently discovered this "feature" in a thread on fedora-list[1].
I did mention that maybe the yum manpage ought to be updated to inform the user, as I always wondered why it never worked for me until I saw the post. Although I knew that globs could be used with certain yum commands, I wasn't aware you needed to use them with this one.
[1] http://www.redhat.com/archives/rhl-list/2008-August/msg00884.html
-
Jerry Geis -
Ralph Angenendt -
S.Tindall -
Spiro Harvey, Knossos Networks Ltd -
Steve Tindall
-
Stewart Williams -
Tony Schreiner