devel July 2019

devel@lists.centos.org

33 participants
20 discussions

forums + portal for {lang}.centos.org sites
by Karanbir Singh 16 Aug '24

16 Aug '24

Hi, Earlier in the evening today Ralph, Fabian and I had a chat about the present state of the language subsites. This email sort of summarises the main issue ( s/w ). We seem to have run into a slight technical hitch with punbb/fluxbb. They dont support LDAP as a backend. And we had decided a few months back that all new rollouts must have ldap backend so we can rollin CentOS-DS / openldap based backend. So we need to look at alternatives, and since the primary focus of these international sites is going be forums : Here is a shortlist ( if there is anything else that people are aware of, please add to this list ) - phpBB - SMF - Fudforum - phorum - fluxbb Requirements: - Must be able to scale ( couple of hundred thousand msgs ) - Must be able to handle ldap auth ( if it cant, whats involved in writing the ldap-auth portion ) - Must address the specific requirements raised by the present www.centos.org forum users ( Can you please fill this section in ? ) - Must support all languages we need ( pure utf8 support would be good ) - Secure - Skin'able Nice to have: - Capable of running multiple instances from a single deployment - responsive community :D Things we will need to do: - Decide on what s/w to use. - Give the ArtWork people enough time to get the look & feel sorted. - Migrate newbb forums from www.centos.org to $system ( hey, english is a language too :D ). - Migrate fr.centos.org into the final s/w - setup {de/es/ja/it/pt_br}.centos.org Actions: Ralph and Fabian are going to work on setting up a test ldap server, once that is online we will then start by installing into our test-vm-farm the various s/w to eval them. If anyone would like to help, please feel free to jump right in. I'll setup a wiki page for this issue, which might be a good place to track progress. -- Karanbir Singh : http://www.karan.org/ : 2522219@icq

22 81

CentOS 8 Artwork needed
by Rich Bowen 31 Jan '20

31 Jan '20

To all the artists and designers here, we need your help. With RHEL 8 beta released, we need to start producing artwork for CentOS 8. It's time for the CentOS Artwork SIG, and anyone else that's interested in contributing to this effort, to start working on everything that will be needed for the new release. What we know we need is anaconda artwork, and new desktop backgrounds to replace the current '7' themed stuff. As we dig, we may find more things that need to be updated to the new 8 theme. Additionally, we will need to update some of the assets listed here: https://wiki.centos.org/ArtWork/Identity ... and produce new assets for 8 to be listed here: https://wiki.centos.org/ArtWork/Brand/Logo And, finally, we need someone to step up to lead this effort. While we don't yet know for certain when RHEL 8 will officially release, it's safe to assume that it's soon, and we need your help. -- Rich Bowen - rbowen(a)redhat.com @CentOSProject // @rbowen 859 351 9166

10 30

Using mirrorlist in centos-release-* packages
by Anssi Johansson 12 Sep '19

12 Sep '19

Hi, as mentioned in https://lists.centos.org/pipermail/centos-devel/2018-September/016949.html mirrorlist.centos.org has been updated to produce mirror lists for SIG content as well. Some centos-release-* packages have already been modified to use mirrorlist.centos.org instead of mirror.centos.org, but many still point to mirror.centos.org. Most of mirror.centos.org hosts are also used for seeding the 600+ external mirrors we have. By directing some of their download traffic to external mirrors we can offer faster sync speeds for those external mirrors, and for people downloading individual rpms from mirror.centos.org. Second, most of those external mirrors offer faster download speeds to end users than what could be achieved by downloading from mirror.centos.org, so the users will benefit from this change as well. The better geographical coverage does not hurt either. mirror.centos.org nodes are donated servers, and it would be kind to the sponsors to use their bandwidth sparingly. The .repo files should be modified so that the current baseurl line gets commented out and a mirrorlist entry gets added, like this: mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch… #baseurl=http://mirror.centos.org/$contentdir/$releasever/storage/$basearch/gluster-4.1/ Note that mirrorlist.c.o can automatically choose between main and altarch content based on the arch parameter. The repo names are constructed from the repository path by stripping away the architecture and changing any slashes to dashes: sclo/x86_64/rh -> sclo-rh, sclo/x86_64/sclo -> sclo-sclo, paas/x86_64/openshift-origin311 -> paas-openshift-origin311, storage/x86_64/gluster-5 -> storage-gluster-5 etc. You can use 'curl' to check what mirrorlist outputs for your repository. New repos are added to mirrorlist.centos.org automatically once the repository hits mirror.centos.org. That script is currently run every three hours. I guess it could be run more frequently (it's fairly lightweight), but you should give the external mirrors a few hours to sync before announcing your release anyway. You can either submit an update to your current centos-release-* file now, or wait until you need to create a new centos-release-* package for other reasons such as releasing softwarepackage-(version+1) which uses different paths. My recommendation would be to submit an update to your current centos-release-* package, so that you would not need to worry about this when you eventually need to publish a new one for other reasons. We released an updated centos-release package for CentOS AltArch before 7.6.1810 was released for this exact reason, ie. we didn't need to worry about this change at 7.6.1810 release time. Other people (such as bstinson, arrfab and hughesjr) can probably help with creating and publishing an updated centos-release-* package, but the usual tagging procedure to extras will apply. The SIG Guide https://wiki.centos.org/SIGGuide should have all the needed details for this (if not, complain to bstinson). It is highly recommended to actually test your new centos-release-* package from buildlogs before you ask that package to be signed and pushed to extras. The holiday season is fast approaching so (I) don't expect much activity regarding these changes in the following days. I'm hoping that the SIGs would take a look at this in early 2019, though. Thanks to those SIGs who have already made these changes to their centos-release-* packages! If you have questions, feel free to ask either here or on #centos-devel. Thanks for your time!

1 2

rh-ruby26
by Marko Bevc 13 Aug '19

13 Aug '19

Hi. Not sure this is the right mailing list, but do we have a status when those packages would be available for CentOS 7? Or can someone point me in the right direction? Thanks. Cheers, Marko

2 2

Community build services and EPEL8
by Thomas Oulevey 31 Jul '19

31 Jul '19

Hello folks, In the planning of next Community build services, a new question came up. In the past we never allowed EPEL repositories to be used as external repositories for SIGs. Doing so, would allow to build against EPEL packages and not duplicate the work for maintainers in EPEL/SIGs. However it would mean also building against a moving target which can be difficult if EPEL policies are the same as today. As EPEL 8 is also in the making it would be good to hear what SIGs think about this specific issue. Let us know ! -- Thomas Oulevey

17 48

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

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

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel July 2019