Need help with Yum Repoquery

 
Thread Tools Search this Thread
Special Forums UNIX and Linux Applications Need help with Yum Repoquery
# 1  
Old 07-05-2012
Need help with Yum Repoquery

I was trying to get some dependency checks done in one of my task.

I was running repoquery for one of the package in my repository, output is

repoquery --repoid=gsix-usb --tree-requires App-A-1.1.1-1.i386

App-A-1.1.1-1.i386 [cmd line]
\_ Core-2.2.2-1.i386 [2: Core < 2.1.1-1, Core >= 1.1.1-1]

I was checking for dependencies of App-A-1.1.1-1 which gave me this output. But --tree-requires is giving me wrong output. As per my dependency check App-A is dependent on Core <2.1.1-1 and Core >=1.1.1-1, but it is giving me Core-2.2.2-1, which is not < 2.1.1-1.


Could any one please help me out in this, how to get through this defect.

Thanks in advance.
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. UNIX for Beginners Questions & Answers

Installation of virt-manager while yum update and yum install rhvm does not work

I have downloaded RHEV-H 4.2 Red Hat Virtualization - Red Hat Customer Portal (RHVirtualization 4.2 Host and Manager iso). I uploaded the image and installed on an HP G9 server baremetal. I found I dont have a WAN/net connectivity later on HPG9 server. How can I still install virt-manager on... (1 Reply)
Discussion started by: Paras Pandey
1 Replies

2. Linux

Need help on YUM

HI, First I'll use yum check-update to check any updates. Q1: How can I know that how much space needed to update all packages listed by yum check-update command? Q2: How can I list kernel related packages? TIA (2 Replies)
Discussion started by: Sumanthsv
2 Replies

3. UNIX and Linux Applications

yum provides help

Is there a reason why yum provide can't find libquazip? I did this. yum whatprovides */libquazip A quick google search told me it was in quazip and libquazip. RPM resource libquazip.so.1 (1 Reply)
Discussion started by: cokedude
1 Replies

4. Red Hat

Need help with Yum Repoquery

I was trying to get some dependency checks done in one of my task. I was running repoquery for one of the package in my repository, output is repoquery --repoid=gsix-usb --tree-requires App-A-1.1.1-1.i386 App-A-1.1.1-1.i386 \_ Core-2.2.2-1.i386 I was checking for... (1 Reply)
Discussion started by: sumantkukunooru
1 Replies

5. Red Hat

help with YUM

Hi All, Just installed new Redhat server. I am trying to do rhn_register. I get this error message. Fatal error: The SSL certificate failed verification. Any one ran into this error. Please let me know. I do have internet connection- ping www.google.com PING... (1 Reply)
Discussion started by: samnyc
1 Replies

6. Red Hat

Yum is unusable

How do I delete all of my repo information and start completely fresh? (8 Replies)
Discussion started by: cokedude
8 Replies

7. UNIX for Advanced & Expert Users

yum issue

Hi Guys, I am trying install mysql.i386 with yum... But unfortunately I am getting error as listed below: # yum install mysql.i386 Loaded plugins: fastestmirror Loading mirror speeds from cached hostfile Traceback (most recent call last): File "/usr/bin/yum", line 29, in ? ... (2 Replies)
Discussion started by: mahesh_raghu
2 Replies

8. Red Hat

yum problem

hi i am not able to do yum update in centos5 i was not able to use yum at all.i am getting an like this. #yum update Loaded plugins: fastestmirror Loading mirror speeds from cached hostfile Setting up Update Process No Packages marked for Update please help me what i have missed (6 Replies)
Discussion started by: praneel2k
6 Replies

9. UNIX for Dummies Questions & Answers

Centos commands: Yum Upgrade versus Yum update

Hi, I would like to know the difference between YUM UPDATE and YUM UPGRADE. The man pages say upgrade is same as update with the obsolete option. And by default it says the obsolete option is turned on, which would make them equivalent. Does not say what obsolete does. Can someone please... (3 Replies)
Discussion started by: mojoman
3 Replies

