devel

devel@lists.centos.org

4590 discussions

Point-release Freeze is Active
by Brian Stinson 01 Nov '18

01 Nov '18

Hi Folks, As is usual, we freeze the SIG Sign + Push process as part of preparing for a point release. This helps us once CR is ready (it isn't yet, though) so that we can seed it quickly in CBS to build against. 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 once it's ready. 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. If there are any questions, please let us know and discuss here on the list. Cheers! -- Brian Stinson

2 3

Volunteers needed: FOSDEM Dojo content selection
by Rich Bowen 01 Nov '18

01 Nov '18

I need 3 or 4 people who are willing to review the submitted content for the FOSDEM Dojo and select a schedule. I estimate 2-3 hours of your time, and I'm able to "pay" for your participation with CentOS swag - see https://photos.app.goo.gl/a9GqLnm1WUUJebU17 - and my undying appreciation. :) Please contact me off-list if you're willing to do this, and you feel competent to evaluate the quality of submission abstracts. It is not required that you'll be attending the event to participate. You're also welcome if you're one of the people who have submitted a presentation. Thanks. -- Rich Bowen - rbowen(a)redhat.com @CentOSProject // @rbowen 859 351 9166

1 0

Fwd: FOSDEM 2019 - Distributions Devroom Call for Participation
by Rich Bowen 01 Nov '18

01 Nov '18

The Distributions devroom will take place Sunday 3 February 2019 at FOSDEM, in Brussels, Belgium at the Université Libre de Bruxelles. As more and more workloads are being considered for containerization in the future and are finally landing in virtualized environments today, distributions remain a critical success factor and are more important than ever. Containers, like virtual machines, are not magical and rely on piles of software being assembled in a way that is repeatable, reliable, and functional. This is at the very heart of the problem that distributions have always solved. Each distribution is responsible for building, testing, and releasing software as well as managing the lifecycle of each application in the collection. Additionally, distributions do very important work in ensuring that various versions of upstream software work well together and can co-exist. Distributions are also, often responsible, for "de-vendoring" upstream software so that security fixes can be applied more quickly. We welcome submissions targeted at contributors interested in issues unique to distributions, especially in the following topics: # Topics and Areas of Focus ## Focus Areas - The ways that distribution technologies can be leveraged to allow for easier creation of a multi-verse of artifacts from single source trees. This includes the increasing move toward self-contained applications and providing multiple non-parallel installed versions of software. - Efforts being made in shared environments around Build/Test/Release cycles. - Topics related to the delivery problem as it impacts updates in terms of both size and rollback/reliability are expected to be featured. ## Additional Topic Ideas - Distribution and Community collaborations, eg: how does code flow from developers to end users across communities, ensuring trust and code audibility - Automating building software for redistribution to minimize human involvement, eg: bots that branch and build software, bots that participate as team members extending human involvement - Cross-distribution collaboration on common issues, eg: content distribution, infrastructure, and documentation - Growing distribution communities, eg: onboarding new users, helping new contributors learn community values and technology, increasing contributor technical skills, recognizing and rewarding contribution - Principals of Rolling Releases, Long Term Supported Releases (LTS), Feature gated releases, and calendar releases - Distribution construction, installation, deployment, packaging and content management - Balancing new code and active upstreams verus security updates, back porting and minimization of user breaking changes - Delivering architecture independent software universally across architectures within the confines of distribution systems - Effectively communicating the difference in experience across architectures for developers, packagers, and users - Working with vendors and including them in the community - The future of distributions, emerging trends and evolving user demands from the idea of a platform Ideal submissions are actionable and opinionated. Submissions may be in the form of 25 or 50 minute talks, panel sessions, round-table discussions, or Birds of a Feather (BoF) sessions. Dates ------ Submission Deadline: 02-Dec-2018 @ 2359 GMT Acceptance Notification: 7-Dec-2018 Final Schedule Posted: 14-Dec-2018 How to submit -------------- Visit https://penta.fosdem.org/submission/FOSDEM19 1.) If you do not have an account, create one here 2.) Click 'Create Event' 3.) Enter your presentation details 4.) Be sure to select the Distributions Devroom track! 5.) Submit What to include --------------- - The title of your submission - A 1-paragraph Abstract - A longer description including the benefit of your talk to your target audience, including a definition of your target audience. - Approximate length / type of submission (talk, BoF, ...) - Links to related websites/blogs/talk material (if any) Administrative Notes ---------------- We will be live-streaming and recording the Distributions Devroom. Presenting at FOSDEM implies permission to record your session and distribute the recording afterwards. All videos will be made available under the standard FOSDEM content license (CC-BY). If you have any questions, feel free to contact the devroom organizers: distributions-devroom(a)lists.fosdem.org (https://lists.fosdem.org/listinfo/distributions-devroom)

1 0

python-jwt in RHEL's addons and CentOS
by Ken Dreyer 01 Nov '18

01 Nov '18

Red Hat recently shipped python-jwt in http://access.redhat.com/errata/RHEA-2018:1032 This went into the "High Availability" and "Resilient Storage" add-ons of RHEL, not the usual RHEL Base/Optional/Extras. I was wondering why CentOS has this package in its base repositories now. Does CentOS 7 include RHEL's HA addon or the Resilient Storage addon? - Ken

3 2

Re: [CentOS-devel] [CentOS-docs] Authorization to use CentOS logo in GNOME Boxes
by Karsten Wade 01 Nov '18

01 Nov '18

On 09/19/2018 03:35 AM, Pablo Sebastián Greco wrote: > From someone who doesn't know anything about design/legal, what is the > difference between this instance and what was done in point 7.3 of the > link (7.3. For special sub-projects)? Essentially similar, in that specific permission was granted and a specific logo was prepared. In this case, the permission has been requested and there is not a corresponding logo prepared on the ArtWork page. > BTW, that is the logo only; There are two aspects here: 1. Should the project allow for the graphical logo to be used without the wordmark? 2. If yes to 1, the project should adjust one or both guidelines to make it explicit what can and cannot be done. For #1 it may be that we want to do so for various cases, but there may be reasons and risks we are not aware of in using the logo stand-alone in various situations. For this I am seeking expert advice. As it happens, the trademark guidelines do allow for some uses of just the logo, point 5 here: https://www.centos.org/legal/trademarks/#acceptable-uses But there is not a corresponding graphic and how-to on the ArtWork page. What I want to do is i) as quickly as we can resolve the question of permission for GNOME so they can move on with their development, and ii) fix any actual or perceived inconsistencies between the trademark guidelines and the logo usage guidelines. Best regards, - Karsten -- Karsten Wade | Community Architect | @quaid Red Hat Open Source and Standards (OSAS) : @redhatopen https://community.redhat.com | https://next.redhat.com | https://osci.io gpg: AD0E0C41 | https://red.ht/sig

3 4

[CentOS PaaS SIG]: Origin v3.11 rpms available for testing
by Daniel Comnea 31 Oct '18

31 Oct '18

Hi, We would like to announce that OKD v3.11 rpms are available for testing at [1]. As such we are calling for help from community to start testing and let us know if there are issues with the rpms and its dependencies. And in the spirit of transparency see below the plan to promote the rpms to mirror.centos.org repo: 1. in the next few days the packages should be promoted to the test repo [2] (currently it does not exist, we are waiting to be sync'ed in the background) 2. in one/two weeks time if we haven't heard any issues/ blockers we are going to promote to [3] repo (currently it doesn't exist, it will once the rpm will be promoted and signed) Please note the ansbile version use (and supported) *must be* 2.6.x and not 2.7, if you opt to ignore the warning you will run into issues. On a different note the CentOS Infra team are working hard (thanks !) to package and release a centos-ansible rpm which we'll promote in our PaaS repos. The rational is to bring more control around the ansible version used/ required by OpenShift-ansible installer and not rely on the latest ansbile version pushed to epel repo we caused friction recently (reflected on our CI as well as users reporting issues) Thank you, PaaS SiG team [1] https://cbs.centos.org/repos/paas7-openshift-origin311-testing/ [2] https://buildlogs.centos.org/centos/7/paas/x86_64/openshift-origin311/ [3] http://mirror.centos.org/centos/7/paas/x86_64/openshift-origin311/

6 10

What is the preferred approach to get golang >= 1.9.4 in buildroots in the CBS?
by Niels de Vos 31 Oct '18

31 Oct '18

Hi, It seems that the golang version (1.8) in the CentOS build (base?) repository is not recent enough to build one of the Gluster components. GlusterD2-5.0 needs golang >= 1.9.4. There is a build of golang-1.10.2-1.el7 in the CBS, but that is only for x86_64, and I would need a version that has ppc64le and aarch64 as well. Early on, golang was included in CentOS Extras, is that a possible location to keep a more recent version? Thanks, Niels

2 3

RSB filling is enabled for CentOS 7 Kernel?
by Veetil, Vyshnav 30 Oct '18

30 Oct '18

Hi All, We ran the spectre meltdown checker tool provided by: https://github.com/speed47/spectre-meltdown-checker. And it says that we are still vulnerable to variant #2 since RSB filling is not enabled in our kernel When we googled, the following bugzilla from RH suggests that it is enabled by default: https://bugzilla.redhat.com/show_bug.cg ... 2018-15572 When I was checking the source code of the latest CentOS kernel ,i don't see this feature flag set anywhere - X86_FEATURE_RSB_CTXSW. Could you please tell us ,If the Latest CentOS kernel supports RSB filling or not ?! Regards, Vyshnav

2 1

multistage booting and grubby
by Element, Paul-Emile 30 Oct '18

30 Oct '18

Hi, We are working with a system configure to boot using tboot Using grub2 and multiboot2, we have grub2 booting tboot and then booting centos. Grub2 fully supports this scenario and it works fine. The problem we have is that some centos packages use grubby to modify the boot configuration / boot parameters. Grubby does not appear to have any support for this, and so all invocations of grubby end up doing nothing and fail silently. Question is, would you know if there is any plan to add support for multiboot2 in an upcoming version of grubby? Thanks, Paul-Emile

1 0

Upcoming changes to git.centos.org are now in staging
by Jim Perrin 26 Oct '18

26 Oct '18

In August, the CentOS Project and Fedora announced the intention to combine their dist-git sources, and since then Fabian Arrotin of CentOS and Patrick Uiterwijk of Fedora have worked to make that happen. Last week at the CERN dojo, they demonstrated this work, and today we’d like to welcome community testing of it. We’ll be keeping this content updated, so you'll be able to continue to track sources appropriately. You can help us by testing the new system, providing feedback, and contributing additional tooling to help improve the overall state of the project. Structure: Currently git.stg.centos.org and src.stg.fedoraproject.org are linked via RepoSpanner[1], and sharing common repositories. Packagers for the roughly 6700 common packages in both communities will see the additional branches.. For the Fedora community, there should be no changes required for the day to day operation of dist-git or packaging. CentOS community members will note that the platform change to pagure brings a variety of new features, including a new API[2] , a new UI, pull requests, and issue tracking. The current tooling for CentOS sources will continue to work (after updating to the staging server) and we plan to add support for tooling for centpkg, which would mirror the functionality found in fedpkg. In the coming weeks we'll be putting out documentation around the expected uses for pull requests, and the issue tracking features within pagure, as we don't intend it to replace bugs.centos.org. Permissions and ownership: There are protections enabled to prevent either community from accidentally overwriting code from the other, so only CentOS community members will be able to push to c#-* branches, while only Fedora community members can push to f#*/epel#* branches. With the new dynamic ACL validation in place, CentOS SIG members will automatically get the rights to push on their specific branches. While the repositories and content are shared between the communities, authentication is not. To push to c# branches, you will have to authenticate against accounts.centos.org. Similarly Fedora community members will continue to authenticate against accounts.fedoraproject.org. 1. https://github.com/repoSpanner/repoSpanner 2. https://git.stg.centos.org/api/0/ -- Jim Perrin The CentOS Project | http://www.centos.org twitter: @BitIntegrity | GPG Key: FA09AD77

5 9

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