devel August 2019

devel@lists.centos.org

21 participants
13 discussions

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

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

New Linux team member at CERN
by Ben Morrice 27 Aug '19

27 Aug '19

Hello all, My name is Ben Morrice and I wanted to introduce myself to this list. I have recently started work at CERN, working in the Linux team. I will be maintaining our internal CERN CentOS distribution and I look forward to contributing anything that I can back to the CentOS project. I am known as 'figless' on freenode. Hope to work with you soon! Cheers, Ben Morrice

5 5

CentOS - AltArch ; ARM
by Douglas E. Hopley Jr. 26 Aug '19

26 Aug '19

CentOS - AltArch ; ARM Greetings. After some more reading I understand I can offer to help via a message to this list. How can I provide any help? Is there something specific needed or best for a new participant to work on or for? What is best to do to get started? Thanks in advance for your time.

1 0

CentOS oVirt Guest Image test report
by Sandro Bonazzola 23 Aug '19

23 Aug '19

Hi, tested https://buildlogs.centos.org/centos/images/ovirt/CentOS-7-x86_64-oVirt-2019… and seems overall functional. The ovirt-guest-agent service is disabled. Pushed https://github.com/CentOS/sig-cloud-instance-build/pull/157 for fixing it, please review / merge. I think we can limit the release to the qcow2c image only. 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.*

1 0

Maintenance window for UI of registry.centos.org
by Bamacharan Kundu 19 Aug '19

19 Aug '19

Hi, We are facing some issues with UI for registry.centos.org. We are working on it to get it back properly. Image pull from registry.centos.org are working normal. Service: registry.centos.org Impact: GUI for registry.centos.org is unavailable. We will update on resolution, sorry for the inconvenience caused. Regards Bamacharan Kundu

1 2

Delete own forks on git.centos.org
by Phil Wyett 18 Aug '19

18 Aug '19

Hi all, Are there plans to enable the deleting of own repo forks in the near future on git.centos.org? Regards Phil -- *** Playing the game for the games sake. *** IRC: kathenas Twitter: kathenasorg Website: https://kathenas.org

1 0

rh-ruby26
by Marko Bevc 13 Aug '19

13 Aug '19

Hi. Not sure this is the right mailing list, but do we have a status when those packages would be available for CentOS 7? Or can someone point me in the right direction? Thanks. Cheers, Marko

2 2

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel August 2019