devel

devel@lists.centos.org

18 participants
4604 discussions

CentOS 7 Release Schedule
by Shafiee Roozbeh 22 Jun '14

22 Jun '14

Hi community is there any release schedule for CentOS 7 ? not exact schedule I mean... I follow all topics in development mailing list and I know that there is no release schedule announcement by Karanbir and the other guys. I mean approximate schedule... I asked this question because the time interval between RHEL 6.0 and CenOS 6.0 was more than 240 days. (according to wikipedia: http://en.wikipedia.org/wiki/CentOS ) . For CentOS 7 we should await this much ? Thanks -- Roozbeh Shafiee Linux/BSD System Administrator and Python Developer RoozbehShafiee.Com

4 4

Cloud and VM Images
by Karanbir Singh 22 Jun '14

22 Jun '14

hi, I have just pushed a public build for a qcow2 image, this should be suiteable for any HVM environment. Please test as widely as possible. http://buildlogs.centos.org/centos/7/cloud/ I also spoke with Rich Jones earlier in the day today and we will try and get virt-builder images registered, with signs etc ready to go in sync with 7GA, making it much easier for people to get and consume these images on standalone virtualised environs. Send reports here, or to bugs.centos.org, but note: there is no cloud-init included as yet. I spoke with Sam Kottler earlier as well today and he's going to work on pushing that through soon. - KB -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc

4 7

[OT, partly]epel question
by Fred Smith 21 Jun '14

21 Jun '14

I've installed MATE desktop (and related packages) from epel on my C7 VM, just to see how it works on C7. The answer I've got is "not too well", but I fear I may have done something wrong. Before I go any further, is it not toally unreasonable to ask this here? or should I be banished to redhat bugzilla? I've got it to the point where when I log in I get top and bottom panels, and desktop wallpaper. But nothing is drawn in front of the wallpaper, and right-click context menu on the desktop doesn't do anything. Everything that I can access thru a panel icon, a panel menu, or a terminal seems to be working. I did log on epel IRC and talked with "wolfy" about it, but he didn't have any firm answers (several good suggestions, though). -- ---- Fred Smith -- fredex(a)fcshome.stoneham.ma.us ----------------------------- But God demonstrates his own love for us in this: While we were still sinners, Christ died for us. ------------------------------- Romans 5:8 (niv) ------------------------------

3 5

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

21 Jun '14

> > So in summary : I think we should continue to use CentOS-7/Final as the > main distro that everyone runs, and use the 7.YYMM to indicate the isos > set, with metadata inside the installed machine still reporting whatever > rhel point release it originated or maps to. Everything that has > happened in the past, stays intact - except the ISOS release is > announced as '7 1406 - rebuilt from RHEL 7.0 sources'. > Fairly lost now, doesn't take much I'll grant but there we go. In all the organisations I've ever worked at we've kept our own mirrors of each X.Y directory/step and then at some places kept snapshots of those per month by postfixing them in spacewalk with YYYYMM when cloning channels via cron job. Just referring to CentOS 5, 6 or 7 without the .Y is so vague as to be meaningless in any technical or patching discussion. -- Regards, Phil

1 0

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

21 Jun '14

Wading in late as usual. :^) Message: 28 > Date: Fri, 20 Jun 2014 11:35:08 +0100 > From: Karanbir Singh <mail-lists(a)karan.org> > Subject: Re: [CentOS-devel] CentOS 7 and release numbering > ... > So, personally - I think the community feedback was great, how badly we > communcated the idea was apareny and clear for everyone to see. And I > personally feel that a large chunk of the response was down to fear of > change in areas that we had never even imaged were going to change. I'm also assuming that my last email to this thread cleared all the > technical issues that people had brought up, if there are still some > outstanding now is a great time for people to raise those. > Not really, I think the idea was communicated fine but the motivations and the absolute technical requirements for deviating from upstream's format at the Core level rather than at the SIG level were never nailed down? It's because of the cloud images and the fact that a CVE fix isn't recorded into an release string? " > 2) 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, > which points at the latest images ); this is becoming more of an issue as the > cloud side of things grows, even within CentOS we've seen a massive increase in > uptake on that side and I am sure everyone sees that. " ...surely cloud images should be a product of the Cloud SIG and as to how those final releases or images (in their specific scenario) are named is entirely up to them? A SIG could eschew numbering all together in it's final product and, as was suggested earlier, perhaps even go for a release entitled CentOS: Constipated Chihuahua? People missing CVEs, other important updates or not bothering to update at all and then expecting support/help is just par for the course. No project such as a CentOS is out to educate people at such a fundamental level, you just have to politely point them in the right direction and hope they find the right page. We've all been there, seen that and "Stupid is as Stupid does" at the end of the day. I seem to be saying this a lot, but getting better at what we do should > never really be optional - and I definitely feel that the numbering > change allows us to do just that. > How can we make it even more aparent as to what we are trying to do ? > Given the code changes are apparently trivial to less than trivial, this is being done simply to obviate a direct link between RHEL 7.x and CentOS 7.x by calling it CentOS 7.YYMM, hence allowing CentOS to do other things without the baggage of being too closely coupled and the expectations that would bring from some users? > I will aim to deliver two sets of tree's today to buildlogs.centos.org, > one that targets a 7.0 release tag and another one that does 7.1406, > lets see if we can find, in using the 7.1406 metrics on what breaks and > how. We can then work backwards to fix the issues, and move the > conversation forward. > Might be able to do some testing with that next week. -- Regards, Phil

