devel

devel@lists.centos.org

2 participants
4591 discussions

SIG Meeting notes
by Karanbir Singh 12 Jun '18

12 Jun '18

hi everyone, Can I request that when you are attending or running a SIG meeting in #centos-devel, please use the #info command to the bot to record interesting events/objects/releases/information - these can then be collected and used for the Newsletter that Rich is putting together. It would dramatically increase the audience you can get this information out to as well. Regards and thanks, -- 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

1 0

[centos-devel] Ceph Storage SIG packages for Ceph Mimic
by Tobias Urdin 12 Jun '18

12 Jun '18

Hello Ceph Storage SIG, I'm researching support for Ceph Mimic for implementations in OpenStack projects. Is anybody working on CentOS packages for Ceph Mimic? i.e not the upstream EL7 packages on download.ceph.com Best regards

4 7

Status of Ansible within CentOS 7 and SIGs
by Thomas Oulevey 09 Jun '18

09 Jun '18

Hello Folks, Starting with CentOS 7.5, ansible package will no be available in CentOS -extras anymore as Red Hat decided to ship Ansible on a separate channel. Looking at ansible package in CBS [1] I see that Troy, Fabian, Sandro and Alan are rebuilding it. Can we get better at that task ? My proposal would to initiate a rebuild of the new Ansible channel[2](within the Config Management SIG) and follow a better release cycle. What do you think ? Would it be a solution from all SIG, or should we continue to ship Ansible within each SIG ? I would be happy to contribute the rebuild/debranding of existing source rpms (all available versions) if we all agree. Please note that EPEL is shipping again Ansible 2.5 as it was removed from Extras [3] -- Thomas Oulevey [1]: http://cbs.centos.org/koji/packageinfo?packageID=1947 [2]: http://ftp.redhat.com/pub/redhat/linux/enterprise/7Server/en/Ansible/SRPMS/ [3]: https://koji.fedoraproject.org/koji/packageinfo?packageID=13842

8 14

[Cloud SIG] Rocky Milestone 2 RDO Test Days June 14-15
by Rain Leander 07 Jun '18

07 Jun '18

Who’s up for a rematch? Rocky Milestone 2 is here and we’re ready to rumble! Join RDO [0] on June 14 & 15 for an awesome time of taking down bugs and fighting errors in the most recent release [1]. We certainly won’t be pulling any punches. Want to get in on the action? We’re looking for developers, users, operators, quality engineers, writers, and, yes, YOU. If you’re reading this, we think you’re a champion and we want your help! We’ll have packages for the following platforms: * RHEL 7 * CentOS 7 You’ll want a fresh install with latest updates installed so that there’s no hard-to-reproduce interactions with other things. We’ll be collecting feedback, writing up tickets, filing bugs, and answering questions. Even if you only have a few hours to spare, we’d love your help taking this new version for a spin to work out any kinks. Not only will this help identify issues early in the development process, but you can be the one of the first to cut your teeth on the latest versions of your favorite deployment methods like TripleO, PackStack, and Kolla. Interested? We’ll be gathering on #rdo (on Freenode IRC) for any associated questions / discussions, and working through the “Does it work?” tests [2]. Like Rocky said, “The world ain’t all sunshine and rainbows,” but with your help, we can keep moving forward and make the RDO world better for those around us. Hope to see you on the 14th & 15th! [0] https://www.rdoproject.org/ [1] https://www.rdoproject.org/testday/ [2] https://www.rdoproject.org/testday/tests/ -- K Rain Leander OpenStack Community Liaison Open Source and Standards Team https://www.rdoproject.org/ http://community.redhat.com

1 0

SIG Day @ CERN, October 18th
by Rich Bowen 06 Jun '18

06 Jun '18

Dear SIG members, As you've no doubt seen, we have a CentOS Dojo scheduled at CERN on October 19th. CERN has also generously offered us a meeting room on the day before, Thursday, October 18th, for SIG meetings. If your SIG is interested in taking advantage of this opportunity, please contact me with: * SIG Name * Primary contact for coordination * List of those likely to be in attendance Thanks. -- Rich Bowen - rbowen(a)redhat.com @CentOSProject // @rbowen 859 351 9166

1 0

Untag golang-1.9.4 from Centos PaaS Sig 3.7 Candidate Repo
by Daniel Comnea 06 Jun '18

06 Jun '18

I'll take care Scott in the next few hours, will update once is done. ---------- Forwarded message ---------- > From: Scott Dodson <sdodson(a)redhat.com> > To: Troy Dawson <tdawson(a)redhat.com>, "The CentOS developers mailing > list." <centos-devel(a)centos.org> > Cc: Steve Kuznetsov <skuznets(a)redhat.com> > Bcc: > Date: Mon, 4 Jun 2018 11:06:44 -0400 > Subject: [CentOS-devel] Untag golang-1.9.4 from Centos PaaS Sig 3.7 > Candidate Repo > Our CI team makes use of the centos paas sig repos and they've noticed > that we've got golang-1.9 tagged into the 3.7 repo where as Origin 3.7 > should be built with golang 1.8. > > Can we get golang-1.9.2-4.el7 untagged from paas7-openshift-origin37-candidate > ? > > _______________________________________________ > CentOS-devel mailing list > CentOS-devel(a)centos.org > https://lists.centos.org/mailman/listinfo/centos-devel > >

