Sponsored Content
Operating Systems Linux Red Hat get default rpms on RH4 for Oracle 9i Post 302129011 by MarGur on Friday 27th of July 2007 02:35:38 PM
Old 07-27-2007
get default rpms on RH4 for Oracle 9i

Hi all,
please advise.

i need to install Oracle 9i database on RHES4 and i've totally screwed up with RPMs trying to install the wrong (i386) on 64bit machine.
my question is: how do i can get back to the whole default bunch of RPMs and start from the beginning?
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

rpms vs make

Ok, this is probably a real simple question....I have RH 7.1 and i wanted to know do I have to install the RPM packages for software or can i use the binaries and do make ...make install. ?? (6 Replies)
Discussion started by: macdonto
6 Replies

2. Red Hat

How do I find out which rpms to install to cover dependencies?

Howdy all, I am trying to install dk-milter on a postfix mail machine, but am running up against some dependencies, and I don't know how to find out which rpms contain the required packages. # cat /etc/redhat-release Red Hat Enterprise Linux ES release 3 (Taroon Update 9) # uname -a ... (2 Replies)
Discussion started by: zefflyn
2 Replies

3. Red Hat

How to update all rpms using single command option

Can any one help me to know the command option that will update all rpms Thanks in advance.. (2 Replies)
Discussion started by: RajendraKumar
2 Replies

4. Red Hat

Updating Red Hat from RH4 to the latest

hi all, i have a redhat 4 as (nahant) which i need to update to the latest. i need to download it from my subscription site. my worry is that this is my first time to do it. is there a safe backout on it? do you have procedures for this? my backup on the linux is from ibm tsm. i will... (2 Replies)
Discussion started by: itik
2 Replies

5. UNIX for Dummies Questions & Answers

Building single rpm from 2 different rpms?

Hi all, I have to automate server installation. For this its needed to install 2 - 3 different RPMs. Is there any way of creating a single rpm from these two rpms? How the spec file will look like? thanks... (0 Replies)
Discussion started by: zing_foru
0 Replies

6. Red Hat

How to remove installed RPMs by a specific date?

Hi there, Is there a way to remove rpms installed after specific date? I was improvising on my unixacademy Linux training and messed up with installation options. Can I remove the rpms installed after specific date? (1 Reply)
Discussion started by: newlinuxuser1
1 Replies

7. Shell Programming and Scripting

download rpms from fedora 11 repositry

Hello folks, I want to download rpms from below link, but problem is that only able to download with wget command, but problem is that if internet delay or packet loss comes from remote site then it will break the download and download next file not continue the broken file, though i start from... (0 Replies)
Discussion started by: learnbash
0 Replies

8. Red Hat

What is RPMs?

Would you please give us the definition and usage of RPMs in linux? thanks to reply.... (1 Reply)
Discussion started by: jaydul
1 Replies

9. Proxy Server

Building up apache httpd on AIX - acquiring RPMs etc.

pardon the ed URL refs but I'm not allowed to post URLs yet. and the misspelling in the original thread title, which I can't edit even in 'advanced' greetings all, posting this here rather than in Web Development since I suspect this is rather AIX-specific and will need some arcane knowledge,... (2 Replies)
Discussion started by: maraixadm
2 Replies
build(1)						      General Commands Manual							  build(1)

NAME
build - build SuSE Linux RPMs in a chroot environment SYNOPSIS
build [--clean|--no-init] [--rpms path1:path2:...] [--arch arch1:arch2:...] [--root buildroot] [specfile|srcrpm] build --help build --verify DESCRIPTION
build is a tool to build SuSE Linux RPMs in a safe and clean way. build will install a minimal SuSE Linux as build system into some direc- tory and will chroot to this system to compile the package. This way you don't risk to corrupt your working system (due to a broken spec file for example), even if the package does not use BuildRoot. build searches the spec file for a BuildRequires: line; if such a line is found, all the specified rpms are installed. Otherwise a selec- tion of default packages are used. Note that build doesn't automatically resolve missing dependencies, so the specified rpms have to be sufficient for the build. If a spec file is specified on the command line, build will use this file and all other files in the directory for building the package. If a srcrpm is specified, build automatically unpacks it for the build. If neither is given, build will use all the specfiles in the current directory. OPTIONS
--clean remove the build system and reinitialize it from scratch. --no-init skip the build system initialization and start with build immediately. --list-state list rpms that would be used to create a fresh build root. Does not create the build root or perform a build. --rpms path1:path2:path3... Where build can find the SuSE Linux RPMs needed to create the build system. This option overrides the BUILD_RPMS environment vari- able. --arch arch1:arch2:arch3... What architectures to select from the RPMs. build automatically sets this to a sensible value for your host if you don't specify this option. --root buildroot Specifies where the build system is set up. Overrides the BUILD_ROOT enviroment variable. --useusedforbuild Tell build not to do dependency expansion, but to extract the list of packages to install from "# usedforbuild" lines or, if none are found, from all "BuildRequires" lines. This option is useful if you want to re-build a package from a srcrpm with exactly the same packages used for the srcrpm build. --norootforbuild --help Print a short help text. --verify verify the files in an existing build system. .spec FILE OPTIONS The build command interprets some special control comments in the specfile: # norootforbuild # needsrootforbuild build uses either user root or user abuild in the build system to do the build. For non-SUSE distros as well as since SUSE 10.2, the default build user is abuild. For 10.2 and before, the default build user is root. These two flags in the spec file allow to deviate from the defaults and force-set the build user to abuild and root (for # norootforbuild and # needsrootforbuild respec- tively. # needsbinariesforbuild provide the binary rpms that have been used to set up the build root in /.build.binaries within the build root. ENVIRONMENT
BUILD_ROOT The directory where build should install the chrooted build system. "/var/tmp/build-root" is used by default. BUILD_RPMS Where build can find the SuSE Linux RPMs. build needs them to create the build system. "/media/dvd/suse" is the default value which will do the trick if you have the SuSE Linux DVD mounted. BUILD_RPM_BUILD_STAGE The rpm build stage (-ba, -bb, ...). This is just passed through to rpm, check the rpm manpage for a complete list and descrip- tions. "-ba" is the default. You can use this to add more options to RPM. SEE ALSO
rpm(1), Maximum RPM: http://www.rpm.org/max-rpm/ cross distribution packaging: http://en.opensuse.org/Build_Service/cross_distribution_package_how_to SUSE packaging standards and guidelines: http://en.opensuse.org/Packaging (c) 1997-2008 SuSE Linux AG Nuernberg, Germany build(1)
All times are GMT -4. The time now is 05:45 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy