10 More Discussions You Might Find Interesting
1. UNIX for Beginners Questions & Answers
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. SuSE
Hello All,
I'm trying to configure a SLES 10.3 machine as our Zypper server. I created the zypper directories with all the RPMs, made the directory structure accessible over HTTP but I'm stuck at the final stage: createrepo.
Looks like 'createrepo' is not present on this version :confused:
... (3 Replies)
Discussion started by: satish51392111
3 Replies
3. SuSE
Hi guys,
I have a SUSE 10 box and is missing 2 commands:
reposync
createrepo
When I try to search for these using zypper :
server:/tmp # zypper search createrepo
Restoring system sources...
Not found: Media Exception
Not found: Media Exception
/repodata/repomd.xml (http://<REPO>)... (0 Replies)
Discussion started by: Junaid Subhani
0 Replies
4. UNIX and Linux Applications
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
5. Red Hat
Hi, Here is the issue:
# yum install createrepo
Warning, could not load sqlite, falling back to pickle
Setting up Install Process
Setting up repositories
file://var/yum_rpm/repodata/repomd.xml: OSError: No such file or directory: '/yum_rpm/repodata/repomd.xml'
Trying other mirror.
Cannot... (5 Replies)
Discussion started by: aixlover
5 Replies
6. Red Hat
Hello all,
I'm stuck with a problem on REDHAT Enterprise (uname -r show: 2.4.21-57.ELsmp)
The only way to install package is using RPM, but since I'm a newbie I got a lot of dependencies warnings. I installed yum, but the problem now is that I'm not able to create a local repository to install... (6 Replies)
Discussion started by: Lord Spectre
6 Replies
7. UNIX for Dummies Questions & Answers
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
8. Red Hat
Hi,
I have configured YUM repository on a server and we have 10 linux machine (clients).
Is there any way we can install a package on all the 10 machines from YUM repository server?
Please help me. (7 Replies)
Discussion started by: uday123
7 Replies
9. Red Hat
Friends ,
I want to install package using yum from DVD in RHEL 5 . Hence I just follow the below rules :
1)
# mount /dev/hdc /cdrom/
mount: block device /dev/hdc is write-protected, mounting read-only
2)
Edit the yum rhel-debuginfo.repo file like following way :
# pwd... (3 Replies)
Discussion started by: shipon_97
3 Replies
10. Solaris
hello solaris friends,
I've tried installing Sun Solaris 10.0, but everytime it seems to bypass the network config. screen that looks similar to this...here's the url:
http://www.hup.hu/old/images/hup/Solaris/Sol10beta7/9.png
I'm able to install it all the way through but I get no... (2 Replies)
Discussion started by: cadmiumgreen
2 Replies
yumdb(8) yumdb(8)
NAME
yumdb - query and alter the Yum database
SYNOPSIS
yumdb [command] [packages ...]
DESCRIPTION
This command is used to query and alter the yum database, which is a simple key value store used in conjunction with the rpm database. Any
installed package can have arbitrary data in the yum database, however the main use case is to store extra data about packages as they are
installed.
yumdb commands are:
yumdb get <key> [pkg-wildcard]...
This command will get the value for the given key, limiting to any specified packages.
yumdb set <key> <value> [pkg-wildcard]...
This command will set the value for the given key, to the given value, limiting to any specified packages.
yumdb del <key> [pkg-wildcard]...
This command will delete the given key, limiting to any specified packages.
yumdb rename <old-key> <new-key> [pkg-wildcard]...
This command will rename the given old-key, to the given new-key, limiting to any specified packages. If the old-key does not exist, noth-
ing happens.
yumdb rename-force <old-key> <new-key> [pkg-wildcard]...
This command will rename the given old-key, to the given new-key, limiting to any specified packages. If the old-key does not exist, new-
key is deleted.
yumdb copy <old-key> <new-key> [pkg-wildcard]...
This command will copy the given old-key, to the given new-key, limiting to any specified packages. If the old-key does not exist, nothing
happens.
yumdb copy-force <old-key> <new-key> [pkg-wildcard]...
This command will copy the given old-key, to the given new-key, limiting to any specified packages. If the old-key does not exist, new-key
is deleted.
yumdb search <key> <wildcard>...
This command will search all packages for the given key, against any of the given wildcard values.
yumdb exist <key> [pkg-wildcard]...
This command will print any packages which have the given key, limiting to any specified packages.
yumdb unset <key> [pkg-wildcard]...
This command will print any packages which do not have the given key, limiting to any specified packages.
yumdb info [pkg-wildcard]...
This command will display all the data stored in the yumdb, limiting to any specified packages.
yumdb sync [pkg-wildcard]...
This command will add any missing data to the yumdb from the repositories, limiting to any specified packages. This is useful to run if you
have had any aborted transactions (and thus. missing yumdb data). Note that "yumdb sync" cannot know all the information that would have
been put into the yumdb at the time.
yumdb sync-force [pkg-wildcard]...
This command will replace any data in the yumdb from the repositories, limiting to any specified packages.
EXAMPLES
List all the packages which don't have a from_repo key/value:
yumdb unset from_repo
List all the packages which were installed as dependencies:
yumdb search reason dep
WELL KNOWN KEYS
Note that there is no limit to the number of keys that can be created or what they may contain (for installed packages only). However this
is a list of well known keys, and what they store.
checksum_data
checksum_type
These keys store the createrepo checksum, and it's type, of the available
package yum installed. Note that these are used by "yum version" to calculate
the rpmdb version.
command_line
This key stores the entire command line, of the yum command (if it was called).
from_repo
from_repo_revision
from_repo_timestamp
These keys take values from the available package yum installed, and store the
repo id, it's revision and timestamp.
reason
This key stores either "user" or "dep", currently. To mark if the user requested
the package to be installed, or if it was brought in automatically as a
dependency. Note that this is kept over updates.
releasever
This key stores the value of releasever, when the package was installed.
installonly
If this attribute has the value "keep" then this package will not be
removed automatically by the installonly process (and does not count towards
the installonly_limit).
SEE ALSO
yum (8)
rpm (8)
AUTHORS
James Antill <james.antill@redhat.com>.
James Antill 8 April 2010 yumdb(8)