3 2

how to disable nscd and nm-dispatcher logs from centos console.
by Veetil, Vyshnav 06 Jun '18

06 Jun '18

Hi, After upgraded to CentOS7.4 we are getting some logs printed on the console. nscd logs are getting printed after executing the command service nscd restart. Nm-dispatcher logs are getting printed on the console after every restart. Can you please suggest any solution for disabling this logs. NetworkManager-1.8.0-9.el7.x86_64 nscd-2.17-196.el7.i686 Please find the attached config files using for nscd and NetworkManager.(/etc/NetworkManager/NetworkManager.conf) ----------------------------------------------------------------------------------------------------------------- Also please find the nscd logs getting printed on the console after executing service nscd restart nscd: 4220 monitoring file '/etc/passwd' nscd: 4220 monitoring directory '/etc/(2) nscd: 4220 monitoring file '/etc/group'(3) nm-dispatcher logs are getting printed on the console after every reboot. localhost login:nm-dispatcher:req:1 'hostname':new request (4 scripts) nm-dispatcher: req:2 'up' [eth0]: new request (4 scripts) nm-dispatcher: req:2 'up' [eth0]: start running ordered scripts... nm-dispatcher: req:3 'connectivity-change': new request (4 scripts) nm-dispatcher: req:4 'hostname':new request (4 scripts) nm-dispatcher: req:4 'hostname':start running ordered scripts... Can you please provide a solution for disabling this logs from console ? Thanks and Regards, Vyshnav

1 0

Untag golang-1.9.4 from Centos PaaS Sig 3.7 Candidate Repo
by Scott Dodson 04 Jun '18

04 Jun '18

Our CI team makes use of the centos paas sig repos and they've noticed that we've got golang-1.9 tagged into the 3.7 repo where as Origin 3.7 should be built with golang 1.8. Can we get golang-1.9.2-4.el7 untagged from paas7-openshift-origin37-candidate ?

1 0

docker and podman packages should be part of virt7-container-common-candidate or extra repos.
by Praveen Kumar 04 Jun '18

04 Jun '18

Hi, I can see docker packages are part of virt7-container-common-candidate[0] and also extra[1] repo same with podman but on the virt repo side docker packages are not updated to latest version and for podman extra repo doesn't have latest packages. It becomes really confusing what repo to chose when installing those packages and if we include both repos then there is conflict:( [0] https://cbs.centos.org/repos/virt7-container-common-candidate/x86_64/os/Pac… [1] http://mirror.centos.org/centos/7/extras/x86_64/Packages/ ``` Transaction couldn't start: 10:06:29 file /usr/libexec/cni/bridge conflicts between attempted installs of containernetworking-plugins-0.7.0-4.gitb51d327.el7.x86_64 and containernetworking-cni-0.6.0-4.el7.x86_64 10:06:29 file /usr/libexec/cni/dhcp conflicts between attempted installs of containernetworking-plugins-0.7.0-4.gitb51d327.el7.x86_64 and containernetworking-cni-0.6.0-4.el7.x86_64 ``` -- Praveen Kumar http://fedoraproject.org/wiki/User:Kumarpraveen http://fedoraproject.org/ http://kumar-pravin.blogspot.com

1 0

__gthrw___pthread_key_create in devtoolset-6
by dacav 01 Jun '18

01 Jun '18

Hello good people I'm packaging for CentOS 7 a piece of proprietary software. The software is written in C++14, so I need to use the devtoolset to run it. Unfortunately I'm having some issues with linking of pthreads. First off I'm getting this warning: In file included from /opt/rh/devtoolset-6/root/usr/include/c++/6.3.1/x86_64-redhat-linux/bits/gthr.h:148:0, from /opt/rh/devtoolset-6/root/usr/include/c++/6.3.1/ext/atomicity.h:35, from /opt/rh/devtoolset-6/root/usr/include/c++/6.3.1/bits/ios_base.h:39, from /opt/rh/devtoolset-6/root/usr/include/c++/6.3.1/ios:42, from /opt/rh/devtoolset-6/root/usr/include/c++/6.3.1/ostream:38, from /opt/rh/devtoolset-6/root/usr/include/c++/6.3.1/iostream:39, from src/logd-main.cpp:23: /opt/rh/devtoolset-6/root/usr/include/c++/6.3.1/x86_64-redhat-linux/bits/gthr-default.h:236:10: warning: 'int __gthrw___pthread_key_create(pthread_key_t*, void (*)(void*)) throw ()' used but never defined __gthrw2(__gthrw_(__pthread_key_create), …Where the problematic line is a `#include <iostream>`. Then of course it gets problematic upon linking time objs/intel-debug/src/logd-main.o:(.rodata+0x8): undefined reference to `__gthrw___pthread_key_create(unsigned int*, void (*)(void*))' collect2: error: ld returned 1 exit status I searched around on the Web: the classic suggestion (from stackoverflow and such) will be to check for the `-pthread` flag to be present at compilation. This is of course tackled already. Since the compilation is working in other contexts, I started to wonder if this is some known problem in CentOS + Devtoolset: did someone have similar issues? Perhaps there's something wrong in how I do the build. Is there in CentOS some software which is using Devtoolset which I could take as example for my build? Thanks in advance for any suggestion :)

2 3

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