devel

devel@lists.centos.org

4 participants
4640 discussions

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

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