Description of problem: If we add a rpm file (which is not in standard repository) we can see the informatons about this file when using «yum search» Is it normal ? I thought that «yum search» give information in repositories and not in repositories AND local rpm files. One or two weeks/monthes after the installation we could think that the displayed informations are standard repositories informations. If it is the normal feature how can we avoid the local rpm files ? There is no detail about this feature in the documentation. How can have a special tag for each local file.
yum search looks in both the rpmdb and the repositories currently.
Would it be possible to highlight a bit more when the package has not been installed from a repository ?
Have you looked at what "yum list" shows you?
yum list shows me the external rpm as installed like other rpm from repositories Example: mediainfo-gui.x86_64 0.7.20-2.1 installed There is no difference between an external rpm (installed manually) and an official rpm (from repositories). yum resolvedep mediainfo-gui Loaded plugins: refresh-packagekit No Package Found for mediainfo-gui yum deplist mediainfo-gui Loaded plugins: refresh-packagekit Finding dependencies: «No display» rpm -q --whatprovides mediainfo-gui mediainfo-gui-0.7.20-2.1.x86_64 rpm -q --whatrequires mediainfo-gui aucun paquetage ne requiert mediainfo-gui -------------------------------------------------------------- With libmediainfo which is needed by mediainfo-gui yum resolvedep libmediainfo0 Loaded plugins: refresh-packagekit No Package Found for libmediainfo0 yum deplist libmediainfo0 Loaded plugins: refresh-packagekit Finding dependencies: «No display» rpm -q --whatrequires libmediainfo0 mediainfo-gui-0.7.20-2.1.x86_64 rpm -q --whatprovides libmediainfo0 libmediainfo0-0.7.20-4.1.x86_64
Ok it looks like an older version of yum was used to install the pkgs. Newer version will produce information like: # yum list installed yum\* and-httpd\* Loaded plugins: aliases, noop, presto, security Installed Packages and-httpd-tools.x86_64 0.99.11-1 @/and-httpd-tools-0.99.11-1.x86_64 yum.noarch 3.2.24-9.fc12 @rawhide yum-metadata-parser.x86_64 1.1.2-12.fc11 @fedora yum-plugin-aliases.noarch 1.1.22-1.fc11 @updates yum-plugin-security.noarch 1.1.22-1.fc11 @updates yum-presto.noarch 0.5.0-1.fc11 @updates yum-utils.noarch 1.1.22-1.fc11 @updates yumex.noarch 2.0.5-6.fc11 @fedora ...where and-httpd-tools was installed from an rpm file. Also see "yumdb" for more info. Is that good?
Another option, if you still want this functionality, might be to have a search option for repoquery.
yum list installed yum\* and-httpd\* yum.noarch 3.2.24-2.fc11 @updates yum-NetworkManager-dispatcher.noarch 1.1.22-1.fc11 @updates yum-metadata-parser.x86_64 1.1.2-12.fc11 installed yum-utils.noarch 1.1.22-1.fc11 installed
yum list installed mediainfo-gui\* libmediainfo0\* libmediainfo0.x86_64 0.7.20-4.1 installed mediainfo-gui.x86_64 0.7.20-2.1 installed mediainfo-gui and libmediainfo0 was installed from an rpm file.
(In reply to comment #8) > yum list installed mediainfo-gui\* libmediainfo0\* > libmediainfo0.x86_64 0.7.20-4.1 installed > mediainfo-gui.x86_64 0.7.20-2.1 installed > > mediainfo-gui and libmediainfo0 was installed from an rpm file. As James said, it is because at the point in time where the rpm files was installed, the current yum version did not have the features to store information about the source of the installation. Another cause could be that you was using rpm to install the package, instead of yum localinstall <rpm file> So packages installed with current versions of yum, will store information about the source of the installation and show it in yum list cmds as in #5.
Those file have been installed last week and last release of yum was installed in October the first. I erased the installation with three rpm -e rpm -e mediainfo-gui rpm -e libmediainfo0 rpm -e libzen0 in order to respect the dependencies. If I try to install with «yum localinstall» the first file yum localinstall libzen0-0.4.3-1.x86_64.Fedora_11.rpm Public key for libzen0-0.4.3-1.x86_64.Fedora_11.rpm is not installed yum --nogpgcheck localinstall libzen0-0.4.3-1.x86_64.Fedora_11.rpm It work's fine but yum search libzen libzen0.x86_64 : Shared library for libmediainfo and medianfo-* yum list installed libzen0 libzen0.x86_64 0.4.3-3.1 @/libzen0-0.4.3-1.x86_64.Fedora_11 We have no information about external rpm with «yum search» and it was my first question.
This message is a reminder that Fedora 11 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 11. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '11'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 11's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 11 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
I think the answer here is 'no' not from within yum the command line tool. If you only want to search the repos you can do something like that with repoquery or another tool using the yum bindings - but I don't really see the merit in searching only the repos. Maybe I'm misunderstanding the need/demand for it, though, so please feel free to expand on it. closing this deferred, pending more explanation. thank you
Also note that as of F-13 you can do: yum --installroot=/tmp/nothing --releasever=13 search blah ...and you will have an "empty rpmdb".