devel

devel@lists.centos.org

2 participants
4695 discussions

Buildlogs Push
by kbsingh＠centos.org 31 Oct '19

31 Oct '19

N: 7/configmanagement/x86_64/ansible26/ ansible-2.6.20-1.el7.noarch.rpm N: 7/configmanagement/aarch64/ansible26/ ansible-2.6.20-1.el7.noarch.rpm N: 7/configmanagement/ppc64le/ansible26/ ansible-2.6.20-1.el7.noarch.rpm N: 7/configmanagement/x86_64/ansible27/ ansible-2.7.13-1.el7.noarch.rpm N: 7/configmanagement/aarch64/ansible27/ ansible-2.7.13-1.el7.noarch.rpm N: 7/configmanagement/ppc64le/ansible27/ ansible-2.7.13-1.el7.noarch.rpm

1 0

Fwd: DevConf.CZ 2020 CfP Deadline Extended to Nov 6
by Rich Bowen 31 Oct '19

31 Oct '19

FYI, in case you were considering submitting to DevConf.cz for next year. -------- Forwarded Message -------- DevConf.CZ 2020 CfP Deadline Extended to Nov 6 Hi all, The CfP deadline for DevConf.CZ 2020 has been extended*to next Wednesday, Nov 6*. A few more days to make sure you get your proposals in: https://www.devconf.info/cz/

1 0

Buildlogs Push
by kbsingh＠centos.org 31 Oct '19

31 Oct '19

N: 7/cloud/x86_64/openstack-rocky/ python2-swiftclient-3.6.1-1.el7.noarch.rpm N: 7/cloud/x86_64/openstack-rocky/ python-swiftclient-doc-3.6.1-1.el7.noarch.rpm N: 7/cloud/aarch64/openstack-rocky/ python2-swiftclient-3.6.1-1.el7.noarch.rpm N: 7/cloud/aarch64/openstack-rocky/ python-swiftclient-doc-3.6.1-1.el7.noarch.rpm N: 7/cloud/ppc64le/openstack-rocky/ python2-swiftclient-3.6.1-1.el7.noarch.rpm N: 7/cloud/ppc64le/openstack-rocky/ python-swiftclient-doc-3.6.1-1.el7.noarch.rpm

1 0

Call for content: November newsletter
by Rich Bowen 30 Oct '19

30 Oct '19

