devel

devel@lists.centos.org

16 participants
4590 discussions

Start a nNew thread

CS8 repos / repomd.xml.asc
by Leon Fauster 02 Mar '22

02 Mar '22

Hey. It seems that the mirrors do not have the repomd.xml.asc file. Does the main repo provide it? -- Thanks Leon

5 8

Fw: [CentOS-announce] CESA-2022:0442 Important CentOS 7 log4j Security Update
by Kumar, Sanjeev 02 Mar '22

02 Mar '22

Hi John (Johnny Hughes), Is there a way to get this latest log4j 1.2.17 version be certified as a supported version in the Tenable Plugin Alert as seen below: https://www.tenable.com/plugins/nessus/156032 Since the fix is officially deployed in the mirrors, wouldn't that make the 1.2.17 version a supported version for the nessus plugin? Regards, Sanjeev ________________________________ From: CentOS-announce <centos-announce-bounces(a)centos.org> on behalf of Johnny Hughes <johnny(a)centos.org> Sent: Monday, February 7, 2022 11:47 AM To: centos-announce(a)centos.org <centos-announce(a)centos.org> Subject: [CentOS-announce] CESA-2022:0442 Important CentOS 7 log4j Security Update Warning: Replies to this message will go to centos-announce-bounces(a)centos.org. If you are unsure this is correct please contact the helpdesk. CentOS Errata and Security Advisory 2022:0442 Important Upstream details at : https://usg02.safelinks.protection.office365.us/?url=https%3A%2F%2Faccess.r… The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 1b461b4e217ac5f51d8990aad583c7f189e73fd3220a54053124772b83c42eba log4j-1.2.17-18.el7_4.noarch.rpm e4950b148639895cb3ed78b8a00c0708abe4685bd380e0003ebeb947ea1edc42 log4j-javadoc-1.2.17-18.el7_4.noarch.rpm 7bbf77456d5e310210c4bd541fee70097c26568f34f44184c878e5874e2b57f1 log4j-manual-1.2.17-18.el7_4.noarch.rpm Source: c4224181672eede65a1b3d8f829c9ed475cade9b7234f58c03994f39459ca732 log4j-1.2.17-18.el7_4.src.rpm -- Johnny Hughes CentOS Project { https://usg02.safelinks.protection.office365.us/?url=http%3A%2F%2Fwww.cento… } irc: hughesjr, #centos(a)libera.chat Twitter: @JohnnyCentOS _______________________________________________ CentOS-announce mailing list CentOS-announce(a)centos.org https://usg02.safelinks.protection.office365.us/?url=https%3A%2F%2Flists.ce…

3 2

Building python38-createrepo_c in CentOS 8 Stream
by Ewoud Kohl van Wijngaarden 02 Mar '22

02 Mar '22

Hello everyone, I'm sending this on behalf of the packagers of the Pulp project. The Pulp project uses createrepo_c and in particular the Python bindings. The appstream repository does contain python3-createrepo_c but Pulp needs Python 3.8 so it uses the 3.8 module. There is no python38-createrepo_c so for now we're building it ourselves. The problem shows up when createrepo_c is bumped in CentOS Stream. From repoclosure: Depsolve Error occured: Problem: package python38-createrepo_c-0.17.7-3.2.el8.x86_64 requires createrepo_c-libs = 0.17.7-3.2.el8, but none of the providers can be installed - cannot install both createrepo_c-libs-0.17.7-4.el8.x86_64 and createrepo_c-libs-0.17.7-3.2.el8.x86_64 - cannot install both createrepo_c-libs-0.17.7-3.2.el8.x86_64 and createrepo_c-libs-0.17.7-4.el8.x86_64 - cannot install the best update candidate for package python38-createrepo_c-0.17.7-3.2.el8.x86_64 - cannot install the best update candidate for package createrepo_c-libs-0.17.7-3.2.el8.x86_64 It would be ideal if CentOS itself built python38-createrepo_c (and possibly also for other Python modules). Is this something that could be done? Regards, Ewoud

2 3

vault outage
by BC 01 Mar '22

01 Mar '22

I have been unable to connect to vaul since yesterday. Is this a known issue? I can ping in from multiple regions.

2 1

c8 container images - old - ?
by lejeczek 01 Mar '22

01 Mar '22

Hi guys I pulled one yesterday: -> $ podman pull registry.centos.org/centos:latest and it's old EOL centOS 8. Should not there be 'stream' in repos already and EOL ones be removed & gone? (or am I missing something) many thanks, L.

3 3

CentOS SIGs and lookaside cache
by Pierre-Yves Chibon 28 Feb '22

28 Feb '22

Good Morning Everyone, There are currently two lookaside caches in use around the CentOS project: * One used by CentOS-Stream: https://sources.stream.centos.org/sources it's not browsable, but it uses the structure: `baseurl/pkgname/tarball/hashtype/hash/tarball`. Example: https://sources.stream.centos.org/sources/rpms/kernel/linux-5.14.0-62.el9.t… * One used by CentOS-Linux, CentOS-Stream 8 and the SIGs: https://git.centos.org/sources/ this one is browsable and as you can see uses the structure: `baseurl/pkgname/branch/hash`. Example: https://git.centos.org/sources/kernel/c8s/0c4e10577cfd4b4f8e3d83c0406da8ab0… The rest of this email focuses on this second one. SIGs upload to it using the route: https://git.centos.org/sources/upload.cgi In an email last week [1] was proposed an idea for how SIGs could leverage the centos namespace in gitlab for those who wishes. One of the benefits of using gitlab would be increased flexibility for SIGs and a clear example for this would be the ability to drop the branch structures currently imposed on the git repositories. That structure is imposed because the git repositories are shared between CentOS-Linux, CentOS-Stream and (potentially multiple) SIGs, so that structure ensures groups are not stepping on each other's toes. By moving the SIGs out of these shared repositories, imposing that structure is no longer needed. However, since the lookaside cache relies on branch name, lifting that structure would break the lookaside cache. I have already brought this idea to a few folks to see if the idea was sane. The consensus that emerged is: * Introduce a new upload endpoint next to the existing one, something like: https://git.centos.org/sources/sig_upload.cgi * That new endpoint would upload the sources given using the same structure as the one used for CentOS-Stream, but ensuring that the person uploading is member of at least one SIG. The idea of using `sig_upload.cgi` instead of just replacing `upload.cgi` is the assumption that we want to preserve the current structure used for CentOS-Linux and CentOS-Stream, allowing to find more easily which sources are used where and not impacting the process Red Hat uses to push its releases. Since the structures used by the two upload scripts are different, they will not conflict. What we will end up seeing is something like: sources │ ├── pkg1 │ ├── c7 │ │ ├── hash1 │ │ └── hash2 │ ├── c8 │ │ ├── hash3 │ │ └── hash4 │ ├── tarball1 │ │ └── sha name │ │ └── hash5 │ │ └── tarball1 │ └── tarball2 │ └── sha name │ └── hash6 │ └── tarball2 │ └── pkg2 ├── c8 │ ├── hash7 │ └── hash8 ├── c8s │ ├── hash9 │ └── hash10 ├── tarball3 │ └── sha name │ └── hash11 │ └── tarball3 └── tarball4 └── sha name └── hash12 └── tarball4 and so on On CBS, the script that downloads the sources, will then need to be adjusted to try first the old structure before trying the new one. This may slow down a little bit the builds, but that should be most of the time, at most by a single http request. In this email I'm calling for feedback, do you like the idea? I'm happy to work on making it happen if there is consensus on this :) Looking forward for your thoughts, Pierre [1] https://lists.centos.org/pipermail/centos-devel/2022-February/120216.html

5 11

Using lookaside_upload in combination with the "flat" dist-git layout
by Daan De Meyer 25 Feb '22

25 Feb '22

Hi, Recently there was an announcement that the "flat" layout can now be used by SIGs that want to pull in changes from the Fedora RPM repos directly. I'm trying to switch the hyperscale branches for the systemd RPM to use the "flat" layout but I'm running into issues trying to upload the systemd tarball to the CentOS lookaside cache. I've successfully used the lookaside_upload script from centos-git-common to upload tarballs for use with the rpmbuild metadata layout before, but I'm struggling to get it to work with the "flat" layout. The main issue comes from the fact that in the "flat" layout, the sources file is used which contains a SHA512 hash that's used to find the corresponding tarball in the centos lookaside cache. However, the lookaside_upload script tries to upload tarballs to the lookaside cache using the sha1sum of the tarball as the identifier. This leads to CBS not finding the tarball when trying to do a build. I tried modifying the lookaside_upload script to use sha512sum instead of sha1sum but when doing this, I get a 500 HTTP internal error from the lookaside cache (https://paste.centos.org/view/5e7ef15c). Any other way to upload a tarball under the SHA512 identifier to the lookaside cache? Cheers, Daan De Meyer

