devel

devel@lists.centos.org

17 participants
4590 discussions

Sphinx - Warnings treated as errors
by Neale Ferguson 24 Jan '20

24 Jan '20

Hi, I am attempting to python-oslo-reports-1.30.0-1.el7 but Sphinx 1.8.4 is treating warnings as errors and terminating the build: DEBUG: Warning, treated as error: DEBUG: /builddir/build/BUILD/oslo.reports-1.30.0/oslo_reports/generators/conf.py:docstring of oslo_reports.generators.conf.ConfigReportGenerator:1:duplicate object description of oslo_reports.generators.conf.ConfigReportGenerator, other instance in /builddir/build/BUILD/oslo.reports-1.30.0/doc/source/reference/api/oslo_reports.generators.rst, use :noindex: for one of them I note from the CentOS build logs Sphinx is encountering the warnings but they are not being treated as errors. How is this behavior being changed? Neale Ferguson

2 6

Git Forge Requirements: Please see the CentOS blog - https://blog.centos.org/2020/01/git-forge-requirements-odf/
by Jim Perrin 23 Jan '20

23 Jan '20

Hi Everyone, This email has me wearing multiple hats, both as a member of the CentOS Project, and as a manager within RH's Community Platform Engineering team. For those of you who may not be know, CPE is the team inside RH responsible for CentOS and Fedora infra and engineering and is home to many of the Project folks you may be used to working with such as Fabian, Johnny, and Brian. On behalf of the CPE team I want to draw the communities attention to a recent blog post[1] which may impact you. The TL;DR is we're attempting to determine if our needs are best served by one of 3 solutions (in no particular order): * Pagure * Gitlab * Github We will be seeking input and requirements in an open and transparent manner on the future of a git forge solution which will be run by the CPE team on behalf of the CentOS community. A similar message was sent to Fedora's devel list[2] as both projects use Pagure so this message may be duplicated if you participate in both communities. If you have specific features, use cases or workflows you'd like us to consider, please call them out to make sure they're heard. Rich Bowen and I will be gathering these to bring to the CentOS Board as a stakeholder as described in the blog post. 1. https://blog.centos.org/2020/01/git-forge-requirements-odf/ 2. https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org… Thanks! -- Jim Perrin The CentOS Project | http://www.centos.org twitter: @BitIntegrity | GPG Key: FA09AD77

2 2

CentOS 8 Stream: updated rpm, dnf, and systemd
by Carl George 22 Jan '20

22 Jan '20

Howdy everyone, The CentOS team is pleased to announce that we have updated the rpm, dnf, and systemd packages in CentOS 8 Stream. These updates have already been published and are propagating out to the mirror network now. We're hoping to get developer feedback on these packages to help demonstrate the value of Stream and identify any potential issues before they make their way into RHEL and regular CentOS. We've listed notable features from these updates below. Enjoy! ## rpm-4.14.2-36.el8 * Enable zstd support * https://bugzilla.redhat.com/show_bug.cgi?id=1715799 ## dnf-4.2.17-3.el8 * Support for variables in repo IDs * https://bugzilla.redhat.com/show_bug.cgi?id=1748841 * https://github.com/rpm-software-management/dnf/pull/1537 * Versionlock plugin now works with check-update command and dnf-automatic * https://bugzilla.redhat.com/show_bug.cgi?id=1750620 * https://github.com/rpm-software-management/dnf/pull/1530 * https://github.com/rpm-software-management/dnf-plugins-core/pull/370 * https://bugzilla.redhat.com/show_bug.cgi?id=1746562 * https://github.com/rpm-software-management/dnf/pull/1477 * Used a fixed time of day for dnf-automatic timers * https://bugzilla.redhat.com/show_bug.cgi?id=1754609 * https://github.com/rpm-software-management/dnf/pull/1521 * Add module repoquery command * https://github.com/rpm-software-management/dnf/pull/1536 * Do not load metadata for repolist command * https://bugzilla.redhat.com/show_bug.cgi?id=1728894 * https://github.com/rpm-software-management/dnf/pull/1423 * Add --ids option to the group command * https://bugzilla.redhat.com/show_bug.cgi?id=1706382 * https://github.com/rpm-software-management/dnf/pull/1513 * Show transaction errors inside dnf shell * https://bugzilla.redhat.com/show_bug.cgi?id=1743644 * https://github.com/rpm-software-management/dnf/pull/1468 * Add new modular API method ModuleBase.get_modules * https://github.com/rpm-software-management/dnf/commit/ba2320a ## systemd-239-21.el8 * Allow user names with dots to be used in unit files * https://bugzilla.redhat.com/show_bug.cgi?id=1717603 * https://github.com/systemd/systemd/issues/12754 * Prevent failed reload command from killing main process * https://bugzilla.redhat.com/show_bug.cgi?id=1735787 * https://github.com/systemd/systemd/issues/11238 * Treat smb3 as a remote filesystem to prevent boot failures * https://github.com/systemd/systemd/pull/13686 * Add udev support for FIDO (U2F) keys * https://bugzilla.redhat.com/show_bug.cgi?id=1753369 * https://github.com/systemd/systemd/issues/11996 P.S. We won't always announce updated Stream packages like this, but we wanted to highlight some of the early successes as we figure out the Stream workflow. -- Carl George

3 2

Re: [CentOS-devel] Git Forge Requirements: Please see the CentOS blog - https://blog.centos.org/2020/01/git-forge-requirements-odf/
by Patrick Laimbock 22 Jan '20

22 Jan '20

Hi Jim, -----Original message----- [snip] > The TL;DR is we're attempting to determine if our needs are best served > by one of 3 solutions (in no particular order): > > * Pagure > * Gitlab > * Github As both the CentOS & Fedora Communities revolve around code that is open source, I'd like to see that extended to the Git Forge tool too so welcome Pagure or Gitlab or any other open source Git Forge tool (Gitea?). Best, Patrick

1 0

CentOS 8 license / EULA URL?
by Jan Pazdziora 21 Jan '20

21 Jan '20

Hello, I'm attempting to create a SWID tag for CentOS Linux. In Fedora's SWID tag https://src.fedoraproject.org/rpms/fedora-release/blob/master/f/distro-temp… we are able to reference https://fedoraproject.org/wiki/Legal:Licenses/LicenseAgreement as the URL of the license for the distribution. What is the similar URL for CentOS 8? For CentOS 7 I've found http://mirror.centos.org/centos/7/os/x86_64/EULA but I don't see anything similar under http://mirror.centos.org/centos/8/. Based on https://linoxide.com/wp-content/uploads/2019/09/31-centos8-licence-agreemen… it seems like CentOS 8 uses the same wording but having stable URL to reference would be nice. Thank you, -- Jan Pazdziora Senior Principal Software Engineer, Security Engineering, Red Hat

2 2

CentOS Stream -- centos-release
by Jan Pazdziora 21 Jan '20

21 Jan '20

Hello, what is the mechanism of contributing change to CentOS Stream but not necessarily to CentOS? In RHEL, redhat-release package ships SWID tag(s) for the distribution. Looking at http://mirror.centos.org/centos/8-stream/BaseOS/x86_64/os/Packages/ redhat-release rpm is not included there but centos-release is, the same as in CentOS. What is the mechanism of submit pull request for centos-release which will end up in CentOS Stream? -- Jan Pazdziora Senior Principal Software Engineer, Security Engineering, Red Hat

3 3

Out of the box USB wireless NIC?
by Jeffrey Layton 20 Jan '20

20 Jan '20

Good afternoon, I'm installing CentOS 8.1 on a new box (thank you for the new version!). I have an Alfa AWUS036ACH USB wireless NIC that has good specs. Unfortunately, you have to build the driver for your kernel and I'm all sorts of trouble getting this done. What is a good, but simple USB Wireless adapter that CentOS 8.1 will pick up and I don't have to build any kernel modules? Thanks! Jeff

1 0

2020-01-21 cbs.centos.org infrastructure upgrade.
by Thomas Oulevey 20 Jan '20

20 Jan '20

Dear All, Please note that tomorrow morning cbs.centos.org will be upgraded to support newer features and allow us to finally create C8 buildroots. An email will follow-up next week with the instruction to create C8 targets after we finish the test with selected SIGs. * What does that mean for you ? We'll upgrade koji and tools to 1.19 version. You can convert to local time with $(date -d '2019-01-21 7:00 UTC') * What will be the impact ? Koji build service will be down for 1 hour. 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. Sorry for the short notice. -- Thomas Oulevey on behalf of the infrastructure team.

1 0

sign push is down
by Karanbir Singh 20 Jan '20

20 Jan '20

hi there were hardware issues that required emergency changes in the content release pipelines, one artifact of that is the sign push for sig content is down till that is changed to match some of the new paths. I'll aim at getting that fixed in the next day or so - in the mean time, if someone has time based release work going through let me know ( ideally on irc in #centos-devel ) and we can do something manual if needed. regards,

3 5

Re: [CentOS-devel] Minutes for CentOS Board of Directors 2019-12-18 Meeting
by Giulio 20 Jan '20

20 Jan '20

>2. Project strategic goals: 1. AGREED: Undergo a revision of the project goals, to include a range of topics from > technical to social/cultural. Do this work transparently, reaching out to > specific community members and stakeholders such as RHEL Engineering. The only current reference to "goals" on centos.org that I can find is in the about page: "...The CentOS Project is a community-driven free software effort focused around the goal of providing a rich base platform for open source communities to build upon...." Can you clarify what you mean by "range of topics from technical to social/cultural"? Maybe using some examples? I don't remember reading anything on the centos lists about anyone suggesting to refresh the goals; is it possible to know who decided that there was a need to refresh the goals: a) Red Hat, b) Karsten Wade, c) others (who)? To me "transparently" means posting publicly about this on the centos-users list. Reaching out to specific members and RHEL engineering is the complete opposite of "transparently". OTOH, I understand Red Hat owns CentOS, so you have the right to do whatever you want with it, but please, just be open and say "Red Hat decided this". Please, don't do what corporations usually do, when they first decide what is useful to them, and then they try to put it like they are doing it for the users. Thanks

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