I am working on the November newsletter (See https://wiki.centos.org/Newsletter for past issues) and would like content from you. Relevant topics include: * What interesting things you're working on, in or on CentOS * SIG reports (these have already been requested, but if you have something interesting to report, that would be of interest) * Releases (either of SIG projects, or something else that you're working on) * Tutorials/Howtos * Upcoming events that you would like to promote * Recent events that you attended and want to tell us about Please either contact me directly, or (better yet) post to the centos-promo mailing list (copied here) with your ideas, your articles, or suggestions of who I should be approaching. Thanks! -- Rich Bowen - rbowen(a)redhat.com @CentOSProject // @rbowen 859 351 9166

1 0

Buildlogs Push
by kbsingh＠centos.org 30 Oct '19

30 Oct '19

N: 7/virt/x86_64/container/ podman-1.6.2-3.el7.x86_64.rpm N: 7/virt/x86_64/container/ podman-docker-1.6.2-3.el7.noarch.rpm N: 7/virt/x86_64/container/ podman-manpages-1.6.2-3.el7.noarch.rpm

1 0

Buildlogs Push
by kbsingh＠centos.org 30 Oct '19

30 Oct '19

N: 7/virt/x86_64/container/ conmon-2.0.2-1.el7.x86_64.rpm

1 0

Buildlogs Push
by kbsingh＠centos.org 30 Oct '19

30 Oct '19

N: 7/cloud/x86_64/openstack-stein/ openstack-ironic-api-12.1.3-1.el7.noarch.rpm N: 7/cloud/x86_64/openstack-stein/ openstack-ironic-common-12.1.3-1.el7.noarch.rpm N: 7/cloud/x86_64/openstack-stein/ openstack-ironic-conductor-12.1.3-1.el7.noarch.rpm N: 7/cloud/x86_64/openstack-stein/ python2-ironic-tests-12.1.3-1.el7.noarch.rpm N: 7/cloud/x86_64/openstack-stein/ python2-swiftclient-3.7.1-1.el7.noarch.rpm N: 7/cloud/x86_64/openstack-stein/ python-swiftclient-doc-3.7.1-1.el7.noarch.rpm N: 7/cloud/aarch64/openstack-stein/ openstack-ironic-api-12.1.3-1.el7.noarch.rpm N: 7/cloud/aarch64/openstack-stein/ openstack-ironic-common-12.1.3-1.el7.noarch.rpm N: 7/cloud/aarch64/openstack-stein/ openstack-ironic-conductor-12.1.3-1.el7.noarch.rpm N: 7/cloud/aarch64/openstack-stein/ python2-ironic-tests-12.1.3-1.el7.noarch.rpm N: 7/cloud/aarch64/openstack-stein/ python2-swiftclient-3.7.1-1.el7.noarch.rpm N: 7/cloud/aarch64/openstack-stein/ python-swiftclient-doc-3.7.1-1.el7.noarch.rpm N: 7/cloud/ppc64le/openstack-stein/ openstack-ironic-api-12.1.3-1.el7.noarch.rpm N: 7/cloud/ppc64le/openstack-stein/ openstack-ironic-common-12.1.3-1.el7.noarch.rpm N: 7/cloud/ppc64le/openstack-stein/ openstack-ironic-conductor-12.1.3-1.el7.noarch.rpm N: 7/cloud/ppc64le/openstack-stein/ python2-ironic-tests-12.1.3-1.el7.noarch.rpm N: 7/cloud/ppc64le/openstack-stein/ python2-swiftclient-3.7.1-1.el7.noarch.rpm N: 7/cloud/ppc64le/openstack-stein/ python-swiftclient-doc-3.7.1-1.el7.noarch.rpm N: 7/cloud/x86_64/openstack-train/ openstack-ironic-api-13.0.2-1.el7.noarch.rpm N: 7/cloud/x86_64/openstack-train/ openstack-ironic-common-13.0.2-1.el7.noarch.rpm N: 7/cloud/x86_64/openstack-train/ openstack-ironic-conductor-13.0.2-1.el7.noarch.rpm N: 7/cloud/x86_64/openstack-train/ python2-ironic-tests-13.0.2-1.el7.noarch.rpm N: 7/cloud/aarch64/openstack-train/ openstack-ironic-api-13.0.2-1.el7.noarch.rpm N: 7/cloud/aarch64/openstack-train/ openstack-ironic-common-13.0.2-1.el7.noarch.rpm N: 7/cloud/aarch64/openstack-train/ openstack-ironic-conductor-13.0.2-1.el7.noarch.rpm N: 7/cloud/aarch64/openstack-train/ python2-ironic-tests-13.0.2-1.el7.noarch.rpm N: 7/cloud/ppc64le/openstack-train/ openstack-ironic-api-13.0.2-1.el7.noarch.rpm N: 7/cloud/ppc64le/openstack-train/ openstack-ironic-common-13.0.2-1.el7.noarch.rpm N: 7/cloud/ppc64le/openstack-train/ openstack-ironic-conductor-13.0.2-1.el7.noarch.rpm N: 7/cloud/ppc64le/openstack-train/ python2-ironic-tests-13.0.2-1.el7.noarch.rpm

1 0

SIGs - Please submit for FOSDEM and CentOS Dojo
by Rich Bowen 29 Oct '19

29 Oct '19

FOSDEM will be February 1st and 2nd in Brussels, Belgium. It would be great to have representation from each of our SIGs at FOSDEM. There are dozens of devrooms this year - https://fosdem.org/2020/news/2019-10-01-accepted-developer-rooms/ - and many of them have some direct relevance to you. Note that each devroom handles its own call for presentations separately, which is a bit of a hassle. So have a look at the list and see the track(s) where your content would be most relevant. Please keep me informed once you know that your talk(s) have been accepted. We are also running the annual CentOS Dojo on the Friday before the main FOSDEM event (January 31). The details are at https://wiki.centos.org/Events/Dojo/Brussels2020 and we need (roughly) 14 presentations. I would love to have representation from our various SIGs there. The audience tends to be those most passionate about CentOS, and they're looking for fairly deep technical content about what you're working on, both *in* and *on* CentOS. If you want help with an idea, or with your abstract, please let me know. -- Rich Bowen - rbowen(a)redhat.com @CentOSProject // @rbowen 859 351 9166

1 0

Re: [CentOS-devel] CBS and SIGs consuming CentOS 8 / Stream
by Thomas Oulevey 29 Oct '19

29 Oct '19

Hi Folks, >> We are going to announce soon a plan to upgrade cbs.centos.org and >> associated builders to be able to build standard C8 RPM packages, >> without interfering too much with SIGs ongoing work. > > is this plan discussed on Mondays CBS meetings? > I don't see it logged in https://www.centos.org/minutes/2019/September/ We didn't manage to have a meeting on Monday. >> To conclude, we will send an update beginning of next week with more >> information, a schedule and a list of points that need to be sorted out >> with the community. I'll try to give a summary of my investigation. I'll decouple two problems : the koji upgrade and having a working CentOS 8 target/buildroot in cbs.centos.org with CentOS 7 builders. 1/ koji upgrade The first step is to upgrade our version of koji to match the version mbox uses. At the same time we move away from puppet to ansible (thanks Arrfab for all the work! [1] & [2]) and upgrade the base operating system from CentOS 6 to CentOS 7. At the same time the builders (where mock runs) need to run specific version of certain tools for C8 buildroots : distribution-gpg-keys.noarch 1.21-1.el7 kernel.x86_64 4.19.34-300.el7 mock.noarch 1.3.4-1.el7_build.rhel8 python-perf.x86_64 4.19.34-300.el7 python2-distro.noarch 1.0.3-1.el7.rhel8 * Status: Update works and db schema can be easily upgraded. We have few more test to validate that the previous mentioned RPM updates don't break anything for C6 & C7 targets. Next step is to announce a downtime and execute the upgrade plan. 2/ CentOS 8 buildroot When 1/ is done we can create an C8 buildroot without enabling the Appstream repo. Due to the nature of Appstream, and how koji uses mergerepo (--koji)/updaterepo/mock, more work is needed to get a working buildroot. I don't fully understand the underlying issue so comments are very welcome to enlighten us ! One of the solution found by Fedora team is to split Appstream per repository and enable only the one needed in a specific buildroot [3]. We are evaluating the tools. And see if we can use koji external-repo or tag inheritance to achieve it (which is mbox solution [4]) However for a community build service, we don't know exactly what people will build and what Appstream packages will be needed in each buildroot (we have 290 targets at this time for C7). So we still need time and new ideas :-) * Status: Investigating possible solutions. -- Thomas Oulevey [1] : https://github.com/CentOS/ansible-role-kojihub [2] : https://github.com/CentOS/ansible-role-kojid [3] : https://github.com/fedora-modularity/GrobiSplitter [4] : https://koji.mbox.centos.org/koji/taginfo?tagID=3

6 8

[REMINDER] 2019-10-28 cbs.centos.org infrastructure upgrade.
by Thomas Oulevey 28 Oct '19

28 Oct '19

Dear All, As previously announced [1], an intervention on cbs.centos.org will start in few minutes at 2019-10-28 7:00 UTC. -- Thomas on behalf of the infrastructure team. [1]: * What does that mean for you ? Next Monday, we'll upgrade koji and tools to 1.16 version. At the same time the koji hub server will be moved from CentOS 6 to CentOS 7. The change is scheduled to be implemented on Monday October 28th, 7:00 am UTC time You can convert to local time with $(date -d '2019-10-28 7:00 UTC') * What will be the impact ? Koji build service will be down for 4 hours. It will not be possible to build new packages or images. Please note that temporary repositories served on cbs.centos.org will be also affected ; they are mostly used for CI. Please let us know before Friday October 25th if it could impact dramatically your work/releases schedule.

2 1

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel