10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi All,
Do you have any sample script,
- auto get file from SFTP remote server and delete file in remove server after downloaded.
- only download specify filename
- auto upload file from local to SFTP remote server and delete local folder file after uploaded
- only upload specify filename
... (3 Replies)
Discussion started by: weesiong
3 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. 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
4. Shell Programming and Scripting
Hi, I have text file abc.txt. In this file, I have the following data.
Input:
Mr Smith & Mrs Smith
Mr Smith &apos Mrs Smith
Mr Smith & Mrs Smith
Mr Smith& Mrs Smith
Mr Smith &Mrs Smith
Output:
Mr Smith & Mrs Smith
Mr Smith &apos Mrs Smith
Mr Smith & Mrs Smith
Mr Smith&... (4 Replies)
Discussion started by: naveed
4 Replies
5. 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
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. Shell Programming and Scripting
Hello All
I have a xml file with many sets of records
like this
<mytag>mydata</mytag>
<tag2>data&</tag2>
also same file can be like this
<mytag>mydata</mytag>
<tag2>data&</tag2>
<tag3>data2&data3</tag3>
Now i can grep & and replace with & for whole file but it will replace all... (4 Replies)
Discussion started by: lokaish23
4 Replies
8. Shell Programming and Scripting
Hi, I hope the title does not scare people to look into this thread but it describes roughly what I'm trying to do. I need a solution in PHP.
I'm a programming beginner, so it might be that the approach to solve this, might be easier to solve with an other approach of someone else, so if you... (0 Replies)
Discussion started by: lowmaster
0 Replies
9. Red Hat
i have 5 cd's of RHEL 5.
how do i know which cd is the createrepo package in...
is there any command or
flags you can add to rpm command to install and the install processes will automatically ask for certain # of cd... (0 Replies)
Discussion started by: dplinux
0 Replies
10. UNIX for Dummies Questions & Answers
Dear unix gurus,
I have a data file with header information about a subject and also 3 columns of n rows of data on various items he owns. The data file looks something like this:
adam peter
blah blah blah
blah blah blah
car
01 30 200
02 31 400
03 57 121
.. .. ..
.. .. ..
n y... (8 Replies)
Discussion started by: tintin72
8 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)
