Sponsored Content
Operating Systems Linux Red Hat Yum repository linking to ftp site of Redhat Post 302748335 by fpmurphy on Tuesday 25th of December 2012 09:51:18 AM
Old 12-25-2012
Since I have absolutely no idea what you call "normal RPMs" in your "yum repository" are, I cannot give you a firm answer.

However, they are the official DebugInfo RPMs.

Note Debug RPMs are not the same as DebugInfo RPMs!
 

9 More Discussions You Might Find Interesting

1. Linux

linking HTML web site to DB oracle

Hi if i have an HTML web site and oracle database and i need to link them, both r on a linux server. please can u tell me what can i use to link the DB to the web site? (1 Reply)
Discussion started by: seemharoun
1 Replies

2. UNIX for Dummies Questions & Answers

How do I verify the integrity of a package? And how do I configure yum to add a site

How do I verify the integrity of a package? And how do I configure yum to add a site (3 Replies)
Discussion started by: 3junior
3 Replies

3. Red Hat

Local yum repository

Hi Friends, I have succesfully configured a local yum repository using ios image. Please let me know how i can synchronize the local repository with RHN. Is it possible, so that i can update the local repository with latest updates. Regards, Arumon (1 Reply)
Discussion started by: arumon
1 Replies

4. Red Hat

Trying to install boost 1.4.1 without success maybe yum repository is wrong

Hi I following the tutorial to install boost 1.4.1 in centos 5.6 32 bit But without success maybe it doesn't find it in my repository in yum , but also when I compile the lib It doesn't find the libs . The tutorial link: Compiling gearman on CentOS 5.6 - gearman | Google Groups the error... (1 Reply)
Discussion started by: umen
1 Replies

5. Red Hat

installing Redhat Repository server

Hello, can someone please assist me userguide to setup simple Redhat yum Repository server with out using redhat satellite server. So all client will be pointing to this repository server to install rpm's. Thanks, (3 Replies)
Discussion started by: bobby320
3 Replies

6. Red Hat

Configure yum repository

how to configure yum server to get rpms from any repository or redhat repo. (4 Replies)
Discussion started by: leganti
4 Replies

7. Red Hat

Yum cannot install from repository

Hi guys, thanks for you help on this issue. I built a dvd repository on my server and when I try to install a package from it, I get this error ftp://10.0.0.12/pub/Packages/httpd-2.2.15-26.el6.x86_64.rpm: PYCURL ERROR 9 - "Server denied you to change to the given directory" I will... (2 Replies)
Discussion started by: cjashu
2 Replies

8. Fedora

Yum repository not working in Fedora 16

Hi, while installing/updating package using yum I am getting (repomd.xml) error # yum list Loaded plugins: langpacks, presto, refresh-packagekit http://mirror.cse.iitk.ac.in/fedora-archive/fedora/linux/fedora/linux/releases/16/Everything/x86_64/os/repodata/repomd.xml: HTTP Error 404 -... (12 Replies)
Discussion started by: muzaffar.k
12 Replies

9. Linux

Local YUM Repository for RHEL versions

Hello, I need to know regarding setting up of Local repositories so that I can update or install packages on other RHEL servers. In our environment we have many servers with different RHEL versions. Like RHEL 7.2, RHEL 7.3, RHEL 7.4, RHEL 7.5 Arch = x86_64 I have setup one Repo server;... (0 Replies)
Discussion started by: SunshineMLinux
0 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 09:13 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy