devel

devel@lists.centos.org

4604 discussions

[Artwork] CentOS Stream logo
by Rich Bowen 23 Jun '21

23 Jun '21

Hi, Artwork folks (and everyone else!) Some people within Red Hat have a need/desire for a CentOS Stream logo which can be used to distinguish CentOS Linux from CentOS Stream for some messaging. They have proposed the attached for this purpose. There were, in fact, several other proposed ideas, too, and I have pointed them to https://git.centos.org/centos/Artwork/issue/1 to continue that part of the conversation, as many of them involved changes to the core CentOS logo, which is, of course, a much larger conversation. Are there any objections from the Artwork SIG to using the proposed image? I think maybe it's not *strictly* compliant with our brand guidelines. Any thoughts here?

3 4

Wordpress theme: Call for volunteer(s)
by Rich Bowen 20 Jun '21

20 Jun '21

If you are adept at designing Wordpress themes, or adapting existing ones, I am looking for you. While there's nothing wrong with our existing blog theme, it's time to freshen it up, and possibly incorporate some of the CentOS 8 imagery and bring it into the same style family as the main centos.org website. If you're able and willing to work on this, please let me know. Thanks. -- Rich Bowen: CentOS Community Manager rbowen(a)redhat.com @rbowen // @CentOSProject 1 859 351 9166

2 7

[NFV SIG] NFV SIG meeting minutes - 2020-06-16
by Alfredo Moralejo Alonso 16 Jun '21

16 Jun '21

============================================= #centos-meeting: NFV SIG meeting - 2020-06-16 ============================================= Meeting started by amoralej at 15:07:50 UTC. The full logs are available athttps://www.centos.org/minutes/2021/June/centos-meeting.2021-06-16-15.07.… . Meeting summary --------------- * status of OpenvSwitch and OVN 2.15 (amoralej, 15:11:22) * ovn-2021 builds are available for CentOS Stream 8 in official mirrors no (amoralej, 15:11:52) * RDO is moving to openvswitch2.15 and ovn-2021 in Xena release https://review.rdoproject.org/r/c/rdoinfo/+/33919 (amoralej, 15:12:33) Meeting ended at 15:35:31 UTC. Action Items ------------ Action Items, by person ----------------------- * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * amoralej (38) * dholler (14) * centbot (3) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot

1 0

CentOS Board welcomes new directors
by Rich Bowen 15 Jun '21

15 Jun '21

The CentOS Board of Directors is delighted to welcome two new directors - Davide Cavalca and Josh Boyer - to the Board. Please join us in welcoming them, and thanking them for their willingness to dedicate some of their time to the endeavor of steering the CentOS Project. Once again, we thank outgoing directors Karsten Wade and Carl Trieloff for their years of service.

3 2

Purpose of composes.centso.org?
by redbaronbrowser 11 Jun '21

11 Jun '21

I am curious about composes.centos.org and it's intended use case or guidance on what it should/can be used for. If it is reasonable, I would like to try to write a dnf plugin to simplify using it for package rollbacks. Is someone else already working on this? Is there a better way to go about doing this? Ultimately, I would like it so when submitting a bug about a regression, it is easy for the user to specify between what compose dates the regression first appeared.

5 6

repomd.xml.asc outdated?
by Leon Fauster 11 Jun '21

11 Jun '21

JFYI: LANG=C yum update --noplugins ... Error: Failed to download metadata for repo 'appstream': repomd.xml GPG signature verification error: Bad GPG signature http://mirror.centos.org/centos-8/8/AppStream/x86_64/os/repodata/ shows repomd.xml 2021-03-16 15:43 repomd.xml.asc 2021-03-03 00:29 -- Leon

5 6

RFC: kmods SIG Proposal
by Peter Georg 11 Jun '21

11 Jun '21

