September 2019 - devel - lists.centos.org

ksplice and CentOS
by Karanbir Singh 25 Sep '25

25 Sep '25

hi guys, lots of people on this list are keen on contributing to the CentOS effort - and one place where we could, as a group of people, make a massive difference is being able to deliver a ksplice upgrade model. A couple of people have started in silo's to try and get something together but I feel it might be a good time to try and see if we can do somethng as a group. Do we have people on the list who find the idea of rebootless kernel upgrades interesting ? Is there some desire to try and make that happen within the CentOS Ecosystem ? - KB

24 47

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

CentOS 8 Artwork needed
by Rich Bowen 31 Jan '20

31 Jan '20

To all the artists and designers here, we need your help. With RHEL 8 beta released, we need to start producing artwork for CentOS 8. It's time for the CentOS Artwork SIG, and anyone else that's interested in contributing to this effort, to start working on everything that will be needed for the new release. What we know we need is anaconda artwork, and new desktop backgrounds to replace the current '7' themed stuff. As we dig, we may find more things that need to be updated to the new 8 theme. Additionally, we will need to update some of the assets listed here: https://wiki.centos.org/ArtWork/Identity ... and produce new assets for 8 to be listed here: https://wiki.centos.org/ArtWork/Brand/Logo And, finally, we need someone to step up to lead this effort. While we don't yet know for certain when RHEL 8 will officially release, it's safe to assume that it's soon, and we need your help. -- Rich Bowen - rbowen(a)redhat.com @CentOSProject // @rbowen 859 351 9166

10 30

Reasoning behind RHEL8 packages without corresponding -devel?
by Anthony Alba 12 Dec '19

12 Dec '19

(Of course, we should be asking RH... but nevertheless) EPEL 8 has several issues regarding packages without corresponding -devel. E.g., libXvMC, libbluray. I see that this causes grief for EPEL 8 and collateral damage to RPMFusion. Did RH disclose the reason for this? Was there any discussion on where CentOS will put them, like in Extras perhaps? (I was rolling out some testing VMs in RHEL8 and OL8, and noticed the new but "unsupported" CodeReady repos with -devel packages; yet not all -devels are them.) Cheers Anthony

16 43

CentOS 8 docker images
by Lance Albertson 06 Dec '19

06 Dec '19

When can we expect docker images with CentOS 8? I see there's already an issue [1] open for it. Is there anything we can do to help make it happen? Thanks! [1] https://github.com/CentOS/sig-cloud-instance-images/issues/151 -- Lance Albertson Director Oregon State University | Open Source Lab

10 11

VDO on CentOS Stream
by Andrew Walsh 21 Oct '19

21 Oct '19