10. Red Hat

Yum Update

I am using Cent OS 5 i need to update proxy server address in yum, i don't know where to update and how exactly i need to specify the proxy address can anyone help me in the issue. (2 Replies)
Discussion started by: praneel2k
2 Replies
Login or Register to Ask a Question
repoquery(1)															      repoquery(1)

NAME
repoquery - query information from Yum repositories SYNOPSIS
repoquery [options] <item ...> repoquery -a [options] DESCRIPTION
repoquery is a program for querying information from YUM repositories similarly to rpm queries. GENERAL OPTIONS
--querytags List valid queryformat tags and exit.. -v, --version Report program version and exit. --repoid=<repo> Specify which repository to query. Using this option disables all repositories not explicitly enabled with --repoid option (can be used multiple times). By default repoquery uses whatever repositories are enabled in YUM configuration. --enablerepo=<repo> In addition to the default set, query the given additional repository, even if it is disabled in YUM configuration. Can be used multiple times. --disablerepo=<repo> Do not query the given repository, even if it is enabled in YUM configuration. Can be used multiple times. --repofrompath=<repoid>,<path/url> Specify a path or url to a repository (same path as in a baseurl) to add to the repositories for this query. This option can be used multiple times. If you want to view only the pkgs from this repository combine this with --repoid. The repoid for the repository is specified by <repoid>. --plugins Enable YUM plugin support. -q, --query For rpmquery compatibility, doesn't do anything. -h, --help Help; display a help message and then quit. --quiet Run quietly: no warnings printed to stderr. --verbose Produce verbose output. -C, --cache Tells repoquery to run entirely from YUM cache - does not download any metadata or update the cache. Queries in this mode can fail or give partial/incorrect results if the cache isn't fully populated beforehand with eg "yum makecache". --tempcache Create and use a private cache instead of the main YUM cache. This is used by default when run as non-root user. -c <config file>, --config=<config file> Use alternative config file (default is /etc/yum.conf). --releasever=version Pretend the current release version is the given string. This is very useful when combined with --installroot. You can also use --releasever=/ to take the releasever information from outside the installroot. Note that with the default upstream cachedir, of /var/cache/yum, using this option will corrupt your cache (and you can use $releasever in your cachedir configuration to stop this). --installroot=root Specifies an alternative installroot, relative to which all packages will be installed. Think of this like doing "chroot <root> yum" except using --installroot allows yum to work before the chroot is created. Note: You may also want to use the option --relea- sever=/ when creating the installroot as otherwise the $releasever value is taken from the rpmdb within the installroot (and thus. will be empty, before creation). --setopt=option=value Set any config option in yum config or repo files. For options in the global config just use: --setopt=option=value for repo options use: --setopt=repoid.option=value PACKAGE QUERY OPTIONS
-i, --info Show general information about package similarly to "rpm -qi" -l, --list List files in package. -R, --requires List package dependencies. --resolve When used with --requires, resolve capabilities to originating packages. --provides List capabilities package provides. --obsoletes List capabilities obsoleted by package. --conflicts List capabilities conflicting with package. --changelog List package changelog. --location Show a location where the package could be downloaded from. For example: wget `repoquery --location yum` -s, --source Show package source RPM name. --srpm Operate on corresponding source RPM. --groupmember PACKAGE List the repodata groups (yumgroups.xml) belongs to (if any). --nvr Use name-version-release output format (rpm query default) --nevra Use name-epoch:version-release.architecture output format (default) --envra Use epoch:name-version-release.architecture output format (easier to parse than nevra) --qf=FORMAT, --queryformat=FORMAT Specify custom output format for queries. You can add ":date", ":day" and ":isodate" to all the tags that are a time, and you can add ":k", ":m", ":g", ":t" and ":h" to sizes. You can also specify field width as in sprintf (Eg. %-20{name}) --output [text|ascii-tree|dot-tree] Output format which can be used with --requires/--whatrequires/--obsoletes/--conflicts. Default output is 'text'. --level [all|any int] In combination with --output ascii-tree|dot-tree this option specifies the number of level to print on the tree. Default level is 'all'. PACKAGE SELECTION OPTIONS
-a, --all Query all available packages (for rpmquery compatibility / shorthand for repoquery '*') --show-duplicates Query all versions of packages. -f, --file FILE Query package owning FILE. --whatobsoletes CAPABILITY Query all packages that obsolete CAPABILITY. --whatconflicts CAPABILITY Query all packages that conflict with CAPABILITY. --whatprovides CAPABILITY Query all packages that provide CAPABILITY. --whatrequires CAPABILITY Query all packages that require CAPABILITY. --alldeps When used with --whatrequires, look for non-explicit dependencies in addition to explicit ones (e.g. files and Provides in addition to package names). This is the default. --exactdeps When used with --whatrequires, search for dependencies only exactly as given. This is effectively the opposite of --alldeps. --recursive When used with --whatrequires, and --requires --resolve, query packages recursively. --archlist=ARCH1[,ARCH2...] Limit the query to packages of given architecture(s). Valid values are all architectures known to rpm/yum such as 'i386' and 'src' for source RPMS. Note that repoquery will now change yum's "arch" to the first value in the archlist. So "--archlist=i386,i686" will change yum's canonical arch to i386, but allow packages of i386 and i686. --pkgnarrow=WHAT Limit what packages are considered for the query. Valid values for WHAT are: installed, available, recent, updates, extras, all and repository (default). --installed Restrict query ONLY to installed pkgs - disables all repos and only acts on rpmdb. GROUP QUERY OPTIONS
-i, --info Show general information about group. -l, --list List packages belonging to (required by) group. --grouppkgs=WHAT Specify what type of packages are queried from groups. Valid values for WHAT are all, mandatory, default, optional. --requires List groups required by group. GROUP SELECTION OPTIONS
-a Query all available groups. -g, --group Query groups instead of packages. EXAMPLES
List all packages whose name contains 'perl': repoquery '*perl*' List all packages depending on openssl: repoquery --whatrequires openssl List all package names and the repository they come from, nicely formatted: repoquery -a --qf "%-20{repoid} %{name}" List name and summary of all available updates (if any), nicely formatted: repoquery -a --pkgnarrow=updates --qf "%{name}: %{summary} " List optional packages in base group: repoquery -g --grouppkgs=optional -l base List build requirements from 'anaconda' source rpm: repoquery --requires anaconda.src List packages which BuildRequire gail-devel repoquery --archlist=src --whatrequires gail-devel NB: This command will only work if you have repositories enabled which include srpms. MISC
Specifying package names A package can be referred to in all queries with any of the following: name name.arch name-ver name-ver-rel name-ver-rel.arch name-epoch:ver-rel.arch epoch:name-ver-rel.arch For example: repoquery -l kernel-2.4.1-10.i686 Additionally wildcards (shell-style globs) can be used. FILES
As repoquery uses YUM libraries for retrieving all the information, it relies on YUM configuration for its default values like which repos- itories to use. Consult YUM documentation for details: /etc/yum.conf /etc/yum/repos.d/ /var/cache/yum/ SEE ALSO
yum.conf (5) http://yum.baseurl.org/ AUTHORS
See the Authors file included with this program. BUGS
There are of course no bugs, but should you find any, you should first consult the FAQ section on http://yum.baseurl.org/wiki/Faq and if unsuccessful in finding a resolution contact the mailing list: yum-devel@lists.baseurl.org. To file a bug use http://bugzilla.redhat.com for Fedora/RHEL/Centos related bugs and http://yum.baseurl.org/report for all other bugs. Panu Matilainen 17 October 2005 repoquery(1)