devel

devel@lists.centos.org

4 participants
4660 discussions

CentOS for IBM Mainframes.
by Javier Romero 20 Feb '18

20 Feb '18

Hi all, I see that IBM LinuxONE, provides a Z Mainframe running with Linux Red Hat, SUSE OR Ubuntu Server distros. Do you think that could also be useful for CentOS to be another option for LinuxONE? Maybe a a CentOS Mainframe SIG can be created to work on this. Thanks for your attention. Regards, Javier Romero

3 4

Atomic Container in github.com/centos/atomic-container
by Karanbir Singh 20 Feb '18

20 Feb '18

Hi, As the atomic container process has matured to a point where we can move towards a release, I've moved the content from kbsingh/atomic-container to centos/atomic-container on github.com Bama, can you move the index to point at this ? also move the container to be available in the registry from /centos/ namespace and confirm once its there. Regards -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc

2 1

G++ Testsuite tls/thread_local-order2.C fails with 4.8.5 20150623 and older
by Jan Boehme 19 Feb '18

19 Feb '18

Hello, while playing with building a current gcc by myself I detected that the latest Centos 7 g++ isn't able to pass the respective test suite because of FAIL: g++.dg/tls/thread_local-order2.C -std=c++11 execution test Is this accepted behavior? If so, it basically breaks C++11 support on this platform. What is already known in terms of a cause? Is it a glibc problem (I'm not seeing it using Fedora with glibc 2.26)? g++ --version g++ (GCC) 4.8.5 20150623 (Red Hat 4.8.5-16) g++ /tmp/gcc-7.3.0/gcc/testsuite/g++.dg/tls/thread_local-order2.C -o /tmp/thread_local-order2.exe -std=c++11 /tmp/thread_local-order2.exe Aborted (core dumped) /lib64/libc.so.6 GNU C Library (GNU libc) stable release version 2.17 Thanks, Jan.

1 0

Some way to validate SIG repo repodata (via HTTPS or GPG-signed repomd?)
by Neal Gompa 19 Feb '18

19 Feb '18

Hey, I've been trying to get the CentOS SIG repositories enabled in the openSUSE Build Service[1]. Today, I started working with Adrian Schröter (who is CC'd to this email) on getting this done, and the issue right now is that there's no way to securely validate the repodata. OBS supports two ways: 1. Validating repodata from a mirror using the copy on the master server fetched through HTTPS. 2. Validating repodata through GPG-signed repodata (signed repomd.xml) While the base repositories do the latter, none of the repositories produced through CBS do, and _nothing_ currently does the former. Is there something that can be done to make this better so we can have nice things? Best regards, Neal [1]: https://progress.opensuse.org/issues/29568 -- 真実はいつも一つ！/ Always, there's only one truth!

3 3

[Infra] - planned outage : bugs.centos.org (Bug Tracker)
by Fabian Arrotin 19 Feb '18

19 Feb '18

This notification to let you know that we'll migrate our https://bugs.centos.org bug tracker service to a different node, and also updated to a new version of MantisBT (version 2.x) This migration will give us more possibilities, including soon trying to get SSO working even on our bug tracker (that part still need to be done though) Migration is scheduled for """"Tuesday February 20th, 8:00 am UTC time"""". You can convert to local time with $(date -d '2018-2-20 8:00 UTC') The expected "downtime" is estimated to ~10 minutes , time needed to update/propagate updated dns A/AAAA records + last mysql dump/restore on the new node. 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

Dockerfiles for CentOS containers with GlusterFS.
by Javier Romero 16 Feb '18

16 Feb '18

