devel

devel@lists.centos.org

4 participants
4696 discussions

Start a nNew thread

RHEL 8.1 Beta
by Thomas Stephen Lee 30 Jul '19

30 Jul '19

Hi, https://www.redhat.com/en/blog/red-hat-enterprise-linux-81-beta-now-availab… RHEL 8.1 Beta released. -- Lee

4 4

qemu-kvm-ev issues creating a VM
by Stefano Mingoli 24 Jul '19

24 Jul '19

Hello, not sure if it's the right place to post. I have a VMWare Workstation 15.1 VM based on Centos 7.6 (Kenel 3.10.0-957) with the CentOS-QEMU-EV repository enabled. Version of qemu is: 10:2.12.0-18.el7_6.5.1 I'm having an issue with qemu-kvm-ev, basically it looks like I'm not able to create any VM. I'm getting a "NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kworker/0:0H:5]" and the installation will not proceed. Everything works fine if I use the standard qemu-kvm B R Stefano Mingoli

2 1

[SCLo SIG] new sclo-php*-php-pecl-redis5 packages available for testing
by Remi Collet 23 Jul '19

23 Jul '19

Yet another package available in centos-sclo-sclo-testing This extension provides an API for communicating with Redis servers. https://pecl.php.net/package/redis For rh-php72 (EL-7 only) * sclo-php72-php-pecl-redis5-5.0.1-1 For rh-php71 (EL-7 only) * sclo-php71-php-pecl-redis5-5.0.1-1 For rh-php70 * sclo-php70-php-pecl-redis5-5.0.1-1 Notices: - this extension is already available, as sclo-php7#-php-pecl-redis (version 3.1.6) and php7#-php-pecl-redis4 version 4.3.0. But as version 5 introduce some API changes, we choose to provide it as a separate package, giving users the choice to install v3, v4 or v5 - both versions cannot be installed simultaneously. - new collections (e.g. PHP 7.3, 7.4...) will only provide the v5 package. - upstream Changelog: https://pecl.php.net/package-changelog.php?package=redis Remi. P.S.1: https://wiki.centos.org/SpecialInterestGroup/SCLo P.S.2: you can follow activity on sclo-php* packages on https://blog.remirepo.net/post/2017/02/23/Additional-PHP-packages-for-RHSCL

1 0

Recreating the centos.org website
by jatin 15 Jul '19

15 Jul '19

Recently fedora changed their website design and is now having alot more professional look and feel. centos.org hasnt changed alot. With the release of CentOS 8 it will be great to present it with a new centos.org. Just a suggestion... A bit about myself - Jatin Garg Nation- India DOB - 18th December 2001 Notable contributions to CentOS project - https://github.com/jatin-cbs/Lutris-RHEL-CentOS7 making lutris wine gaming accessible on RHEL, CentOS to users creating sh scripts. Contribution to Vulkan, Unreal Engine to optimize performance and wiki improvements for CentOS.

1 0

Rpm post scriplet failed with exit status 1 but return status of rpm is 0
by Maheshwari, Shagun 15 Jul '19

15 Jul '19

