No.. it isn't there
Also, the machine is SLES 11.3 (not 10.3 as wrongly mentioned by me). This is the last
step and I'm blocked here. I had configured this machine's HTTP so that I can use this as a Repo server for other SLES clients.
I recently installed SLES 10 on an x86 64bit blade server. I then installed vsftpd from the suse cds through network services; however after configuring the vsftpd.conf file, the server fails to start:
# /etc/init.d/vsftpd start
Starting vsftpd startproc: exit status of parent of... (5 Replies)
Dear All,
I have two intel xeon servers running with SLES 10 on a cluster environment (Veritas Cluster 4.1 - 2 Node Cluster - Active Passive). Both the systems are having hardware RAID 1 for OS disk. Both the systems are having DVD writer.
I would like to take the OS backup on DVD which can... (0 Replies)
Hi,
I would like to programmatically find if given OS is SLES 10 / RHEL 3/.RHEL 4/RHEL5 etc ..
For this do we have any library call/sys call? Or should we use any sys. structure which would give me detailed info. Share me if you have any pointers.
Thanks in advance
- Krishna (1 Reply)
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)
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)
Can anyone give me a little clue on why the hard drive cache read timings on sles 9 is better then sles 11? The same hardware was used in both test. I even deleted the ata_generic module from initrd.
The speed difference is 10MB vs 5 MB
Thanks (1 Reply)
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)
Hi guys,
I have a SUSE 10 box and is missing 2 commands:
reposync
createrepo
When I try to search for these using zypper :
server:/tmp # zypper search createrepo
Restoring system sources...
Not found: Media Exception
Not found: Media Exception
/repodata/repomd.xml (http://<REPO>)... (0 Replies)
Discussion started by: Junaid Subhani
0 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)