Sponsored Content
Full Discussion: Rolling Back an Update
Operating Systems Linux Rolling Back an Update Post 302635269 by Brandon9000 on Friday 4th of May 2012 01:32:45 PM
Old 05-04-2012
I do have the ability to tell them how my software is installed.

I don't have the ability to tell them how updates for every other package on their system created by some random source should be updated, which is what I am discussing. Some packages may not be offered in tgz format, and when my software installs available updates for their other software by calling yum, apt-get, zypper, etc., those utilities will default to packages of type .rpm, .deb, etc.
 

8 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Rolling back time

Hi all, Have a small problem. Back in October the pervious sys-admin (of a client's company) made the necessary adjustments to the system clock for daylight savings (Sydney time - +11 GMT). As far as I can gather, they just amended the time - NO TIMEZONE !?! Is there an effective and safe... (5 Replies)
Discussion started by: Cameron
5 Replies

2. AIX

back to back printing in UNIX

Hi , Can you suggest me how to back to back printing in UNIX? Is there any way? Kindly advise. Regards Vijaya Amirtha Raj (3 Replies)
Discussion started by: amirthraj_12
3 Replies

3. Shell Programming and Scripting

log rolling

Hi, I'm thinking of running a script via cron (every hour) to do the log rolling. The file is "file.txt" and there going to be 10 files rolling (file.txt.n). The file is being written constantly by an application. The script will do the following: 1. cat file.txt > file.txt.0 2. cat... (0 Replies)
Discussion started by: chaandana
0 Replies

4. IP Networking

Back-to-Back Connection using HBAs

Hi every body, Is it possible to connect two servers Back-to-Back (Point-to-Point) using HBA adapters & using Fiber. Note it is direct connection & there is no switches between the servers. I'm concern about using HBA adapters, it is possible or not. Thanks in advance. :) (3 Replies)
Discussion started by: aldowsary
3 Replies

5. AIX

rolling back Technology Level

Hi, is it possible to roll back currently updated Technology level ? what are steps required? Regards, Manoj (2 Replies)
Discussion started by: manoj.solaris
2 Replies

6. UNIX for Dummies Questions & Answers

Rolling back SQL transaction

Can some one help me related to .sql file issue. I have a .sqlfile and tried to read the file thru unix. In the .sqlfile I have error rows as well and when error comes I dont want to proceed further and need to roll back all the transactions. sample .sql file below insert into test... (2 Replies)
Discussion started by: sri_aue
2 Replies

7. UNIX for Dummies Questions & Answers

Middled Rolling average

Dear Help, The input file is below --- 13 2238422.00000 101083.00000 0.89024 0.00416 0.00467 14 2238318.00000 101090.00000 0.89100 0.00416 0.00467 15 2238209.00000 101100.00000 0.90964 0.00424 0.00466 16 2238104.00000 101104.00000 0.97568 0.00463 0.00475 17 2237991.00000 101113.00000... (8 Replies)
Discussion started by: Indra2011
8 Replies

8. What is on Your Mind?

SEO Update: Back On Page 1 for Google SERPs (between #6 and #8)

Well, good news... Just checked a number of browsers set to the US region of Google , NCR https://www.google.com/ncr unix.com was back on the first page, between #6 and #8. Will be interesting to see if we can make it back to our highest #4 ranking in 2019. Google Webmaster Tools... (4 Replies)
Discussion started by: Neo
4 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 10:39 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy