devel

devel@lists.centos.org

10 participants
4617 discussions

when the fix for CVE-2018-2794 & CVE-2018-2814 would be available in OpenJDK 1.7?
by Maheshwari, Shagun 02 May '18

02 May '18

Hi All, We are currently on OpenJDK 1.7.0_161 and OpenJDK 1.7.0_161 is impacted by CVE-2018-2794 & CVE-2018-2814 It seems we do NOT have an ETA for the fix. I could see RH already posted a fix for OpenJDK 1.8 here - https://clicktime.symantec.com/a/1/OXdEaLeTBZV355U3VoZGXHSsHP8TO8kMoHYzvixK… Can you please find out when the fix for OpenJDK 1.7 would be available ? If this is getting delayed, can you help to back port this fix ? Regards, Shagun

2 1

SIG meeting times
by Rich Bowen 01 May '18

01 May '18

I noticed this afternoon that the .ics file linked from https://www.centos.org/community/calendar/ was AWOL, and I've replaced it with one that agrees with all of the times on that page. I suspect, however, that that page is incomplete and/or out of date. If you are responsible for a SIG's meeting schedule, please have a look at that page, and let me know if any updates. Thanks. -- Rich Bowen - rbowen(a)redhat.com @CentOSProject // @rbowen

1 0

CentOS 7.4.1708 CR Available in CBS
by Brian Stinson 27 Apr '18

27 Apr '18

Hi Folks, The CR (https://wiki.centos.org/AdditionalResources/Repositories/CR) repository was released earlier today. 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. As we discussed earlier (https://lists.centos.org/pipermail/centos-devel/2018-April/016627.html) 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. Cheers! -- Brian Stinson

3 2

[HPC SIG] "talking points" for an HPC event
by Rich Bowen 27 Apr '18

27 Apr '18

I was hoping to get the attention of folks from the HPC SIG to help me craft a message to take to an HPC event that I'll be attending soon - ISC-HPC in Frankfurt. I expect that you're aware of it. Last year, I got questions regarding what's happening in the HPC SIG in CentOS, and I know at that time it was still fairly young. I was hoping to get something from you - whether bullet points, a blog post, a video I should watch, or whatever - so that this year I will be better informed, and can answer questions intelligently about what's happening in HPC in CentOS. I see just one email to this list, from back in October, from Adrian Reber, about the first SIG meeting, but nothing since then. Are you having regular meetings that I should attend between now and June? Thanks for any info you can pass my way. --Rich -- Rich Bowen - rbowen(a)redhat.com @CentOSProject // @rbowen

2 2

[Meeting] RDO meeting - 2018-04-25
by Chandan kumar 25 Apr '18

25 Apr '18

============================== #rdo: RDO meeting - 2018-04-25 ============================== Meeting started by chandankumar at 15:04:54 UTC. The full logs are available at http://eavesdrop.openstack.org/meetings/rdo_meeting___2018_04_25/2018/rdo_m… . Meeting summary --------------- * Test day preparation status (chandankumar, 15:06:12) * LINK: https://dashboards.rdoproject.org/rdo-dev (chandankumar, 15:09:13) * Rocky M1 RDO test day on May 03-04, 2018 (chandankumar, 15:11:17) * ACTION: chandankumar to post a blog post for M1 ROcky test day (chandankumar, 15:20:47) * backup volunteers as well as demo volunteers for Red Hat Summit and OpenStack Summit (chandankumar, 15:22:01) * LINK: https://etherpad.openstack.org/p/rdo-manageIQ-ceph-rhSummit2018 (leanderthal, 15:25:55) * LINK: https://etherpad.openstack.org/p/rdo-vancouver-summit-booth (leanderthal, 15:26:10) * stemming from tripleo-ci community meeting (chandankumar, 15:29:11) * chair for next meeting (chandankumar, 15:43:40) * ACTION: leanderthal to chair for next meeting (chandankumar, 15:44:26) * open floor (chandankumar, 15:44:41) Meeting ended at 15:48:50 UTC. Action items, by person ----------------------- * chandankumar * chandankumar to post a blog post for M1 ROcky test day * leanderthal * leanderthal to chair for next meeting People present (lines said) --------------------------- * chandankumar (51) * leanderthal (40) * myoung (14) * dmsimard (11) * amoralej (10) * openstack (9) * kashyap (7) * jpena (6) * PagliaccisCloud (2) * rdogerrit (2) * mollyk (2) * ykarel (1) * panda|ruck (1) * mjturek (1) * Duck (0) Generated by `MeetBot`_ 0.1.4 Thanks, Chandan Kumar

1 0

CentOS PaaS SIG meeting (2018-04-25)
by Troy Dawson 25 Apr '18

25 Apr '18

Hello, It's time for our weekly PaaS SIG sync-up meeting Time: 1700 UTC - Wedensdays (date -d "1700 UTC") Date: Today Wedensday, 25 April 2018 Where: IRC- Freenode - #centos-devel Agenda: - OpenShift Current Status -- rpms -- automation - Training for new committee members - Open Floor Minutes from last meeting: https://www.centos.org/minutes/2018/April/centos-devel.2018-04-18-17.00.log…

1 0

SIGs: Possibility to drop EOL content at 7.5 release time
by Anssi Johansson 23 Apr '18

23 Apr '18

Hi, this is not really my job, but I don't mind ruffling a few feathers if I need to. RHEL/CentOS 7.5 is probably around the corner. This would be an excellent time to remove any EOL software you may have floating around on mirror.centos.org. Unless otherwise specified, any SIG content under 7.4 will be copied over to 7,5. I'd imagine that for example openstack-newton could be dropped because it went EOL in 2017-10-25. Is there some other content that could be dropped? If SIGs want to drop something at 7.5 release time, please let hughesjr know. Filing a bug would be one way to do that. Content can be removed either by directory name, or by individual package names. You should also communicate to your users in advance that the EOL packages will disappear, and if necessary, instruct them to migrate to a newer supported version. Having instructions for that procedure published somewhere would be nice. The old content under 7.4.1708, including any EOL content, will be archived to vault.centos.org, and that content will be available in the vault indefinitely. The 7.4.1708 directory on mirror.centos.org will be emptied some time after 7.5 is released. For reference and inspiration, here are some directories from mirror.centos.org, including both up-to-date content and potentially EOL content. SIG chairs should review the list to make sure these directories can be copied over to 7.5.18xx when that time comes. Making the decisions now would save a bit of time at 7.5 release time. cloud/x86_64/openstack-newton cloud/x86_64/openstack-ocata cloud/x86_64/openstack-pike cloud/x86_64/openstack-queens configmanagement/x86_64/yum4 dotnet nfv/x86_64/fdio nfv/x86_64/fdio/vpp nfv/x86_64/fdio/vpp/vpp-1710 opstools/x86_64/fluentd opstools/x86_64/logging opstools/x86_64/perfmon opstools/x86_64/sensu paas/x86_64/openshift-origin paas/x86_64/openshift-origin13 paas/x86_64/openshift-origin14 paas/x86_64/openshift-origin15 paas/x86_64/openshift-origin36 paas/x86_64/openshift-origin37 rt sclo/x86_64/rh/devassist09 sclo/x86_64/rh/devtoolset-3 sclo/x86_64/rh/devtoolset-4 sclo/x86_64/rh/devtoolset-6 sclo/x86_64/rh/devtoolset-7 sclo/x86_64/rh/git19 sclo/x86_64/rh/go-toolset-7 sclo/x86_64/rh/httpd24 sclo/x86_64/rh/llvm-toolset-7 sclo/x86_64/rh/mariadb55 sclo/x86_64/rh/maven30 sclo/x86_64/rh/mongodb24 sclo/x86_64/rh/mysql55 sclo/x86_64/rh/nginx16 sclo/x86_64/rh/nodejs010 sclo/x86_64/rh/passenger40 sclo/x86_64/rh/perl516 sclo/x86_64/rh/php54 sclo/x86_64/rh/php55 sclo/x86_64/rh/postgresql92 sclo/x86_64/rh/python27 sclo/x86_64/rh/python33 sclo/x86_64/rh/python34 sclo/x86_64/rh/rh-eclipse46 sclo/x86_64/rh/rh-git29 sclo/x86_64/rh/rh-java-common sclo/x86_64/rh/rh-mariadb100 sclo/x86_64/rh/rh-mariadb101 sclo/x86_64/rh/rh-mariadb102 sclo/x86_64/rh/rh-maven33 sclo/x86_64/rh/rh-maven35 sclo/x86_64/rh/rh-mongodb26 sclo/x86_64/rh/rh-mongodb30upg sclo/x86_64/rh/rh-mongodb32 sclo/x86_64/rh/rh-mongodb34 sclo/x86_64/rh/rh-mysql56 sclo/x86_64/rh/rh-mysql57 sclo/x86_64/rh/rh-nginx110 sclo/x86_64/rh/rh-nginx112 sclo/x86_64/rh/rh-nginx18 sclo/x86_64/rh/rh-nodejs4 sclo/x86_64/rh/rh-nodejs6 sclo/x86_64/rh/rh-nodejs8 sclo/x86_64/rh/rh-perl520 sclo/x86_64/rh/rh-perl524 sclo/x86_64/rh/rh-php56 sclo/x86_64/rh/rh-php70 sclo/x86_64/rh/rh-php71 sclo/x86_64/rh/rh-postgresql94 sclo/x86_64/rh/rh-postgresql95 sclo/x86_64/rh/rh-postgresql96 sclo/x86_64/rh/rh-python35 sclo/x86_64/rh/rh-python36 sclo/x86_64/rh/rh-redis32 sclo/x86_64/rh/rh-ror42 sclo/x86_64/rh/rh-ror50 sclo/x86_64/rh/rh-ruby23 sclo/x86_64/rh/rh-ruby24 sclo/x86_64/rh/rh-scala210 sclo/x86_64/rh/rh-thermostat16 sclo/x86_64/rh/rh-varnish4 sclo/x86_64/rh/ror40 sclo/x86_64/rh/ror41 sclo/x86_64/rh/ruby193 sclo/x86_64/rh/ruby200 sclo/x86_64/rh/ruby22 sclo/x86_64/rh/rust-toolset-7 sclo/x86_64/rh/thermostat1 sclo/x86_64/rh/v8314 sclo/x86_64/sclo/sclo-git212 sclo/x86_64/sclo/sclo-git25 sclo/x86_64/sclo/sclo-httpd24more sclo/x86_64/sclo/sclo-php54 sclo/x86_64/sclo/sclo-php55 sclo/x86_64/sclo/sclo-php56 sclo/x86_64/sclo/sclo-php70 sclo/x86_64/sclo/sclo-php71 sclo/x86_64/sclo/sclo-python27 sclo/x86_64/sclo/sclo-python34 sclo/x86_64/sclo/sclo-python35 sclo/x86_64/sclo/sclo-ror42 sclo/x86_64/sclo/sclo-subversion19 sclo/x86_64/sclo/vagrant1 storage/x86_64/ceph-hammer storage/x86_64/ceph-jewel storage/x86_64/ceph-luminous storage/x86_64/gluster-3.6 storage/x86_64/gluster-3.7 storage/x86_64/gluster-3.8 storage/x86_64/gluster-3.9 storage/x86_64/gluster-3.10 storage/x86_64/gluster-3.12 storage/x86_64/gluster-3.13 storage/x86_64/gluster-4.0 virt/x86_64/kubernetes19 virt/x86_64/kvm-common virt/x86_64/libvirt-latest virt/x86_64/ovirt-4.1 virt/x86_64/ovirt-4.2 virt/x86_64/xen-46 virt/x86_64/xen-48

9 8

CentOS PaaS SIG meeting (2018-04-18)
by Troy Dawson 18 Apr '18

18 Apr '18

Hello, It's time for our weekly PaaS SIG sync-up meeting Time: 1700 UTC - Wedensdays (date -d "1700 UTC") Date: Today Wedensday, 18 April 2018 Where: IRC- Freenode - #centos-devel Agenda: - OpenShift Current Status -- rpms -- automation - Training for new committee members -- How to get packages into repo's -- How to create tags, build targets, and repo's - New time for weekly meeting - Open Floor Minutes from last meeting: https://www.centos.org/minutes/2018/April/centos-devel.2018-04-04-17.00.log…

1 0

Proposal : potential "freeze" for SIG content to be built and/or pushed to mirrors
by Fabian Arrotin 17 Apr '18

17 Apr '18

Hi, As you're all aware, RHEL 7.5 was released yesterday, and at the CentOS side, the massive rebuild started for all arches (x86_64, i386, ppc64, ppc64le, aarch64 and armhfp). We'd like to have your opinion about the following proposal (TBD) : - we freeze the signing process for now, while we have focus on the distro rebuild. - we can also eventually freeze the CBS builders, so that all SIGs are now waiting for 7.5.1804 content to be available in CBS/koji and so rebuild against those pkgs We hope (but can't have any estimate) that for this release, all arches should be in "sync", so normally content should be available faster (in comparison with 7.4.1708 release) to CBS/Koji builders. Of course that's just a discussion, so feel free to comment. For example, we can also think about security issues for rpm packages built through koji that would need to be ASAP available on mirror.centos.org, and that wouldn't need to be built for/against 7.5.1804. Please comment on this. -- Fabian Arrotin The CentOS Project | https://www.centos.org gpg key: 56BEC54E | twitter: @arrfab

3 2

[SIG Process] Point-Release Freeze of SIG Content while CR is Active
by Brian Stinson 17 Apr '18

17 Apr '18

Hi Folks, At the CBS meeting yesterday we discussed a proposal to freeze the Sign and Push-to-mirror processes during the period between when CR is active and a point release. https://lists.centos.org/pipermail/centos-devel/2018-April/016610.html You may recall that we did something similar for 7.1708 We need to Freeze because we make CR content available in CBS for builds, and in CI for testing purposes. But, releasing content built against CR to mirror.centos.org would have had some unintended consequences (e.g. we don't want to require that end-users enable CR to get content from the SIGs). The Point-release Freeze does not affect content moving from the testing tags in CBS to buildlogs.c.o, that will continue to show up as it is built. Do note: since we do want to give testers and developers an opportunity to build and test against an upcoming point-release before it goes GA, content coming from buildlogs.centos.org may require enabling the CR repo. Any new requests for sign+push (adding new tags to mirror.c.o) during Point-release Freeze will be held until the point release goes GA. We approved this as part of the CR checklist during the meeting yesterday, and will include another note about this in the CR release announcement. https://www.centos.org/minutes/2018/April/centos-devel.2018-04-16-14.00.html If there are any questions, please let us know and discuss here on the list. Cheers! -- Brian Stinson

1 0

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