I have a build process that runs on CentOS that builds RPMs for a java-based product. I'd like to be able to install these RPMs on my Mac OS X laptop for testing purposes. I don't need an RPM database to manage dependencies or previously installed packages. Consider this RPM to be a glorified tar file.
When I try to install I get a message like this:
I can run rpm -qlp to list the file contents of the RPM. I can run rpm2cpio to extract the contents of the RPM. This suggests that the RPM is in a valid format and is not corrupt.
I'm able to install RPMs that I build on OS X on my OS X laptop. I'm also able to install RPMs built on OS X on CentOS using the
rpm --ignoreos option.
rpm --showrc on OS X shows:
rpm --showrc on CentOS shows:
Is there a way to determine why the package was skipped? The debug message indicates that no binary packages were found.
Hi everyone
I have just joined a software developing team. I am new to unix. Basically
we are developing a product, the problem is when the end user will install this package we would like to install the datbase associated with our product using RPM.
Can it be done?
how secure it is?
and... (0 Replies)
I am working on a HP-UX PARISC 64 architecture.
I am trying to install RPM but without success.
Has any body successfully installed RPM on the above architecture.
I couldnt find a compatible depot file.
I tried to compile the source code for rpm-4.0 package.
All the dependencies are... (3 Replies)
Hi,
I have an application to be installed and I want a user to be able to install it.
But I meet the following issues:
Removing MyApp
error: cannot get exclusive lock on /var/lib/rpm/Packages
error: cannot open Packages index using db3 - Operation not permitted (1)
error: cannot open... (1 Reply)
Hi guys, I am trying to install some packages for my oracle 11g r2 installation, the below error shows up when I try below:
warning: glibc-devel-2.5-24.i386.rpm: Header V3 DSA signature: NOKEY, key ID 37017186
error: Failed dependencies:
glibc-headers is needed by... (8 Replies)
Hi,
I would like to know is it possible to install rpm along its depedable rpm from mounted .iso image on Redhat Linux
while installing rpm it is showing so many depandancy, so I would like to know with single command wheather it will take all depedable rpm from mounted iso image. (1 Reply)
hi,
i am try to install a package in centos 6.2 x86-64 but unable to find any package in centos media iso.
In RHEL we have a product folder which contain all the list of rpm but in centos i cant found that.
I have use yum command but it also cant work show me the message no module named yum.... (1 Reply)
I am attempting to install an rpm of Apache from perzl.org on an AIX 6100-07-03-1207 server and it is failing. I think I have all of the dependencies installed. Can anyone help? Any help would be appreciated.
It fails with the following error:
# rpm -Uvh httpd-2.4.2-2.aix5.1.ppc.rpm ... (3 Replies)
I am trying to install an rpm : libiconv-1.14-1.aix5.1.ppc.rpm which is a dependency to install GIT.
While I gave the command I got the foll message:
root:user-> $ rpm -i -v libiconv-1.14-1.aix5.1.ppc.rpm
libiconv-1.14-1
ar: Cannot open or remove a file containing a running program.... (2 Replies)
Discussion started by: gaugeta
2 Replies
LEARN ABOUT OSX
build
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)