September 2022 - devel - lists.centos.org

anaconda dependency calculation?
by Nicholas Byrne 04 Aug '25

04 Aug '25

Hi all, I'm trying to find a tool that calculates all dependencies for a specific package or group of packages for use with CentOS 5 (beta) with the intention of putting together a custom single CD build of CentOS 5. With CentOS 4 i used a python script that used the hdrlist module to find all dependencies which borrowed code from a number of sources. I've looked at yumdownloader and how it checks dependencies (using the --resolve option) but if i pass it the list of packages defined in say the Base and the Core yum groups which generally form an absolute minimal install i end up with about 200 packages. If i do a custom install (using beta 1 disks) and deselect everything i end up with over 300 packages. So i'm guessing anaconda calculates dependencies in a slightly different way, can anyone point me to files/code where i should be looking to find out? Thanks very much in advance for help Nick This e-mail is the property of Quadriga Worldwide Ltd, intended for the addressee only and confidential. Any dissemination, copying or distribution of this message or any attachments is strictly prohibited. If you have received this message in error, please notify us immediately by replying to the message and deleting it from your computer. Messages sent to and from Quadriga may be monitored. Quadriga cannot guarantee any message delivery method is secure or error-free. Information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. We do not accept responsibility for any errors or omissions in this message and/or attachment that arise as a result of transmission. You should carry out your own virus checks before opening any attachment. Any views or opinions presented are solely those of the author and do not necessarily represent those of Quadriga.

6 11

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

Few questions on cloud images
by Pino Toscano 06 Jun '23

06 Jun '23

Hello, I have few questions related to the cloud images provides for c8s and c9s, i.e.: - https://cloud.centos.org/centos/8-stream/x86_64/images/ - https://cloud.centos.org/centos/9-stream/x86_64/images/ 1) I see the c9s images are regularly updated, while the c8s images not; is this wanted, or simply a mistake/miss somewhere? If so, will they be kept up-to-date just like the c9s images? 2) are the Vagrant images there officially supported? Let's say you use one, and find a bug; then check on a "classic" installation (baremetal/VM), and the bug isn't there; can users report problems in those cases? 3) would it be possible to have either unversioned or "-latest" symlinks for the latest versions of all the files (i.e. images, checksums, etc)? This way, it will be much easier for users to fetch the latest versions with no need to change URLs frequently. Of course, the assumption is that users of this are always willing to use the latest version. Thanks! -- Pino Toscano

7 14

Proposal: CentOS Public Board Meetings
by Rich Bowen 07 Jan '23

07 Jan '23

In January of 2021, the CentOS Board of Directors opened our monthly meetings to all SIG chairs, in a first step towards more transparent governance. We wanted to see how the larger audience changed the meeting dynamics, if at all, as well as welcoming a broader pool of voices. We are now ready for the second part of this process. Starting in the August meeting, we will be inviting the entire CentOS community to attend these meetings. Due to the nature of the Internet, we won’t be simply publishing the meeting URL, as this often leads to disruptive behavior in meetings, as I am sure many of you have experienced. Rather, in the week before the meeting, we’ll send, to this list, a way to request an invitation to the meeting. In this way, we hope to limit the incidence of such disruptions, while also making the meeting available to anyone who wishes to attend. We will be working on the rules of engagement for these meetings, but they will be, at minimum: * 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/redactions, 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. Because there will seldom be time for Q&A during the meeting itself, we plan to add a post-meeting IRC office hours session for followup questions. This will probably be scheduled for a week after the board meeting, to allow time to publish meeting minutes We welcome your comments about the above proposal, and thank you all for your patience as we implement these changes to our governance process.

8 27

EPEL 8 Modules get the axe on Halloween 2022
by Troy Dawson 14 Oct '22

14 Oct '22

When EPEL-8 was launched, it came with some support for modules with the hope that a module ecosystem could be built from Fedora packages using RHEL modules as an underlying tool. This has never happened and we have ended up with a muddle of modular packages which will 'build' but may not install or even run on an EL-8 system. Attempts to fix this and work within how EPEL is normally built have been tried for several years by different people but have not worked. At this point we are saying that this experiment with modules in EPEL has not worked and we will focus our resources on what does work. Schedule of EPEL 8 Module Retirement: Next Week: - epel-release will be updated. -- epel-modular will set enabled = 0 -- epel-modular full name will have "Deprecated" in it October 31 2022: - The EPEL 8 modules will be archived and removed. -- The mirror manager will be pointed to the archive. - Packagers will no longer be able to build EPEL 8 modules. After October 31st (Actual date to be determined): - epel-release will be updated again. -- epel-modular repo configs will be removed. Questions and Answers: Question: Will I still be able to access the modules after October 31st? Answer: It is not recommended, because the modules will not get any security or bug fixes, but yes. They will be in the Fedora archives, and the mirror managers will point at them. Question: What will you be dressed as on Halloween? Answer (Troy): A Penguin EPEL Steering Committee [1] - https://pagure.io/epel/issue/198

2 3

Re: [CentOS-devel] CentOS Stream 8
by Rich Bowen 11 Oct '22

11 Oct '22

I'm now at AWS on the open source team. Shaun McCance has taken my centos role Shosholoza, Rich On Thu, Sep 29, 2022, 16:49 John Aron <john(a)aronetics.com> wrote: > Thank you Rich. What are you doing now? > > John > > -----Original Message----- > From: Rich Bowen <rbowen(a)rcbowen.com> > Sent: Thursday, September 29, 2022 4:24 PM > To: John Aron <john(a)aronetics.com>; rbowen(a)centosproject.org > Subject: Re: CentOS Stream 8 > > I am no longer working with the CentOS project. I encourage you email > centos-devel(a)centos.org which is where all of the experts hang out. > > --Rich > > On Thu, 2022-09-29 at 15:16 -0400, John Aron wrote: > > Rich, > > > > I am happy that I have your card and info to email you. The new kernel > > on CentOS Stream 8 is significantly unstable. I have a Dell > > R710 with the PERC H700 raid controller. > > > > Here’s my last dmesg from vmcore-dmesg. > > -- > > [root@stinkfist 127.0.0.1-2022-09-29-14:57:49]# less vmcore- dmesg.txt > > 00 00 48 c7 40 08 00 00 00 00 4b 8d 44 [ 1755.255275] RSP: > > 0018:ffffb04146423cc0 EFLAGS: 00010206 [ 1755.255279] RAX: > > ffff8a76ce9e2800 RBX: ffff8a7608c3c400 RCX: > > 0000000000000000 > > [ 1755.255283] RDX: 0000000000000860 RSI: ffffb0414be4daa0 RDI: > > 0000000000000003 > > [ 1755.255285] RBP: 0000000000000000 R08: ffff8a80fffd5000 R09: > > 0000000000000000 > > [ 1755.255288] R10: ffffb0414be4d8c8 R11: fffffffffffffff0 R12: > > ffffb0414be4d000 > > [ 1755.255291] R13: 0000000000000000 R14: 0000000000000001 R15: > > ffff8a76ce9e2800 > > [ 1755.255294] FS: 00007fc871437700(0000) GS:ffff8a80cfa80000(0000) > > knlGS:0000000000000000 > > [ 1755.255298] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ > > 1755.255301] CR2: 000000000000000b CR3: 0000000e72b00006 CR4: > > 00000000000226e0 > > [ 1755.255305] Call Trace: > > [ 1755.255312] ? kmem_cache_alloc_trace+0x142/0x280 > > [ 1755.255321] kvm_set_memslot+0x248/0x480 [kvm] [ 1755.255371] > > kvm_set_memory_region+0x26/0x40 [kvm] [ 1755.255433] > > kvm_vm_ioctl+0x62c/0xcc0 [kvm] [ 1755.255509] ? > > handle_pte_fault+0x480/0x870 [ 1755.255518] ? > > seccomp_run_filters+0x77/0x120 [ 1755.255525] ? > > __handle_mm_fault+0x44f/0x6c0 [ 1755.255533] do_vfs_ioctl+0xa4/0x680 > > [ 1755.255541] ? handle_mm_fault+0xc1/0x1e0 [ 1755.255548] > > ksys_ioctl+0x60/0x90 [ 1755.255555] __x64_sys_ioctl+0x16/0x20 [ > > 1755.255562] do_syscall_64+0x5b/0x1a0 [ 1755.255572] > > entry_SYSCALL_64_after_hwframe+0x65/0xca > > [ 1755.255581] RIP: 0033:0x7fd0860217cb [ 1755.255587] Code: 73 01 c3 > > 48 8b 0d bd 66 38 00 f7 d8 64 89 01 48 > > 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa b8 10 00 00 > > 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 8d 66 38 00 f7 d8 64 > > 89 01 48 > > [ 1755.255593] RSP: 002b:00007fc871436198 EFLAGS: 00000246 ORIG_RAX: > > 0000000000000010 > > [ 1755.255600] RAX: ffffffffffffffda RBX: 00007fc84abc0298 RCX: > > 00007fd0860217cb > > [ 1755.255604] RDX: 00007fc871436200 RSI: 000000004020ae46 RDI: > > 0000000000000011 > > [ 1755.255608] RBP: 00007fc871e00000 R08: 000055e7e9920a60 R09: > > 0000000000000000 > > [ 1755.255613] R10: 0000000000000000 R11: 0000000000000246 R12: > > 000055e7ea69daf0 > > [ 1755.255617] R13: 00007fc871436200 R14: 00000000000e8000 R15: > > 00007fc84abc0298 > > [ 1755.255624] Modules linked in: tun nft_fib_inet nft_fib_ipv4 > > nft_fib_ipv6 nft_fib nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 > > nft_reject nft_ct nf_tables_set nft_chain_nat nf_nat nf_conntrack > > nf_defrag_ipv6 bridge nf_defrag_ipv4 stp llc ip_set nf_tables > > nfnetlink sunrpc intel_powerclamp coretemp kvm_intel kvm irqbypass > > crct10dif_pclmul iTCO_wdt crc32_pclmul iTCO_vendor_support gpio_ich > > ghash_clmulni_intel dcdbas intel_cstate ipmi_ssif joydev intel_uncore > > pcspkr lpc_ich wmi ipmi_si acpi_power_meter i7core_edac xfs > > dm_thin_pool dm_persistent_data dm_bio_prison dm_bufio libcrc32c > > sr_mod cdrom ata_generic sd_mod t10_pi sg mgag200 drm_kms_helper > > syscopyarea sysfillrect sysimgblt fb_sys_fops drm ata_piix libata > > crc32c_intel serio_raw i2c_algo_bit megaraid_sas bnx2 dm_mirror > > dm_region_hash dm_log dm_mod ipmi_devintf ipmi_msghandler fuse [ > > 1755.255765] CR2: 000000000000000b ~ > > -- > > What’s the origin of this crash? I don’t have anyone else to cc’ on > > this matter. I could recompile the kernel cleaning out the unrelated > > functionality present. This could assist? > > > > John > > > > aronetics.com > > We Speak IT® > > > > > >