Hello, First, let me express how excited I am by the news of the CentOS Stream offering. I am really looking forward to how this works out in the long run. I am in the group that builds VDO, and it is currently delivered as a kmod in CentOS Stream, RHEL, and CentOS. This requires that if the signatures of the symbols that VDO uses change from one kernel to the next, we may need to rebuild the package against the more recent kernel. The current version of kmod-kvdo (6.2.0.293-50.el8) delivered in CentOS Stream is the equivalent of the RHEL-8.0/CentOS-8.0 GA, while the version of the kernel (4.18.0-144.el8) is newer. In the time between the kernel that kmod-kvdo was built against (4.18.0-72.el8) and the current kernel in CentOS Stream, the signatures have changed. As a result, the kernel modules delivered in the kmod-kvdo package cannot be loaded due to symbol mismatches (all device mapper related symbols that change periodically, from what I've experienced). I believe that a simple rebuild of kmod-kvdo-6.2.0.293-50.el8 against kernel-4.18.0-144.el8 should be effective enough to get it working again. How can I help facilitate this rebuild now and/or moving forward? I realize that things are still very much in motion and not fully implemented/decided at this point. Andy Walsh

4 5

RPM-GPG-KEY-CentOS-8
by Leon Fauster 17 Oct '19

17 Oct '19

Hi All! Congratulations to the CentOS Team! Great handcraft! I am impressed! While trying to the verify the downloaded stuff - my mental questions got answered by my self. So, no need to ask the list but this introspection shows a hidden workflow that is not so streamlined, but very crucial. So, I let it go ... As mentioned I wanted to verify the downloaded stuff and wonder where to find a trusted source for the RPM-GPG-KEY-CentOS-8 key file (yes, -8)? Okay its here https://www.centos.org/keys/ and and the trust-level is based on TLS. But I still have some questions marks: - We all use gpg2, right? So the/my first check will go through gnupg, but GPG keyservers are not the first choice because everyone can upload keys but there are some efforts to have the identities at least verified https://keys.openpgp.org/about/news#2019-06-12-launch . Maybe a good idea to have full key informations (verified) for all CENTOS-Keys also there? so I switched to - http://mirror.centos.org/centos/ via HTTP without TLS upgrade. So, also not a source. Is it planned to lift this up to https-only? BTW, no RPM-GPG-KEY-CentOS-8 under http://mirror.centos.org/centos/ Ah, its RPM-GPG-KEY-CentOS-Official (another flow break). I ended up here - WWW via TLS as mentioned above https://www.centos.org/keys/ and https://wiki.centos.org/Download/Verify while the latter suggest wget over http:// (I known the fingerprint is https://wiki...-TLS protected). the wiki is still CentOS7 specific. From the usability point of view there is a forced translation needed from the user (my/users goal has CentOS8 as target). So the only trusted source is https://www.centos.org/keys/ with https://www.centos.org/keys/RPM-GPG-KEY-CentOS-Official for CentOS8. Finally, this would speed up this crucial part of verifying to new distro stuff (ISO etc.): Suggestions: Generalized https://wiki.centos.org/Download/Verify content and a included link to https://www.centos.org/keys/ (actually missing), and the same URI could be added to the CHECKSUM.asc file. Maybe its also a good best practice to have the fingerprints and the key files in two different realms too? BTW, the wiki search result for gpg, pgp or keys does not bring "Download/Verify" as the first entry. Can this be upvoted or tagged? Just thinking loud. Thanks, Leon

4 4

Booting CentOS 8 in a VM - can't find the disk
by Richard W.M. Jones 03 Oct '19

03 Oct '19

I'm trying to boot CentOS 8 in a VM using my usual kickstart and virt-install recipes. Dracut fails in a way that indicates it cannot find the install disk: [ 4.984555] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready [ 4.985509] 8021q: adding VLAN 0 to HW filter on device enp1s0 [ 5.599558] IPv6: ADDRCONF(NETDEV_CHANGE): enp1s0: link becomes ready [ 7.058879] dracut-initqueue[926]: RTNETLINK answers: File exists [ 134.439929] dracut-initqueue[926]: Warning: dracut-initqueue timeout - starting timeout scripts [ 134.969517] dracut-initqueue[926]: Warning: dracut-initqueue timeout - starting timeout scripts [ 135.488283] dracut-initqueue[926]: Warning: dracut-initqueue timeout - starting timeout scripts (repeated endlessly until it drops into the emergency shell) The kernel sees the virtio-blk device, the kmod is loaded, and /dev/vda exists ... So I don't really know. Can anyone see my mistake? Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com libguestfs lets you edit virtual machines. Supports shell scripting, bindings from many languages. http://libguestfs.org

7 9

CentOS QA Team.
by Akim Grudzitsky 01 Oct '19

01 Oct '19

Hi, My name is Akim Grudzitsky. I live in Washington, D.C. area. >From the CentOS-announce I've learned that you are looking for people to get involved with the QA process in CentOS. That is exactly what I am interested in. I have about 3 years of experience as Linux Sys Admin (particularly with CentOS 7 and RHEL 7), I am currently studying for the RHCSA exam, and additionally, I possess 8 years of experience in Software Quality Assurance. I thought It would be great to have an opportunity to contribute to the CentOS project by combining my interest in Linux and previous QA experience. Could you please advise what kind of information I should provide to be considered? Also, it would be great to learn more about the CentOS QA process and how I can start? Thank you in advance. Regards, Akim

2 1

CentOS Streams q&a
by Lamar Owen 01 Oct '19

01 Oct '19

So, now that Earth has caught up to the TARDIS...... Would someone from the CentOS team like to explain CentOS Streams? I saw an article at The NewStack yesterday that gave some info; oddly enough that article is giving a 404 right now, but Google still has it in cache. But Johnny's statement a few days ago, and then this announcement, makes this new CentOS Streams business look interesting. I see a new directory on the mirrors called 8-stream with interesting content......

24 40

Request to join storage-sig group
by Francesco Pantano 30 Sep '19

30 Sep '19

Hi all, I'm Francesco (fmount upstream), I recently joined #centos-devel and, as discussed with some members of the SIG, I wish to start contributing to the storage special interest group (in particular for Ceph related projects) to help with ceph builds. I currently work on OpenStack and I'm involved in the ceph-openstack integration projects (mainly TripleO and ceph-ansible), so it would be great being accepted in the storage-sig group since I can actively contribute to help with ceph packages. Thanks Francesco -- Francesco Pantano GPG KEY: F41BD75C

2 1

CentOS 8 Raid10 Error (mdadm)
by Günther J. Niederwimmer 30 Sep '19

30 Sep '19

Hello, On my system (Supermicro motherboard) with a Intel SCU Controller and a Raid 10 System it is not possible to install with a Raid10. It is not found I found on start the Installation a Error from mdadm that ist all. I have tested this with a CentOS 7 and Opensuse all found my Raid but with CentOS 8 this is broken? Thanks for help and answers, -- mit freundlichen Grüssen / best regards Günther J, Niederwimmer

1 0

'virt-devel' module not present in PowerTools repository
by Ondrej Famera (centos-devel) 30 Sep '19

30 Sep '19

Hi, It looks like the 'PowerTools' repository is missing the 'virt-devel' module. I can see it in RHEL 8 CodeReady repository but not in PowerTools. See below for examples. Is this intentional or rather something that is missing? The only package I'm interested in from this 'virt-devel' repository is 'libssh2-devel' which I can see that was build in this link - https://koji.mbox.centos.org/koji/buildinfo?buildID=3832 for x86_64 that I use. As I can rebuild this missing package by myself consider this to be 'low priority' request/question. Thank you. # yum module list ... Red Hat CodeReady Linux Builder for RHEL 8 x86_64 (RPMs) Name Stream Profiles Summary javapackages-tools 201801 common Tools and macros for Java packaging support virt-devel rhel Virtualization module ========= # yum module list ... CentOS-8 - PowerTools Name Stream Profiles Summary javapackages-tools 201801 common Tools and macros for Java packaging support ========= -- Ondrej Famera

2 2

CentOS 8 - Full SCL availability?
by EXT-Eckert III, George W 28 Sep '19

28 Sep '19

Hello all, When a new major version of CentOS is released, what is the typical timeframe for the Software Collections Library to catch up? Specifically, I'm looking for devtoolset-8 for CentOS 8, and I can't seem to find it. Thanks, George Eckert

7 8

Where to find CentOS 8 HA + RS AddOn Packages
by Heinz Deinhart 27 Sep '19

27 Sep '19

Hi, i am unable to locate the HA and RS addon packages, e.g. pacemaker or dlm. I found the pacemaker packages at build system page (https://koji.mbox.centos.org/koji/build ... ildID=4449), but when trying to download them, i get an 403 Forbidden. Is it possible to access this packages somehow, binary or source rpms? thanks, Heinz

1 0

Missing kernel security updates for CentOS 8
by Morten Stevens 27 Sep '19

27 Sep '19

Hello, After checking the latest CentOS 8, it looks like some kernel security updates are missing. kernel-4.18.0-80.11.2.el8_0 https://access.redhat.com/errata/RHSA-2019:2827 Release date: 2019-09-20 Security Advisory: Important kernel-4.18.0-80.11.1.el8_0 https://access.redhat.com/errata/RHSA-2019:2703 Release date: 2019-09-10 Security Advisory: Important kernel-4.18.0-80.7.2.el8_0 https://access.redhat.com/errata/RHSA-2019:2411 Release date: 2019-08-07 Security Advisory: Important Best regards, Morten

2 1

os/ and kickstart/ seem identical on Centos 8?
by Kaj Niemi 27 Sep '19

27 Sep '19

Hi, Is it on purpose that under AppStream, BaseOS, PowerTools (but not under extras, fasttrack and centosplusplus) there is an os and a kickstart directory for each architecture? On a quick glance the directory layout and contents seem rather identical. Asking as "we" do a local mirror of releases and started wondering about the amount of disk space 8 takes. Kaj

5 6

CentOS 8 and codeready-developer repo
by Troy Dawson 27 Sep '19

27 Sep '19

Hi, Where is the CentOS 8 codeready-developer equivalent repo? I've looked through all the release notes I can find and don't see it anywhere. Nor does anything in "dnf repolist all" show anything. (cr stands for "continuous release" not "codeready") There are several developement things I cannot do on CentOS 8 without that repo. One of which is install the KDE desktop :) Troy Dawson

4 5

CBS and SIGs consuming CentOS 8 / Stream
by Sandro Bonazzola 26 Sep '19

26 Sep '19

Hi, how can SIGs start building their packages for the newly released CentOS 8 and CentOS Stream? CBS seems missing CentOS 8. Thanks, -- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo(a)redhat.com <https://www.redhat.com/>*Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.*

9 10

ansible for CentOS 8
by Orion Poplawski 26 Sep '19

26 Sep '19

Are there any plans for ansible to be distributed in CentOS 8 in any way? Since RHEL8 provides it in the ansible-2.8-for-rhel-8-x86_64-rpms repo, it seems like it would be a candidate for extras or something similar. Work is just getting underway for ansible in EPEL - https://bugzilla.redhat.com/show_bug.cgi?id=1744975 but I thought it might make sense to coordinate efforts. -- Orion Poplawski Manager of NWRA Technical Systems 720-772-5637 NWRA, Boulder/CoRA Office FAX: 303-415-9702 3380 Mitchell Lane orion(a)nwra.com Boulder, CO 80301 https://www.nwra.com/

2 1

[ppc64le] Request to publish python-boto3 and python-s3transfer
by Michael Turek 26 Sep '19

26 Sep '19

Hello all, Recently our containers build job started failing to build gnocchi-* containers [0] due to missing python-boto3 [1]. After a discussion with avij, we found that this package also requires python-s3transfer [2]. Both of these are noarch packages can be found for x86_64 and aarch64 in the base repo [3][4]. Can these be published for ppc64le to restore our container builds? I've included a log showing a successful install using the packages from x86_64 on a ppc64le VM [5]. Thanks, Mike Turek <mjturek> [0] https://centos.logs.rdoproject.org/tripleo-upstream-containers-build-master… [1] https://cbs.centos.org/koji/buildinfo?buildID=15271 [2] https://cbs.centos.org/koji/buildinfo?buildID=15281 [3] http://mirror.centos.org/centos/7/os/x86_64/Packages/ [4] http://mirror.centos.org/altarch/7/os/aarch64/Packages/ [5] https://paste.centos.org/view/45fdce6d

3 5

CentOS 8 srpms and debuginfos
by Dominique Martinet 25 Sep '19

25 Sep '19

Hi, (Welcome to supporting a new distro hell -- thanks for all the work getting CentOS 8 out and everything involved) As usual, I come myself needing some debuginfo packages pretty fast, and found that both debuginfo.centos.org and vault.centos.org (and thus their mirrors either) are yet to have any 8 directory (8.0.1905 or 8-stream) For the srpms, since I've already been told twice I've finally remembered I could get them on git.centos.org e.g. https://git.centos.org/rpms/kernel/commits/c8 For the debuginfos I can obviously just rebuild what sources I got locally and carry on. So this isn't a pressing question at all, but when are the two estimated to become more broadly available ? (Will the 'Stream' version work the same? git.centos.org does not have a c8-stream branch, for example, so it might just be a binary dump of some internal rhel git?) Cheers, -- Dominique

2 2

Meaning of separate kickstart/ and os/ folders in CentOS 8 repos?
by Anthony Alba 25 Sep '19

25 Sep '19

What is the significance of separate kickstart/ and os/ folders in the repos? (If you are using kickstart does that mean you should point to kickstart/ instead of os/ in the ks file?) I could not find a mention of it in the release notes. E.g. under centos/8.0.1905/BaseOS/x86_64/ my nearest mirror has kickstart/ os/ Cheers Anthony Alba

3 2

CentOS 8/7.7
by victor mason 23 Sep '19

23 Sep '19

What's the hold up on both of these? Are we back to the old days? https://linux.slashdot.org/story/09/07/30/130249/CentOS-Project-Administrat… The whole point of setting the update page at https://wiki.centos.org/About/Building_8 was so people didn't constantly ask about release dates. Redirecting queries there is completely fair if someone updates the damn thing. It's now been a few weeks with complete radio silence. It's been 4 months since RHEL8 was released and we are coming over a month for 7.7 with a bunch of security updates piling up. Nobody from the outside who depends on this has any visibility into it and it's frustrating. Is this an IBM thing? What the hell is going on?

32 60

CentOS 7.7 sources
by Jacco Ligthart 19 Sep '19

19 Sep '19

Hi Guys, Thanks for the hard work. I noticed some minor issues with the 7.7 sources: 1. There are many SRPMs double in the os source tree. I guess that from every item from the 7.6 CR tree there is also still the old version present 2. There are some source packages *older* in 7.7 than previously in 7.6. I made this list with repodiff: Downgraded Packages: gnome-boxes: gnome-boxes-3.28.5-4.el7 -> gnome-boxes-3.28.5-2.el7 kmod-kvdo: kmod-kvdo-6.1.2.41-5.el7 -> kmod-kvdo-6.1.1.125-5.el7 libpsm2: libpsm2-11.2.78-1.el7 -> libpsm2-10.3.58-1.el7 nbdkit: nbdkit-1.8.0-1.el7 -> nbdkit-1.2.6-1.el7 nvml: nvml-1.5.1-2.1.el7 -> nvml-1.4-3.el7 opa-ff: opa-ff-10.9.0.0.204-1.el7 -> opa-ff-10.7.0.0.133-1.el7 opa-fm: opa-fm-10.9.0.0.204-1.el7 -> opa-fm-10.7.0.0.141-1.el7 oracleasm: oracleasm-2.0.8-26.el7 -> oracleasm-2.0.8-22.el7 shim: shim-15-2.el7.centos -> shim-15-1.el7.centos shim-signed: shim-signed-15-2.el7.centos -> shim-signed-15-1.el7.centos spice: spice-0.14.0-7.el7 -> spice-0.14.0-6.el7 spice-streaming-agent: spice-streaming-agent-0.2-4.el7 -> spice-streaming-agent-0.2-3.el7 tboot: tboot-1.9.9-1.el7 -> tboot-1.9.6-3.el7 vdo: vdo-6.1.2.41-4.el7 -> vdo-6.1.1.125-3.el7 Jacco

1 0

1:libguestfs-1.40.2-5.el7_7.1.ppc64le required kernel-core on POWER8
by Lance Albertson 18 Sep '19

18 Sep '19

I was working on upgrading some of our POWER8 ppc64le nodes and ran into the following issue with the libguestfs package that's currently in updates: $ yum upgrade libguestfs Loaded plugins: fastestmirror, priorities Loading mirror speeds from cached hostfile Resolving Dependencies --> Running transaction check ---> Package libguestfs.ppc64le 1:1.38.2-12.el7_6.2 will be updated --> Processing Dependency: libguestfs = 1:1.38.2-12.el7_6.2 for package: 1:libguestfs-tools-c-1.38.2-12.el7_6.2.ppc64le --> Processing Dependency: libguestfs = 1:1.38.2-12.el7_6.2 for package: 1:perl-Sys-Guestfs-1.38.2-12.el7_6.2.ppc64le --> Processing Dependency: libguestfs = 1:1.38.2-12.el7_6.2 for package: 1:libguestfs-tools-1.38.2-12.el7_6.2.noarch --> Processing Dependency: libguestfs = 1:1.38.2-12.el7_6.2 for package: 1:python-libguestfs-1.38.2-12.el7_6.2.ppc64le ---> Package libguestfs.ppc64le 1:1.40.2-5.el7_7.1 will be an update --> Processing Dependency: kernel-core for package: 1:libguestfs-1.40.2-5.el7_7.1.ppc64le --> Running transaction check ---> Package libguestfs.ppc64le 1:1.40.2-5.el7_7.1 will be an update --> Processing Dependency: kernel-core for package: 1:libguestfs-1.40.2-5.el7_7.1.ppc64le ---> Package libguestfs-tools.noarch 1:1.38.2-12.el7_6.2 will be updated ---> Package libguestfs-tools.noarch 1:1.40.2-5.el7_7.1 will be an update ---> Package libguestfs-tools-c.ppc64le 1:1.38.2-12.el7_6.2 will be updated ---> Package libguestfs-tools-c.ppc64le 1:1.40.2-5.el7_7.1 will be an update ---> Package perl-Sys-Guestfs.ppc64le 1:1.38.2-12.el7_6.2 will be updated ---> Package perl-Sys-Guestfs.ppc64le 1:1.40.2-5.el7_7.1 will be an update ---> Package python-libguestfs.ppc64le 1:1.38.2-12.el7_6.2 will be updated ---> Package python-libguestfs.ppc64le 1:1.40.2-5.el7_7.1 will be an update --> Finished Dependency Resolution Error: Package: 1:libguestfs-1.40.2-5.el7_7.1.ppc64le (updates) Requires: kernel-core You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest It seems as though this package was likely built using the power9 repos since kernel-core only shows up on the POWER9 nodes. Is anyone else seeing this problem? Thanks! -- Lance Albertson Director Oregon State University | Open Source Lab

2 2

llvm-toolset-7.0 availability
by Ken Roser 18 Sep '19

18 Sep '19

Redhat has had llvm-toolset-7.0 available since March 2019. It adds support for clang and llvm version 7. See https://developers.redhat.com/blog/2019 ... rust-1-31/ <https://developers.redhat.com/blog/2019/03/29/red-hat-enterprise-linux-comp…> Is this going to be available on Centos 7 and if so, when? Don't confuse this with llvm-toolset-7 which supports the older clang version 5 which is already available with Centos 7.

5 7

Please remove
by Paige “Stormblade” Roberts 18 Sep '19

18 Sep '19

This is every day this has gone way overbord with email i have a business to run this is spaming when it is emailing daily remove us from the list now.

3 2

CentOS 7.7.1908 being available in CBS/koji
by Fabian Arrotin 17 Sep '19

17 Sep '19

As you probably saw it, we released CentOS 7.7.1908 for all architectures earlier today : - https://lists.centos.org/pipermail/centos-announce/2019-September/023405.ht… - https://lists.centos.org/pipermail/centos-announce/2019-September/023406.ht… Just after that we regenerated the koji internal repos to use that new release so it's now done : https://cbs.centos.org/koji/tasks?state=all&owner=koji&view=flat&method=cre… That means that all your builds for CentOS 7 will be built against 7.7.1908 content. -- Fabian Arrotin The CentOS Project | https://www.centos.org gpg key: 17F3B7A1 | twitter: @arrfab

3 2

Re: [CentOS-devel] CentOS-devel Digest, Vol 175, Issue 15
by Paige “Stormblade” Roberts 17 Sep '19

17 Sep '19

This dont pertain to shit wtf > > On Sep 17, 2019 at 7:00 AM, <Centos-Devel-Request (mailto:centos-devel-request@centos.org)> wrote: > > > > > Send CentOS-devel mailing list submissions to > centos-devel(a)centos.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.centos.org/mailman/listinfo/centos-devel > or, via email, send a message with subject or body 'help' to > centos-devel-request(a)centos.org > > You can reach the person managing the list at > centos-devel-owner(a)centos.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of CentOS-devel digest..." > > Today's Topics: > > 1. unexpected failure emails from centos container pipeline and > maintenance window (Bamacharan Kundu) > 2. Re: CentOS 8/7.7 (Chandan kumar) > 3. Re: CentOS 8/7.7 (Chandan kumar) > 4. Re: CentOS 8/7.7 (Anssi Johansson) > 5. Re: {Disarmed} Origin RPMs for ppc64le (Peeyush Gupta) > > ---------------------------------------------------------------------- > > Message: 1 > Date: Mon, 16 Sep 2019 18:41:38 +0530 > From: Bamacharan Kundu <bkundu(a)redhat.com> > To: centos-devel(a)centos.org > Subject: [CentOS-devel] unexpected failure emails from centos > container pipeline and maintenance window > Message-ID: <3e66c77b-b3e3-dd5d-ab0e-3d5450d8f41c(a)gmail.com> > Content-Type: text/plain; charset=utf-8; format=flowed > > Hi, > There have been few unexpected failure emails today from centos > community container pipeline, due to pods failing to run the builds in > the cluster. > Please ignore today's failure emails we are working to get things > sorted. > We would also need to update the nodes, so will take some > maintenance window this week (we will keep a separate thread posting for > that). > > We are sorry for the inconvenience caused. > > Note: There is no affect on the availability of registry.centos.org > (build logs will not be available for sometime). > > Thanks and Regards > Bama Charan Kundu > > ------------------------------ > > Message: 2 > Date: Mon, 16 Sep 2019 23:45:14 +0530 > From: Chandan kumar <chkumar246(a)gmail.com> > To: "The CentOS developers mailing list." <centos-devel(a)centos.org> > Subject: Re: [CentOS-devel] CentOS 8/7.7 > Message-ID: > <CAMzQOd=aSh_VRzo6=gUyOiK2V1kTL+nChxhYTLvhZdT50P=OhA(a)mail.gmail.com> > Content-Type: text/plain; charset="UTF-8" > > Hello, > > On Thu, Sep 12, 2019 at 12:42 AM Akemi Yagi <amyagi(a)gmail.com> wrote: > > > > On Wed, Sep 11, 2019 at 12:00 PM Matthew Miller <mattdm(a)mattdm.org> wrote: > > > > > > On Tue, Sep 10, 2019 at 03:48:43PM -0500, Pat Riehecky wrote: > > > > I've been able to do much of my RHEL8 bootstrapping from the RHEL8 > > > > UBI containers. > > > > > Can we update this page https://wiki.centos.org/About/Building_8 > as twitter says https://twitter.com/CentOSProject/status/1173652996305170432 > CentOS 8 is coming on 24th Sept, 2019 ? > > Thanks, > > Chandan Kumar > > ------------------------------ > > Message: 3 > Date: Mon, 16 Sep 2019 23:53:25 +0530 > From: Chandan kumar <chkumar246(a)gmail.com> > To: "The CentOS developers mailing list." <centos-devel(a)centos.org> > Subject: Re: [CentOS-devel] CentOS 8/7.7 > Message-ID: > <CAMzQOdk6ZtKJpiqtET1zJqDZGryPYOdEfag+-Z2jSvAHu4EXyw(a)mail.gmail.com> > Content-Type: text/plain; charset="UTF-8" > > On Mon, Sep 16, 2019 at 11:45 PM Chandan kumar <chkumar246(a)gmail.com> wrote: > > > > Hello, > > > > On Thu, Sep 12, 2019 at 12:42 AM Akemi Yagi <amyagi(a)gmail.com> wrote: > > > > > > On Wed, Sep 11, 2019 at 12:00 PM Matthew Miller <mattdm(a)mattdm.org> wrote: > > > > > > > > On Tue, Sep 10, 2019 at 03:48:43PM -0500, Pat Riehecky wrote: > > > > > I've been able to do much of my RHEL8 bootstrapping from the RHEL8 > > > > > UBI containers. > > > > > > > > Can we update this page https://wiki.centos.org/About/Building_8 > > as twitter says https://twitter.com/CentOSProject/status/1173652996305170432 > > CentOS 8 is coming on 24th Sept, 2019 ? > > > > Sorry taking my statement back, It might be CentOS 7.7 as it mentions > next version of CentOS. > > Thanks, > > Chandan Kumar > > ------------------------------ > > Message: 4 > Date: Mon, 16 Sep 2019 22:59:44 +0300 > From: Anssi Johansson <avij(a)centosproject.org> > To: centos-devel(a)centos.org > Subject: Re: [CentOS-devel] CentOS 8/7.7 > Message-ID: <71660186-a255-1d3f-0dd7-315d72d05f3e(a)centosproject.org> > Content-Type: text/plain; charset=utf-8; format=flowed > > Chandan kumar kirjoitti 16.9.2019 klo 21.15: > > Hello, > > > > On Thu, Sep 12, 2019 at 12:42 AM Akemi Yagi <amyagi(a)gmail.com> wrote: > >> > >> On Wed, Sep 11, 2019 at 12:00 PM Matthew Miller <mattdm(a)mattdm.org> wrote: > >>> > >>> On Tue, Sep 10, 2019 at 03:48:43PM -0500, Pat Riehecky wrote: > >>>> I've been able to do much of my RHEL8 bootstrapping from the RHEL8 > >>>> UBI containers. > >>> > > > > Can we update this page https://wiki.centos.org/About/Building_8 > > as twitter says https://twitter.com/CentOSProject/status/1173652996305170432 > > CentOS 8 is coming on 24th Sept, 2019 ? > > Yes, I just updated the page. The tweet indeed refers to the next major > version, not 7.7.1908 which is just around the corner to be released. > > Thank you for your patience! I know it's been a long wait, but it's > worth it. > > ------------------------------ > > Message: 5 > Date: Tue, 17 Sep 2019 10:43:45 +0000 > From: "Peeyush Gupta" <peeygupt(a)in.ibm.com> > To: centos-devel(a)centos.org > Cc: centos-devel(a)centos.org > Subject: Re: [CentOS-devel] {Disarmed} Origin RPMs for ppc64le > Message-ID: > <OF3A11BFE6.F238D82A-ON00258478.003A8174-00258478.003AF031(a)notes.na.collabserv.com> > > Content-Type: text/plain; charset="us-ascii" > > An HTML attachment was scrubbed... > URL: <http://lists.centos.org/pipermail/centos-devel/attachments/20190917/3a99c26…> > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > CentOS-devel mailing list > CentOS-devel(a)centos.org > https://lists.centos.org/mailman/listinfo/centos-devel > > ------------------------------ > > End of CentOS-devel Digest, Vol 175, Issue 15 > ********************************************* >

1 0

Origin RPMs for ppc64le
by Peeyush Gupta 17 Sep '19

17 Sep '19

3 3

unexpected failure emails from centos container pipeline and maintenance window
by Bamacharan Kundu 16 Sep '19

16 Sep '19

Hi, There have been few unexpected failure emails today from centos community container pipeline, due to pods failing to run the builds in the cluster. Please ignore today's failure emails we are working to get things sorted. We would also need to update the nodes, so will take some maintenance window this week (we will keep a separate thread posting for that). We are sorry for the inconvenience caused. Note: There is no affect on the availability of registry.centos.org (build logs will not be available for sometime). Thanks and Regards Bama Charan Kundu

1 0

centos-7.7 or centos-cr brakages building python3 packages with EPEL enabled
by Nico Kadel-Garcia 16 Sep '19

16 Sep '19

I've started testing with the "cr" repositorory enabled, and we are going to have a *lot* of problems building EPEL packages unless we get well ahead of the game. RHEl has elected to publish their python3 modules as "python3-module", and to obsolete "python36-module" names. All well and good, this will help provide upgrade paths from EPEL. The problem is that they've also updated "pythone_pkgversion" to be "3", instead of "36". And every package that uses "python%{python3_pkgversion} is going to break if the package is published as an EPEL package, such asl "python36-pylint", and is not available as a "python3-pylint" package. It's potentially soluble by every single EPEL package being updated to "Provide:" python3-module, as well as python36-module. But then that gets into the "we never, never, never overlap with RHEL published packages". So the technological fix that allows Red Hat to Obsolete: the EPEL versions, as they just did with "python3" obsoleting ade past and over packages as they just die, with "python3-devel" and "python3-devel", is going to have to be done with almost every python EPEL package and those packages ingested into the RHEL upstream repository. I'm not sure where to best resolve this. I ran into it while trying to update a "mock" SRPM with the "cr" repository enabled, and savagery ensued with dependencies on "python3-pylint", for which there is not EPEL or CentOS package.

2 2

Using mirrorlist in centos-release-* packages
by Anssi Johansson 12 Sep '19

12 Sep '19

Hi, as mentioned in https://lists.centos.org/pipermail/centos-devel/2018-September/016949.html mirrorlist.centos.org has been updated to produce mirror lists for SIG content as well. Some centos-release-* packages have already been modified to use mirrorlist.centos.org instead of mirror.centos.org, but many still point to mirror.centos.org. Most of mirror.centos.org hosts are also used for seeding the 600+ external mirrors we have. By directing some of their download traffic to external mirrors we can offer faster sync speeds for those external mirrors, and for people downloading individual rpms from mirror.centos.org. Second, most of those external mirrors offer faster download speeds to end users than what could be achieved by downloading from mirror.centos.org, so the users will benefit from this change as well. The better geographical coverage does not hurt either. mirror.centos.org nodes are donated servers, and it would be kind to the sponsors to use their bandwidth sparingly. The .repo files should be modified so that the current baseurl line gets commented out and a mirrorlist entry gets added, like this: mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch… #baseurl=http://mirror.centos.org/$contentdir/$releasever/storage/$basearch/gluster-4.1/ Note that mirrorlist.c.o can automatically choose between main and altarch content based on the arch parameter. The repo names are constructed from the repository path by stripping away the architecture and changing any slashes to dashes: sclo/x86_64/rh -> sclo-rh, sclo/x86_64/sclo -> sclo-sclo, paas/x86_64/openshift-origin311 -> paas-openshift-origin311, storage/x86_64/gluster-5 -> storage-gluster-5 etc. You can use 'curl' to check what mirrorlist outputs for your repository. New repos are added to mirrorlist.centos.org automatically once the repository hits mirror.centos.org. That script is currently run every three hours. I guess it could be run more frequently (it's fairly lightweight), but you should give the external mirrors a few hours to sync before announcing your release anyway. You can either submit an update to your current centos-release-* file now, or wait until you need to create a new centos-release-* package for other reasons such as releasing softwarepackage-(version+1) which uses different paths. My recommendation would be to submit an update to your current centos-release-* package, so that you would not need to worry about this when you eventually need to publish a new one for other reasons. We released an updated centos-release package for CentOS AltArch before 7.6.1810 was released for this exact reason, ie. we didn't need to worry about this change at 7.6.1810 release time. Other people (such as bstinson, arrfab and hughesjr) can probably help with creating and publishing an updated centos-release-* package, but the usual tagging procedure to extras will apply. The SIG Guide https://wiki.centos.org/SIGGuide should have all the needed details for this (if not, complain to bstinson). It is highly recommended to actually test your new centos-release-* package from buildlogs before you ask that package to be signed and pushed to extras. The holiday season is fast approaching so (I) don't expect much activity regarding these changes in the following days. I'm hoping that the SIGs would take a look at this in early 2019, though. Thanks to those SIGs who have already made these changes to their centos-release-* packages! If you have questions, feel free to ask either here or on #centos-devel. Thanks for your time!

1 2

SIG Content to remove for the 7.7.1908 release
by Johnny Hughes 11 Sep '19

11 Sep '19

For all the c7 SIGs, if you have content that you want removed (to make inactive) when we create the new 7.7.1908 tree, please let me know here what needs to be removed. If all files in a specific directory can be removed, you can just list the directory. You will also obviously need to make any changes to your centos-release-* files to remove those file locations from your repos. After we release 7.7.1908 .. we will copy over the SIG directories prune the SIG content. The http://mirror.centos.org/centos/7/<repo>/ paths will then be shifted to the new 7.7.1908 tree. I expect that some time early next week we will release the CR content .. with the full release coming 7 to 14 days after that .. so full release likely some time between 29 August to 6 September 2019. If you don't tell us to remove content, we will move everything over as is. Thanks, Johnny Hughes

5 4

Origin RPMs for ppc64le
by Peeyush Gupta 09 Sep '19

09 Sep '19

3 3

Issue with python-urllib3 update in CentOS 7 CR.
by Lamar Owen 04 Sep '19

04 Sep '19

So, updated to CR yesterday evening, and for the most part things are ok. However: [lowen@dhcp-pool101 ~]$ sudo yum --enablerepo=cr update ..... Resolving Dependencies --> Running transaction check ---> Package python-urllib3.noarch 0:1.10.2-5.el7 will be updated ---> Package python-urllib3.noarch 0:1.10.2-7.el7 will be an update --> Finished Dependency Resolution Dependencies Resolved ================================================================================ Package Arch Version Repository Size ================================================================================ Updating: python-urllib3 noarch 1.10.2-7.el7 cr 103 k Transaction Summary ================================================================================ Upgrade 1 Package Total download size: 103 k Is this ok [y/d/N]: y Downloading packages: No Presto metadata available for cr python-urllib3-1.10.2-7.el7.noarch.rpm | 103 kB 00:00 Running transaction check Running transaction test Transaction test succeeded Running transaction Updating : python-urllib3-1.10.2-7.el7.noarch 1/2 Error unpacking rpm package python-urllib3-1.10.2-7.el7.noarch error: unpacking of archive failed on file /usr/lib/python2.7/site-packages/urllib3/packages/ssl_match_hostname: cpio: rename Verifying : python-urllib3-1.10.2-7.el7.noarch 1/2 python-urllib3-1.10.2-5.el7.noarch was supposed to be removed but is not! Verifying : python-urllib3-1.10.2-5.el7.noarch 2/2 Failed: python-urllib3.noarch 0:1.10.2-5.el7 python-urllib3.noarch 0:1.10.2-7.el7 Complete! [lowen@dhcp-pool101 ~]$

3 3

CentOS 7.6.1810 CR Available in CBS
by Thomas Oulevey 02 Sep '19

02 Sep '19

Hi Folks, The CR (https://wiki.centos.org/AdditionalResources/Repositories/CR) repository was released last week. We have regenerated all the CentOS 7 buildroots in CBS so you can build against the content that will make it into the next point-release of CentOS Linux. Machines in ci.centos.org are available with CR as well so you may continue your testing. We are currently in Point-release Freeze which means anything tagged for release will *NOT* get pushed out to mirror.centos.org and we will be holding new push requests until we have a GA point-release. If there are any questions please find us here or in #centos-devel on Freenode. Happy building and testing ! -- Thomas 'alphacc' Oulevey and the CBS team.

2 1

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel September 2019