devel

devel@lists.centos.org

10 participants
4625 discussions

devtoolset 4.1
by Michael Madden 23 Sep '16

23 Sep '16

I noticed that devtoolset 4.1 was available at http://buildlogs.centos.org/centos/6/sclo/x86_64/rh/devtoolset-4/. Howeever it's not available on the official mirrors at http://mirror.centos.org/centos-6/6/sclo/x86_64/rh/devtoolset-4/. Any idea when devtoolset-4 will be available for general release. I'd be glad to help building or testing devtoolset 4.1. Thanks.

2 2

Re: [CentOS-devel] VPAT for centos 7 - section 508 compliance statement
by Jason Pyeron 23 Sep '16

23 Sep '16

Can my jpyeron user be blessed to update the WIKI, so a CentOS 6 and CentOS 7 VPAT can be posted? > -----Original Message----- > From: Jason Pyeron [mailto:jpyeron@pdinc.us] > Sent: Friday, October 30, 2015 14:08 > To: 'centos-devel(a)centos.org' > Subject: VPAT for centos 7 - section 508 compliance statement > > I am working on getting Centos 7 approved for use at a > federal agency, RHEL is already approved for use in production. > > One of the blockers I hit is, "Does the vendor provide a VPAT?" > > Does the attached look right? Where should this be posted? > > P.S. where is the git repo for the website, I only see bugs > in https://git.centos.org/project/websites . > > -Jason > > -- > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- > - - > - Jason Pyeron PD Inc. http://www.pdinc.us - > - Principal Consultant 10 West 24th Street #100 - > - +1 (443) 269-1555 x333 Baltimore, Maryland 21218 - > - - > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- >

1 1

CentOS OpenShift Origin 1.3 rpm's to be relesed Sept. 26
by Troy Dawson 22 Sep '16

22 Sep '16

Hi, We are currently planning on releasing the CentOS origin 1.3 rpm's on Monday, September 26. The rpm's are created and have passed all of our tests, but we want to give users a chance to get ready for the update. Some users have expressed concerns about not being able to control when OpenShift Origin get's updated. For this we have created openshift-excluder [1]. Although the excluder has gone through many tests, it was not released or documented until today. We wanted to give people a chance to be prepared for their OpenShift Origin update, so we have delayed the 1.3 origin release until Monday. If you want the install origin 1.3 before September 26, you can do the following. - yum install centos-release-openshift-origin -- (If you haven't done this already) - yum --enablerepo=centos-openshift-origin-testing install origin origin-clients -- (or whatever you need to install) On a related note, the openshift-ansible installer won't be released until at least the 26th. We are having issues with some variables. Troy [1] - https://wiki.centos.org/SpecialInterestGroup/PaaS/OpenShift-Origin-Control-…

1 0

Control when OpenShift get's updated on CentOS
by Troy Dawson 22 Sep '16

22 Sep '16

Hello, Many people are concerned about OpenShift Origin being updated automatically when they do their normal system updates. This is very understandable. OpenShift is more like an infrastructure than a single program running. We have created openshift-excluder. It will exclude all openshift packages from being updated via yum. (If compiled on fedora, it does the same for dnf) How does it work. 1- yum -y install openshift-excluder * All OpenShift Origin packages are now excluded. 2 - yum -y update * All non-openshift packages are updated 3 - openshift-excluder unexclude * OpenShift Origin packages are no longer excluded. 4 - yum -y update * All packages, including openshift origin packages, are updated 5 - openshift-excluder exclude * All OpenShift Origin packages are excluded again. When the openshift-excluder rpm is completely removed, it will un-exclude openshift packages. Download by hand or grab source: https://cbs.centos.org/koji/packageinfo?packageID=4461 Documentation for use: https://wiki.centos.org/SpecialInterestGroup/PaaS/OpenShift-Origin-Control-… Troy

1 0

Code complexity survey
by Vard Antinyan 21 Sep '16

21 Sep '16

Dear centos developers, We have undertaken a task to assess code complexity triggers and generate recommendations for developing simple and understandable code. Our intension is to share the results with you, developers, so everyone can learn the triggers behind complex software. We need your help for rigorous results. My request to you is - if you get 5-10 min. time, would you please consider to answer the questions of this survey on code complexity? https://goo.gl/forms/h9WXZ8VSEw7BUyHg1 You are welcome to learn preliminary results through this link: https://www.facebook.com/SoftwareCodeQuality/photos/?tab=album&album_id=163… The results will be shared in a public webpage and everyone possible will be invited to learn and discuss them. Your knowledge and experience is vital for achieving substantial and generalizable results, and your effort is much appreciated! Sincerely Vard Antinyan PhD candidate in University of Gothenburg, Sweden Tel: 0046317725707