3 3

[messaging] any plans for RabbitMQ 3.10 and Erlang 25?
by Marcin Juszkiewicz 04 Oct '22

04 Oct '22

In OpenStack Kolla project we are building OpenStack components as container images. And some extra images for infrastructure. One of components we use is RabbitMQ. For each of supported distributions (CentOS Stream 9, Debian 11, Ubuntu 22.04) we want to use the same versions: - rabbitmq-server 3.10.* - erlang 25.* We use upstream provided repositories for each distro/arch as there are no up-to-date versions provided in distribution repositories. Are there plans for updating RabbitMQ and Erlang in Messaging SIG repo to 3.10.* and 25.*? This would allow us to support CentOS Stream 9 on AArch64 (where we now have no working builds and consider downgrading to whatever is in CS9 for now).

3 2

[REPORT] Quarterly Report - CentOS Automotive SIG
by Jeffrey Osier-Mixon 30 Sep '22

30 Sep '22

October 2022 Quarterly report submitted by: Jefro Osier-Mixon, Red Hat - acting chair _____________________________________ Membership update This SIG does not have a formal membership process. The mailing list currently has 99 subscribers representing at least 31 organizations, though not all subscribers use corporate emails and some are participating as individuals. _____________________________________ Releases in the most recent quarter (or most recent release, if none in that quarter) The SIG provides a new distribution: Automotive Stream Distribution (AutoSD), a CentOS Stream derivative designed specifically around the needs of an automotive OS, and transparently the upstream project for Red Hat's eventual in-vehicle OS product. AutoSD has been downloaded and used by many organizations who have commented or asked for help, so we know it is getting some traction though of course we don't have exact metrics on usage. _____________________________________ Health report and general activity narrative The CentOS Automotive SIG celebrated its first year anniversary in August. The SIG has typically had 1-2 public meetings per month, one formal and one informal "office hours", each with 25-40 attendees, with visible participation from 7-10 separate organizations. The office hours portion has been on hiatus since July as summer vacations brought attendance to a crawl, but we intend to start them back up in October. This SIG is intended to be a community effort with contributions and shared benefits from all participants. All formal meetings are recorded and posted on this page: https://wiki.centos.org/SpecialInterestGroup/Automotive/Meetings Several Red Hat employees made the initial contributions to the project as well as the infrastructure required to build and test it. We occupy a gitlab repository in the CentOS namespace building software regularly using CI, with build instructions provided on the documentation page at https:// sigs.centos.org/automotive/ . Sample images are present and downloadable along with customization and build instructions. This is a high-level summary of activity over our first year as outlined on the CentOS blog <https://blog.centos.org/2022/08/centos-automotive-sig-first-year-in-review/> : We worked to define what the Automotive SIG is producing and we landed on three artifacts: - AutoSD, a CentOS-Stream based linux distribution which is the public, in-development version of the Red Hat In-Vehicle Operating System (similar to CentOS Stream for RHEL). - An Automotive SIG RPM repository that allows the community to expand the content of AutoSD or experiment with some of its parts. - Sample images, built using OSBuild, which provide examples of how to assemble production images based on AutoSD, customized for some hardware, including container images, based on CoreOS/ostree technologies. All of this resides in a repository on gitlab, in the CentOS namespace with the infrastructure to enable CI/CD for a basic distribution. We are building a set of nightly images for different use-cases, and have a robust set of documentation at the above link. Not a lot of high-level features have been introduced over the past few months due to vacation schedules, but the distro is doing very well and now supports a SOAFEE implementation along with container support based on podman and systemd. In addition, we are pleased to have had the first contribution from outside Red Hat (thanks Volvo!). _____________________________________ Issues for the board to address, if any None, keep up the excellent work :) Jeffrey "Jefro" Osier-Mixon | jefro(a)redhat.com Red Hat Office of the CTO | Sr. Principal Community Architect, Automotive