Dear all, I've built GlusterFS 3.12 image from Dockerfile and changed Gluster version and vendor, a pull request has been sent on Github. # docker images REPOSITORY TAG IMAGE ID CREATED SIZE dockerfile-gluster-3.12 latest 4647c9d71843 53 minutes ago 371.2 MB docker.io/centos 7 ff426288ea90 5 weeks ago 207.2 MB # docker ps -a CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 9afa8c0ab468 dockerfile-gluster-3.12 "/usr/sbin/init" 38 minutes ago Up 38 minutes small_shannon # docker exec -it 9afa8c0ab468 bash # glusterd -V glusterfs 3.12.5 There was just a Dockerfile on the gluster-3.10 branch for building GlusterFS 3.10. Have updated that Dockerfile and sent a pull request on Github. # docker images REPOSITORY TAG IMAGE ID CREATED SIZE dockerfile-gluster-3.10 latest fbedfea074f6 36 minutes ago 435.5 MB docker.io/centos 7 ff426288ea90 5 weeks ago 207.2 MB # docker ps -a CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 0269de7f42bd dockerfile-gluster-3.10 "/usr/sbin/init" 7 seconds ago Up 6 seconds high_jang # docker exec -it 0269de7f42bd sh sh-4.2# glusterd -V glusterfs 3.10.10 Have created a new Dockerfile for image creation to run containers on CentOS 7 with GlusterFS 3.13 already installed. Also sent a pull request on Github to merge a new branch named gluster-3.13 with this new Dockerfile included. Tested on Centos 7 release 7.4.1708 (Core) with kernel 3.10.0-693.17.1.el7.x86_64 and works ok: # docker images REPOSITORY TAG IMAGE ID CREATED SIZE dockerfile-gluster-3.13 latest 07931ac54c87 About an hour ago 371.9 MB docker.io/centos 7 ff426288ea90 5 weeks ago 207.2 MB # docker ps -a CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 4e164d71256f dockerfile-gluster-3.13 "/usr/sbin/init" About an hour ago Up About an hour backstabbing_babbage # docker exec -it 4e164d71256f sh sh-4.2# glusterd -V glusterfs 3.13.2 Regards, Javier Romero

1 0

[Storage SIG] Building storage7-ceph-luminous-release for ppc64le
by Mark Hamzy 16 Feb '18

16 Feb '18

Hey y'all, So what scripts/process builds the group of rpms for the tag storage7-ceph-luminous-release? I would like to build them for ppc64le So the packages in http://mirror.centos.org/centos/7/storage/x86_64/ceph-luminous/ Would end up http://mirror.centos.org/altarch/7/storage/ppc64le/ceph-luminous/ Is this something I could help with? -- Mark You must be the change you wish to see in the world. -- Mahatma Gandhi Never let the future disturb you. You will meet it, if you have to, with the same weapons of reason which today arm you against the present. -- Marcus Aurelius

1 0

Call for papers: CentOS Dojo, Singapore, March 25th
by Rich Bowen 16 Feb '18

16 Feb '18

We will be holding a dojo in Singapore, on March 25th, in conjunction with the FOSSAsia event. If you will be there, and have a proposal for a talk during that event, please let us know. https://goo.gl/forms/P2rFro03FUt2Tp3C3 More details on the event are available here: https://wiki.centos.org/Events/Dojo/Singapore2018 Thanks. -- Rich Bowen - rbowen(a)redhat.com @RDOcommunity // @CentOSProject // @rbowen

1 0

CentOS PaaS SIG meeting (2018-02-14)
by Troy Dawson 14 Feb '18

14 Feb '18

Hello, It's time for our weekly PaaS SIG sync-up meeting Time: 1700 UTC - Wedensdays (date -d "1700 UTC") Date: Today Wedensday, 14 February 2018 Where: IRC- Freenode - #centos-devel Agenda: - OpenShift Current Status -- rpms -- Automated rpm building and Automated testing -- Multi-arch -- Documentation -- Images and Image building - Open Floor Minutes from last meeting: https://www.centos.org/minutes/2018/January/centos-devel.2018-01-24-17.03.h…

1 0

Cleaning-up Extras for inconsistencies (aka golang in aarch64)
by Fabian Arrotin 12 Feb '18

12 Feb '18

Last week I tried to build a pkg for infra, that has all the arches enabled (so x86_64, ppc64, ppc64le and aarch64) That package has "BuildRequires: golang >= 1.8" , which is in the base distro but the --scratch build failed starting with aarch64 and complaining with "DEBUG util.py:417: Error: No Package found for golang >= 1.8 " So, while there is a golang 1.8.3 package in [base], there is still an old version in [extras] : golang.aarch64 1.6.3-2.el7 extras And because koji will not pick automatically the higher ENVR, but rather a pkg based on the repository it's coming from (with different priorities), it doesn't want to use the one from [base], but rather the one from [extras] (so that it impacts everybody actually building in koji) So the proposal is : can someone have a look at cleaning-up older releases from extras when it was replaced by a newer version that landed in [base] ? Yum will always use the highest ENVR, but koji will not, breaking some builds on https://cbs.centos.org right now -- Fabian Arrotin The CentOS Project | https://www.centos.org gpg key: 56BEC54E | twitter: @arrfab

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