September 2016 - devel - lists.centos.org

anaconda dependency calculation?
by Nicholas Byrne 04 Aug '25

04 Aug '25

Hi all, I'm trying to find a tool that calculates all dependencies for a specific package or group of packages for use with CentOS 5 (beta) with the intention of putting together a custom single CD build of CentOS 5. With CentOS 4 i used a python script that used the hdrlist module to find all dependencies which borrowed code from a number of sources. I've looked at yumdownloader and how it checks dependencies (using the --resolve option) but if i pass it the list of packages defined in say the Base and the Core yum groups which generally form an absolute minimal install i end up with about 200 packages. If i do a custom install (using beta 1 disks) and deselect everything i end up with over 300 packages. So i'm guessing anaconda calculates dependencies in a slightly different way, can anyone point me to files/code where i should be looking to find out? Thanks very much in advance for help Nick This e-mail is the property of Quadriga Worldwide Ltd, intended for the addressee only and confidential. Any dissemination, copying or distribution of this message or any attachments is strictly prohibited. If you have received this message in error, please notify us immediately by replying to the message and deleting it from your computer. Messages sent to and from Quadriga may be monitored. Quadriga cannot guarantee any message delivery method is secure or error-free. Information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. We do not accept responsibility for any errors or omissions in this message and/or attachment that arise as a result of transmission. You should carry out your own virus checks before opening any attachment. Any views or opinions presented are solely those of the author and do not necessarily represent those of Quadriga.

6 11

forums + portal for {lang}.centos.org sites
by Karanbir Singh 16 Aug '24

16 Aug '24

Hi, Earlier in the evening today Ralph, Fabian and I had a chat about the present state of the language subsites. This email sort of summarises the main issue ( s/w ). We seem to have run into a slight technical hitch with punbb/fluxbb. They dont support LDAP as a backend. And we had decided a few months back that all new rollouts must have ldap backend so we can rollin CentOS-DS / openldap based backend. So we need to look at alternatives, and since the primary focus of these international sites is going be forums : Here is a shortlist ( if there is anything else that people are aware of, please add to this list ) - phpBB - SMF - Fudforum - phorum - fluxbb Requirements: - Must be able to scale ( couple of hundred thousand msgs ) - Must be able to handle ldap auth ( if it cant, whats involved in writing the ldap-auth portion ) - Must address the specific requirements raised by the present www.centos.org forum users ( Can you please fill this section in ? ) - Must support all languages we need ( pure utf8 support would be good ) - Secure - Skin'able Nice to have: - Capable of running multiple instances from a single deployment - responsive community :D Things we will need to do: - Decide on what s/w to use. - Give the ArtWork people enough time to get the look & feel sorted. - Migrate newbb forums from www.centos.org to $system ( hey, english is a language too :D ). - Migrate fr.centos.org into the final s/w - setup {de/es/ja/it/pt_br}.centos.org Actions: Ralph and Fabian are going to work on setting up a test ldap server, once that is online we will then start by installing into our test-vm-farm the various s/w to eval them. If anyone would like to help, please feel free to jump right in. I'll setup a wiki page for this issue, which might be a good place to track progress. -- Karanbir Singh : http://www.karan.org/ : 2522219@icq

22 81

NFV SIG - update
by Dave Neary 30 May '17

30 May '17

Hi, There has been a recent resurgence of interest in the NFV SIG, and in the interest of keeping the momentum going, I would like to step aside as SIG char, and recommend that Tom Herbert take over. Tom has taken on the packaging and building of VPP and DPDK-accelerated OVS for OPNFV, and has been active in the SIG in recent weeks, and I think he will help add the structure that has been sorely lacking from me in recent months. I'm not sure what the process is for replacing a SIG chair - can someone let us know, please? Thanks, Dave. -- Dave Neary - NFV/SDN Community Strategy Open Source and Standards, Red Hat - http://community.redhat.com Ph: +1-978-399-2182 / Cell: +1-978-799-3338

4 4

Openshift Origin Containers for v1.2.1 and v1.3 on container pipeline.
by Mohammed Ahmed 07 Oct '16

07 Oct '16

Hi, We currently have openshift origin containers being delivered through the Container Pipeline. However, with the release of openshift origin 1.3, we have to consider how we are going to deliver containers for v1.2.1 and v1.3. Currently, the dockerfiles basically do a yum install origin[1] and other origin packages. This could possibly result in the latest origin rpms being used even in 1.2.1 containers. We need to consider how we are going to differentiate the versions. Even if there aren't any updates to 1.2 containers on toe repos, its still possible the containers might get rebuilt from other triggers, such as base image rebuilds and so on. KB, Troy Dawson, thoughts? Others are welcome to chime in as well. [1] https://github.com/openshift/origin/blob/release-1.2/images/origin/Dockerfi… -- *Mohammed Zeeshan Ahmed* Associate Software Engineer, Redhat Developers Team (Devtools) http://mohammedzee1000.wordpress.com RED HAT | DIFFERENT FOR THE SAKE OF BETTER TECHNOLOGY Find out why every airline, telecom, commercial bank, healthcare, and financial data services company in the Fortune 500 relies on Red Hat. Trusted | Red Hat <https://www.redhat.com/en/about/trusted>