1 0

CPE Weekly Update for Week 39 of 2022
by Akashdeep Dhar 30 Sep '22

30 Sep '22

Hi everyone, This is a weekly report from the CPE (Community Platform Engineering) Team. The report could be found at https://communityblog.fedoraproject.org/cpe-weekly-update-week-39-2022/. If you want to receive weekly reports by email in the future, please subscribe to either https://communityblog.fedoraproject.org/ or https://discussion.fedoraproject.org/c/news/commblog/61. We will stop sending them in the future. Regards, CPE Team

1 0

CentOS Hyperscale SIG conference recap
by Davide Cavalca 29 Sep '22

29 Sep '22

Hello, I've posted a recap of the CentOS Hyperscale SIG conference activities from the past few months on the CentOS Blog: https://blog.centos.org/2022/09/centos-hyperscale-sig-conference-recap/ Cheers Davide

1 0

Gitlab Expiration Notice
by Leigh Griffin 29 Sep '22

29 Sep '22

Hey folks, You may have seen a notification on a banner within Gitlab that talks about an upcoming expiration date and a potential loss of features. This is unfortunately an automated message, our renewal as part of their OSS Program is in motion and no service interrupts are expected. Leigh -- Leigh Griffin Senior Manager, Emerging OS Platforms Red Hat Waterford <https://www.redhat.com/> Communications House Cork Road, Waterford City lgriffin(a)redhat.com M: +353877545162 IM: lgriffin @redhatjobs <https://twitter.com/redhatjobs> redhatjobs <https://www.facebook.com/redhatjobs> @redhatjobs <https://instagram.com/redhatjobs> <https://red.ht/sig>

1 0

Keylime configuration changes
by Anderson Sasaki 27 Sep '22

27 Sep '22

Hello, We would like to announce that the new versions of the keylime and keylime-agent-rust packages will include major changes in their configuration files. These changes were introduced in the upstream Keylime 6.5.0 release [1] and rust-keylime 0.1.0 release [2], and implement the specification from the enhancement proposal [3]. The goal of the changes is to make the configuration process easier, with more intuitive and consistent options. The first and more notable change is the split of the previous single file configuration into multiple per-component configuration files. The old “/etc/keylime.conf” file is replaced with six separate configuration files: - /etc/keylime/agent.conf: the Keylime agent configuration file - /etc/keylime/verifier.conf: the Keylime verifier configuration file - /etc/keylime/registrar.conf: the Keylime registrar configuration file - /etc/keylime/tenant.conf: the Keylime tenant configuration file - /etc/keylime/ca.conf: the shared CA configuration file - /etc/keylime/logging.conf: the shared logging configuration file The “ca.conf” and “logging.conf” are shared configuration files that need to be present regardless of the Keylime component installed. In CentOS Stream they are included in the keylime-base subpackage which is required by the other components. The other configuration files are delivered as part of the respective component subpackage. For example, the keylime-verifier subpackage includes the “verifier.conf” file. Another feature introduced is the ability to override the default configuration options through configuration snippets. For each component configuration file, there is a respective /etc/keylime/*.conf.d directory where the user can place files containing snippets to override previously set options. This is the recommended way of overriding configuration options instead of modifying the default configuration file directly. Keep in mind that the configuration processing applies the snippets files in lexicographic order. The last value set to an option is kept. Finally, various options names were modified, especially those related with the TLS configuration. The goal was to make them consistent and intuitive, using the same option name for similar configurations in all components. For example, the “server_key” option sets the private key file used by the server for each of the components that run a server. For more information, please refer to the enhancement proposal [3] or contact us on upstream Slack channel [4] (#keylime on CNCF Slack instance). Thank you, Keylime development team [1] https://github.com/keylime/keylime/releases/tag/v6.5.0 [2] https://github.com/keylime/rust-keylime/releases/tag/v0.1.0 [3] https://github.com/keylime/enhancements/blob/master/72_config_and_simplify_… [4] https://cloud-native.slack.com/messages/C01ARE2QUTZ

1 0

Fwd: Planned Outage - networking work - 2022-09-26 21:00 UTC and 2022-09-27 21:00 UTC
by Fabian Arrotin 26 Sep '22

26 Sep '22

FYI, as that means also some CentOS Services hosted there too (including - but not limited to - SSO) -------- Forwarded Message -------- Subject: Planned Outage - networking work - 2022-09-26 21:00 UTC and 2022-09-27 21:00 UTC Date: Fri, 23 Sep 2022 14:50:01 -0700 From: Kevin Fenzi <kevin(a)scrye.com> Reply-To: Fedora Infrastructure <infrastructure(a)lists.fedoraproject.org> To: announce(a)lists.fedoraproject.org, infrastructure(a)lists.fedoraproject.org, devel-announce(a)lists.fedoraproject.org

1 0

CS9: current firefox not in compose
by Leon Fauster 23 Sep '22

23 Sep '22

I wonder about the current firefox build 91.13.0-1.el9? Its not on the mirrors (comp 20220829) nor in the last prod compose (20220909) / both lists firefox-91.11.0-2.el9 ... Thanks. -- Leon

6 15

CPE Weekly Update - Week 38 2022
by Michal Konecny 23 Sep '22

23 Sep '22

Hi everyone, This is a weekly report from the CPE (Community Platform Engineering) Team. The report could be found at https://communityblog.fedoraproject.org/cpe-weekly-update---week-38-2022/. If you want to receive weekly reports by emails in the future, please subscribe to either https://communityblog.fedoraproject.org/ or https://discussion.fedoraproject.org/c/news/commblog/61. We will stop sending them in the future. Regards, CPE Team

1 0

[Messaging] RabbitMQ for EPEL 9
by Robby Callicotte 21 Sep '22

21 Sep '22

Hello all, I recently stumbled onto this bugzilla issue[1]. It has gone a couple of months without a response from the assignee. I know that the stalled package request procedures can be started now, but I also see that RabbitMQ was built by the Messaging SIG in the past. So... Where should this get routed? Is the messaging SIG still active? I see some info[2] saying that it is, but the lack of response leads me to think that it may not be. Thanks! [1] https://bugzilla.redhat.com/show_bug.cgi?id=2105791 [2] https://wiki.centos.org/SpecialInterestGroup/Messaging -- Robby Callicotte He/Him/His Timezone: America/Chicago IRC: c4t3l | Twitter: @robbycl2v

3 3

Planned service outage : Stream 9 koji build infra
by Fabian Arrotin 20 Sep '22

20 Sep '22

Due to an underlying storage migration (migrating from local NFS host to centralized Netapp filer), we'll have to freeze the dedicated CentOS Stream koji infrastructure (externally known as https://kojihub.stream.centos.org) At the same time we'll migrate the lookaside cache server (aka https://sources.stream.centos.org) from local iscsi target volume to new iscsi lun served also from new Netapp filer. Impacted services: - kojihub and builders for CentOS Stream (https://kojihub.stream.centos.org) - lookaside cache server (https://sources.stream.centos.org) That also means that external services pointing to kojihub (like for cbs.centos.org for SIGs/tag using directly upstream koji as buildroot[s]) will be impacted , so take that into account. Migration is scheduled for """"Friday September 30th, 11:00 am UTC time"""". You can convert to local time with $(date -d '2022-09-30 11:00 UTC') The expected "downtime" is estimated to (maximum) 4h , time needed to : - freeze koji infra and builders - freeze lookaside cache server - (final) data sync between old and new storage volumes - storage volume swap - validate service[s] and have these available again You can also join us in either #centos-devel or #centos-stream irc channels on irc.libera.chat if you encounter any issue. Thanks for your understanding and patience. on behalf of the CentOS Stream Infra team, -- Fabian Arrotin The CentOS Project | https://www.centos.org gpg key: 17F3B7A1 | twitter: @arrfab

1 0

August board meeting recording and office hours
by Shaun McCance 17 Sep '22

17 Sep '22

Hi folks, I've uploaded the recording of last week's board meeting: https://youtu.be/MkB7atd82KU If you'd like to discuss any issues with the board, we'll have an open board office hours this Thursday, September 22, at 14:00 UTC. https://meet.google.com/buz-dvqw-cgk Email me directly if you need dial-in info instead. Thanks, Shaun

1 0

CPE Weekly Update – Week 37 2022
by Lenka Segura 16 Sep '22

16 Sep '22

Hi everyone, You can find this week's CPE (Community Platform Engineering) weekly report here: https://communityblog.fedoraproject.org/cpe-weekly-update-week-37-2022/ If you want to keep receiving weekly reports by email, please subscribe to either https://communityblog.fedoraproject.org/ or https://discussion.fedoraproject.org/c/news/commblog/61. We will stop sending them in the future. Cheers, CPE Team

1 0

libknet1- in more than one repo
by lejeczek 09 Sep '22

09 Sep '22

Hi guys. that most certainly should not be, right? -> $ dnf list libknet1 Last metadata expiration check: 0:00:37 ago on Fri 09 Sep 2022 10:44:07 BST. Installed Packages libknet1.x86_64 1.24-2.el8 @ha Available Packages libknet1.i686 1.24-2.el8 ha libknet1.i686 1.24-2.el8 powertools but in case it should then the problem is: -> $ dnf update ... Error: Problem 1: package libknet1-compress-bzip2-plugin-1.24-3.el8.x86_64 requires libknet1(x86-64) = 1.22-1.el8, but none of the providers can be installed - cannot install both libknet1-1.22-1.el8.x86_64 and libknet1-1.24-2.el8.x86_64 - cannot install the best update candidate for package libknet1-compress-bzip2-plugin-1.24-2.el8.x86_64 - cannot install the best update candidate for package libknet1-1.24-2.el8.x86_64 many thanks, L.

4 5

CPE Weekly Update - Week 36 2022
by Michal Konecny 09 Sep '22

09 Sep '22

Hi everyone, This is a weekly report from the CPE (Community Platform Engineering) Team. The report could be found at https://communityblog.fedoraproject.org/ cpe-weekly-update---week-36-2022/. If you want to receive weekly reports by emails in the future, please subscribe to either https://communityblog.fedoraproject.org/ or https://discussion.fedoraproject.org/c/news/commblog/61. We will stop sending them in the future. Regards, CPE Team

1 0

CentOS Cloud SIG meeting minutes (2022-08-09)
by Joel Capitao 08 Sep '22

08 Sep '22

====================================================== #centos-meeting: CentOS Cloud SIG meeting (2022-09-08) ====================================================== Meeting started by jcapitao at 15:03:36 UTC. The full logs are available athttps://www.centos.org/minutes/2022/September/centos-meeting.2022-09-08-1… . Meeting summary --------------- * roll call (jcapitao, 15:03:45) * OKD/SCOS (CentOS Stream CoreOS 9) update (jcapitao, 15:07:46) * LINK: https://github.com/okd-project/okd-coreos-pipeline contains Tekton definitions for building the OS, the other repos are mostly concerned with building the container images deployed on top (lorbus, 15:18:41) * ACTION: lorbus to send an email on centos-devel ML to announce his nomination as co-chair (jcapitao, 15:39:37) Meeting ended at 15:49:37 UTC. Action Items ------------ * lorbus to send an email on centos-devel ML to announce his nomination as co-chair Action Items, by person ----------------------- * lorbus * lorbus to send an email on centos-devel ML to announce his nomination as co-chair * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * jcapitao (39) * lorbus (31) * davdunc[m (21) * spotz (13) * centguard (6) * davide (3) * davdunc (0) Generated by `MeetBot`_ 0.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot

1 0

IPA + dependencies issue - fail to update
by lejeczek 06 Sep '22

06 Sep '22

Hi guys. This issue is almost a month old - could @devel please look into it. Also a personal comment - this does not look too good as this is not the first time IPA when deployed has this very kind of problems - something there where freeIPA team & Centos team(s) co-exists/operate seems broken - it would be great if you guys(everybody involved) could look into it as well. many thanks, L Last metadata expiration check: 0:00:18 ago on Mon 05 Sep 2022 10:17:13 BST. Error: Problem 1: package ipa-server-trust-ad-4.9.8-7.module_el8.6.0+1103+a004f6a8.x86_64 requires libsmbconf.so.0(SMBCONF_0)(64bit), but none of the providers can be installed - cannot install both samba-client-libs-4.16.4-1.el8.x86_64 and samba-client-libs-4.16.2-1.el8.x86_64 - cannot install both samba-client-libs-4.16.4-1.el8.x86_64 and samba-client-libs-4.13.3-3.el8.x86_64 - cannot install both samba-client-libs-4.16.4-1.el8.x86_64 and samba-client-libs-4.14.4-4.el8.x86_64 - cannot install both samba-client-libs-4.16.4-1.el8.x86_64 and samba-client-libs-4.14.5-0.el8.x86_64 - cannot install both samba-client-libs-4.16.4-1.el8.x86_64 and samba-client-libs-4.14.5-2.el8.x86_64 - cannot install both samba-client-libs-4.16.4-1.el8.x86_64 and samba-client-libs-4.15.3-0.el8.x86_64 - cannot install both samba-client-libs-4.16.4-1.el8.x86_64 and samba-client-libs-4.15.4-0.el8.x86_64 - cannot install both samba-client-libs-4.16.4-1.el8.x86_64 and samba-client-libs-4.15.5-0.el8.x86_64 - cannot install both samba-client-libs-4.16.4-1.el8.x86_64 and samba-client-libs-4.15.5-3.el8.x86_64 - cannot install both samba-client-libs-4.16.4-1.el8.x86_64 and samba-client-libs-4.15.5-4.el8.x86_64 - cannot install both samba-client-libs-4.16.4-1.el8.x86_64 and samba-client-libs-4.15.5-5.el8.x86_64 - cannot install both samba-client-libs-4.16.4-1.el8.x86_64 and samba-client-libs-4.15.5-8.el8.x86_64 - cannot install both samba-client-libs-4.16.4-1.el8.x86_64 and samba-client-libs-4.16.1-0.el8.x86_64 - cannot install the best update candidate for package samba-client-libs-4.16.2-1.el8.x86_64 - cannot install the best update candidate for package ipa-server-trust-ad-4.9.8-7.module_el8.6.0+1103+a004f6a8.x86_64 Problem 2: problem with installed package ipa-server-trust-ad-4.9.8-7.module_el8.6.0+1103+a004f6a8.x86_64 - package ipa-server-trust-ad-4.9.8-7.module_el8.6.0+1103+a004f6a8.x86_64 requires libsmbconf.so.0(SMBCONF_0)(64bit), but none of the providers can be installed - cannot install both samba-client-libs-4.16.4-1.el8.x86_64 and samba-client-libs-4.16.2-1.el8.x86_64 - cannot install both samba-client-libs-4.16.4-1.el8.x86_64 and samba-client-libs-4.13.3-3.el8.x86_64 - cannot install both samba-client-libs-4.16.4-1.el8.x86_64 and samba-client-libs-4.14.4-4.el8.x86_64 - cannot install both samba-client-libs-4.16.4-1.el8.x86_64 and samba-client-libs-4.14.5-0.el8.x86_64 - cannot install both samba-client-libs-4.16.4-1.el8.x86_64 and samba-client-libs-4.14.5-2.el8.x86_64 - cannot install both samba-client-libs-4.16.4-1.el8.x86_64 and samba-client-libs-4.15.3-0.el8.x86_64 - cannot install both samba-client-libs-4.16.4-1.el8.x86_64 and samba-client-libs-4.15.4-0.el8.x86_64 - cannot install both samba-client-libs-4.16.4-1.el8.x86_64 and samba-client-libs-4.15.5-0.el8.x86_64 - cannot install both samba-client-libs-4.16.4-1.el8.x86_64 and samba-client-libs-4.15.5-3.el8.x86_64 - cannot install both samba-client-libs-4.16.4-1.el8.x86_64 and samba-client-libs-4.15.5-4.el8.x86_64 - cannot install both samba-client-libs-4.16.4-1.el8.x86_64 and samba-client-libs-4.15.5-5.el8.x86_64 - cannot install both samba-client-libs-4.16.4-1.el8.x86_64 and samba-client-libs-4.15.5-8.el8.x86_64 - cannot install both samba-client-libs-4.16.4-1.el8.x86_64 and samba-client-libs-4.16.1-0.el8.x86_64 - package libsmbclient-4.16.4-1.el8.x86_64 requires libsamba-debug-samba4.so(SAMBA_4.16.4_SAMBA4)(64bit), but none of the providers can be installed - package libsmbclient-4.16.4-1.el8.x86_64 requires libsmbconf.so.0(SMBCONF_0.0.1)(64bit), but none of the providers can be installed - package libsmbclient-4.16.4-1.el8.x86_64 requires libreplace-samba4.so(SAMBA_4.16.4_SAMBA4)(64bit), but none of the providers can be installed - package libsmbclient-4.16.4-1.el8.x86_64 requires libsamba-security-samba4.so(SAMBA_4.16.4_SAMBA4)(64bit), but none of the providers can be installed - package libsmbclient-4.16.4-1.el8.x86_64 requires libsamba3-util-samba4.so(SAMBA_4.16.4_SAMBA4)(64bit), but none of the providers can be installed - package libsmbclient-4.16.4-1.el8.x86_64 requires libsecrets3-samba4.so(SAMBA_4.16.4_SAMBA4)(64bit), but none of the providers can be installed - package libsmbclient-4.16.4-1.el8.x86_64 requires libcli-smb-common-samba4.so(SAMBA_4.16.4_SAMBA4)(64bit), but none of the providers can be installed - package libsmbclient-4.16.4-1.el8.x86_64 requires libdcerpc-samba-samba4.so(SAMBA_4.16.4_SAMBA4)(64bit), but none of the providers can be installed - package libsmbclient-4.16.4-1.el8.x86_64 requires libmsrpc3-samba4.so(SAMBA_4.16.4_SAMBA4)(64bit), but none of the providers can be installed - package libsmbclient-4.16.4-1.el8.x86_64 requires libgse-samba4.so(SAMBA_4.16.4_SAMBA4)(64bit), but none of the providers can be installed - package libsmbclient-4.16.4-1.el8.x86_64 requires liblibsmb-samba4.so(SAMBA_4.16.4_SAMBA4)(64bit), but none of the providers can be installed - package libsmbclient-4.16.4-1.el8.x86_64 requires liblibcli-lsa3-samba4.so(SAMBA_4.16.4_SAMBA4)(64bit), but none of the providers can be installed - cannot install the best update candidate for package libsmbclient-4.16.2-1.el8.x86_64 (try to add '--allowerasing' to command line to replace conflicting packages or '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)

3 2

Re: [CentOS-devel] [EPEL-devel] Re: [Messaging] RabbitMQ for EPEL 9
by Davide Cavalca 04 Sep '22

04 Sep '22

On Sat, 2022-09-03 at 13:39 -0500, Richard Shaw wrote: > Have you tried building the package yourself yet? When asking for > someone to support an EPEL branch it's not always straightforward. I > tried building the rawhide branch for EPEL 9 and ran into the > following: > > No matching package to install: 'elixir' > No matching package to install: 'erlang >= 23' I breifly looked into this a couple of months ago as someone asked me about it at work. From what I recall, erlang is mostly doable, but elixir is a problem because it pulls in a bunch of other stuff and seems to have a bit of a bootstrapping problem. I'm sure someone familiar with this ecosystem could get it sorted out, but that's not me so I ended up leaving it alone. Cheers Davide

1 0

Opensourcing the CentOS brand creative work, licensing thoughts
by Alain Reguera Delgado 03 Sep '22

03 Sep '22

Dear community, I would like to bring up this topic once again because it is relevant for the well-being of CentOS visual identity, and its future improvements on the long-term. This mail is probably for Red Hat Liaison, considering the legalities involved in relation to CentOS branding matters. Nevertheless, I would like to keep the discussion open to collect the vast majority of opinions possible about it. Considering the CentOS brand is presently a registered trademark of Red Hat, the exact questions are: 1. Related to CentOS brand changes, and design improvements: What does Red Hat allow the CentOS community to do, and not to do? Here, please, consider the legal and not-legal matters. 2. Would it be possible for Red Hat to explicitly set the license under which the CentOS brand (creative/design) work is released, so to grantee its openness inside the CentOS community? If not, please, elaborate why, and share the expected process to follow in order to keep the brand design relevant through time. I deliberately have collected some thoughts[1] about the recent CentOS brand actualization process but am not sure if they are aligned with Red Hat needs and expectations. The goal here would be to make a very clean and simple statement about how much autonomy does the CentOS community have over its own brand. Also, complement the CentOS Trademark Guidelines[2] document with such information, since there isn't mention of it at the moment. [1] https://gitlab.com/areguera/centos-brand [2] https://www.centos.org/legal/trademarks/ Appreciate your comments. Best regards. -- Alain Reguera Delgado <alain.reguera(a)gmail.com>

3 4

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel September 2022