Hi, On CentOS 6, when we try to install any rpm it fails with scriplet failed with exit status 1 but return status of rpm is also 1 which is correct. Example: But On CentOS 7, we are not getting return status of rpm as 1 it is coming 0, which is installing the RPM. rpm -Uvh /home/seldridg/rpmbuild/RPMS/noarch/test-1.0-1.el6.noarch.rpm; echo $? Preparing... ########################################### [100%] 1:test ########################################### [100%] Test Script called failure seen while executing test-script error: %post(test-1.0-1.el6.noarch) scriptlet failed, exit status 1 1 <-- verified this works as expected I checked the source code of rpm package for CentOS6/7 and found that one patch is applicable in CentOS6 rpm package and because of this any failure is coming during scriplet failure it treats warning as an error and giving rpm status as a 1 and not installing that RPM in your system. rpm -Uvh /home/seldridg/rpmbuild/RPMS/noarch/test-1.0-1.el7.noarch.rpm; echo $? Preparing... ########################################### [100%] 1:test ########################################### [100%] Test Script called failure seen while executing test-script error: %post(test-1.0-1.el7.noarch) scriptlet failed, exit status 1 0 <-- verified this works as expected Below is the patch: +++ b/rpm-4.8.x-strict-script-errors.patch @@ -0,0 +1,25 @@ +diff -up rpm-4.8.0/lib/psm.c.strict-script rpm-4.8.0/lib/psm.c +--- rpm-4.8.0/lib/psm.c.strict-script 2013-08-05 11:09:40.290136043 +0300 ++++ rpm-4.8.0/lib/psm.c 2013-08-05 11:12:18.465137945 +0300 +@@ -517,7 +517,9 @@ static rpmRC runLuaScript(rpmpsm psm, He + if (rc != RPMRC_OK) { + if ((stag != RPMTAG_PREIN && stag != RPMTAG_PREUN && + stag != RPMTAG_VERIFYSCRIPT && stag != RPMTAG_PRETRANS)) { +- warn_only = 1; ++ if (!rpmExpandNumeric("%{?_strict_script_errors}")) { ++ warn_only = 1; ++ } + } + } + umask(oldmask); +@@ -774,7 +776,9 @@ static rpmRC runScript(rpmpsm psm, Heade + } else { + /* filter out "regular" error exits from non-pre scriptlets */ + if ((stag != RPMTAG_PREIN && stag != RPMTAG_PREUN && stag != RPMTAG_VERIFYSCRIPT && stag != RPMTAG_PRETRANS)) { +- warn_only = 1; ++ if (!rpmExpandNumeric("%{?_strict_script_errors}")) { ++ warn_only = 1; ++ } + } + rpmlog(warn_only ? RPMLOG_WARNING : RPMLOG_ERR, + _("%s scriptlet failed, exit status %d\n"), I tried to modify the code according to this but not getting success. Please help me on this. I want the same behavior of CentOS 6 on CentOS 7. Regards, Shagun

4 4

EPEL 8
by Thomas Stephen Lee 12 Jul '19

12 Jul '19

Hi, It looks like Fedora EPEL people are having issues with the "modules" architecture. You all are probably busy with CentOS 8. If anyone has spare time, take a look. https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraprojec… thanks -- Lee

5 9

CentOS Atomic Host 7.1906 Available for Download
by Jason Brooks 10 Jul '19

10 Jul '19

