devel March 2019

devel@lists.centos.org

18 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

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

contributions to websites
by Florian Winter 01 Apr '19

01 Apr '19

Hi all, I'd like to contribute to websites belonging to CentOS. How can I start, what's the best way ? One suggestion I have, is to migrate centos.org from nanoc to a python based static site generator for example pelican. best regards, florian

6 17

[scl.org] [SCLo SIG] new sclo-php*-unit-php packages available for testing
by Remi Collet 25 Mar '19

25 Mar '19

Yet another package available in centos-sclo-sclo-testing NGINX Unit is a dynamic web and application server, designed to run applications in multiple languages. Unit is lightweight, polyglot, and dynamically configured via API. The design of the server allows reconfiguration of specific application parameters as needed by the engineering or operations. See https://unit.nginx.org/ unit-php is the module for the php language designed to work with "unit" from official nginx repository. For rh-php72 (EL-7 only) * sclo-php72-unit-php-1.8.0-1 For rh-php71 (EL-7 only) * sclo-php71-unit-php-1.8.0-1 For rh-php70 * sclo-php70-unit-php-1.8.0-1 Remi. P.S. https://wiki.centos.org/SpecialInterestGroup/SCLo

1 0

CentOS Atomic Host 7.1902 Available for Download
by Jason Brooks 20 Mar '19

20 Mar '19

The CentOS Atomic SIG has released an updated version (https://wiki.centos.org/SpecialInterestGroup/Atomic/Download) of CentOS Atomic Host (7.1902), an operating system designed to run Linux containers, built from standard CentOS 7 RPMs, and tracking the component versions included in Red Hat Enterprise Linux Atomic Host. CentOS Atomic Host includes these core component versions: * atomic-1.22.1-26.gitb507039.el7.centos.x86_64 * rpm-ostree-client-2018.5-2.atomic.el7.x86_64 * ostree-2018.5-1.el7.x86_64 * cloud-init-18.2-1.el7.centos.1.x86_64 * docker-1.13.1-91.git07f3374.el7.centos.x86_64 * kernel-3.10.0-957.5.1.el7.x86_64 * podman-0.12.1.2-2.git9551f6b.el7.centos.x86_64 * flannel-0.7.1-4.el7.x86_64 * etcd-3.3.11-2.el7.centos.x86_64 ## Download CentOS Atomic Host CentOS Atomic Host is available as a VirtualBox or libvirt-formatted Vagrant box, or as an installable ISO, qcow2 or Amazon Machine image. For links to media, see the CentOS wiki (https://wiki.centos.org/SpecialInterestGroup/Atomic/Download). ## Upgrading If you're running a previous version of CentOS Atomic Host, you can upgrade to the current image by running the following command: # atomic host upgrade ## Release Cycle The CentOS Atomic Host image follows the upstream Red Hat Enterprise Linux Atomic Host cadence. After sources are released, they're rebuilt and included in new images. After the images are tested by the SIG and deemed ready, we announce them. ## Getting Involved CentOS Atomic Host is produced by the CentOS Atomic SIG (http://wiki.centos.org/SpecialInterestGroup/Atomic), based on upstream work from Project Atomic (http://www.projectatomic.io/). If you'd like to work on testing images, help with packaging, documentation -- join us! You'll often find us in #atomic and/or #centos-devel if you have questions. You can also join the atomic-devel (https://lists.projectatomic.io/mailman/listinfo/atomic-devel) mailing list if you'd like to discuss the direction of Project Atomic, its components, or have other questions. ## Getting Help If you run into any problems with the images or components, feel free to ask on the centos-devel (http://lists.centos.org/mailman/listinfo/centos-devel) mailing list. Have questions about using Atomic? See the atomic (https://lists.projectatomic.io/mailman/listinfo/atomic) mailing list or find us in the #atomic channel on Freenode.

1 0

openjdk headless now requires gtk2
by Gordon Messmer 19 Mar '19

19 Mar '19

Does anyone know why the headless openjdk now requires gtk2? Changelogs say "see RHBZ 1598152" but that bug is private. It looks like the change was intended to affect the "headful" package and not the headless one... Curiosity has the better of me.

2 3

dist-git
by Miroslav Suchý 15 Mar '19

15 Mar '19

I would like to ask what is status of dist-git in CentOS? Do you use it is as bunch of packages or as package? Originally dist-git was just bunch of packages copied to propper places. But since we started using dist-git in Copr we packaged it: https://koji.fedoraproject.org/koji/packageinfo?packageID=20308 and gave it propper upstream: https://github.com/release-engineering/dist-git Copr and Fedora now use this package. Does CentOS use this package or do you have just files you maintain on your own? Miroslav

1 0

[Meeting] RDO meeting (2019-03-13) minutes
by Michael Turek 13 Mar '19

13 Mar '19

============================== #rdo: RDO meeting - 2019-03-13 ============================== Meeting started by mjturek at 15:00:13 UTC. The full logs are available at http://eavesdrop.openstack.org/meetings/rdo_meeting___2019_03_13/2019/rdo_m… . Meeting summary --------------- * roll call (mjturek, 15:00:28) * Logging woes for containers job (mjturek, 15:03:45) * As per tripleo-ci change pike w/ ceph is workikng again (see https://review.rdoproject.org/r/#/c/19141 + depends-on) (mjturek, 15:06:08) * Ansible 2.7 blocked in Stein on Nautilus build on PPC (fultonj, 15:07:27) * LINK: https://review.rdoproject.org/r/#/c/18721 (mjturek, 15:08:06) * LINK: https://bugs.centos.org/view.php?id=15906 (fultonj, 15:11:09) * PPC build of ceph nautilus is failing with an OOM, need to talk with centos folks for help here. E-mail sent and bug opened (mjturek, 15:14:59) * chair for next meeting (mjturek, 15:16:01) * amoralej to chair next meeting (mjturek, 15:16:48) * open floor (mjturek, 15:17:17) * LINK: https://review.rdoproject.org/r/#/c/19236/ (mjturek, 15:20:33) Meeting ended at 15:32:15 UTC. People present (lines said) --------------------------- * mjturek (45) * fultonj (26) * amoralej (25) * ykarel (20) * openstack (9) * jschlueter (4) * rdogerrit (3) * gfidente (3) * baha (2) * PagliaccisCloud (1) * jpena (1) * Duck (1) Generated by `MeetBot`_ 0.1.4

1 0

Delivery Status Notification (Failure)
by 82ee9d11＠opayq.com 08 Mar '19

08 Mar '19

** Recipient inbox full ** Your message couldn't be delivered to curtiskwong101(a)gmail.com. Their inbox is full, or it's getting too much mail right now. The response was: Storage quota exceeded 505; Thu, 07 Mar 2019 21:07:30 -0800 (PST) X-Google-Smtp-Source: APXvYqwqjttOCYXh4ZR1W0Q/VprVQ9fJ74419RyKyaGEhxC9MwAB/= kNWAfFobsReYLBGlfh7/ous X-Received: by 2002:a50:b1ab:: with SMTP id m40mr30917065edd.268.1552021649= 299; Thu, 07 Mar 2019 21:07:29 -0800 (PST) ARC-Seal: i=3D1; a=3Drsa-sha256; t=3D1552021649; cv=3Dnone; d=3Dgoogle.com; s=3Darc-20160816; b=3DlwvPPNGfKW55llPbH7WjDteA/L2NXbcFS4dbS1Tn469JVPhyqS5SuBoT6HYIUKb= 2nN 2kJJXI0tQdgEfNZlwwC9o/KxycdMOmQ/T5mHze9NEpMxouMd7VBOkFT/iYD/Ev0N5C= PO HCz53C+ze5on9K/KNtCfOH6yZpiKB6ivNcoUz+t20TSFMJKgsFXIxU6myIZbsW3M/q= Eh vD/SaSak6nKvqskltOX6XL+2VO6tr25WtOGsJ9RKqKVrGDOCVUbyK4YJfr3pAFzmO1= sw FP0/agy/hYdiP/013pQJjfvi+NlyGVIw11BRQqg5j2AAZXGkbO6x/oOOIeUxTFwpeN= Nz 9OiQ=3D=3D ARC-Message-Signature: i=3D1; a=3Drsa-sha256; c=3Drelaxed/relaxed; d=3Dgoog= le.com; s=3Darc-20160816; h=3Derrors-to:list-subscribe:list-help:list-post:list-archive :list-unsubscribe:list-unsubscribe:list-id:precedence:message-id :date:subject:to:reply-to:sender:from:content-transfer-encoding :mime-version:dkim-signature:delivery-date; bh=3DaQQ0nbuqIKYRASWgXORZo4zKyYMtYXyLrH9uPVN5o+I=3D; b=3DJZKnfrnDsQx0xVARcjTYu3d+S3Y+zGji1FQ0q5FvxFAFqmdOFz4zwD9BSgmZRk0= Nky uaM/vdIJjQJRJNpopg4EKybMMISjSrPmrHaJCZaFNXQEHbovDAxsalKJ2VB8IxkOtx= LP 0YFnXOcCf/TB7n0Zp14QKAq0djlP9r4pqToq4EGe5zrfznc3Wfol8Id9wYNYbjC2ix= dz 4g2R0PROxpEVBOwkTUwp7XFAxelC9bH+QjG9zODtf4RVt/8Ax98YNEcDVK03ArCdgs= Bh CXPuxu5ucg+1/E9Ymv/KBGXTGcRKDmH6iWHIe2LZUh6EwBz4f09rJkQh9LtRfyWGF8= a4 yQXA=3D=3D ARC-Authentication-Results: i=3D1; mx.google.com; dkim=3Dpass header.i=3D(a)opayq.com header.s=3Dabine header.b=3D"JAwXX= /P0"; spf=3Dpass (google.com: domain of fwd.8ltx5hf60pqr(a)opayq.com designa= tes 184.105.182.73 as permitted sender) smtp.mailfrom=3DFWD.8ltx5hf60pqr@op= ayq.com; dmarc=3Dpass (p=3DNONE sp=3DNONE dis=3DNONE) header.from=3Dopayq.com Return-Path: <FWD.8ltx5hf60pqr(a)opayq.com> Received: from 125-he.filtered.junkemailfilter.com (retry2.ctyme.com. [184.= 105.182.73]) by mx.google.com with ESMTPS id g18si2870930edh.169.2019.03.07.21.0= 7.28 for <curtiskwong101(a)gmail.com> (version=3DTLS1_2 cipher=3DECDHE-RSA-AES128-GCM-SHA256 bits=3D128/1= 28); Thu, 07 Mar 2019 21:07:29 -0800 (PST) Received-SPF: pass (google.com: domain of fwd.8ltx5hf60pqr(a)opayq.com design= ates 184.105.182.73 as permitted sender) client-ip=3D184.105.182.73; Authentication-Results: mx.google.com; dkim=3Dpass header.i=3D(a)opayq.com header.s=3Dabine header.b=3D"JAwXX= /P0"; spf=3Dpass (google.com: domain of fwd.8ltx5hf60pqr(a)opayq.com designa= tes 184.105.182.73 as permitted sender) smtp.mailfrom=3DFWD.8ltx5hf60pqr@op= ayq.com; dmarc=3Dpass (p=3DNONE sp=3DNONE dis=3DNONE) header.from=3Dopayq.com Delivery-date: Thu, 07 Mar 2019 21:07:28 -0800 Received: from 133-he.filtered.junkemailfilter.com ([184.105.182.133]:49195= ) helo=3D133-he.filtered.junkemailfilter.com by retry2.junkemailfilter.com with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SH= A384:256) (Exim 4.90_1) id 1h19Qd-0007WB-GT on interface=3D184.105.182.73 for curtiskwong101(a)gmail.com; Tue, 05 Mar 2019 04:44:15 -0800 Received: from smtp3.opayq.com ([23.23.126.237]:33946) helo=3D[23.23.126.23= 7] by opayq-outbound.junkemailfilter.com with esmtps (TLSv1.2:AES256-SHA256:2= 56) (Exim 4.90) id 1h18lG-0007Mv-10 on interface=3D184.105.182.150 for curtiskwong101(a)gmail.com; Tue, 05 Mar 2019 04:01:30 -0800 DKIM-Signature: v=3D1; d=3Dopayq.com; t=3D1551787273; b=3DJAwXX/P00r9hz2RIc= 2CUrC9trpG8i37xFVOFE/RPVlJRMRBVzJYotCQjRwvkB6s3KlWD3LtE2WTrQdWT5nBOoGcjTwHG= OPFmDL/whkcpuEhzJhEcmSJegdeHzjNfuptqYUUO1CzEVBEC0foYRRUEbslM6lj237MVuD7xsj8= 9FIM=3D; s=3Dabine; c=3Drelaxed/relaxed; a=3Drsa-sha256; bh=3DaQQ0nbuqIKYRA= SWgXORZo4zKyYMtYXyLrH9uPVN5o+I=3D; h=3DDate:From:Reply-To:Subject:To:List-U= nsubscribe; MIME-Version: 1.0 Content-Type: text/plain; charset=3D"us-ascii" Content-Transfer-Encoding: 7bit X-GetAbine-Processed: 1 From: "centos.org [Masked]" <FWD.8ltx5hf60pqr(a)opayq.com> Sender: "centos.org [Masked]" <FWD.8ltx5hf60pqr(a)opayq.com> Reply-To: FWD.8ltx5hf60pqr(a)opayq.com To: 82ee9d11(a)opayq.com X-GetAbine-Sender: centos-devel-bounces(a)centos.org X-GetAbine-Disposable: 82ee9d11(a)opayq.com X-GetAbine-Host-Address: 23.23.126.237 Subject: CentOS-devel Digest, Vol 169, Issue 3 Date: Tue, 05 Mar 2019 12:00:04 +0000 Message-ID: <mailman.17.1551787204.6105.centos-devel(a)centos.org> X-BeenThere: centos-devel(a)centos.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "The CentOS developers mailing list." <centos-devel.centos.org> List-Unsubscribe: <https://lists.centos.org/mailman/options/centos-devel>, <mailto:centos-devel-request@centos.org?subject=3Dunsubscribe> List-Unsubscribe: <mailto:unsubscribe-345585171-82ee9d11@opayq.com>, <https= ://emails.abine.com/disableDisposable?fwd=3DFWD.8ltx5hf60pqr@opayq.com> List-Archive: <http://lists.centos.org/pipermail/centos-devel/> List-Post: <mailto:centos-devel@centos.org> List-Help: <mailto:centos-devel-request@centos.org?subject=3Dhelp> List-Subscribe: <https://lists.centos.org/mailman/listinfo/centos-devel>, <mailto:centos-devel-request@centos.org?subject=3Dsubscribe> X-Sender-Domain: centos.org X-Spamfilter-host: plato.junkemailfilter.com - http://www.junkemailfilter.c= om X-Key-ID: ODJlZTlkMTFAb3BheXEuY29tIGNlbnRvcy1kZXZlbC1ib3VuY2VzQGNlbnRvcy5vc= mcgMjAxOS0wMy0wNSAwNDowMToxMS44OTIgMWgxOGt4LTAwMDM5ay1OZA=3D=3D X-Content-flags: aging attachment available dashes date delivered delivery = design designa devel doitnow email email-adr fwd goog google https image in= terface ios ip-address link links longword message notification opics optou= t pass phone-num please post quota re received reply replying request respo= nse right subscribe text-plain time-ref transfer unsubscribe utf-8 via web X-Domain-list: centos.org steadfastdns.net steadfast.net X-Sender-Host-Address: 208.100.23.70 X-Sender-Host-Name: mail.centos.org Errors-to: <> X-Key-ID: Y3VydGlza3dvbmcxMDFAZ21haWwuY29tIGZ3ZC44bHR4NWhmNjBwcXJAb3BheXEuY= 29tIDIwMTktMDMtMDUgMDQ6MDE6MzAuMjE4IDFoMThsRy0wMDA3TXYtMTA=3D X-Outscan: http://www.junkemailfilter.com X-Sender-Domain: junkemailfilter.com -------------------------Blur------------------------- This email is forwarded from a MASKED EMAIL you created using Blur. (https= ://dnt.abine.com/#help/faq/faq-whataremaskedemails). IF THIS IS SPAM, CLICK HERE TO BLOCK: https://dnt.abine.com/#/block_email/82ee9d11@opayq.com/FWD.8ltx5hf60pqr@opa= yq.com Want to shop safely and privately online? Go Premium: https://dnt.abine.com= /?pk_campaign=3DmaskHeader#premium -------------------------by Abine------------------------- 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. Delivery Status Notification (Failure) (82ee9d11(a)opayq.com) ---------------------------------------------------------------------- Message: 1 Date: Mon, 04 Mar 2019 21:11:42 -0800 (PST) From: 82ee9d11(a)opayq.com To: centos-devel(a)centos.org Subject: [CentOS-devel] Delivery Status Notification (Failure) Message-ID: <973264783.4558.1551762704991.JavaMail.root(a)smtp5.opayq.com> Content-Type: text/plain; charset=3D"utf-8" ** Recipient inbox full ** Your message couldn't be delivered to curtiskwong101(a)gmail.com. Their inbox= is full, or it's getting too much mail right now. The response was: Storage quota exceeded

1 0

Messaging SIG
by Matthias Runge 06 Mar '19

06 Mar '19

Hello, quite a while ago, I asked for creation of the messaging SIG. There is even a wiki page for this[1], and it was created over half a year ago, the initial discussion has even been older. However, this wasn't resolved (yet). I also have to realise, I couldn't put the deserved energy and time to this proposal. Nevertheless, I still think the idea is good and would help other SIGs with their use of messaging related packages and setups. So with that, can we please go back to start and get this finished? Maybe it would be benificial, if someone else from the Centos Board could jump in and help KB with this? Thank you, Matthias [1] https://wiki.centos.org/SpecialInterestGroup/Messaging -- Matthias Runge <mrunge(a)matthias-runge.de>

3 6

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel March 2019