devel

devel@lists.centos.org

7 participants
4632 discussions

Reminder : CentOS 7 tags in CBS/koji will be locked next Monday
by Fabian Arrotin 28 Jun '24

28 Jun '24

Hi all, Just a reminder that CentOS 7 is reaching EOL and so content will be removed from mirrors. That also means that I'll lock the various CentOS 7 SIGs tags on https://cbs.centos.org and SIG content will also be removed from mirror.centos.org network. Worth knowing that SIG content (like OS itself) will be archived to https://vault.centos.org (as always) -- Fabian Arrotin The CentOS Project | https://www.centos.org gpg key: 17F3B7A1 | @arrfab[@fosstodon.org]

1 0

centpkg-sig - should we change to gitlab.com
by Troy Dawson 27 Jun '24

27 Jun '24

There is a pull request[1] for centpkg-sig to change the gitbaseurl from git.centos.org to gitlab.com/CentOS I have no idea how many CentOS SIG's are using centpkg-sig. And of those that do use it, if you are using git.centos.org or gitlab.com/CentOS. If your SIG is making rpm's, can you please let me know if you are using centpkg-sig. And if you are, what your gitbaseurl is set to. Thank You Troy [1] - https://git.centos.org/centos/centpkg/pull-request/99

2 2

Connecting Centos7 from different network
by talhakaynak96＠hotmail.com 26 Jun '24

26 Jun '24

Hello, I have no previous experience with CentOS and network administration. Therefore, I would like to emphasize that my questions may be at a basic level. I am currently working on a project and my goal is to be able to access and transfer files between my CentOS 7 computer and a Windows computer over different networks. My CentOS 7 computer is connected to the internet via ethernet via a modem, which has a static IP address (which I can provide if needed). I have also assigned a static IP address to the CentOS 7 computer. My goal is to use my Windows computer to remotely connect to my CentOS computer over different networks and transfer files. Best regards

2 2

Please fix linux-firmware in c10s
by pyhvtnr3＠duck.com 18 Jun '24

18 Jun '24

I noticed that in c10s, linux-firmware is still on 20240115, which is still on the kernel.org mirrors. On the GitLab however, it uses 20240328 which causes a 404 and is probably causing these builds to fail. I also noticed that the extra packages like "realtek-firmware" aren't being compiled, not sure if this is related. For those who want to run c10s on real hardware and have instant gratification, I have already compiled some RPMs in a virtual machine. But you should wait for them to be released officially, these can contain who knows what and may be outdated by the time you download them: https://mega.nz/folder/nRhGiIgS#RUKmzv9aDi2R3xIpR6gRhA By the way these were built with 20240610's files. Sorry if this email was bad, this was my first time doing release engineering ;)

2 2

2024-06-12 - CentOS Public Board Meeting
by Thomas Oulevey 11 Jun '24

11 Jun '24

Hi Everyone, Our next board meeting will take place at 20:00 UTC tomorrow `date -d "2024-06-12 20:00 UTC"` If you would like to attend please send me an email to alphacc(a)centosproject.org ( please do not reply to @centos-devel or use another email address) and you will receive a link to a meeting room with a passcode, 1 hour before the meeting takes place. The agenda can be checked at (work in progress) : https://hackmd.io/@centosboard/H19jLKNSA As a reminder we will enforce few rules : * Wait to be recognized by the Chair before speaking * Respect the Chair when told your time to speak is over - this will allow us to remain on agenda, and complete the meetings in the allotted time * In the event that there are Board-confidential topics, these will be put at the end of the meeting, in Executive Session, and guests will be asked to leave. We hope to minimize these items, but they do sometimes happen. The most common scenarios in which this may happen are personnel issues, or information that Red Hat wishes to share with the Board, but is not yet public. * Muting of participants, or, in extreme situations, ejection from the meeting, is at the sole discretion of the Chair. * Meetings will be recorded, and published to YouTube (possibly with edits/redaction, as approved by the Directors). Thus, by joining the meeting you consent to have your presence at the meeting, and anything you say during the meeting, made public. I hope some of you can join. thanks, -- Thomas 'alphacc' Oulevey CentOS Board of Directors Secretary alphacc(a)centosproject.org

1 0

Announcing CentOS Stream 10 tags/targets availability for cbs.centos.org/SIGs !
by Fabian Arrotin 11 Jun '24

11 Jun '24

As signed content landed on https://mirror.stream.centos.org (and so third-party/public mirrors too) , I implemented the needed changes at the https://cbs.centos.org side (tested before so just waiting for publicly available content) to support c10s (https://pagure.io/centos-infra/issue/1406) So you can now (as usual) create infra ticket (https://pagure.io/centos-infra/issues) to request tags for your SIG[s]. We tested the build+sign+push workflow for infra tag, and it worked fine, and got initial feedback from Storage SIG (https://pagure.io/centos-infra/issue/1360) for one test pkg and it worked too (so content is available through buildlogs.centos.org for testing and mirror.stream.centos.org for release tags) Worth knowing that SIGs depending on EPEL will have to wait, or rebuild themselves needed dependencies, as EPEL10 doesn't exist (yet). Happy building and testing against/for CentOS Stream 10 ! -- Fabian Arrotin The CentOS Project | https://www.centos.org gpg key: 17F3B7A1 | @arrfab[@fosstodon.org]

1 0

CentOS Stream 10 compose with 100% signed RPMs
by Adam Samalik 11 Jun '24

11 Jun '24

Hey everyone! The CentOS Stream 10 compose with 100% signed RPMs is now available! (links below) Please note the compose is still taking shape. Packages are still being added and even removed at this point. Not all packages are fully onboarded to gating, so just some updates are landing (more and more every day!). Packages are being moved between repositories. Comps groups are being updated... well you get the idea. But you can already contribute! Just please talk to the maintainers [1] first. Every team has their own plan and capacity to accommodate various levels of change. Oh and we don't have mirrors in place yet (coming soon though)! So I'm sending this just to the devel list. But the repo configuration (coming from the centos-stream-release package) points to the compose for now, so package installation and updates will work. Cheers! Adam PS: I know the compose URL says "production". That's the tooling doing this, it's a hardcoded word. But in reality it means "only signed packages from the pending tag" [2]. (It's actually c10s-compose: https://kojihub.stream.centos.org/koji/taginfo?tagID=1556 ) There's also a "development" compose which means "unsigned packages from the candidate tag". (And this one is in fact c10s-compose-development: https://kojihub.stream.centos.org/koji/taginfo?tagID=3301 ) As a reminder, the "candidate" tag represents builds that pass gating, but haven't gone through internal paperwork and "haven't properly landed" yet. They're also not in the buildroot. The "pending" means it went through all that. PPS: Compose tests are not passing yet! But they're running, and the system is installable (at least was for me when writing this!) and definitely usable for playing around with. Test results: https://testing.stream.centos.org/view/c10s%20-%20compose/ PPPS: Yes, I know, the installer still has the old CentOS logo. But the Artwork SIG has it all ready, we just need to update the package: https://gitlab.com/CentOS/artwork/centos-brand/-/issues/2 --- The links! The compose: https://composes.stream.centos.org/stream-10/production/latest-CentOS-Strea… Install ISOs: - aarch64: https://composes.stream.centos.org/stream-10/production/latest-CentOS-Strea… - https://composes.stream.centos.org/stream-10/production/latest-CentOS-Strea… - ... and other arches, it should be findable! Container images: - $ podman pull quay.io/centos/centos:stream10-development - https://quay.io/repository/centos/centos?tab=tags [1] Open a RHEL bug / issue: https://docs.centos.org/en-US/stream-contrib/quickstart/#_1_file_an_issue [2] Tag structure: https://docs.centos.org/en-US/stream-contrib/quickstart/#_release_engineeri… -- Adam Samalik --------------------------- Principal Software Engineer Red Hat

7 10

homes
by chintucharan844＠gmail.com 08 Jun '24

08 Jun '24

[url=https://www.example.com] example [/url] <a href="url=https://www.example.com"> example </a>

1 0

Re: CentOS Stream 10 compose with 100% signed RPMs
by Mike Rochefort 06 Jun '24

06 Jun '24

On 6/6/24 1:22 PM, Leon Fauster via devel wrote: > Does libosinfo/osinfo-db needs an update? I don't see a c10s config in osinfo-db. What sections would be okay to add at the current state of development? https://gitlab.com/libosinfo/osinfo-db/-/tree/main/data/os/centos.org

1 0

Reminder about el8 SIG packages moving next week to new location/URL
by Fabian Arrotin 04 Jun '24

04 Jun '24

Per discussion on this list some time ago (https://lists.centos.org/hyperkitty/list/devel@lists.centos.org/thread/BYSK…) , and also aligned with CentOS Stream 8 EOL (including for SIGs content), we'll proceed next Monday with the announced change : The SIG that opted in to build against/for RHEL8 (and not CentOS Stream 8) had their packages pushed the same way centos linux 7 was. Per thread linked above, there was a proposal from the kmods SIG (and no other SIG minded against) to start pushing to the mirror.stream.centos.org network (instead of "legacy" mirror.centos.org, which will be empty soon), and so starting to be using mirrormanager (as mirrorlists.centos.org service itself will disappear end of June, due centos linux 7 going EOL) Since March 2024, there was a script that was just keeping http://mirror.centos.org/centos/8/<SIG>/ content in sync with the new destination https://mirror.stream.centos.org/SIGs/8/<SIG>/ . That ensured that SIGs would have enough time to communicate the new location and also provide eventually newer .repo files # What will happen next week ? Content from mirror.centos.org will be emptied (for both 8-stream and 8) and SIG content for 8 (rhel8) will be pushed to new location directly (no intermediate step) # What about your .repo files ? Same rule as for 9-stream and so documented in the SIG guide : https://sigs.centos.org/guide/delivery/#centos-stream-9-and-above_1 Kind Regards, -- Fabian Arrotin The CentOS Project | https://www.centos.org gpg key: 17F3B7A1 | @arrfab[@fosstodon.org]

1 1

← Newer
1
...
8
9
10
11
12
13
14
...
464
Older →

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