devel February 2019

devel@lists.centos.org

19 participants
21 discussions

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

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

Weekly SIG meetings
by Rich Bowen 06 Mar '19

06 Mar '19

I've been noticing, over the last 3 or 4 months, that many of our SIGs are no longer in the habit of holding their (bi-)weekly meetings on IRC. I don't know why this is happening - perhaps they're having their discussions elsewhere, or perhaps there's nothing to discuss. However, I want to remind you that these meetings are a window into your work for the larger community. Your meeting minutes are public, and useful for people who are not directly involved in the SIG but who want to know what's happening. Even a 5-minute status checkin is valuable to our users. I would point you to the excellent example of this from the CBS/Infra weekly meeting, the transcript of which you can see here: https://www.centos.org/minutes/2019/February/centos-devel.2019-02-18-14.02.… Note that there's only one meeting participant, but the meeting is held to offer the opportunity for discussion should anyone need it. Please do get back in the habit of meeting regularly. -- Rich Bowen - rbowen(a)redhat.com @CentOSProject // @rbowen 859 351 9166

3 4

Lightning talks at Red Hat Summit
by Rich Bowen 28 Feb '19

28 Feb '19

If you expect to be at Red Hat Summit [1] and if you have some community project that you'd like to tell the world about, please consider submitting a Lightning Talk for the Community Central section of the event: https://docs.google.com/forms/d/e/1FAIpQLSc5phwBJclz7ubP9B3Ax_W7Fr9S0Olcgzk… Lightning talks will be 15 minutes, plus 5 for Q&A. If what you have to talk about is shorter than that, that's fine too. Thanks! --Rich [1] Red Hat Summit - https://www.redhat.com/en/summit/2019 - May 7-9, Boston, MA, USA. -- Rich Bowen - rbowen(a)redhat.com @CentOSProject // @rbowen 859 351 9166

2 2

C7 shim 15-2 update - No announce
by Phil Wyett 28 Feb '19

28 Feb '19

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all, There has been a shim update (to 15-2) but no related announcement. Is one on the way? Regards Phil - -- *** If this is a mailing list, I am subscribed, no need to CC me.*** Playing the game for the games sake. IRC: kathenas Web: https://kathenas.org Github: https://github.com/kathenas GitLab: https://gitlab.com/kathenas Twitter: kathenasorg GPG: A0C3 4C6A AC2B B8F4 F1E5 EDF4 333F 60DC B0B9 BB77 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQIcBAEBAgAGBQJcd9SSAAoJEDM/YNywubt3j1gP/jynow8VlCNISND5qZgXcsHJ /FYAOXLEvt/zoTeHENVFxcRHZ1LxZ09IgrbywZIOqSIwwmmf0/zgrMM2ovPa+1Zb +agGKbW8b8ejHGMc646IrxqilpdsBHWppulZqSZSHBSbkW1H0jmq6nVSJZKEaaZm Z/L/EsfI5BmhhgqqgIr/Znibr/CpS1B1pf3lqVHgdt2A2dsB2yBeZqVkL9+h3rXi I09LMa3irr4eS1gn0xetiZpoCdcD3Er382hfbLhXO+Eq14XbdR+UueJuWS3+UDxR A/2EIPzNn8D9/sXlwRpAxeoAN4jnYEt4Ft2sG5hpR68xj7ge2lYNbEBA5Wc3eSgA bISZqI2JL2/YvFzI79GFBkClvXG8zzLAseqC91MuzO9cgyScT2FusGuDBdv1lOFj 0CmDqsZLkxXu1vRkeWZs8ynxZD+02R+WWNX+MgB7viEp+7FV3RSh2S1VB5AwREWw 8iMAb9ohe6mIpoPNRCaVjCe6xf0wubY+r6MRU4ARv+weU4zzW2tovIAcY+OgeFkM /ZQyemGOaIIDTMzgtSmRBwYni5CKmZRL+OTdaHo6toAo/bvhbjIOBFKtDKLYHF3V fL3GZSpRlfi7a/UOYbzrncFaLidIWXg4aL3OMsMazwvYOgjeIGdFG3Q6+dn6Ajvh mnjm6dfac9KyT2J2rWq9 =4jKQ -----END PGP SIGNATURE-----

2 3

GlusterFS 6.0RC Test Days (27th, 28th Feb)
by Rich Bowen 28 Feb '19

28 Feb '19

Gluster users/developers, We are calling out our users, and developers to contribute in validating ‘glusterfs-6.0rc’ build in their usecase. Specially for the cases of upgrade, stability, and performance. Full details and participation information may be found on the Gluster-devel mailing list, here: https://lists.gluster.org/pipermail/gluster-devel/2019-February/055876.html -- Rich Bowen - rbowen(a)redhat.com @CentOSProject // @rbowen 859 351 9166

2 1

Need a knob to disable all spectre/meltdown fixes
by Priya, Nupur 26 Feb '19

26 Feb '19

Hi there, I would like to implement a command , to be able to disable all variants(or at least the ones causing performance impact). As per the RH article: https://access.redhat.com/articles/3311301, we would be able to only disable spectre variant 2 and 3(pti). I need an option to disable variant 1, 3a and 4 as well. Some of the recent articles suggest that options like no_spectre_v1, no_spectre_v2 and spec_store_bypass_disable parameters are available in latest versions of kernel(4.15 and above). https://www.zdnet.com/article/linux-kernel-gets-another-option-to-disable-s… https://www.kernel.org/doc/html/latest/admin-guide/kernel-parameters.html?h… Can this be made available in our Centos 7 kernels? Or is there any plan for RH to implement the same in any future release? Regards, Nupur

2 1

Centpkg and the converged git project
by Brian Stinson 22 Feb '19

22 Feb '19

Hi Folks, I've done a bit of work on centpkg, now that we have a testbed at git.stg.centos.org. The goal here is to allow centpkg and fedpkg (Fedora's site) to both understand the different formats. The test version of centpkg described below is the first step in that direction. Basically you can try this out by pulling a container image: `podman pull quay.io/bstinsonmhk/centpkg:develop` Why a container image? - The patches to make this happen involve invasive changes to rpkg, that are still in flight (basically, https://pagure.io/rpkg/pull-request/393) - I wanted to bake in the sources and configs to develop this a little faster as we find problems. What's included, and where to file bugs? - centpkg from: https://bitbucket.org/bstinsonmhk/centpkg/branch/develop - rpkg from: https://pagure.io/fork/bstinson/rpkg/tree/centpkg-inbound - fedpkg from: https://pagure.io/fedpkg/tree/master Here's how I run it for testing CentOS packages (substitute your centos user certificate and a path to RPMs to fit your workstation): `podman run --rm -it -v /home/bstinson/.centos.cert:/home/centpkg-user/.centos.cert:Z -v /home/bstinson/rpms:/home/centpkg-user/rpms:Z quay.io/bstinsonmhk/centpkg:develop` If you're a SIG member, you can push to a sig branch. For example, if I was a mamber of the atomic SIG I could do: # Clone the repo $ centpkg clone -b c7 a2ps # Download the sources from C7 $ centpkg sources # Change to a SIG branch $ git checkout -b c7-sig-atomic-cockpit-preview # Manual push is needed here until we work out a way to register the # new branches $ git push -u origin c7-sig-atomic-cockpit-preview # Upload sources to the SIG branch in the lookaside $ centpkg upload SOURCES/a2ps-4.14.tar.gz SOURCES/i18n-fonts-0.1.tar.gz # CBS does not yet build from SCM, so still need srpms $ centpkg scratch-build --srpm # Try out a fedora branch $ centpkg switch-branch f28 $ centpkg clean # From a Fedora branch this should use your Fedora creds $ centpkg scratch-build # this should work with Fedora's ko What I need help with: - Review the open PRs to rpkg as they come in - Help me find more places where we need to use the new 'Layout' objects (that is where rpkg has paths hard-coded) - Test Fedora workflows, and other commands with centpkg - Help add new commands - to request SIG branches - to translate from one layout to another (ex. bringing a Fedora branch into a CentOS SIG branch) Happy building! --Brian

2 1

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel February 2019