1 1

[Storage-SIG] cephadm is not last version
by Luis Domingues 21 Feb '22

21 Feb '22

Hello, We are currently testing deploying clusters using CentOS Storage SIG. And while almost all packages are available on last version (16.2.7), we notice that cephadm was only on 16.2.5. Is any reason for that? Thanks, Luis Domingues Proton AG

4 4

Announcing possibility for SIGs to use "flat layout" on git.centos.org
by Fabian Arrotin 21 Feb '22

21 Feb '22

Recently, a thread (see https://lists.centos.org/pipermail/centos-devel/2022-January/120171.html) was started onn this list to discuss the possibility to let SIGs pushing to git in a "flat layout" style instead "rpmbuild layout" style on git.centos.org. As you know, since the beginning of git.centos.org, Red Hat pushed (as is still pushing, no change in sight for that part) in each /rpms/<package_name> git project in the "rpmbuild layout" style (so with SPECS/<pkg_name>.spec , eventually SOURCES/*) That's what SIGs have been using for years now, and it's how it's also documented in the SIG guide (see https://sigs.centos.org/guide/git/) Some SIGs wanted to bring "flat layout" style support so that they can just import existing branch from Fedora/Epel directly on git.centos.org without a need to change the dist-git layout, so get_sources.sh (from https://git.centos.org/centos-git-common) was recently modified to detect in which format the git repo is laid out and so how to retrieve sources from https://git.centos.org/sources. This request was all tracked in ticket https://pagure.io/centos-infra/issue/659 The needed new centpkg-minimal (https://cbs.centos.org/koji/packageinfo?packageID=8196) was built/pushed "live" today on cbs.centos.org , as some --scratch builds were tested with automotive SIG to confirm that it was working fine. We'll just add a simple note on the SIG Guide to mention that it's now possible to use the "flat layout" style (like Fedora/Epel) on git.centos.org for SIGs willing to use that layout. -- Fabian Arrotin The CentOS Project | https://www.centos.org gpg key: 17F3B7A1 | twitter: @arrfab

1 0

Linux Engineering update
by Josh Boyer 16 Feb '22

16 Feb '22

Hi All, I wanted to take a moment to thank the CentOS Stream contributor community and give an update on where we're at from the Red Hat Linux Engineering side. The contributions coming in for CentOS Stream, particularly Stream 9, have been fantastic. This is the kind of feedback loop we are trying to build, and the willingness to jump in headfirst from the community even though we still have some bumpy spots in workflow and guidance is much appreciated. We've seen: - package rebases - compose adjustments - bug fixes - subpackage additions and more from the community. While not all of them were accepted into CentOS Stream, overall it's been great. As we march towards spring, the Linux Engineering team is going to be focusing on finishing up the releases of Red Hat Enterprise Linux 8.6 and 9.0. Thankfully, the continuous development model of CentOS Stream means that it won't stop and community contributions should keep on going. With that being said, what each Linux Eng team needs to do varies widely and it may result in some slower or intermittent responses to contributions for the next few months. If someone doesn't respond quickly or asks to defer a contribution, please have a little patience. We'll get to it eventually. Lastly, I wanted to give some forward-looking contribution advice. CentOS Stream 9 has seen quite a bit of flux since we made it available. This has been quite helpful to shape the Red Hat Enterprise Linux 9 Beta, and what will be the RHEL 9 GA. After RHEL 9 GA, things will solidify more into what one would normally expect from an Enterprise Linux operating system. Package versions will settle, rebases will be less common, and our Linux Eng maintainers will need to evaluate CentOS Stream 9 contributions fully against the standards we have for RHEL. For contributions that are just outside of those standards in some way, we have a variety of other avenues within the CentOS project. Several CentOS SIGs are active today, building additional content on top of CentOS Stream. We also have associated projects like EPEL. If you have a contribution and you're not quite sure if it's something CentOS Stream can accommodate, please reach out to the Feature Request SIG [1]. They're there to help you navigate the best place for a contribution, and to help shephard along where they can. Thank you so much for the success we've had to date. It's far from perfect, but building out a new project is fun in and of itself. josh [1] https://wiki.centos.org/SpecialInterestGroup/StreamFeatureRequest

1 0

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