devel January 2019

devel@lists.centos.org

28 participants
23 discussions

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

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

[CentOS-docs] Authorization to use CentOS logo in GNOME Boxes
by Ladar Levison 21 Feb '19

21 Feb '19

> Who will prepare the logo? I do not know, we could use a volunteer. > I had to track down SVG logo files for the Robox website. Not sure, is this what you need? https://roboxes.org/res/centos.svg

5 18

Availability of updated official CentOS 7 Amazon Machine Images
by Ian Gable 31 Jan '19

31 Jan '19

Hi All, Could someone please point me in the right direction for whom to talk to about getting the official CentOS 7 Amazon Machine Image updated? I’m talking about the AWS market place images here: https://aws.amazon.com/marketplace/pp/B00O7WM7QW which are also linked from the CentOS home page. They haven’t been updated since June 13, 2018 . It would be especially nice to have them updated given the availability of 1810. Thanks in Advance, Ian Gable

5 12

Atomic and Configmanagement
by Neale Ferguson 30 Jan '19

30 Jan '19

Hi, When will these two components’ source reach the vault? Neale

1 0

CentOS will support openssl 1.1.1 in future version of CentOS
by Maheshwari, Shagun 30 Jan '19

30 Jan '19

Hi, There is a plan from CentOS to support OpenSSL 1.1.1 in future versions of CentOS 7 because openssl community has OpenSSL 1.1.1 which was released in Sep 2018 and it has fixed for many vulnerabilities. And CentOS has 1.0.2k version. Can you please update on this? Regards, Shagun

5 4

Observing deadlock between SIPhandler and SDL Router in CUCM.
by Priya, Nupur 25 Jan '19

25 Jan '19

