search for: into_srpm

...source code for the package you want to build .. in > this case the kernel-rt: > > git clone https://git.centos.org/git/rpms/kernel-rt > > then go to the kernel-rt directory and checkout the branch and build it: > > cd kernel-rt > git checkout c7-rt > <patch to>/into_srpms.sh > > that should download and make the SRPM for you. If you do not want the > 'dist' tag for the rpm (currently .el7_2), you can do: > > <patch to>/into_srpms.sh -d .el7 > > That would change the dist tag to .el7 instead of .el7_2 > > Once you have...

Hi I want to build a small rootfs for 32 bit CentOS to the same I plan to build the entire OS but I see https://wiki.centos.org/HowTos/I_need_the_Kernel_Source kernel_build for 32 bit is not supported . Please let me know anybody has built the same Thanks Kavitha

Hi all, how can I install rpms from git.centos.org? I'd like to install and test the realtime-kernel. It seems to me that https://wiki.centos.org/Sources only means to build srpms. What I ned is an rt-kernel with headers for further compiling. Purpose: I'd like to build a digital audio workstation and for this I'd like to try out CentOS with the following packages first: -

...ry/rpms!kernel You would: 1. git clone https://git.centos.org/git/rpms/kernel 2. cd kernel 3. git checkout c7 4. get_sources.sh 5. git checkout c7-i686 Then you would have a full SPECS/ and SOURCES/ directory of the latest i686 kernel for CentOS-7. If you wanted the SRPM you would do: into_srpm.sh ====== NOTE: get_sources.sh and into_srpm.sh come from this git repo (as do other tools for using git.centos.org): https://git.centos.org/summary/centos-git-common -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-sign...

...the SRPMs from source. then you can get the source code for the package you want to build .. in this case the kernel-rt: git clone https://git.centos.org/git/rpms/kernel-rt then go to the kernel-rt directory and checkout the branch and build it: cd kernel-rt git checkout c7-rt <patch to>/into_srpms.sh that should download and make the SRPM for you. If you do not want the 'dist' tag for the rpm (currently .el7_2), you can do: <patch to>/into_srpms.sh -d .el7 That would change the dist tag to .el7 instead of .el7_2 > > Purpose: I'd like to build a digital audio...

...ust happens to be what I am working on right now) cd skopeo git branch -a (so you can see the branches .. optional) git checkout c7-extras get_sources.sh ================= Now you have the full SRPM in the same directory structure as if you had installed the SRPM. If you would have used 'into_srpm.sh' instead of 'get_sources.sh' .. you would have the SRPM generated as well as the full tree. There are switches for the tools (-c for get_sources.sh to check the crc info for already downloaded files .. -d for into_srpm.sh for changing the dist tag of a generated SRPM, etc.) I use t...

...want to build .. in >> this case the kernel-rt: >> >> git clone https://git.centos.org/git/rpms/kernel-rt >> >> then go to the kernel-rt directory and checkout the branch and build it: >> >> cd kernel-rt >> git checkout c7-rt >> <patch to>/into_srpms.sh >> >> that should download and make the SRPM for you. If you do not want the >> 'dist' tag for the rpm (currently .el7_2), you can do: >> >> <patch to>/into_srpms.sh -d .el7 >> >> That would change the dist tag to .el7 instead of .el7_2 &...

...his has been > discussed/explained? > Not sure what you are asking. You don't want to put large GZ tarballs in git .. we only put text file in git. All binary files are put in a look-aside cache. So, when you do git clone you get all the text sources .. when you do get_sources.sh (or into_srpm.sh) you get all the binary sources (tarballs, etc.). You need both to be able to build the SRPM. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: OpenPGP digital signature URL: <http://lists...

Hello Phil, On Wed, 2016-12-14 at 20:57 +0000, Phil Wyett wrote: > The path to the repo is wrong. > > git clone https://git.centos.org/git/centos-git-common.git Too late to boost my brain with more coffee for today. Not as sharp as I would like to be ;) . Still leaves me with the question why a script to download the source tarballs is needed when just not adding a .gitignore entry

I'm getting spec files from centos git which is really convenient when the related source is easy to find. But some things - e.g. from a spec file # How to create the source tarball: # # git clone git://git.fedorahosted.org/git/python-rhsm.git/ # cd client/python-rhsm # tito build --tag python-rhsm-$VERSION-$RELEASE --tgz Never used tito before, so I install it and try, and rather than