1 0

kpatch process
by Karanbir Singh 21 Jun '14

21 Jun '14

hi since we now have a GA kernel and a zero day update kernel, does someone want to have a go at creating the scripts / automation needed to deliver kpatch content ? - KB -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc

3 4

[PATCH] Added script to turn a git.centos.org repo into a source rpm, using these tools.
by Pat Riehecky 20 Jun '14

20 Jun '14

From: Pat Riehecky <riehecky(a)fnal.gov> --- into_srpm.sh | 173 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 1 files changed, 173 insertions(+), 0 deletions(-) create mode 100755 into_srpm.sh diff --git a/into_srpm.sh b/into_srpm.sh new file mode 100755 index 0000000..2e254c4 --- /dev/null +++ b/into_srpm.sh @@ -0,0 +1,173 @@ +#!/bin/bash -u +# +# Turn a centos git repo into a .src.rpm file +# +# Might want to drop this in ~/bin/ and chmod u+x it + +# +# License: GPLv3 +# +# Initial Author: Pat Riehecky <riehecky(a)fnal.gov> +# + +##################################################################### +usage() { + echo '' >&2 + echo "$0 [-hq] [-b branch] [-c shasum]" >&2 + echo '' >&2 + echo 'You need to run this from inside a sources git repo' >&2 + echo '' >&2 + echo ' -h: This help message' >&2 + echo ' -q: Suppress warnings' >&2 + echo '' >&2 + echo ' -b: specify a branch to examine' >&2 + echo " defaults to repo's current branch" >&2 + echo " NOTE: your repo will be set to this branch">&2 + echo '' >&2 + echo ' -c: specify a commit id' >&2 + echo " defaults to repo's current commit id" >&2 + echo " NOTE: your repo will be set to this commit">&2 + echo '' >&2 + echo " $0" >&2 + echo " $0 -b c7" >&2 + echo " $0 -b remotes/origin/c7" >&2 + echo " $0 -c 865ae5909b2b5d5fb37971b7ad7960f1fd5a5ffa" >&2 + echo " $0 -b c7 -c 865ae5909b2b5d5fb37971b7ad7960f1fd5a5ffa" >&2 + exit 1 +} + +##################################################################### + +QUIET=0 +COMMITHASH="" +BRANCH="" + +##################################################################### +# setup args in the right order for making getopt evaluation +# nice and easy. You'll need to read the manpages for more info +# utilizing 'while' construct rather than 'for arg' to avoid unnecessary +# shifting of program args +args=$(getopt -o hqb:c: -- "$@") +eval set -- "$args" + +while [[ 0 -eq 0 ]]; do + case $1 in + -- ) + # end of getopt args, shift off the -- and get out of the loop + shift + break + ;; + -q ) + # suppress warnings + QUIET=1 + shift + ;; + -c ) + # Use this commit id + COMMITHASH=$2 + shift + shift + ;; + -b ) + # Check this particular branch + BRANCH=$2 + shift + shift + ;; + -h ) + # get help + usage + ;; + esac +done + +if [[ ! -d .git ]] || [[ ! -d SPECS ]]; then + echo 'You need to run this from inside a sources git repo' + exit 1 +fi + +which return_disttag.sh >/dev/null 2>&1 +if [[ $? -ne 0 ]]; then + echo 'You need return_disttag.sh from centos-git-common in PATH' + exit 1 +fi + +which get_sources.sh >/dev/null 2>&1 +if [[ $? -ne 0 ]]; then + echo 'You need get_sources.sh from centos-git-common in PATH' + exit 1 +fi + +if [[ "x${BRANCH}" != 'x' ]]; then + if [[ $QUIET -eq 1 ]]; then + git fetch >/dev/null + git checkout ${BRANCH} >/dev/null + else + git fetch + git checkout ${BRANCH} + fi +fi + +if [[ "x${COMMITHASH}" != 'x' ]]; then + if [[ $QUIET -eq 1 ]]; then + git fetch >/dev/null + git checkout ${COMMITHASH} >/dev/null + else + git fetch + git checkout ${COMMITHASH} + fi +fi + +if [[ $QUIET -eq 1 ]]; then + get_sources.sh +else + get_sources.sh -q +fi + +if [[ $QUIET -eq 1 ]]; then + rpmbuild --define "%_topdir `pwd`" --define "%dist `return_disttag.sh -q`" -bs --nodeps SPECS/*.spec +else + rpmbuild --define "%_topdir `pwd`" --define "%dist `return_disttag.sh`" -bs --nodeps SPECS/*.spec +fi + + + +exit 1 + +# commit message contains white space, set IFS to \n +IFS=' +' + +if [[ "x${BRANCH}" != 'x' ]]; then + loglist=$(git log ${BRANCH} --pretty="%H|%s" | filter) + if [[ $? -ne 0 ]]; then + exit 1 + fi +else + loglist=$(git log --pretty="%H|%s" | filter) + if [[ $? -ne 0 ]]; then + exit 1 + fi +fi + +# flag for if nothing is found +FOUND=False +for entry in $loglist; do + FOUND=True + + pkg=$(echo ${entry} | cut -d' ' -f2) + # strip .src.rpm if present + nvr="${pkg%.src.rpm}" + if [[ ${WITHCOMMITHASH} -eq 1 ]]; then + shasum=$(echo ${entry} | cut -d'|' -f1) + echo "${shasum}:${nvr}.src.rpm" + else + echo "${nvr}.src.rpm" + fi +done + +if [ "${FOUND}" != "True" ] +then + warn "No SRPMs found" +fi + -- 1.7.1

