devel May 2018

devel@lists.centos.org

32 participants
39 discussions

SRPMS for AltArch (more specifically aarch64 kernel)
by Dominique Martinet 22 Aug '18

22 Aug '18

Hi folks, I've asked on IRC and have been pointed to this list. I can't seem to find this particular source rpm: kernel-aarch64-4.5.0-29.el7.src.rpm which is what is pointed by `rpm -qi kernel` on my system. Are these supposed to be available anywhere? Looking on google I only see one for an older release in someone's centos user/people page, but I can't seem to find these in any repo. The debuginfo are properly here but it's good to have sources as well when messing around with low level stuff :) Cheers and thanks for the hard work, -- Dominique Martinet

3 8

Latest podman installation broken in CentOS
by Praveen Kumar 13 Jun '18

13 Jun '18

Hi, Looks like there might be issue with spec file of the podman for CentOS because of wrongly put the "Requires" version for *conmon* but this is what I am getting now when trying to install podman :( $ sudo yum install podman [...] --> Finished Dependency Resolution Error: Package: podman-0.5.3-7.gitc54b423.el7.x86_64 (virt7-container-common-candidate) Requires: conmon >= 2:1.10.0-3.gitb0f6d98 Installed: conmon-1.11.0-1.git55a3daa.el7.x86_64 (@virt7-container-common-candidate) conmon = 1.11.0-1.git55a3daa.el7 You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest -- Praveen Kumar http://fedoraproject.org/wiki/User:Kumarpraveen http://fedoraproject.org/ http://kumar-pravin.blogspot.com

3 4

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

__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

CentOS Dojo in Sao Paulo, late July
by Rich Bowen 30 May '18

30 May '18

Community member Leo Vaz is putting together a CentOS Dojo for a day or two before the upcoming OpenStack Days Brazil event, which is scheduled for July 27-28. Details for this event are coming together here: https://wiki.centos.org/Events/Dojo/SaoPaulo2018 If you are likely to be in the area during that time frame, and are interested in speaking at a CentOS event, please indicate your availability in the etherpad linked from the above page. Topics can be anything related to CentOS, or projects that build on top of CentOS such as the CentOS SIGs. If you have further questions, place contact Leo at leonardo.vaz(a)gmail.com -- Rich Bowen - rbowen(a)redhat.com @CentOSProject // @rbowen 859 351 9166

1 1

CentOS community newsletter - Call for content
by Rich Bowen 29 May '18

29 May '18

As part of our community outreach effort, we are rebooting the 'CentOS Pulse' newsletter, which was discontinued about 8 years ago. The purpose of this newsletter is to provide a high-level update on what CentOS is up to, to the peripheral audience - including the tech press - who are less connected with the daily life of the project. If your SIG would like to provide an update, or if you have something else you'd like to share with this audience, please do so here: https://wiki.centos.org/Newsletter/1801 , where I am drafting the newsletter. Or email me directly with what you'd like to put in there. We are targeting Tuesday, June 5th (generally, the first Tuesday of each month) for publication, so you have a few weeks. For historical context, you can read back-issues at https://wiki.centos.org/Newsletter/ to see what these used to look like. -- Rich Bowen - rbowen(a)redhat.com @CentOSProject // @rbowen 859 351 9166

1 1

steps to create efiboot.img in centos
by Veetil, Vyshnav 25 May '18

25 May '18

Hi , Can you please explain the steps to create the efiboot.img in centos. Thanks and Regards, Vyshnav

2 1

[Infra] - planned outage : {bugs, fr, status}.centos.org
by Fabian Arrotin 24 May '18

24 May '18

Due to a hardware replacement, we'll have to power down the hypervisor hosting several VMs, including the ones used for the following impacted services : * https://bugs.centops.org * https://status.centos.org * https://fr.centos.org Hardware maintenance is scheduled for """"Thursay May 24th, 12:00 pm UTC time"""". You can convert to local time with $(date -d '2018-05-24 12:00 UTC') Root cause : a HDD in the array used to host the VMs failed, and there is no hot-swap capabilities, so full "power off" is required to replace the failed HDD and then start the rebuild operation. That means that those services (already impacted) will be slower during the rebuild operation, but at least reachable Thanks for your comprehending and patience. on behalf of the Infra team, -- Fabian Arrotin The CentOS Project | https://www.centos.org gpg key: 56BEC54E | twitter: @arrfab

1 0

Re: [CentOS-devel] [CentOS-announce] CEEA-2018:1670 CentOS 7 kmod-redhat-megaraid_sas Enhancement Update
by James Pearson 24 May '18

24 May '18

centos(a)centos.org wrote: > > CentOS Errata and Enhancement Advisory 2018:1670 > > Upstream details at : https://access.redhat.com/errata/RHEA-2018:1670 > > The following updated files have been uploaded and are currently > syncing to the mirrors: ( sha256sum Filename ) > > > Source: > b243c283592e002f31d604f12edbbfdd26a188f335f2751b92ad129045e79172 kmod-redhat-megaraid_sas-07.702.06.00_rh2_dup7.5-1.el7_5.src.rpm > It looks like the RPMS for this package have ended up in the wrong place ? i.e. they are in .../7.5.1804/updates/x86_64/ not .../7.5.1804/updates/x86_64/Packages/ James Pearson

2 2

CentOS Atomic Host 7.1804 Available for Download
by Jason Brooks 23 May '18

23 May '18

The CentOS Atomic SIG has released an updated version (https://wiki.centos.org/SpecialInterestGroup/Atomic/Download) of CentOS Atomic Host (7.1804), a lean operating system designed to run Linux containers, built from standard CentOS 7 RPMs, and tracking the component versions included in Red Hat Enterprise Linux Atomic Host. This release, which is based on the RHEL 7.5 source code, now ships without any baked-in Kubernetes rpms, which makes it simpler for users to layer their preferred Kubernetes or OpenShift packages onto the host. CentOS Atomic Host includes these core component versions: atomic-1.22.1-3.git2fd0860.el7.x86_64 cloud-init-0.7.9-24.el7.centos.x86_64 docker-1.13.1-63.git94f4240.el7.centos.x86_64 etcd-3.2.18-1.el7.x86_64 flannel-0.7.1-3.el7.x86_64 kernel-3.10.0-862.2.3.el7.x86_64 ostree-2018.1-4.el7.x86_64 rpm-ostree-client-2018.1-1.atomic.el7.x86_64 Download CentOS Atomic Host CentOS Atomic Host is available as a VirtualBox or libvirt-formatted Vagrant box, or as an installable ISO, qcow2 or Amazon Machine image. For links to media, see the CentOS wiki (https://wiki.centos.org/SpecialInterestGroup/Atomic/Download). Upgrading If you’re running a previous version of CentOS Atomic Host, you can upgrade to the current image by running the following command: # atomic host upgrade Release Cycle The CentOS Atomic Host image follows the upstream Red Hat Enterprise Linux Atomic Host cadence. After sources are released, they’re rebuilt and included in new images. After the images are tested by the SIG and deemed ready, we announce them. Getting Involved CentOS Atomic Host is produced by the CentOS Atomic SIG (http://wiki.centos.org/SpecialInterestGroup/Atomic), based on upstream work from Project Atomic. If you’d like to work on testing images, help with packaging, documentation – join us! You’ll often find us in #atomic and/or #centos-devel if you have questions. You can also join the atomic-develmailing list if you’d like to discuss the direction of Project Atomic, its components, or have other questions. Getting Help If you run into any problems with the images or components, feel free to ask on the centos-devel mailing list. Have questions about using Atomic? See the atomic mailing list or find us in the #atomic channel on Freenode.

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel May 2018