devel

devel@lists.centos.org

1 participants
4657 discussions

cosmetic: missing vendor tag
by Leon Fauster 27 Sep '16

27 Sep '16

While making some sanity checks, I noticed that ... has no vendor entry ... # curl -s -O "http://mirror.centos.org/centos/6/os/x86_64/Packages/certmonger-0.77.5-2.el…" # rpm -qpi certmonger-0.77.5-2.el6.x86_64.rpm Name : certmonger Relocations: (not relocatable) Version : 0.77.5 Vendor: (none) Release : 2.el6 Build Date: Mo 09 Mai 2016 17:09:47 CEST Install Date: (not installed) Build Host: CentOS6-Builder.centos.org Group : System Environment/Daemons Source RPM: certmonger-0.77.5-2.el6.src.rpm Size : 2588066 License: GPLv3+ Signature : RSA/SHA1, Do 12 Mai 2016 12:49:49 CEST, Key ID 0946fca2c105b9de URL : http://certmonger.fedorahosted.org Summary : Certificate status monitor and PKI enrollment client Description : Certmonger is a service which is primarily concerned with getting your system enrolled with a certificate authority (CA) and keeping it enrolled. -- LF

1 0

CentOS 6 images bug
by Mohammed Naser 27 Sep '16

27 Sep '16

Hi everyone, We've just finished setting up CD to get images shipped into our public cloud with more automation and noticed that the link pointing from the unversioned file to the latest release is not properly done for CentOS 6. http://cloud.centos.org/centos/6/images/ If you notice, CentOS-6-x86_64-GenericCloud.qcow2 has a date of 2016-07-29 which matches the CentOS-6-x86_64-GenericCloud-1607.qcow2 release. However, there is a newer release which is CentOS-6-x86_64-GenericCloud-1608.qcow2 It seems this problem does not exist for CentOS 7, but perhaps someone forgot to point things over when they were done! Thank you, Mohammed

2 2

Origin 1.3 on CentOS testing
by Christoph Goern 27 Sep '16

27 Sep '16

Hey all, yesterday and today I had a few runs to install and extend Origin 1.3 on CentOS. All seem to work pretty well, I did different permutations of masters/nodes all based on this inventory file at [1] and using openshift-ansible master to do the install. Infrastructure was Vagrant with the latest CentOS box, see [2] for known issues ;) //G [1] https://github.com/goern/my-openshift-origin/blob/centos7/inventory.ini [2] https://seven.centos.org/2016/09/updated-centos-vagrant-images-available-v1… -- Principal Software Engineer - Systems Design & Engineering Mobile: +49 171 2801345 Red Hat GmbH, http://www.de.redhat.com/, Sitz: Grasbrunn, Handelsregister: Amtsgericht München, HRB 153243, Geschäftsführer: Charles Cachera, Michael Cunningham, Michael O'Neill, Eric Shander

2 1

How to package repo files for Long/Short Term Maintenance versions?
by Niels de Vos 27 Sep '16

27 Sep '16

Hi, In the Storage SIG we provide different versions of Gluster. The new upstream release schedule[0] defines two different types of releases: a. Long Term Maintenance - gets updates for ~12 months b. Short Term Maintenance - gets updates for ~3 months The actual time depends a little on how releases are keeping their schedule (a release every 3 months). There are two Long Term Maintenance versions active at a time. The Short Term Maintenance releases provide early access to new features, and are recommended only for early adopters and users who do not mind upgrading their storage environment everye 3 months. This makes for an interesting packaging problem. We would like our users to be able to install the Gluster packages with a command as simple as this: # yum install centos-release-gluster # yum install glusterfs-server Users should not need to care (or know) about the actual version they are installing. Currently Gluster 3.8 is provided by the c-r-gluster38 package, with a "Provides: centos-release-gluster = 3.8". When I add a new c-r-gluster39 package, with a similar "Provides:", I do not want users to get the 3.9 version by default. Users should get the Long Term Maintenance versions, and only opt-in on the Short Term Maintenance version. But, on the other hand, an installed 3.9 version should be usable for other SIGs that depend on Gluster (like the Virt SIG for oVirt). Currently I am thinking to do the "Provides:" like: # Users can install centos-release-gluster to get the latest, but we # do not want to have 3.9 (Short Term Stable) to be selected when # users do install the virtual centos-release-gluster package. Provides: centos-release-gluster = 0.3.9 Conflicts: centos-release-gluster < 0.3.9 Obsoletes: centos-release-gluster < 0.3.9 Existing (all Long Term Stable) release packages do not have the 0. prefix: # Users can install centos-release-gluster to get the latest Provides: centos-release-gluster = 3.8 Conflicts: centos-release-gluster < 3.8 Obsoletes: centos-release-gluster < 3.8 We do not want automatic updating/replacing of the release package in any case (might need manual intervention for major releases). The current approach works sufficiently well. Except for the potential issue where other SIGs/projects depend on 'centos-release-gluster >= 3.8'. This will not work with the 3.9 release package. I am hoping others can suggest a more elegant solution that addresses all of these use-cases. Many thanks! Niels 0. https://www.gluster.org/community/release-schedule/

1 0

devtoolset 4.1
by Michael Madden 22 Sep '16

22 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 22 Sep '16

22 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

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