4 6

Ceph 10.2.3 packages
by Mohammed Naser 29 Sep '16

29 Sep '16

Hi everyone, Ceph has released their 10.2.3 packages a few hours ago and the packages cover many fixes including an important one that blocks upgrades from Hammer for OSDs which had their placement group numbers changed. http://tracker.ceph.com/issues/16672 This is included in the new 10.2.3 release and I would like to know if we can get those packages into the storage SIG. I am also offering my help if needed to do the work required to get it done, as it's pretty important for us to continue with the upgrades of our Ceph cluster. Thanks! Mohammed

4 6

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

28 Sep '16

Hello, It's time for our weekly PaaS SIG sync-up meeting Time: 1700 UTC - Wedensdays Date: Today Wedensday, 28 September 2016 Where: IRC- Freenode - #centos-devel Agenda: - OpenShift Current Status -- rpms -- Documentation -- Automated testing -- images / image building - Open Floor

1 0

[Cloud SIG] Reminder: test day this week (Sept 29, 30)
by Rich Bowen 27 Sep '16

27 Sep '16

Reminder: This Thursday and Friday we will be testing the OpenStack Newton RC packages for CentOS - https://www.rdoproject.org/testday/newton/rc/ Please try to find a few hours on Thursday and/or Friday to drop by #rdo on the Freenode IRC network, and give RDO a spin, to help make this the best version of RDO OpenStack yet. --Rich -- Rich Bowen - rbowen(a)redhat.com RDO Community Liaison http://rdoproject.org @RDOCommunity

1 0

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

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

Origin 1.3 is in testing
by Troy Dawson 19 Sep '16

19 Sep '16

Hello, OpenShift Origin 1.3 has been released upstream. We have the corresponding origin 1.3 and openshift-ansible rpms in our PAAS openshift origin testing repo. Please test before our Paas SIG meeting on Wedensday, Sept 21. If there are no blockers at the meeting, we will release it. - yum install centos-release-openshift-origin (If you haven't done this already) - yum --enablerepo=centos-openshift-origin-testing clean all - yum --enablerepo=centos-openshift-origin-testing list origin\* openshift\* - yum --enablerepo=centos-openshift-origin-testing install origin origin-clients (or whatever you need to install for testing) Happy Testing Troy

1 0

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

16 Sep '16

On 09/16/2016 09:36 AM, Christopher Covington wrote: > If one wanted to install openstack on AArch64 CentOS 7.2 AltArch, are > Marcin's repositories at Linaro still fresh? Or is there something on > centos.org now? Yes, that's still the proper place for now. The current plan is to have aarch64 be natively supported in RDO when Newton comes out in a couple weeks. There are no plans to do anything with mitaka for aarch64 since newton is so close. -- Jim Perrin The CentOS Project | http://www.centos.org twitter: @BitIntegrity | GPG Key: FA09AD77

1 0

Format for the CentOS (openshift) origin rpm
by Troy Dawson 16 Sep '16

16 Sep '16

Hi, I've been debating this all week and decided it's probably better as a community decision than just my own. Problem: The current source rpm for origin is generated using tito on the origin git repo. The biggest problem with this is the tarball is generated on the fly and sortof encorporated into the spec file. That makes it hard for others to duplicate the src.rpm and/or make patches for it. If I were an outsider (not on the openshift team) and making an rpm for Fedora/EPEL, I wouldn't do this. I would grab the released tarball from Github and build my spec file around that. Solution 1: Keep things the same. Do others really care that they can't duplicate the src.rpm without tito, as long as they can recompile it? Solution 2: Create a origin spec file that uses the tarball from Github. I've already done this. It works quite well. But it does involve some manual spec file editing. Troy p.s. I am totally fine either way. The only reason I've been debating this is because I keep having issues with tito making the whole src.rpm.

4 3

[Cloud SIG] CentOS Cloud Sig minutes
by Rich Bowen 15 Sep '16

15 Sep '16

We had a very brief meeting today. The transcript from that meeting is here: https://www.centos.org/minutes/2016/september/centos-devel.2016-09-15-15.00… In particular, I want to draw attention to one item: CBS (the CentOS community build system) is undergoing planned maintenance on October 10th, and so there will be downtime that day. -- Rich Bowen - rbowen(a)redhat.com RDO Community Liaison http://rdoproject.org @RDOCommunity

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel September 2016