Dear all, I'd like to propose a SIG for CentOS Stream. Please see the proposal below. Note: In case anyone has a better suggestion for a name, please let me know. I'm really terrible at naming things. And sorry in advance for any spelling or grammar mistakes (I'm not a native english speaker). For everyone following the previously posted "RFC: Stream Kernel SIG Proposal": The goal of the "kmods" SIG proposed here has previously been proposed to be added to a potential "Stream Kernel SIG" as a fifth goal. However it seems to make sense to split the various different goals into seperate SIGs. Disclaimer: I used the Hyperscale SIG description (https://wiki.centos.org/SpecialInterestGroup/Hyperscale) as a template. I hope that's OK. Best, Peter Proposal: = kmods SIG = == Goals == The kmods SIG will focus on providing kernel modules currently not available in CentOS Stream. == Status == Proposed: RFC and looking for a sponsoring Governing Board member == What's in scope == This SIG is a good place for any kernel module that is beneficial to CentOS Stream, but cannot be directly contributed to any of the involved upstream projects. These kernel modules may be divided in three categories: === Restore support for deprecated devices === The CentOS Stream kernel includes several kernel modules for which the list of supported devices has been limited by Red Hat. This SIG aims to provide versions of these kernel modules with restored support for as many deprecated and removed devices as possible. A close collaboration with the kernel-plus developers is desired for these kernel modules. === In-kernel modules not enabled for CentOS Stream === Many in-kernel modules are simply disabled for the CentOS Stream kernel. This may either be due to drivers being deprecated and removed compared to older CentOS major releases or never being enabled in the first place. This SIG aims to provide these in-kernel drivers as external kernel modules to enable CentOS Stream running on a broader range of available hardware and provide other beneficial functionality. A close collaboration with the kernel-plus developers is desired for these kernel modules. In addition it is desired to work with upstream to get any valuable kernel modules directly into the CentOS Stream kernel. === Third-party external kernel modules === This SIG also aims to provide third-party kernel modules for CentOS Stream not (yet) available in upstream kernel. == What's not in scope == Anything that can be contributed directly to any of the involved upstream projects is not in scope. This includes, but is not limited to: * New user space packages: These should be submitted to Fedora/EPEL * Support for new architectures currently not supported by CentOS Stream * Third-party kernel modules with non compatible license == Roadmap == * Provide packages for in-kernel modules with restored support for deprecated devices * Provide packages for in-kernel modules that have been supported in older CentOS major releases * Provide packages for further beneficial kernel modules requested by the community == Resources == TBD == Communication == The SIG uses the [[https://lists.centos.org/mailman/listinfo/centos-devel|centos-devel]] mailing list for coordination and communication. TBD: Add note about regular meetings once established. == Membership == The current set of members is: ##begin-members * ... ##end-members The SIG is co-chaired by ... and .... Everybody is welcome to join and contribute to the SIG. Membership can be requested by asking on the [[https://lists.centos.org/mailman/listinfo/centos-devel|centos-devel]] mailing list. Any current member can raise objections and request a simple majority vote on membership applications. SIG members are expected to actively contribute or otherwise remain engaged with the project. Stale members may be removed by a simple majority vote after six months of inactivity. The SIG is co-chaired by two equal chairpersons elected by SIG members for one year. Each chairperson is elected individually using a plurality vote.

14 56

[Cloud SIG] CentOS Cloud SIG meeting minutes (2021-06-10)
by Alfredo Moralejo Alonso 10 Jun '21

10 Jun '21

====================================================== #centos-meeting: CentOS Cloud SIG meeting (2021-06-10) ====================================================== Meeting started by amoralej at 15:07:28 UTC. The full logs are available athttps://www.centos.org/minutes/2021/June/centos-meeting.2021-06-10-15.07.… . Meeting summary --------------- * roll call (amoralej, 15:08:18) * Move jobs from ci.centos.org to new openshift cluster (amoralej, 15:12:36) * LINK: https://jenkins-cloudsig-ci.apps.ocp.ci.centos.org/ (amoralej, 15:13:24) * AGREED: to stay on JJB for the new jenkins (amoralej, 15:22:49) * LINK: https://pagure.io/centos-infra/issue/352 (amoralej, 15:23:48) * LINK: https://centosci.github.io/ocp4-docs/ (amoralej, 15:36:49) * LINK: https://centosci.github.io/ocp4-docs/sops/migration/ (apevec, 15:37:59) * ACTION: amoralej to create a trello card for the migration (amoralej, 15:40:19) * open discussion (amoralej, 15:44:14) Meeting ended at 15:48:27 UTC. Action Items ------------ * amoralej to create a trello card for the migration Action Items, by person ----------------------- * amoralej * amoralej to create a trello card for the migration * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * amoralej (91) * apevec (62) * ykarel (15) * jcapitao (6) * centbot (5) * spotz (4) * jpena (3) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot

1 0

CentOS Community Code of Conduct
by Rich Bowen 08 Jun '21

08 Jun '21

As per my email in April - https://lists.centos.org/pipermail/centos-devel/2021-April/076769.html - and per the approval of the Board of Directors, we have published the new CentOS Community Code of Conduct: https://www.centos.org/code-of-conduct/ This Code of Conduct is in effect immediately, and the reporting process described in there is in effect immediately. One note: The doc says that it is "a living document and will be updated when and if it is deemed necessary." One change that we forsee very soon is that, rather than me, as Community Architect, being the sole responsible party for reporting CoC incidents, I will be assembling a small CoC committee. While I have identified some of the people who will be part of that committee, I thought it was good to go ahead and publish the CoC as is, and modify it once that committee is all in place. Thanks to everyone that participated in the review process for this policy. --Rich, on behalf of the Board of Directors.

1 0

docker, CVE-2019-13139 and announcements for updates in extras
by Stefan Puiu 05 Jun '21

05 Jun '21

Hi, We run a CentOS 7-based (actually, CentOS 7 atomic host) image on our hardware boards. We ran a third party "security scan" that seems to look at the list of packages in the distro and check if fixes or advisories have been published for the package versions installed. I guess they have a database of CentOS / RHEL advisories and can cross check the versions there. For a while now, the tool has been complaining that the version of docker we ship is vulnerable to CVE-2019-13139. As far as I can tell, we have a version that includes the fix, based on the Red Hat advisory: https://access.redhat.com/errata/RHBA-2019:3092 says we need docker-1.13.1-104.git4ef4b30, and we have 204.git0be3e21. We've tried to raise this with the tool vendor, but they have asked if we have "vendor documentation" for that fix being applied. My understanding is that they mean something like the centos-announce emails announcing the integration of fixes from RHEL to CentOS, with something like, for example, RHSA-2021:0617 being labeled as CESA-2021:0617; they said they couldn't find the corresponding CEBA-2019:3092. Now, I've looked in the centos-announce list archives since October 2019, when the RH advisory was published, and didn't find anything related to Docker. I saw a mention of the CVE in a CentOS bug, though (https://bugs.centos.org/view.php?id=16804) I'm trying to work with the tool vendor to sort this out. As a developer, I think checking the code is the best way; I've found the Docker RH fork on github, which has a RHEL branch that seems to be used in both CentOS and RHEL (https://github.com/projectatomic/docker/tree/docker-1.13.1-rhel) However, probably the tool people have some kind of different process in place. So my question is: is it reasonable to expect any bugfix or security update fetched from RHEL to CentOS to come with an announcement on the centos-announce mailing list? Is there a filter for some packages? I see docker is in extras, not in CentOS-Base, maybe updates to those are not announced? Thanks, Stefan.

3 4

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