1 0

CentOS PaaS SIG meeting (2016-09-21)
by Troy Dawson 21 Sep '16

21 Sep '16

Hello, It's time for our weekly PaaS SIG sync-up meeting Time: 1700 UTC - Wedensdays Date: Today Wedensday, 21 September 2016 Where: IRC- Freenode - #centos-devel Agenda: - OpenShift Current Status -- rpms --- Is 1.3 rpms ready for release? --- Is the corresponding openshift-ansible ready for release? -- Documentation -- Automated testing -- images / image building - Multi-Arch - Open Floor Minutes from last meeting: https://www.centos.org/minutes/2016/september/centos-devel.2016-09-14-16.59…

1 0

Installing Openshift Origin on CentOs7
by Syam G Krishnan 21 Sep '16

21 Sep '16

Hi all, Today I have successfully installed Openshift Origin on CentOS 7 using `atomic-openshift-installer` which is mentioned on, https://wiki.centos.org/SpecialInterestGroup/PaaS/OpenShift-Quickstart Got hit by 3 errors: 1. No OpenShift version available workaround: $ sed -i '28s/openshift-enterprise/origin/' ~/.config/openshift/installer.cfg.yml $ sed -i '29s/3.3/1.2/' ~/.config/openshift/installer.cfg.yml 2. dict object has no attribute 'stdout' workaround: $ sed -i '195s/g_master_mktemp.stdout/g_master_mktemp/' /usr/share/ansible/openshift-ansible/playbooks/common/openshift-master/config.yml 3. dict object has no attribute 'stdout' workaround: $ sed -i '153s/mktemp.stdout/mktemp/' /usr/share/ansible/openshift-ansible/playbooks/common/openshift-node/config.yml Cheers, -- Syam G Krishnan GPG 4096R/FBB26E60 Red Hat India Pvt Ltd

2 1

Gluster-Swift packaging and repository dependencies
by Niels de Vos 21 Sep '16

21 Sep '16

Hi, We'd like to place Gluster-Swift in the Storage SIG. Users can install (OpenStack) Swift as a pretty much stand-alone (without OpenStack) environment. It is possible to use Gluster in the backend, and the project that enables this is called gluster-swift. The difficulty is that gluster-swift depends on the Swift packages from OpenStack. And of course these packages have yet an other set of dependencies... The way I think is most practical for users that want to install Gluster-Swift, is the following: - create a (Storage SIG) repository that contains glusterfs-swift - create a new centos-release-gluster-swift package (crgs) - have crgs depend on centos-release-gluster for a recent glusterfs-fuse - have crgs depend on centos-release-openstack for other swift bits Currently gluster-swift only works with OpenStack Kilo. Additional work is needed to have it work with more current OpenStack versions. Do others see this as a good way forward? Alternative solutions are most welcome too :) Thanks, Niels

2 2

Re: [CentOS-devel] [Arm-dev] [rdo-list] next steps for altarch with ceph and openstack
by Marcin Juszkiewicz 20 Sep '16

20 Sep '16

W dniu 19.09.2016 o 19:25, Christopher Covington pisze: > (There is also a now-stale people.linaro.org link in the archives > which I had been trying and failing to use.) Recreated directories and added README.txt from Linaro website in case someone gets to people.linaro.org area.

1 0

Status report: packaging VirtualBox Guest Additions
by Laurentiu Pancescu 20 Sep '16

20 Sep '16

Hi there, I've started to work on packaging the VirtualBox Guest Additions. Unfortunately, the upstream build process doesn't work on CentOS Linux 6.8 and 7.2. On 7.2 gcc fails on <linux/compiler.h> from the kernel-devel package (log attached as vbox-ga-c7.txt). I think this might be GCC bug #49718, fixed in January 2014 in the 4.9 branch. [1] With RHEL 7.3 in beta, would a backport of the fix to Red Hat's gcc-4.8 still be possible in a reasonable timeframe? Should I file a bug report against gcc on the CentOS tracker? On 6.8 the compilation stops with an error later, while trying to build vboxvideo (log attached as vbox-ga-c6.txt). On #vbox-dev I was told that this directory requires at least kernel 3.11 to build, and it shouldn't even try. There seems to be no ./configure option for excluding vboxvideo from the build process. Their advice is to install the Guest Additions in a VM using their installer on the .iso image they provide. This should leave all the necessary sources and Makefiles for building the kernel modules in /usr/src, which I could use for the RPMs instead of the original source (the source that their installer creates is able to detect what the guest supports, and will only build what's possible). As far as SRPMs go, this might be somewhat unusual... We'd need to do this for every new version, and we have to look into how package upgrades and removals could work. Regards, Laurențiu [1] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=49718

5 11

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