Observing deadlock between SIPhandler and SDL Router in CUCM. Looks like this is fixed in glibc 2.17.162 version, but we see the issue still https://bugzilla.redhat.com/show_bug.cgi?id=906468 Need help to identify the root cause and add a preventive fix. Here is the error messages: *********************************************************************************************************************************************************************************************************************************** gdb) thread 40 [Switching to thread 40 (Thread 0xaca90b40 (LWP 5935))] #3 0xf67fdbd1 in malloc () from /usr/lib/libc.so.6 (gdb) bt #0 0xf775a430 in __kernel_vsyscall () #1 0xf688d462 in __lll_lock_wait_private () from /usr/lib/libc.so.6 #2 0xf68006c0 in _L_lock_14246 () from /usr/lib/libc.so.6 #3 0xf67fdbd1 in malloc () from /usr/lib/libc.so.6 #4 0xf6a68907 in operator new(unsigned int) () from /usr/local/cm/lib/libstlport.so.5.2 #5 0x0936c3f9 in operator() (this=0xaca8dd70) at /view/BLD-cm_12_5_1-cct-ccm-d/vob/ccm/Common/Include/Utilities/Member.hpp:52 #6 c_str (this=0xaca8dd70) at /view/BLD-cm_12_5_1-cct-ccm-d/vob/ccm/Common/Include/CallManager/TDCLCpShares.hpp:862 #7 assign (len=12, digits=0xaca8de34 "+19570676705", this=0xaca8dd70) at /view/BLD-cm_12_5_1-cct-ccm-d/vob/ccm/Common/Include/CallManager/TDCLCpShares.hpp:1252 #8 CdPNumStringVar::CdPNumStringVar (this=0xaca8dd70, digits=0xaca8de34 "+19570676705", len=12) at /view/BLD-cm_12_5_1-cct-ccm-d/vob/ccm/Common/Include/CallManager/TDCLCpShares.hpp:846 #9 0x092efdf8 in SIPCdpc::processSIPSetupMsg (this=this@entry=0x7de0c8e0, sipContainerWrapper=sipContainerWrapper@entry=0x8e966e78) at ProcessSIPCdpc.cpp:2142 #10 0x0934086d in SIPCdpc::processSIPSetupInd (this=this@entry=0x7de0c8e0) at ProcessSIPCdpc.cpp:3300 #11 0x0934ec08 in SIPCdpc::inCall_waitRSVPRes_PolicyAndCACRegisterRes (this=0x7de0c8e0, s= Name : "PolicyAndCACRegisterRes", Sender : spy:PID (8,100,152,1) "ReservationMgr", Receiver : spy:PID (8,100,180,995813) "SIPCdpc", Priority : kNormalPriority) at ProcessSIPCdpc.cpp:26471 #12 0x09e69c7b in SdlProcessBase::inputSignal (this=0x7de0c8e0, rSignal=0x807d8d80, traceType=SdlSystemLog::SignalRouterThread, highPriority=0, normalPriority=0, lowPriority=0, veryLowPriority=0, lazyPriority=0, dbUpdatePriority=0) at SdlProcessBase.cpp:417 #13 0x09e6ce8a in SdlRouter::callProcess (this=this@entry=0xcfff0e0, _sdlSignal=_sdlSignal@entry=0x807d8d80, _deleteSignal=@0xaca8fdb3: true, _traceType=_traceType@entry=SdlSystemLog::SignalRouterThread, _hp=0, _np=0, _lp=0, _vlp=0, _lzp=0, _dbp=0) at SdlRouter.cpp:257 #14 0x09e6d60c in SdlRouter::scheduler (this=this@entry=0xcfff0e0) at SdlRouter.cpp:164 #15 0x09e6dcad in SdlRouter::schedulerInit (sdlRouter=0xcfff0e0) at SdlRouter.cpp:107 #16 0xf69beb3c in start_thread () from /usr/lib/libpthread.so.0 #17 0xf687f44e in clone () from /usr/lib/libc.so.6 (gdb) thread 1 [Switching to thread 1 (Thread 0xa9136b40 (LWP 5964))] #0 0xf67fb876 in _int_malloc () from /usr/lib/libc.so.6 (gdb) bt #0 0xf67fb876 in _int_malloc () from /usr/lib/libc.so.6 #1 0xf67fdbda in malloc () from /usr/lib/libc.so.6 #2 0xf6a68907 in operator new(unsigned int) () from /usr/local/cm/lib/libstlport.so.5.2 #3 0x09cd4ce2 in sip_get_sipspi_message () at sip_common_spi.cpp:20059 #4 0x09cf94d1 in sipTransportPostSendMessage (msg=0x8a20a150, gcb=gcb@entry=0x8015d208, tcb_context=..., connId=24, destAddr=0x8015d228, destPort=5061, transport=SIP_TRANSPORT_TLS_OVER_TCP, emit_debugs=1 '\001', ip_sig_tos=0 '\000') at sip_common_transport.cpp:3032 #5 0x09cf9946 in sipTransportLogicSendMsg (gcb=gcb@entry=0x8015d208, sw_transport=sw_transport@entry=0 '\000') at sip_common_transport.cpp:2367 #6 0x09cfab6f in sipSPITransportSendMessage (msg=msg@entry=0x8a20a150, context=context@entry=0x8015d208, addr=addr@entry=0xa91355dc, port=port@entry=5061, sentBy_port=sentBy_port@entry=0, is_request=is_request@entry=1 '\001', transport=transport@entry=SIP_TRANSPORT_TLS_OVER_TCP, sw_transport=0 '\000', func=func@entry=0x9cb0080 <sentAck(_sipGenericCB*)>, tcb_context=...) at sip_common_transport.cpp:3323 #7 0x09cbe638 in sipSPISendAck (ccb=0x8015d208, flags=flags@entry=0, func=0x9cb0080 <sentAck(_sipGenericCB*)>) at sip_common_send_msg.cpp:2992 #8 0x09ccc910 in sipSPISendAckForMidCallInvite (ccb=0x8015d208, flag=flag@entry=0) at sip_common_spi.cpp:8745 #9 0x09ccdb37 in sact_sent_mid_invite_new_message_response (ccb=0x8015d208, response=0x89305d58) at sip_common_spi.cpp:9278 #10 0x09cda815 in ccsip_spi_process_event (freeEvent=0xa91359df "\001", event=0x7ca43348) at sip_common_spi.cpp:19333 #11 ccsip_process_sipspi_queue_event (event=event@entry=0x7ca43348) at sip_common_spi.cpp:19997 #12 0x093ef758 in SIPHandler::wait_SIPNormalizeRes (this=0xac1c05e8, s= Name : "SIPNormalizeRes", Sender : spy:PID (8,100,184,1) "SIPNormalization", Receiver : spy:PID (8,100,183,1) "SIPHandler", Priority : kNormalPriority) at ProcessSIPHandler.cpp:1683 #13 0x09e69c7b in SdlProcessBase::inputSignal (this=this@entry=0xac1c05e8, rSignal=rSignal@entry=0x7d2f8a78, traceType=SdlSystemLog::SignalThreadedWithPriorities, highPriority=0, normalPriority=0, lowPriority=0, veryLowPriority=0, lazyPriority=0, dbUpdatePriority=0) at SdlProcessBase.cpp:417 #14 0x09e8d2fd in SdlThreadedProcess::threadQueueReader (this=this@entry=0xac1c05e8) at SdlThreadedProcess.cpp:110 #15 0x09e8d56d in SdlThreadedProcess::threadQueueReaderInit (sdlThreadedProcess=0xac1c05e8) at SdlThreadedProcess.cpp:75 #16 0xf69beb3c in start_thread () from /usr/lib/libpthread.so.0 #17 0xf687f44e in clone () from /usr/lib/libc.so.6 BOth the threads are allocated memory at the same time , eventually resulting in deadlock. -Thanks

1 0

Last minute speaker needed for FOSDEM Dojo
by Rich Bowen 24 Jan '19

24 Jan '19

Hello, friends, One of the scheduled speakers for the FOSDEM Dojo has had to withdraw at the last minute due to a medical emergency. If you will be in Brussels next Friday, and are willing to present on a CentOS-related topic, please contact me off-list with a proposed title and abstract, by end of business tomorrow. Please see https://wiki.centos.org/Events/Dojo/Brussels2019 for an idea of what kind of talks we already have scheduled. Thank you! -- Rich Bowen - rbowen(a)redhat.com @CentOSProject // @rbowen 859 351 9166

1 0

AMI images on AWS
by Rich Bowen 23 Jan '19

23 Jan '19

I asked this on IRC, but posting it here, too, in case someone sees it here and not there. Can someone volunteer to respond to this tweet: https://twitter.com/translatewiki/status/1088137687461183488 "@CentOSProject Can you point me to an active contributor to cloud images in the community? I've searched before, and failed, and the CentOS @awscloud AMIs haven't been updated since May 2018 (i.e. are still on 7.5). https://aws.amazon.com/marketplace/pp/B00O7WM7QW " I have no idea how those are updated, or who provided what's there. I seem to remember asking this before, but I don't think anybody raised their hands. If you know, or if it's you, please document here - https://wiki.centos.org/Cloud/AWS - how one goes about uploading those images, and/or who is responsible for doing so. -- Rich Bowen - rbowen(a)redhat.com @CentOSProject // @rbowen 859 351 9166

1 1

Adding to the PPC arch group
by Philip Prindeville 22 Jan '19

22 Jan '19

Hi. I and my development group are interested in doing ppc (ppc32) development for CentOS 7 and getting that running on certain SoC-based platforms. I imagine that there’s some overlap with the 32-bit component on the Power7 work. We have Centos 7.6 x86_64 servers that we can do in-house builds on. We’re mostly looking for collaboration, and maybe a little initial guidance about the pitfalls of setting up a cross build environment, adapting RPM .spec's for additional architectural builds, etc. We have no idea how much work this will be. We’re also interested in supporting newer (4.10 or later) kernels, so we’ll probably contribute to elrepo as well. Any pointers/wisdom welcome. Thanks, -Philip

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel January 2019