2 2

RDO on CentOS
by Rich Bowen 20 Jun '14

20 Jun '14

Hi, I work with the RDO project - http://openstack.redhat.com/ - where we're trying to make OpenStack as easy as possible to deploy on CentOS, RHEL, Fedora, et al. Since CentOS is (at least anecdotally) the leading platform that we're seeing used with RDO, we're wondering what we can do to make RDO easier to consume on CentOS, and, more generally, what we can do to make OpenStack easier on CentOS. -- Rich Bowen - rbowen(a)redhat.com OpenStack Community Liaison http://openstack.redhat.com/

8 10

2 golang SRPMS fail to build
by Johnny Hughes 20 Jun '14

20 Jun '14

All, We are also trying to build the extras tree (which contains docker). Part of the build requirements are golang and its helpers. I am having issues getting 2 of the golang SRPMs to build .. can anyone see what I am doing wrong? Repo trying to build is c7-extras here: http://buildlogs.centos.org/c7-extras/ Specifically, trying to build golang* on x86_64 and these 2 keep failing x86_64: http://buildlogs.centos.org/c7-extras/golang-github-syndtr-gocapability/ http://buildlogs.centos.org/c7-extras/golang-github-gorilla-context/ All the other golang things seem to build OK. All the SRPMs are available in git.centos.org rpms: https://git.centos.org/project/rpms How to get SRPMs from git: http://wiki.centos.org/Sources Can anyone get a good x86_64 build of those 2 packages? Thanks, Johnny Hughes

3 3

Live Media issue with language other than English (help/fix wanted)
by Fabian Arrotin 20 Jun '14

20 Jun '14

Hi all, We received a bug report for the Live Media for Seven, and it was confirmed : http://bugs.centos.org/view.php?id=7217 So basically, selecting any other language than English makes anaconda/liveinst unhappy. I'm asking for help to find the root cause/issue/fix/patch, assuming people would be interested in helping to have a 7 release :-) I'm currently working on various things at the same time, but my initial '5 minutes search' leads me to multiple bug reports against anaconda version and liveinst. Consider for example that one : https://bugzilla.redhat.com/show_bug.cgi?format=multiple&id=1009278 It seems that some patches were added to anaconda to have it working correctly in the Fedora 20 Live ISO images. So if someone has enough time to browse/find particular patches included in anaconda to make it happy, feel free to browse the anaconda git (https://git.fedorahosted.org/cgit/anaconda.git/) and tell us what needs to be fixed/patched. Or if the issue is happening at another level (livecd-tools, or kickstart being used) , let us know too ! As a reminder : https://github.com/CentOS/sig-core-livemedia contains the kickstarts being used, and the tools we currently use to produce those live images are there : http://people.centos.org/arrfab/CentOS7/LiveMedia/RPMS/ , while SRPMS are there : http://people.centos.org/arrfab/CentOS7/SRPMS/ Happy hunting ! :-) -- Fabian Arrotin gpg key: 56BEC54E | twitter: @arrfab

2 1

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