The CentOS Atomic SIG has released an [updated version](https://wiki.centos.org/SpecialInterestGroup/Atomic/Download) of CentOS Atomic Host (7.1906), an 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. CentOS Atomic Host includes these core component versions: * atomic-1.22.1-26.gitb507039.el7.centos.x86_64 * rpm-ostree-client-2018.5-2.atomic.el7.x86_64 * ostree-2018.5-1.el7.x86_64 * cloud-init-18.2-1.el7.centos.2.x86_64 * docker-1.13.1-96.gitb2f74b2.el7.centos.x86_64 * kernel-3.10.0-957.21.3.el7.x86_64 * podman-1.3.2-1.git14fdcd0.el7.centos.x86_64 * flannel-0.7.1-4.el7.x86_64 * etcd-3.3.11-2.el7.centos.x86_64 ## Download CentOS Atomic Host CentOS Atomic Host is available as a VirtualBox or libvirt-formatted Vagrant box, or as an installable ISO, or qcow2 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](http://www.projectatomic.io/). 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-devel](https://lists.projectatomic.io/mailman/listinfo/atomic-devel) mailing 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](http://lists.centos.org/mailman/listinfo/centos-devel) mailing list. Have questions about using Atomic? See the [atomic](https://lists.projectatomic.io/mailman/listinfo/atomic) mailing list or find us in the #atomic channel on Freenode.

1 0

CentOS, Red Hat, and IBM
by Rich Bowen 09 Jul '19

09 Jul '19

CentOS community, Today marks a new day in the 26-year history of Red Hat. IBM has finalized its acquisition of Red Hat (https://www.redhat.com/en/about/press-releases/ibm-closes-landmark-acquisit…) which will operate as a distinct unit within IBM moving forward. What does this mean for Red Hat’s contributions to the CentOS project? In short, nothing. Red Hat always has and will continue to be a champion for open source and projects like CentOS. IBM is committed to Red Hat’s independence and role in open source software communities so that we can continue this work without interruption or changes. Our mission, governance, and objectives remain the same. We will continue to execute the existing project roadmap. Red Hat associates will continue to contribute to the upstream in the same ways they have been. And, as always, we will continue to help upstream projects be successful and contribute to welcoming new members and maintaining the project. We will do this together, with the community, as we always have. If you have questions or would like to learn more about today’s news, I encourage you to review the list of materials below. Red Hat CTO Chris Wright will host an online Q&A session in the coming days where you can ask questions you may have about what the acquisition means for Red Hat and our involvement in open source communities. Details will be announced on the Red Hat blog - https://www.redhat.com/en/blog Press release - https://www.redhat.com/en/about/press-releases/ibm-closes-landmark-acquisit… Chris Wright blog - Red Hat and IBM: Accelerating the adoption of open source - https://www.redhat.com/en/blog/red-hat-and-ibm-accelerating-adoption-open-s… FAQ on Red Hat Community Blog - https://community.redhat.com/blog/2019/07/faq-for-communities/ -- Rich Bowen - rbowen(a)redhat.com - CentOS Community Manager @CentOSProject // @rbowen

1 0

[Infra] - planned maintenance/outage : cbs.centos.org
by Fabian Arrotin 08 Jul '19

08 Jul '19

Due some maintenance/upgrade on the storage node holding all artifacts used on koji/CBS (https://cbs.centos.org) we'll have to shutdown (maintenance) the koji/cbs service. Migration is scheduled for """"Tuesday July 9th, 7:00 am UTC time"""". You can convert to local time with $(date -d '2019-07-09 07:00 UTC') The expected "downtime" is estimated to ~60 minutes , time needed to reinstall the storage node and have ansible reconfiguring it. Thanks for your comprehending and patience. on behalf of the Infra team, -- Fabian Arrotin The CentOS Project | https://www.centos.org gpg key: 17F3B7A1 | twitter: @arrfab

1 0

Fwd: [ohiolinux-attendees] Call For Presentations and Registration Now Open! Ohio LinuxFest Conference 2019
by Rich Bowen 08 Jul '19

08 Jul '19

FYI: CFP for Ohio LinuxFest is now open. -------- Forwarded Message -------- Subject: [ohiolinux-attendees] Call For Presentations and Registration Now Open! Ohio LinuxFest Conference 2019 Date: Wed, 3 Jul 2019 08:57:49 -0400 From: Susan Rose <srosemedical(a)gmail.com> To: Ohiolinux-attendees(a)lists.ohiolinux.org *Dear Valued Member of the Ohio LinuxFest Open Source Community,* The OLF Conference organized by Ohio LinuxFest is proud to announce that we will hold our 17th annual event at the Hyatt Regency Columbus on *November 1 and 2, 2019. * *Call for Presentations is now open*. August 17, 2019 is the deadline, but the sooner you submit, the better. https://ohiolinux.org/call-for-presentations/ Ohio LinuxFest welcomes all Free and Open Source Software professionals, enthusiasts, and everyone interested in learning more about Free and Open Source Software. In the spirit of the open source software movement, the “Enthusiast” level registration is free (unless you decide to make a donation). Go ahead and *register now*. https://ohiolinux.org/registration/ Hotel info is here: https://ohiolinux.org/hotels/ You can also register for OLF Institute training programs, very reasonably priced and available on Friday Nov 1 of the conference.**Learn more about the training sessions listed below.** 1. Linux Professional Institute (LPI) Boot Camp <https://ohiolinux.org/olfi-training-2019/linux-professional-institute-lpi-b…> 2. AWS Cloud Platform, Cloud Formation and Terraform <https://ohiolinux.org/olfi-training-2019/aws-cloud-platform-cloudformation-…> 3. Kubernetes on Google Cloud <https://ohiolinux.org/olfi-training-2019/kubernetes-on-google-cloud/> 4. Linux Containers Internals <https://ohiolinux.org/olfi-training-2019/linux-containers-internals/> 5. Linux Security Through Layers <https://ohiolinux.org/olfi-training-2019/linux-security-through-layers/> 6. Using Ansible to Simplify Automation and Provisioning <https://ohiolinux.org/olfi-training-2019/ansible-automation-provisioning/> 7. Web Application Security Testing<https://ohiolinux.org/olfi-training-2019/web-app-testing/> If you have additional questions, please reply tospeakers(a)ohiolinux.org <mailto:speakers@ohiolinux.org> We are excited to see you again this year! Friday, Nov. 1 and Saturday, Nov. 2. olfnoyearsm.jpg

1 0

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel