devel June 2019

devel@lists.centos.org

39 participants
18 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

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

Need info about kernel file "randomize_va_space"
by Maheshwari, Shagun 26 Jun '19

26 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? Please suggest. Regards, Shagun

2 1

The future of the community build services
by Thomas Oulevey 26 Jun '19

26 Jun '19

Hi Folks, It's time to have a look to the SIGs and the community needs for the next version of the community build service(cbs). We would like to request feedback and know if the different communities plan on using modular builds, and what would be their timeline to be able to produce C8 artifacts (rpms, imagefactory builds, etc...). As you know Koji is now used to build CentOS 8 [1], and is based on the mbbox [2] distribution. It makes sense for cbs.centos.org to follow this trend and be based on the same templates. At the same time we needed to evaluate how and where we can deploy the new Openshift based templates, and associated builders for different arches. It's understood that the transition between both systems should be smooth and do not impact your C6/C7 builds and release cycle. We will plan accordingly. Please let us know, if you have comments and/or new ideas. -- Thomas Oulevey [1]: https://blog.centos.org/2019/06/centos-8-status-17-june-2019/ [2]: https://github.com/puiterwijk/mbbox

4 4

RFC: CentOS 8 Repository Structure
by Brian Stinson 25 Jun '19

25 Jun '19

Hi Folks, While we cycle through some of the remaining builds I'd like to start a discussion about what the CentOS 8 repo structure might look like. We need to think about what the repos look like on-disk, and how this might impact the mirrors. Currently the thinking is this: 3 "core" repos: - BaseOS (contains a small packageset of the base distribution) - AppStream ("where the modules go") - Devel ("-devel packages and other tools") These descriptions are very much an oversimplification, but it's an ok model to work with. We plan to compose all of those repositories, and deliver updates in the same stream. The x86_64 tree for the BaseOS repository will look something like this: x86_64 ├── debug # Note: we will likely snip this out and move debugs to debuginfo.centos.org │ └── tree │ ├── Packages │ └── repodata ├── iso └── os ├── EFI │ └── BOOT │ └── fonts ├── images │ └── pxeboot ├── isolinux ├── Packages └── repodata The plan is to re-compose BaseOS and all the "release" media like cloud images/ISOs at the traditional point-release times, and refresh the repodata in between as updates come in. Currently there are 3 primary architectures: x86_64, ppc64le, and aarch64, and 1 alternative architecture: armhfp. For CentOS 7 we split our primary and alternate architectures into /centos and /altarch on the mirrors to allow mirror admins to choose which trees to mirror. Is this something we'd like to continue? I welcome any questions and discussion that we might have. -- Brian Stinson brian(a)bstinson.com

12 42

CentOS 8 hardware enablement
by BC 17 Jun '19

17 Jun '19

According to https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/ht… a lot of hardware is no longer supported. Specifically SAS1 drivers are my concern. Does the CentOS team plan to include those drivers in a centos-extras kernel? Likewise, would anaconda's environment have support for them or is it expected that people will have to generate their own kernel and install image? Thanks!

3 2

liibseccomp 2.3.3
by Neale Ferguson 17 Jun '19

17 Jun '19

Hi, Are there any plans to get libseccomp into 7.6.1103? This fixes a problem with docker and the support of the statx() system call used by nodejs. Currently, libseccomp won’t let this call be executed within docker-ce 18.0x and above even though it’s in its seccomp profile. Fedora 28 has it so I could experiment with it but if something official is coming down the pike then I’d rather wait. Is it worth raising an issue? Neale

2 2

CFP for Ceph Days Netherlands closes *TOMORROW*
by Rich Bowen 13 Jun '19

13 Jun '19

Ceph days Netherlands will be held on July 2nd. The CFP closes TOMORROW, June 14th. https://ceph.com/cephdays/netherlands-2019/ -- Rich Bowen - rbowen(a)redhat.com @CentOSProject // @rbowen 859 351 9166

1 0

[CloudSIG] RDO Pike going EOL
by Alfredo Moralejo Alonso 13 Jun '19

13 Jun '19

Hi, OpenStack Pike was moved to Extended Maintenance upstream [1]. This means that no more releases will be produced for Pike series and there is no commitment on validation. Also, some projects may decide to not maintain the branches and go to EOL. >From the RDO perspective, this means that we are setting RDO CloudSIG Pike repo as EOL and the repositories will be dropped from CentOS official mirrors on next oportunity (when CentOS 7.7 is published). For users that still want to keep using packages from pike branches tip, we will keep the RDO Trunk Pike repo running in [2] chasing any new commit being merged, but note that we will probably stop running CI on it at some point in the near future. Best regards, Alfredo [1] https://docs.openstack.org/project-team-guide/stable-branches.html#extended… [2] https://trunk.rdoproject.org/centos7-pike/report.html

1 0

virusscan a RPM file?
by Fred Smith 12 Jun '19

12 Jun '19

Hi all! At work we've developed a package that we ship as an RPM. We also have a requirement to virusscan everything we ship. The company uses AVG antivirus on Windows. It can find and scan all the files in a zip file, but it scans only the RPM itself, not its contents. Anybody out thre know if RH (or Centos) has any tools for scanning contentss of files such as RPM that have other things embedded inside them? Thanks in advance! Fred -- ---- Fred Smith -- fredex(a)fcshome.stoneham.ma.us ----------------------------- Show me your ways, O LORD, teach me your paths; Guide me in your truth and teach me, for you are God my Savior, And my hope is in you all day long. -------------------------- Psalm 25:4-5 (NIV) --------------------------------

6 6

[rdo-users] [Meeting] RDO Meeting (2019-06-12) minutes
by Javier Pena 12 Jun '19

12 Jun '19

----- Forwarded Message ----- ============================== #rdo: RDO meeting - 2019-06-12 ============================== Meeting started by jpena at 15:00:29 UTC. The full logs are available at http://eavesdrop.openstack.org/meetings/rdo_meeting___2019_06_12/2019/rdo_m… . Meeting summary --------------- * roll call (jpena, 15:00:33) * Pike is now extended maintenance, time for EOL in RDO (jpena, 15:03:58) * ACTION: amoralej to send a mail about Pike CloudSIG repos being EOL (amoralej, 15:09:54) * tracking pike removal in https://trello.com/c/6e0bVGzK/712-pike-is-em-removal-from-rdo (amoralej, 15:13:09) * altarch container discussion (jpena, 15:14:02) * New release of python-sqlalchemy-collectd requires collectd subpackage which is included in opstools (jpena, 15:27:40) * LINK: https://review.opendev.org/#/c/659678/ (amoralej, 15:31:25) * LINK: https://review.opendev.org/#/c/659678/ is running with centos7 so we need to provide it (amoralej, 15:40:41) * ACTION: amoralej to follow-up with mrunge about the topic (amoralej, 15:45:03) * Next week's chair (jpena, 15:45:58) * ACTION: ykarel to chair the next meeting (jpena, 15:47:29) * open floor (jpena, 15:47:36) Meeting ended at 15:54:56 UTC. Action items, by person ----------------------- * amoralej * amoralej to send a mail about Pike CloudSIG repos being EOL * amoralej to follow-up with mrunge about the topic * mrunge * amoralej to follow-up with mrunge about the topic * ykarel * ykarel to chair the next meeting People present (lines said) --------------------------- * amoralej (76) * jpena (31) * mjturek (27) * ykarel (19) * mrunge (12) * zzzeek (12) * openstack (5) * baha (2) * gfidente (2) * mriosfer (1) * apevec (1) Generated by `MeetBot`_ 0.1.4 _______________________________________________ users mailing list users(a)lists.rdoproject.org http://lists.rdoproject.org/mailman/listinfo/users To unsubscribe: users-unsubscribe(a)lists.rdoproject.org

1 0

perl-CPAN-Meta-Check.noarch - CentOS 8
by Thomas Stephen Lee 11 Jun '19

11 Jun '19

Hi, Should perl-CPAN-Meta-Check.noarch be built for perl-DateTime-Locale? https://koji.mbox.centos.org/pkgs/work/tasks/9624/29624/root.log thanks -- Thomas Stephen Lee

4 7

Building CentOS Cloud Images
by john+centos＠johnkeates.com 06 Jun '19

06 Jun '19

I’m working on an internal build chain for AWS CentOS images, and I’m looking for any information regarding the changes or modifications made when creating the AMIs, aside from what’s already in the anaconda-ks file in currently uploaded AMIs. I know there isn’t much publicly available on the deployment source for CentOS-AWS images or how they are constructed in the first place, but any information on what’s added/removed on a base install would be great. (p.s. I might have accidentally sent this message twice, but once from an unregistered email address, I hope the first one simply doesn’t reach the list) Regards, John

2 1

Delta RPMs (drpms) for CentOS-6 and CentOS-7
by Johnny Hughes 05 Jun '19

05 Jun '19

We are having issues with drpms on CentOS-6 i386 and x86_64 and on CentOS-7 x86_64. The technical issues sometimes cause us to have to rebuild all drpms over again .. and the time involved is very large. Also storing the drpms and moving them around takes up a lot of space and bandwidth. We would like to remove delta rpms (drpms) from our CentOS-6 and CentOS-7 repositories. But before we do , we would like a discussion on these lists to ensure this is not going to cause people major issues. So, begin the discussion, and we will address this again in about a month. And we'll see where it leads. Thanks, Johnny Hughes

10 13

How altarch will be in CentOS 8?
by Marcin Juszkiewicz 04 Jun '19

04 Jun '19

CentOS 7 supports several architectures: - x86-64 - aarch64 - ppc64le - armhfp - i386 - ppc64 - power9 All except 'x86-64' are stored in /altarch/7/ directory on mirror.centos.org and are mirrored only by subset of mirrors. RHEL 8 treats aarch64, ppc64le, s390x, x86-64 as equals - package has to build on each of them to get included in repositories etc. So the question is how CentOS 8 will be organized? Moving everything into mirrors.centos.org/centos/8/ will simplify live for all of those using non-x86 machines as repos will be widely mirrored and there will be no need of handling centos|altarch in external projects. I think that /altarch/8/ may exist for armhfp, i386, etc architectures which are not a part of RHEL 8. What do you think?

8 9

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel June 2019