Sponsored Content
Full Discussion: pkgadd issues
Top Forums UNIX for Dummies Questions & Answers pkgadd issues Post 302125044 by porter on Tuesday 3rd of July 2007 01:37:15 PM
Old 07-03-2007
Quote:
Originally Posted by GLJ@USC
I do not have a previous version os the pkg installed. Thanks.
What about the prerequisites? It looks like it expects to be patching a previous version and is finding nothing to patch.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

pkgadd

I am adding gcc 3.3.2 to my unix box what is the best way to do it???? (4 Replies)
Discussion started by: alsande
4 Replies

2. Solaris

pkgadd

is there an option in pkgadd to accept the default option? I want to use pkgadd in a script and do not want to stop at intercative questions. thx. (6 Replies)
Discussion started by: melanie_pfefer
6 Replies

3. UNIX for Advanced & Expert Users

pkgadd issues

I have a server running solaris 8 with veritas 4.1. I am trying to install a package on the server. The package install fails miserably though. I have installed the very same package on other development servers, but for some reason, the install fails on this, soon to be prod, server. No idea... (3 Replies)
Discussion started by: Sowser
3 Replies

4. Solaris

pkgadd help

I'm trying to install a package and it worked on most of the sun boxes and one of the box is just freezing and not going further. Her is the output. pkgadd -d packagename.dstream Select package(s) you wish to process (or 'all' to process all packages). (default: all) : Processing... (1 Reply)
Discussion started by: mokkan
1 Replies

5. Solaris

Pkgadd problem

Hi there, I need to install the Sun explorer package on hundreds of boxes and am writing a script to install it ..However, When you run pkgadd -d SUNWexplo It is interactive .....well i say interactive ...it gives you two questions both of which I answer a simple yes to. So i tried ... (9 Replies)
Discussion started by: hcclnoodles
9 Replies

6. Solaris

pkgadd?

Hi all. Is there an option to #pkgadd to test if package bundle you want to install requires a reboot? #pkgadd -d "package bundle" an option like test or a dry run? Suggestions, anyone? :confused: Reloader (2 Replies)
Discussion started by: Reloader
2 Replies

7. Solaris

pkgadd woes

Morning all, I am attempting to load a package from a Solaris 8 CDROM. This fails with the error : "pkgadd: ERROR: unable to access pkgmap file </cdrom/ .........../SUNWlibC/pkgmap> No changes were made to the system" Any help would be appreciated Andy (6 Replies)
Discussion started by: AndyD
6 Replies

8. Solaris

Pkgadd error

Hi All, Good Mng,Here I am getting one error while adding the top package to one of my Aun server. root@HYDREM01 # pkgadd -d top-3.6.1-sol9-sparc-local The following packages are available: 1 SMCtop top (sparc) 3.6.1 Select package(s) you wish to process (or... (6 Replies)
Discussion started by: lbreddy
6 Replies

9. Shell Programming and Scripting

pkgadd question

Hi, Please could someone help me, understand how pkgadd works within unix. I have a software file, and I need to package this up and then pkgadd this to another server. Please could some advise me the best way to do this. regards venhart (2 Replies)
Discussion started by: venhart
2 Replies

10. Solaris

pkgadd changes permissions of /etc

Hi, when I install a package using pkgadd, it correctly installs the binary files with the user name that I want. However it also changes the permissions of /etc/rc2.d. I don't want this to happen. I want to retain original owner of /etc/rc2.d as it is. I could see that before installing,... (1 Reply)
Discussion started by: funwithdolphin
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)
All times are GMT -4. The time now is 02:39 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy