devel

devel@lists.centos.org

10 participants
4625 discussions

Getting Sources for an older revision from git.centos.org
by Johnny Hughes 12 Jun '14

12 Jun '14

So, if you want to get SOURCES from the look-aside cache using get_sources.sh for an older revision, you might possibly hit a DETACHED HEAD snag that I just hit. 1. git checkout https://git.centos.org/git/rpms/firefox.git (or if you already have it, git pull from within the firefox directory) 2. If you look at firefox's log, there are 2 things to build for c7 GA and the beta and the RC are there, so four commits for four different SRPMS. the command "git log" shows us that: commit 9e6d29c3f16d3692c9cb30371b227d6c08edd591 Author: CentOS Sources <bugs(a)centos.org> Date: Tue Jun 10 16:10:41 2014 -0400 import firefox-24.6.0-1.el7_0 commit 9a1d2ed9c6faf3da49e78eb41872bde7cfefece2 Author: CentOS Sources <bugs(a)centos.org> Date: Mon Jun 9 03:31:45 2014 -0400 import firefox-24.5.0-1.el7 commit 6ca8db34a0fc78f0454e96c6f9b715df86529195 Author: CentOS Buildsys <bugs(a)centos.org> Date: Tue Mar 18 09:47:19 2014 +0000 import firefox-24.4.0-1.el7.src.rpm commit 29a772037be917dc94c382403705291699865c88 Author: CentOS Buildsys <bugs(a)centos.org> Date: Fri Nov 8 10:07:07 2013 +0000 import firefox-24.1.0-3.el7.src.rpm commit 591789b9e3e230f74954ed27b377f8e72068d895 Author: CentOS Buildsys <bugs(a)centos.org> Date: Fri Nov 8 10:07:10 2013 +0000 init git for firefox 3. I want to get the sources for .. firefox-24.5.0-1.el7 ... at revision 9a1d2ed9c6faf3da49e78eb41872bde7cfefece2. I tried and failed to get it by simply doing: git checkout 9a1d2ed9c6faf3da49e78eb41872bde7cfefece2 and then get_sources.sh 4. The problem is that going one commit back changes git's HEAD to a link to the commit number and not what it is when you are on the c7 branch .. and that breaks the get_sources.sh script's branch detection. For more on what detached head looks like see this: http://alblue.bandlem.com/2011/08/git-tip-of-week-detached-heads.html 5. So, we will try to fix the get_source.sh script to work in that situation .. in the meantime, you can do this instead. ================================================= 1. go to the firefox repo and make sure you are on the c7 branch: git checkout c7 2. Do a git log and find the revision you want (see the above list, step 2) 3. I want to get the sources for "firefox-24.5.0-1.el7", which is one revision back from current ... so do this command: git reset --hard c7~1 4. It will tell you this: HEAD is now at 9a1d2ed import firefox-24.5.0-1.el7 5. Now you can use get_sources.sh to pull the SOURCES for firefox-24.5.0-1.el7 get_sources.sh 6. Once the sources are done downloading, build the SRPM with the command: rpmbuild --define "_topdir $(pwd)" --define "dist .el7" -bs --nodeps SPECS/firefox.spec 7. To get back to the current revision of firefox in the c7 branch do this: git pull --ff-only 8. It will tell you this: Updating 9a1d2ed..9e6d29c Fast-forward .firefox.metadata | 4 ++-- .gitignore | 4 ++-- SOURCES/xulrunner-2.0-chromium-types.patch | 34 ---------------------------------- SOURCES/xulrunner-webrtc-secondarch.patch | 34 ---------------------------------- SPECS/firefox.spec | 14 ++++++++------ 5 files changed, 12 insertions(+), 78 deletions(-) delete mode 100644 SOURCES/xulrunner-2.0-chromium-types.patch delete mode 100644 SOURCES/xulrunner-webrtc-secondarch.patch ============================================ If you wanted to go two revisions back (in this example that would be version "firefox-24.4.0-1.el7.src.rpm" , you would do: git reset --hard c7~2 (the ~1 or ~2 is the number of revisions to go back) Don't forget to go back to the top with the "git pull --ff-only" when you are ready to be on the current revision again As I said, we are going to try to come up with better branch detection for getting the sources, but until we do, this should help anyone with this issue. Thanks very much to Mike McLean and Karanbir Singh for helping figure out the issue and the workaround. Thanks, Johnny Hughes

1 0

Re: [CentOS-devel] CentOS 7 and release numbering
by Philip Mather 12 Jun '14

12 Jun '14

I've yet to see the technical argument for this release numbering change, the closest thing I've seen is... > A clear example of what the datestamp tries to workaround is > yesterdays docker updates ( and the AMI and GCE images etc ) that were > done to CVE fix openssl content. These are not marked as a point at all, > just a centos-6-x86_64-20140609 ( and in most cases, the link that > people hit is for centos-6-x86_64 ...and that has nothing to do with the Core OS. As far as I can tell it's not even a technical issue but a website/people presentation issue. This could also break system and configuration management tooling as well. I have servers with their OS configuration managed by Puppet and chef recipes controlling their application config (don't ask :^) ). Those systems "shouldn't" barf but we all know some naughty person will have written their own regex to parse up and switch case on the contents of /etc/redhat-release or whatever. I'd be loathed to split it into two tracks either, one for RHEL numbering and one for CentOS. I appreciate this isn't a concern of the OS devels directly as such. Will this version format be compatible with RedHat Satellite, Spacewalk or Katello etc? We were looking at actually buying Satellite at $work as we migrate off of Spacewalk but until I know this is all compatible there's no way I can contemplate any recommendation for investment in Satellite and/or several weeks of setting up Katello and then a migration effort to move the old systems out of Spacewalk if I have to have separate versions. This sort of thing really needs to be confined to a SIG (or some sort of test/beta) or come via RHEL themselves. If it comes from RHEL it will be compatible with their own (and others would follow with their) tooling or at least if it's trailed outside of Core people can test it separately. As is, we now have to wait until any new CentOS numbering is proven to be compatible with RHEL numbering in other tools and then determine if it's viable to continue using both in-step.

1 0

Re: [CentOS-devel] CentOS 7 and release numbering
by Michael.Goldfinger＠inhouse.wko.at 12 Jun '14

12 Jun '14

Morning all, I am a real newbie. In fact I just registered to give my two cents about the release numbering discussion. My vote would be to keep the version numbering in line with RHEL too. I have always found that version numbers that increase normally are much more logical that version numbers that include a date. However as someone who has not installed any Linux distributions before I do not really care about version numbering. I choose CentOS because I think it best matches my needs. Currently I am waiting for CentOS 7 to start with the fresh version but at the end it all comes down to download the latest versions from the repositories, I do not even look at the version numbers. It was a coincident that I found out that 7 is on the way and I decided to wait for it. Hope this helps. Regards, Michael

2 1

[PATCH] Finding %{dist}
by Pat Riehecky 12 Jun '14

12 Jun '14

From: Pat Riehecky <riehecky(a)fnal.gov> This should pull out what I think %{dist} looks like based on the previous commits to git.c.o . At least in theory. Pat Riehecky (1): Added script for extracting what I think is the dist tag return_disttag.sh | 71 +++++++++++++++++++++++++++++++++++++++++++++++++++++ 1 files changed, 71 insertions(+), 0 deletions(-) create mode 100755 return_disttag.sh

4 13

[PATCH] *** SUBJECT HERE ***
by bonniek 12 Jun '14

12 Jun '14

*** BLURB HERE *** bonniek (1): Make the default match what the help text claims it to be ('rpms'). centos.git.repolist.py | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-)

2 3

[PATCH] tool to list repos on git.centos.org
by bonniek 12 Jun '14

12 Jun '14

This will return a list of git repos for a given "project path". Needs simplejson and requests python modules. bonniek (1): Initial commit of script to get git repolist from git.centos.org. centos.git.repolist.py | 57 ++++++++++++++++++++++++++++++++++++++++++++++++ 1 files changed, 57 insertions(+), 0 deletions(-) create mode 100755 centos.git.repolist.py

1 1

[PATCH] Clean up temp src.rpm
by Pat Riehecky 11 Jun '14

11 Jun '14

From: Pat Riehecky <riehecky(a)fnal.gov> --- return_disttag.sh | 3 +++ 1 files changed, 3 insertions(+), 0 deletions(-) diff --git a/return_disttag.sh b/return_disttag.sh index f7dc610..f850356 100755 --- a/return_disttag.sh +++ b/return_disttag.sh @@ -73,6 +73,9 @@ nvr1="${pkg%.src.rpm}" mydist="XXXjsdf9ur7qlkasdh4gygXXX" nvr2=$(rpm --define "dist $mydist" -q --specfile "SPECS/$packagename.spec" --qf '%{n}-%{v}-%{r}\n' 2>/dev/null | head -n 1) +# clean up SRPM, since it is only used for its name +rm -f ${nvr2} >/dev/null 2>&1 + #use our placeholder dist to split the nvr head=${nvr2%$mydist*} -- 1.7.1

3 5

[PATCH] Not all git.c.o repos have SOURCES dir
by Pat Riehecky 11 Jun '14

11 Jun '14

From: Pat Riehecky <riehecky(a)fnal.gov> I've found a few repos without a SOURCES directory. For example, kpatch source cannot be fetched without this patch. Pat Riehecky (1): Fixed so it works on kpatch golang-* get_sources.sh | 3 ++- 1 files changed, 2 insertions(+), 1 deletions(-)

2 4

Welcoming CERN Linux Distro team
by Karanbir Singh 11 Jun '14

11 Jun '14

Hi Everyone, We would like to welcome onboard the CERN Linux Distro team ( http://cern.ch/linux ) to the CentOS Core SIG. Thomas Oulevey and Jaroslaw 'Jarek' Polok are going to be bootstrapping the CentOS Community Buildsystem around Koji and helping run it going forward. The community buildsystem is going to be the central place for all source to binary builds used by all efforts other than CentOS Core ( for now ). The initial target is to get a test instance running in the coming weeks, and then work on the git.centos.org integration, with the aim of having the 'production' buildsys online soon. This is the build service that all SIG's and Core SIG builds will consume going forward ( with the exception of CentOS Linux, we have quite a bit of work to do before we can migrate that ). Communications on this effort will be on the centos-devel mailing list ( http://lists.centos.org/mailman/listinfo/centos-devel ) and on the #centos-devel irc channel on irc.freenode.net. Hardware resources for the effort have been identified, setup and access is being setup so things can start rolling fairly quickly. Mike McLean and Fabian Arrotin are going to be working with them. You can keep up with Jarek on his google+ page at https://plus.google.com/+JaroslawPolok/ and Thomas tweets at https://twitter.com/thomasnomas ; They both also contribute to the http://linux.web.cern.ch/linux/ blog. Please join me in welcoming Thomas and Jarek to the CentOS Project. - KB -- Karanbir Singh, Project Lead, The CentOS Project +44-207-0999389 | http://www.centos.org/ | twitter.com/CentOS GnuPG Key : http://www.karan.org/publickey.asc

6 5

Questions about the new git.centos.org repos
by Pat Riehecky 11 Jun '14

11 Jun '14

Now that there are repos up at git.centos.org, I was wondering if anyone had a python tool I could use to convert a repo back into a source RPM? Similarly, does anyone know how gitblit handles repo change notifications? I'd love to be notified of updates to some repos or their tags. A programmatic tool for gathering that information would work just as well... I'm not sure which would work better for my workflow. There's a fair chance at various intervals I'd be hitting the site somewhat hard, are there any instructions for mirroring all the parts necessary for package assembly? I'd rather beat up my local mirror than pick on the main page. Open to ideas, Pat -- Pat Riehecky Scientific Linux developer http://www.scientificlinux.org/

8 36

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel