10 More Discussions You Might Find Interesting
1. Solaris
Got a repo server with a combined 11.2/11.3 repository.
I want to update latest security patches on server A (which is 11.2). I dont want to upgrade to 11.3 (app reasons).
If I do pkg update all - is there any danger this will happen? If so, how to proceed? (2 Replies)
Discussion started by: psychocandy
2 Replies
2. Solaris
This is the operating system im using
Oracle Solaris 10 9/10 s10s_u9wos_14a SPARC
I need to install some packages by setting local repository
While i run the below command
# pkg publisher
command returns bash: pkg: command not found
while looking for /usr/bin/pkg i get bash:... (2 Replies)
Discussion started by: babinlonston
2 Replies
3. Solaris
I have a local repos on my dev/tst server. pkg server is online and I can query against it on the local server and any LDOMS and zones hosted on the same server. I have another identical Solaris server that should be accessing the pkg repos via the local network.
showmount -e from the local (but... (0 Replies)
Discussion started by: os2mac
0 Replies
4. Solaris
Hi Solaris Experts,
The pkg utility on one of my non-global zones has stopped working, it's trying to connect to port 1008 at pkg.oracle.com
I was using pkg successfully from this zone, but now it's showing this error: lzone1 $ pkg search xterm
pkg: Some repositories failed to respond... (4 Replies)
Discussion started by: ad101
4 Replies
5. Solaris
Hi all,
Could please guideas how to extract SUNWexplo.7.2.pkg & SUNWexplu.7.2.pkg from install_stb.sh.
I need to upgrade my Sun Explorer to 7.2 version from 7.1 .
This what written in read me file about its installation:
The Lightweight Availability Collection Tool (LWACT) is no... (1 Reply)
Discussion started by: manalisharmabe
1 Replies
6. Slackware
Hi!
Let me introduce a project for find and download Slackware packages and browse Slackware repositories.
The site provides following features:
* Large, daily updated database with RPM, DEB, TGZ, TXZ packages for well-known repositories of the Slackware, Fedora, CentOS, RHEL, Debian,... (2 Replies)
Discussion started by: lystor
2 Replies
7. Solaris
can anyone download this solaris pkg and email to me, it wont let me download it anymore from sunsolve.
137481-02 (1 Reply)
Discussion started by: dan7225
1 Replies
8. Solaris
To day i installed boltpkg, hiow ever when i run either a pkg-get install or a pkg-get -u pkg-get re turns the following errors.
pkg-get -u
WARNING: no catalog file for site ftp.sunfreeware.com
Updating catalog file first
Getting catalog...
ld.so.1: wget: fatal: libssl.so.0.9.8: open... (3 Replies)
Discussion started by: FloridaBSD
3 Replies
9. Solaris
HI all,
I would like to know, how we can remove a package?
I know that pkgrm will do the job ,but specifying the right kinda package is important..
And i dont know how to figure that one out?
Eg:if i have installed a pkg called virtualbox,
If i do,
pkgrm SUNWvirtualbox ,it says "no such file... (2 Replies)
Discussion started by: wrapster
2 Replies
10. Solaris
hi guys,
I am wondering instead installing to the default directory, how can I install a package using pkgadd command to a specified directory?
I am using solaris 9, thanks (1 Reply)
Discussion started by: fedora
1 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)