search for: get_sourc

...allows the integrity of the contents to be checked. Such an integrity check is missing from the git repo. Either a checksum file for each file or a single checksums file per package/release holding all checksums for all files of said package/release (including the tarballs that are downloaded with get_sources.sh). Regards, Leonard. -- mount -t life -o ro /dev/dna /genetic/research

...to follow the work flow shown in https://wiki.centos.org/Sources, but it does not seem to work: I did this: mkdir CentOS pushd CentOS git clone https://git.centos.org/git/centos-git-common.git git clone https://git.centos.org/git/rpms/kernel.git pushd kernel/ git checkout c6 ../centos-git-common/get_sources.sh And I got the message: Missing metadata. Please run from inside a sources git repo What am I missing? -- Robert Heller -- 978-544-6933 Deepwoods Software -- Custom Software Services http://www.deepsoft.com/ -- Linux Administration Service...

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

...s.org/summary/centos-git-common.git And they are very easy .. and most are bash scripts. So: git clone https://git.centos.org/summary/rpms!skopeo (that just 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 (...

...it > (that just 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 So far so good. We now got a spec file. Doing the same for bc: a spec file and patches. Still no source. > get_sources.sh The name suggests this is what we need (or do we??) If only I could find that script anywhere... So lets dig around a bit: skopeo]$ cat .gitignore SOURCES/skopeo-1f655f3.tar.gz bc]$ cat .gitignore SOURCES/bc-1.06.95.tar.bz2 python-rhsm]$ cat .gitignore SOURCES/python-rhsm-1.17.9.tar.gz...

On 12/13/2016 03:57 PM, Phil Wyett wrote: > On Tue, 2016-12-13 at 15:39 -0800, Alice Wonder wrote: >> On 12/13/2016 03:34 PM, Phil Wyett wrote: >>> On Tue, 2016-12-13 at 14:16 -0800, Alice Wonder wrote: >>>> 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

...is not supported . Please let me know anybody has > built the same Also, if you are just looking for the 32bit kernel, The Source code is here: https://git.centos.org/summary/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):...

Hi I am aware of steps to build kernel and individual rpms 1. git clone https://git.centos.org/git/rpms/kernel 2. cd kernel 3. git checkout c7 4. get_sources.sh You can get this script from below. git clone https://git.centos.org/git/centos-git-common.git cp centos-git-common/get_sources.sh to kernel folder. 5. git checkout c7 But I want to build entire CentOS distro.Please let me know the build procedure? Thanks Kavitha

...t; > > > Out of interest, which version do you refer to? > > > > Regards > > > > Phil > > > > > > 1.17.9 is the version in CentOS 7.3 and what I needed (and found on a > build server) Hi, To get source for a package in CentOS, you follow the get_sources.sh' section and 'Example workflow' section in: https://wiki.centos.org/Sources For your package... * Setup 'centos-git-common' i.e. clone it to your system. * Do the clone and checkout for your package. git clone https://git.centos.org/summary/rpms!python-rhsm.git cd pyth...

...m trying to retrieve the srpm for the latest centos-release pacakge from centos-git by following the instructions @ https://wiki.centos.org/Sources. If I run the following commands: git clone https://git.centos.org/git/rpms/centos-release.git cd centos-release/ git checkout c7 ~/centos-git-common/get_sources.sh Everything completes without error. The problem is that the sources that get downloaded are not for 1804. (vgeppetto2 pts21) $ ll SOURCES/ SPECS/ SOURCES/: total 28 -rw-rw-r--. 1 mock mock 1584 Aug 6 08:19 1000-centos-release-cr.patch -rw-rw-r--. 1 mock mock 264 Aug 6 08:19 85-display-m...

Hello Jonathan, On Wed, 2016-12-14 at 15:03 -0500, Jonathan Billings wrote: > On Wed, Dec 14, 2016 at 07:29:19PM +0100, Leonard den Ottolander wrote: > > > get_sources.sh > > > > The name suggests this is what we need (or do we??) If only I could find > > that script anywhere... > > Johnny said it at the beginning of his email. I'll paste it again so > you don't have to go re-read it: > On Wed, Dec 14, 2016 at 06:58:02A...

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

On Wed, Dec 14, 2016 at 07:29:19PM +0100, Leonard den Ottolander wrote: > > get_sources.sh > > The name suggests this is what we need (or do we??) If only I could find > that script anywhere... Johnny said it at the beginning of his email. I'll paste it again so you don't have to go re-read it: On Wed, Dec 14, 2016 at 06:58:02AM -0600, Johnny Hughes wrote: >...

On Wed, 2016-12-14 at 21:38 +0100, Leonard den Ottolander wrote: > Hello Jonathan, > > On Wed, 2016-12-14 at 15:03 -0500, Jonathan Billings wrote: > > On Wed, Dec 14, 2016 at 07:29:19PM +0100, Leonard den Ottolander wrote: > > > > get_sources.sh > > > > > > The name suggests this is what we need (or do we??) If only I could find > > > that script anywhere... > > > > Johnny said it at the beginning of his email. I'll paste it again so > > you don't have to go re-read it: > &gt...

...to a thread where this 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 UR...

Hello Johnny, On Thu, 2017-02-09 at 09:07 -0600, Johnny Hughes wrote: > Yes .. that content will be republished. It was an accident. How about my request for checksums in the git repo? Regards, Leonard. -- mount -t life -o ro /dev/dna /genetic/research

...ntents to be > checked. Such an integrity check is missing from the git repo. > > Either a checksum file for each file or a single checksums file per > package/release holding all checksums for all files of said > package/release (including the tarballs that are downloaded with > get_sources.sh). > > Regards, > Leonard. > Red Hat exports the source code to the repo, I don't think they are going to change what the put in. It is an extracted SRPM. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp...

...ntegrity of its history. Every change and every file is thus protected. It's impossible to insert changes or to modify the history of the git repository in a way that wouldn't be extremely visible to all users. If you check out a module using git, and fetch its external sources using get_sources.sh, you can rest assured that every file used to build an RPM has been hashed and verified.

...test centos-release pacakge > from centos-git by following the instructions @ > https://wiki.centos.org/Sources. > > If I run the following commands: > git clone? https://git.centos.org/git/rpms/centos-release.git > cd centos-release/ > git checkout c7 > ~/centos-git-common/get_sources.sh > > Everything completes without error. The problem is that the sources that > get > downloaded are not for 1804. > > (vgeppetto2 pts21) $ ll SOURCES/ SPECS/ > SOURCES/: > total 28 > -rw-rw-r--. 1 mock mock? 1584 Aug? 6 08:19 1000-centos-release-cr.patch > -rw-r...

...hecked. Such an integrity check is missing from the git repo. >> >> Either a checksum file for each file or a single checksums file per >> package/release holding all checksums for all files of said >> package/release (including the tarballs that are downloaded with >> get_sources.sh). >> >> Regards, >> Leonard. >> > > Red Hat exports the source code to the repo, I don't think they are > going to change what the put in. It is an extracted SRPM. At the time of extraction, the <name>.metadata file is created (again, not by us, bu...