devel

devel@lists.centos.org

5 participants
4641 discussions

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

CR repo messes ctdb package deps badly
by lejeczek 06 Jul '19

06 Jul '19

hi @devel guys, there is something broken in CR either with ctdb or some deps, take a look below. This problem does not occur with CR disabled. (should this be a bug report?) may thanks, L. $ yum install ctdb Resolving Dependencies --> Running transaction check ---> Package ctdb.x86_64 0:4.8.3-4.el7 will be installed --> Processing Dependency: samba-client-libs = 4.8.3-4.el7 for package: ctdb-4.8.3-4.el7.x86_64 --> Running transaction check ---> Package samba-client-libs.i686 0:4.8.3-4.el7 will be installed --> Processing Dependency: samba-common = 4.8.3-4.el7 for package: samba-client-libs-4.8.3-4.el7.i686 --> Processing Dependency: samba-common = 4.8.3-4.el7 for package: samba-client-libs-4.8.3-4.el7.i686 --> Processing Dependency: libwbclient = 4.8.3-4.el7 for package: samba-client-libs-4.8.3-4.el7.i686 --> Processing Dependency: libz.so.1 for package: samba-client-libs-4.8.3-4.el7.i686 --> Processing Dependency: libwbclient.so.0(WBCLIENT_0.9) for package: samba-client-libs-4.8.3-4.el7.i686 --> Processing Dependency: libwbclient.so.0 for package: samba-client-libs-4.8.3-4.el7.i686 --> Processing Dependency: libtevent.so.0(TEVENT_0.9.9) for package: samba-client-libs-4.8.3-4.el7.i686 --> Processing Dependency: libtevent.so.0(TEVENT_0.9.31) for package: samba-client-libs-4.8.3-4.el7.i686 --> Processing Dependency: libtevent.so.0(TEVENT_0.9.30) for package: samba-client-libs-4.8.3-4.el7.i686 --> Processing Dependency: libtevent.so.0(TEVENT_0.9.21) for package: samba-client-libs-4.8.3-4.el7.i686 --> Processing Dependency: libtevent.so.0(TEVENT_0.9.20) for package: samba-client-libs-4.8.3-4.el7.i686 --> Processing Dependency: libtevent.so.0(TEVENT_0.9.16) for package: samba-client-libs-4.8.3-4.el7.i686 --> Processing Dependency: libtevent.so.0(TEVENT_0.9.14) for package: samba-client-libs-4.8.3-4.el7.i686 --> Processing Dependency: libtevent.so.0(TEVENT_0.9.13) for package: samba-client-libs-4.8.3-4.el7.i686 --> Processing Dependency: libtevent.so.0(TEVENT_0.9.12) for package: samba-client-libs-4.8.3-4.el7.i686 --> Processing Dependency: libtevent.so.0 for package: samba-client-libs-4.8.3-4.el7.i686 --> Processing Dependency: libtdb.so.1(TDB_1.3.11) for package: samba-client-libs-4.8.3-4.el7.i686 --> Processing Dependency: libtdb.so.1(TDB_1.3.0) for package: samba-client-libs-4.8.3-4.el7.i686 --> Processing Dependency: libtdb.so.1(TDB_1.2.5) for package: samba-client-libs-4.8.3-4.el7.i686 --> Processing Dependency: libtdb.so.1(TDB_1.2.2) for package: samba-client-libs-4.8.3-4.el7.i686 --> Processing Dependency: libtdb.so.1(TDB_1.2.1) for package: samba-client-libs-4.8.3-4.el7.i686 --> Processing Dependency: libtdb.so.1 for package: samba-client-libs-4.8.3-4.el7.i686 --> Processing Dependency: libtalloc.so.2(TALLOC_2.1.0) for package: samba-client-libs-4.8.3-4.el7.i686 --> Processing Dependency: libtalloc.so.2(TALLOC_2.0.2) for package: samba-client-libs-4.8.3-4.el7.i686 --> Processing Dependency: libtalloc.so.2 for package: samba-client-libs-4.8.3-4.el7.i686 --> Processing Dependency: libsystemd-journal.so.0(LIBSYSTEMD_JOURNAL_183) for package: samba-client-libs-4.8.3-4.el7.i686 --> Processing Dependency: libsystemd-journal.so.0 for package: samba-client-libs-4.8.3-4.el7.i686 --> Processing Dependency: libsystemd-daemon.so.0(LIBSYSTEMD_DAEMON_31) for package: samba-client-libs-4.8.3-4.el7.i686 --> Processing Dependency: libsystemd-daemon.so.0 for package: samba-client-libs-4.8.3-4.el7.i686 --> Processing Dependency: librt.so.1(GLIBC_2.2) for package: samba-client-libs-4.8.3-4.el7.i686 --> Processing Dependency: librt.so.1 for package: samba-client-libs-4.8.3-4.el7.i686 --> Processing Dependency: libresolv.so.2(GLIBC_2.2) for package: samba-client-libs-4.8.3-4.el7.i686 --> Processing Dependency: libresolv.so.2 for package: samba-client-libs-4.8.3-4.el7.i686 --> Processing Dependency: libpthread.so.0(GLIBC_2.3.2) for package: samba-client-libs-4.8.3-4.el7.i686 --> Processing Dependency: libpthread.so.0(GLIBC_2.2) for package: samba-client-libs-4.8.3-4.el7.i686 --> Processing Dependency: libpthread.so.0(GLIBC_2.12) for package: samba-client-libs-4.8.3-4.el7.i686 --> Processing Dependency: libpthread.so.0(GLIBC_2.1) for package: samba-client-libs-4.8.3-4.el7.i686 --> Processing Dependency: libpthread.so.0(GLIBC_2.0) for package: samba-client-libs-4.8.3-4.el7.i686 --> Processing Dependency: libpthread.so.0 for package: samba-client-libs-4.8.3-4.el7.i686 --> Processing Dependency: libpam.so.0(LIBPAM_1.0) for package: samba-client-libs-4.8.3-4.el7.i686 --> Processing Dependency: libpam.so.0 for package: samba-client-libs-4.8.3-4.el7.i686 --> Processing Dependency: libnsl.so.1(GLIBC_2.0) for package: samba-client-libs-4.8.3-4.el7.i686 --> Processing Dependency: libnsl.so.1 for package: samba-client-libs-4.8.3-4.el7.i686 --> Processing Dependency: libldb.so.1(LDB_1.3.0) for package: samba-client-libs-4.8.3-4.el7.i686 --> Processing Dependency: libldb.so.1(LDB_1.1.30) for package: samba-client-libs-4.8.3-4.el7.i686 --> Processing Dependency: libldb.so.1(LDB_1.1.19) for package: samba-client-libs-4.8.3-4.el7.i686 --> Processing Dependency: libldb.so.1(LDB_1.1.1) for package: samba-client-libs-4.8.3-4.el7.i686 --> Processing Dependency: libldb.so.1(LDB_0.9.23) for package: samba-client-libs-4.8.3-4.el7.i686 --> Processing Dependency: libldb.so.1(LDB_0.9.15) for package: samba-client-libs-4.8.3-4.el7.i686 --> Processing Dependency: libldb.so.1(LDB_0.9.10) for package: samba-client-libs-4.8.3-4.el7.i686 --> Processing Dependency: libldb.so.1 for package: samba-client-libs-4.8.3-4.el7.i686 --> Processing Dependency: libldap-2.4.so.2 for package: samba-client-libs-4.8.3-4.el7.i686 --> Processing Dependency: liblber-2.4.so.2 for package: samba-client-libs-4.8.3-4.el7.i686 --> Processing Dependency: libkrb5.so.3(krb5_3_MIT) for package: samba-client-libs-4.8.3-4.el7.i686 --> Processing Dependency: libkrb5.so.3 for package: samba-client-libs-4.8.3-4.el7.i686 --> Processing Dependency: libk5crypto.so.3(k5crypto_3_MIT) for package: samba-client-libs-4.8.3-4.el7.i686 --> Processing Dependency: libk5crypto.so.3 for package: samba-client-libs-4.8.3-4.el7.i686 --> Processing Dependency: libgssapi_krb5.so.2(gssapi_krb5_2_MIT) for package: samba-client-libs-4.8.3-4.el7.i686 --> Processing Dependency: libgssapi_krb5.so.2 for package: samba-client-libs-4.8.3-4.el7.i686 --> Processing Dependency: libgcc_s.so.1(GCC_3.3.1) for package: samba-client-libs-4.8.3-4.el7.i686 --> Processing Dependency: libgcc_s.so.1(GCC_3.0) for package: samba-client-libs-4.8.3-4.el7.i686 --> Processing Dependency: libgcc_s.so.1 for package: samba-client-libs-4.8.3-4.el7.i686 --> Processing Dependency: libdl.so.2(GLIBC_2.1) for package: samba-client-libs-4.8.3-4.el7.i686 --> Processing Dependency: libdl.so.2(GLIBC_2.0) for package: samba-client-libs-4.8.3-4.el7.i686 --> Processing Dependency: libdl.so.2 for package: samba-client-libs-4.8.3-4.el7.i686 --> Processing Dependency: libcups.so.2 for package: samba-client-libs-4.8.3-4.el7.i686 --> Processing Dependency: libcom_err.so.2 for package: samba-client-libs-4.8.3-4.el7.i686 --> Processing Dependency: libcap.so.2 for package: samba-client-libs-4.8.3-4.el7.i686 --> Processing Dependency: libc.so.6(GLIBC_2.11) for package: samba-client-libs-4.8.3-4.el7.i686 --> Processing Dependency: libavahi-common.so.3 for package: samba-client-libs-4.8.3-4.el7.i686 --> Processing Dependency: libavahi-client.so.3 for package: samba-client-libs-4.8.3-4.el7.i686 --> Processing Dependency: libattr.so.1(ATTR_1.0) for package: samba-client-libs-4.8.3-4.el7.i686 --> Processing Dependency: libattr.so.1 for package: samba-client-libs-4.8.3-4.el7.i686 --> Processing Dependency: libacl.so.1(ACL_1.0) for package: samba-client-libs-4.8.3-4.el7.i686 --> Processing Dependency: libacl.so.1 for package: samba-client-libs-4.8.3-4.el7.i686 --> Running transaction check ---> Package avahi-libs.i686 0:0.6.31-19.el7 will be installed --> Processing Dependency: libdbus-1.so.3 for package: avahi-libs-0.6.31-19.el7.i686 ---> Package cups-libs.i686 1:1.6.3-35.el7 will be installed --> Processing Dependency: libstdc++.so.6(GLIBCXX_3.4) for package: 1:cups-libs-1.6.3-35.el7.i686 --> Processing Dependency: libstdc++.so.6(CXXABI_1.3) for package: 1:cups-libs-1.6.3-35.el7.i686 --> Processing Dependency: libstdc++.so.6 for package: 1:cups-libs-1.6.3-35.el7.i686 --> Processing Dependency: libssl.so.10(libssl.so.10) for package: 1:cups-libs-1.6.3-35.el7.i686 --> Processing Dependency: libssl.so.10 for package: 1:cups-libs-1.6.3-35.el7.i686 --> Processing Dependency: libselinux.so.1 for package: 1:cups-libs-1.6.3-35.el7.i686 --> Processing Dependency: libcrypto.so.10(libcrypto.so.10) for package: 1:cups-libs-1.6.3-35.el7.i686 --> Processing Dependency: libcrypto.so.10 for package: 1:cups-libs-1.6.3-35.el7.i686 --> Processing Dependency: libaudit.so.1 for package: 1:cups-libs-1.6.3-35.el7.i686 ---> Package glibc.i686 0:2.17-260.el7_6.5 will be installed --> Processing Dependency: libfreebl3.so(NSSRAWHASH_3.12.3) for package: glibc-2.17-260.el7_6.5.i686 --> Processing Dependency: libfreebl3.so for package: glibc-2.17-260.el7_6.5.i686 ---> Package krb5-libs.i686 0:1.15.1-37.el7_6 will be installed --> Processing Dependency: libverto.so.1 for package: krb5-libs-1.15.1-37.el7_6.i686 --> Processing Dependency: libkeyutils.so.1(KEYUTILS_1.5) for package: krb5-libs-1.15.1-37.el7_6.i686 --> Processing Dependency: libkeyutils.so.1(KEYUTILS_1.0) for package: krb5-libs-1.15.1-37.el7_6.i686 --> Processing Dependency: libkeyutils.so.1(KEYUTILS_0.3) for package: krb5-libs-1.15.1-37.el7_6.i686 --> Processing Dependency: libkeyutils.so.1 for package: krb5-libs-1.15.1-37.el7_6.i686 ---> Package libacl.i686 0:2.2.51-14.el7 will be installed ---> Package libattr.i686 0:2.4.46-13.el7 will be installed ---> Package libcap.i686 0:2.22-9.el7 will be installed ---> Package libcom_err.i686 0:1.42.9-13.el7 will be installed ---> Package libgcc.i686 0:4.8.5-36.el7_6.2 will be installed ---> Package libldb.i686 0:1.3.4-1.el7 will be installed ---> Package libtalloc.i686 0:2.1.13-1.el7 will be installed ---> Package libtdb.i686 0:1.3.15-1.el7 will be installed ---> Package libtevent.i686 0:0.9.36-1.el7 will be installed ---> Package libwbclient.i686 0:4.8.3-4.el7 will be installed ---> Package openldap.i686 0:2.4.44-21.el7_6 will be installed --> Processing Dependency: libssl3.so for package: openldap-2.4.44-21.el7_6.i686 --> Processing Dependency: libsmime3.so for package: openldap-2.4.44-21.el7_6.i686 --> Processing Dependency: libsasl2.so.3 for package: openldap-2.4.44-21.el7_6.i686 --> Processing Dependency: libplds4.so for package: openldap-2.4.44-21.el7_6.i686 --> Processing Dependency: libplc4.so for package: openldap-2.4.44-21.el7_6.i686 --> Processing Dependency: libnssutil3.so for package: openldap-2.4.44-21.el7_6.i686 --> Processing Dependency: libnss3.so(NSS_3.9) for package: openldap-2.4.44-21.el7_6.i686 --> Processing Dependency: libnss3.so(NSS_3.2) for package: openldap-2.4.44-21.el7_6.i686 --> Processing Dependency: libnss3.so(NSS_3.12.5) for package: openldap-2.4.44-21.el7_6.i686 --> Processing Dependency: libnss3.so(NSS_3.12) for package: openldap-2.4.44-21.el7_6.i686 --> Processing Dependency: libnss3.so for package: openldap-2.4.44-21.el7_6.i686 --> Processing Dependency: libnspr4.so for package: openldap-2.4.44-21.el7_6.i686 ---> Package pam.i686 0:1.1.8-22.el7 will be installed --> Processing Dependency: libdb-5.3.so for package: pam-1.1.8-22.el7.i686 --> Processing Dependency: libcrack.so.2 for package: pam-1.1.8-22.el7.i686 ---> Package samba-client-libs.i686 0:4.8.3-4.el7 will be installed --> Processing Dependency: samba-common = 4.8.3-4.el7 for package: samba-client-libs-4.8.3-4.el7.i686 --> Processing Dependency: samba-common = 4.8.3-4.el7 for package: samba-client-libs-4.8.3-4.el7.i686 ---> Package systemd-libs.i686 0:219-62.el7_6.6 will be installed --> Processing Dependency: liblzma.so.5(XZ_5.0) for package: systemd-libs-219-62.el7_6.6.i686 --> Processing Dependency: liblzma.so.5 for package: systemd-libs-219-62.el7_6.6.i686 --> Processing Dependency: liblz4.so.1 for package: systemd-libs-219-62.el7_6.6.i686 --> Processing Dependency: libgpg-error.so.0 for package: systemd-libs-219-62.el7_6.6.i686 --> Processing Dependency: libgcrypt.so.11(GCRYPT_1.2) for package: systemd-libs-219-62.el7_6.6.i686 --> Processing Dependency: libgcrypt.so.11 for package: systemd-libs-219-62.el7_6.6.i686 --> Processing Dependency: libdw.so.1 for package: systemd-libs-219-62.el7_6.6.i686 ---> Package zlib.i686 0:1.2.7-18.el7 will be installed --> Running transaction check ---> Package audit-libs.i686 0:2.8.4-4.el7 will be installed --> Processing Dependency: libcap-ng.so.0 for package: audit-libs-2.8.4-4.el7.i686 ---> Package cracklib.i686 0:2.9.0-11.el7 will be installed ---> Package cyrus-sasl-lib.i686 0:2.1.26-23.el7 will be installed ---> Package dbus-libs.i686 1:1.10.24-13.el7_6 will be installed ---> Package elfutils-libs.i686 0:0.172-2.el7 will be installed --> Processing Dependency: elfutils-libelf(x86-32) = 0.172-2.el7 for package: elfutils-libs-0.172-2.el7.i686 --> Processing Dependency: libelf.so.1(ELFUTILS_1.7) for package: elfutils-libs-0.172-2.el7.i686 --> Processing Dependency: libelf.so.1(ELFUTILS_1.6) for package: elfutils-libs-0.172-2.el7.i686 --> Processing Dependency: libelf.so.1(ELFUTILS_1.5) for package: elfutils-libs-0.172-2.el7.i686 --> Processing Dependency: libelf.so.1(ELFUTILS_1.4) for package: elfutils-libs-0.172-2.el7.i686 --> Processing Dependency: libelf.so.1(ELFUTILS_1.3) for package: elfutils-libs-0.172-2.el7.i686 --> Processing Dependency: libelf.so.1(ELFUTILS_1.1.1) for package: elfutils-libs-0.172-2.el7.i686 --> Processing Dependency: libelf.so.1(ELFUTILS_1.0) for package: elfutils-libs-0.172-2.el7.i686 --> Processing Dependency: libelf.so.1 for package: elfutils-libs-0.172-2.el7.i686 --> Processing Dependency: libbz2.so.1 for package: elfutils-libs-0.172-2.el7.i686 ---> Package keyutils-libs.i686 0:1.5.8-3.el7 will be installed ---> Package libdb.i686 0:5.3.21-24.el7 will be installed ---> Package libgcrypt.i686 0:1.5.3-14.el7 will be installed ---> Package libgpg-error.i686 0:1.12-3.el7 will be installed ---> Package libselinux.i686 0:2.5-14.1.el7 will be installed --> Processing Dependency: libsepol(x86-32) >= 2.5-10 for package: libselinux-2.5-14.1.el7.i686 --> Processing Dependency: libsepol.so.1(LIBSEPOL_1.0) for package: libselinux-2.5-14.1.el7.i686 --> Processing Dependency: libsepol.so.1 for package: libselinux-2.5-14.1.el7.i686 --> Processing Dependency: libpcre.so.1 for package: libselinux-2.5-14.1.el7.i686 ---> Package libstdc++.i686 0:4.8.5-36.el7_6.2 will be installed ---> Package libverto.i686 0:0.2.5-4.el7 will be installed ---> Package lz4.i686 0:1.7.5-2.el7 will be installed ---> Package nspr.i686 0:4.19.0-1.el7_5 will be installed ---> Package nss.i686 0:3.36.0-7.1.el7_6 will be installed --> Processing Dependency: nss-softokn(x86-32) >= 3.36.0-1 for package: nss-3.36.0-7.1.el7_6.i686 --> Processing Dependency: nss-pem(x86-32) for package: nss-3.36.0-7.1.el7_6.i686 ---> Package nss-softokn-freebl.i686 0:3.36.0-5.el7_5 will be installed ---> Package nss-util.i686 0:3.36.0-1.1.el7_6 will be installed ---> Package openssl-libs.i686 1:1.0.2k-16.el7_6.1 will be installed ---> Package samba-client-libs.i686 0:4.8.3-4.el7 will be installed --> Processing Dependency: samba-common = 4.8.3-4.el7 for package: samba-client-libs-4.8.3-4.el7.i686 --> Processing Dependency: samba-common = 4.8.3-4.el7 for package: samba-client-libs-4.8.3-4.el7.i686 ---> Package xz-libs.i686 0:5.2.2-1.el7 will be installed --> Running transaction check ---> Package bzip2-libs.i686 0:1.0.6-13.el7 will be installed ---> Package elfutils-libelf.i686 0:0.172-2.el7 will be installed ---> Package libcap-ng.i686 0:0.7.5-4.el7 will be installed ---> Package libsepol.i686 0:2.5-10.el7 will be installed ---> Package nss-pem.i686 0:1.0.3-5.el7_6.1 will be installed ---> Package nss-softokn.i686 0:3.36.0-5.el7_5 will be installed --> Processing Dependency: libsqlite3.so.0 for package: nss-softokn-3.36.0-5.el7_5.i686 ---> Package pcre.i686 0:8.32-17.el7 will be installed ---> Package samba-client-libs.i686 0:4.8.3-4.el7 will be installed --> Processing Dependency: samba-common = 4.8.3-4.el7 for package: samba-client-libs-4.8.3-4.el7.i686 --> Processing Dependency: samba-common = 4.8.3-4.el7 for package: samba-client-libs-4.8.3-4.el7.i686 --> Running transaction check ---> Package samba-client-libs.i686 0:4.8.3-4.el7 will be installed --> Processing Dependency: samba-common = 4.8.3-4.el7 for package: samba-client-libs-4.8.3-4.el7.i686 --> Processing Dependency: samba-common = 4.8.3-4.el7 for package: samba-client-libs-4.8.3-4.el7.i686 ---> Package sqlite.i686 0:3.7.17-8.el7 will be installed --> Processing Dependency: libtinfo.so.5 for package: sqlite-3.7.17-8.el7.i686 --> Processing Dependency: libreadline.so.6 for package: sqlite-3.7.17-8.el7.i686 --> Processing Dependency: libncurses.so.5 for package: sqlite-3.7.17-8.el7.i686 --> Running transaction check ---> Package ncurses-libs.i686 0:5.9-14.20130511.el7_4 will be installed ---> Package readline.i686 0:6.2-10.el7 will be installed ---> Package samba-client-libs.i686 0:4.8.3-4.el7 will be installed --> Processing Dependency: samba-common = 4.8.3-4.el7 for package: samba-client-libs-4.8.3-4.el7.i686 --> Processing Dependency: samba-common = 4.8.3-4.el7 for package: samba-client-libs-4.8.3-4.el7.i686 --> Finished Dependency Resolution Error: Package: samba-client-libs-4.8.3-4.el7.i686 (base) Requires: samba-common = 4.8.3-4.el7 Installed: samba-common-4.8.3-4.el7.0.1.noarch (@fasttrack) samba-common = 4.8.3-4.el7.0.1 Available: samba-common-4.8.3-4.el7.noarch (base) samba-common = 4.8.3-4.el7 You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest

5 8

Known issues with c8 - release notes submissions
by Phil Wyett 04 Jul '19

04 Jul '19

Hi, Is there anyone responsible or a mechanism for CentOS 8 known issues for possible inclusion in release notes? For those who are running RHEL 8 like myself, it would be good if we could give a heads up for c8 folks with certain issues when it releases. Regards Phil -- *** Playing the game for the games sake. *** IRC: kathenas Twitter: kathenasorg Website: https://kathenas.org

2 1

SIG reports and the July newsletter
by Rich Bowen 01 Jul '19

01 Jul '19

Due to two months of back-to-back travel, I am way behind on the July newsletter. I still hope to get it done for Tuesday or Wednesday this week. This month, we expect reports from: * Alt Arch * Cloud * NFV * Promo * Storage as per the listing at https://wiki.centos.org/SpecialInterestGroup As I haven't given any of these groups my usual two-week warning, I imagine that this comes as a surprise. But if you can get me a report of some kind in the next couple of days, it would be hugely appreciated. If not, that's on me, not on you. Thanks. -- Rich Bowen - rbowen(a)redhat.com @CentOSProject // @rbowen 859 351 9166

1 0

Speakers needed: DefConf.US CentOS Dojo (August 14th, Boston)
by Rich Bowen 01 Jul '19

01 Jul '19

Hi, folks, I've had two of my speakers for the Dojo at DevConf.US fall through, and I need to find replacements. If you are interested in speaking at this event - August 14th, 2019 in Boston - please submit your proposed talk here: https://forms.gle/UgbodVpEUhnqHdNh6 Talks should be about something you're doing with, or on, or for, CentOS. Expect the audience to be very familiar with CentOS, and able to grasp deep technical details. -- Rich Bowen - rbowen(a)redhat.com @CentOSProject // @rbowen 859 351 9166

1 0

About PCYNLITX project and its innovations ( for C+++ multi-threading )
by Erkam Murat Bozkurt 01 Jul '19

01 Jul '19

Previously, I have presented my project to you. The current name of my project is PCYNLITX. PCYNLITX platform offers completely new programming technology which can be named as Programmable Meta-Programming System and PCYNLITX platform is just a particular application of this new programming methodology. Basically, PCYNLITX is an intelligent integrated development environment ( IDE ) which can produce an application-specific multi-threading library based on your needs and assists you in multi-thread software development process. PCYNLITX is not a multi-threading library. Instead, it is a multi-threading library generator. You can find out very comprehensive documentation about pcynlitx project from both project web site and source code repository. The addresses of the project web page and source code repository are given in below links. www.pcynlitx.tech https://sourceforge.net/projects/pcynlitx The outcome of the PCYNLITX platform acts as an autonomous thread management system provides deterministic scheduling of the threads. You can control the thread with the numbers given by you and determine the relation of the threads. In other words, different from the other multi-threading tools, you can directly schedule the threads independently from the operating system. The scientific journal of the project is under review on IEEE Transactions on Software Engineering. Currently, the PCYNLITX platform only works on Linux based operating systems and the other versions ( Windows and McOSx ) are under development. The License of the PCYNLITX platform is GNU GPLv3 Free Software License. You can find out many other documents including scientific introduction of the project (“Technical Introduction” ), code examples and GUI tutorial form the project web sites. You can also find out a documents introducing std::thread programming, pthread programming and OpenMP programming on the web sites. I am always waiting your valuable comments and contributions. Thanks and best regards. Erkam Murat Bozkurt M.Sc in Control Systems

2 1

Re: [CentOS-devel] Need info about kernel file "randomize_va_space"
by Maheshwari, Shagun 28 Jun '19

28 Jun '19

Hi, >> The file "/proc/sys/kernel/randomize_va_space" has write permission for user as below: >> [root@shagun ~]# ls -lrtZ /proc/sys/kernel/randomize_va_space >> rw-r--r--. root root system_u:object_r:proc_security_t:s0 /proc/sys/kernel/randomize_va_space >> >> If we want to change this permission to read only permission for the user. Is it possible? >> >> And i found the code also: >> >> kernel/sysctl.c @@ -1130,7 +1130,11 @@ static struct ctl_table kern_table[] = { .procname = "randomize_va_space", .data = &randomize_va_space, .maxlen = sizeof(int), +#ifdef CONFIG_ASLR_SYSCTL_READ_ONLY + .mode = 0444, +#else .mode = 0644, +#endif >> >> Can we make it as 0444, currently randomize_va_space is 644? > Any changes to the kernel should be requested through > https://clicktime.symantec.com/3KpmXJbD9xEqbGPHpBNCtpd7Vc?u=https%3A%2F%2Fb… for RHEL7's kernel package. > Why do you want root to not be able to write to that sysctl? Do you > not want it to be able to be modified? Because While running dASLR tool, "randomize_va_space unconfigurable" test in "Kernel Check" is FAILED. As per support for dASLR tool, "randomize_va_space_unconfigurable" fail means that "/proc/sys/kernel/randomize_va_space" has write permission. Regards, Shagun

3 2

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