devel

devel@lists.centos.org

17 participants
4590 discussions

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

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel