Hi,
It seems that the selinux-policy rpm is built from
git@gitlab.cee.redhat.com:SELinux/selinux-policy.git which seems to be
a redhat internal repository. More specifically, if I try to checkout
the commit listed in the selinux-policy spec
(https://gitlab.com/redhat/centos-stream/rpms/selinux-policy/-/blob/c9s/seli…)
in the fedora-selinux repository cloned from github, I get an error
saying that the commit does not exist. It would be great if the
repository containing this commit was publicly available and open for
external contributors just like all the other packages in CentOS
Stream. Is it possible to make this happen?
Cheers,
Daan De Meyer
Hi Everyone,
Our next board meeting will take place at 20:00 UTC on Wednesday:
`date -d "2023-07-12 20:00 UTC"`
If you would like to attend please send me an email to
alphacc(a)centosproject.org ( please do not reply to @centos-devel or use
another email address) and you will receive a link to a Zoom meeting
room with a passcode, 1 hour before the meeting takes place.
The agenda can be checked at (work in progress) :
https://hackmd.io/@centosboard/HyP-UuFt2
As a reminder we will enforce few rules :
* Wait to be recognized by the Chair before speaking
* Respect the Chair when told your time to speak is over - this will
allow us to remain on agenda, and complete the meetings in the
allotted time
* In the event that there are Board-confidential topics, these will be
put at the end of the meeting, in Executive Session, and guests will be
asked to leave. We hope to minimize these items, but they do sometimes
happen. The most common scenarios in which this may happen are personnel
issues, or information that Red Hat wishes to share with the Board, but
is not yet public.
* Muting of participants, or, in extreme situations, ejection from the
meeting, is at the sole discretion of the Chair.
* Meetings will be recorded, and published to YouTube (possibly with
edits/redaction, as approved by the Directors). Thus, by joining the
meeting you consent to have your presence at the meeting, and anything
you say during the meeting, made public.
I hope some of you can join.
Sorry for the late announcement.
thanks,
--
Thomas 'alphacc' Oulevey
CentOS Board of Directors Secretary
alphacc(a)centosproject.org
Hi All,
I've been trying to reproduce the centos tests locally. Thank to
Aleksandra and arrfab for the help on IRC to understand the whole
process conceptually.
I successfully ran https://github.com/CentOS/sig-core-t_functional on a
clean centos stream 9 vm. The tests passed.
I'm running into issues trying to run individual playbooks against a
clean centos stream 9 vm from the zuul-jobs and jobs repositories from
here: https://gitlab.com/redhat/centos-stream/ci-cd/zuul
The errors I find are mainly related to dependencies, e.g., missing
users, or packages, which makes me think there are steps I need to do
before.
Is there any documentation for contributors about the zuul CI tests, to
be able to test individual playbooks locally? If there is none, I could
contribute with some in a Readme.md, but I would still need some basic
guidance to get at least some of them working locally. Any help is
appreciated.
Regards,
Carlos.
We met for the first time today.
Florian briefly summarized the status of the CentOS 9 Stream rebuilds
with x86-64-v2 and x86-64-v3. For details, please see:
[CentOS-devel] ISA SIG rebuild status
<https://lists.centos.org/pipermail/centos-devel/2023-June/143007.html>
Since then, Troy has added consumption documentation describing how to
consume the builds:
Convert CentOS Stream 9 to ISA
<https://sigs.centos.org/isa/consuming/centosstream9/#convert-centos-stream-…>
Currently, there are no plans to keep the package set up-to-date with
regards to CentOS 9 Stream.
Troy plans to create centos-release-isa package which, upon
installation, creates the unusual repository configuration. This will
be an explicit download, not part of CentOS Extras, out of concern that
people might try to install it accidentally otherwise.
Ali raised the matter of zlib-ng (see the previous mailing list thread).
Florian thinks that zlib-ng in compat mode is something to explore.
This work should happen in Fedora first, targeting Fedora 40. Florian
to send email to relevant parties.
Troy and Florian are going to explore creating two container images for
each rebuild variant, so that people have a more familiar starting
point for some quick experiments.
We plan to reconvene on July 21st, at 16:00 UTC (date and time still
tentative; it's the alternate slot for the bi-weekly Fedora ELN
meeting). Please drop me a line if you want to be added to the meeting
invitation. Update of the CentOS calendar is still pending:
<https://github.com/CentOS/Calendar/pull/62> (We will likely keep using
Google Meet instead of IRC, though.)
Thanks,
Florian
Hi.
During an installation, I saw that almost all ceph packages for ceph pacific are in the last version, v16.2.13 except for cephadm. The last version is v16.2.7.
Is any reason for that? Or is it just a mistake?
Thanks
Luis Domingues
Proton AG
Hi,
is it possible to have a build from https://kojihub.stream.centos.org/koji/
having subpackages that are not going to be shipped in main CentOS Stream
repos being somehow filtered to ship those subpackages into a SIG repo?
I'm asking specifically about qemu-kvm sub packages we'd like to have in
CentOS AutoSD SIG but that are not going to be shipped in main CentOS
Stream repos as not relevant/supported in RHEL (qemu-kvm-ui-dbus, BZ#
*2207940* <https://bugzilla.redhat.com/show_bug.cgi?id=2207940>).
I would like to avoid having to rebuild the same qemu-kvm build within the
SIG each time a new release lands in CentOS Stream just to get a subpackage.
Is this possible?
Thanks,
--
Sandro Bonazzola
MANAGER, SOFTWARE ENGINEERING - Red Hat In-Vehicle Operating System
Red Hat EMEA <https://www.redhat.com/>
sbonazzo(a)redhat.com
<https://www.redhat.com/>
*Red Hat respects your work life balance. Therefore there is no need to
answer this email out of your office hours.*
Hi Fabian Arrotin,
I submitted a PR with a set of tests for libbpf-tools:
https://github.com/CentOS/sig-core-t_functional/pull/88
The PR is failing because the python package duffy does not work with
pydantic >= 2.0. I provided a commit in my PR that fixes that issue by
pinpointing the version to the latest pydantic 1.x version (1.10.10 from
2023-06-30). That commit may need to be cherry picked first to then see
if my PR passes the checks.
Thank you,
Carlos.