- automotive-sig - lists.centos.org

Repository request for autopack
by Mark Kemel 29 Apr '26

29 Apr '26

Hi everyone, I would like to move the autopack project (https://gitlab.com/mkemel/autopack) to the automotive-sig accounts. Autopack automates the release-to-CBS pipeline and is already used by automotive-image-builder and fusa-gcc-plugin. I would need the following repositories to be created: - https://gitlab.com/CentOS/automotive/src/autopack - https://quay.io/repository/centos-sig-automotive/autopack Currently, autopack uses GitLab project tokens to create releases and propose MRs to distgit repos. This works, but for scalability it would be better to either use a single group token for all projects under https://gitlab.com/CentOS/automotive, or have a bot user that can be given permissions to specific projects. Which approach would be preferred? For CBS builds, I currently use my personal CentOS certificate. It would be better to have a dedicated bot account with permissions to run CBS builds for automotive packages. What would be the process to set that up? Thanks, Mark

3 3

Repository request
by mengel＠redhat.com 29 Apr '26

29 Apr '26

Hi everyone, I would like to request a new repository to be created: https://gitlab.com/CentOS/automotive/src/selcraft This repository will host a project for generating selinux policies for automotive based on a configuration. I intend to move the contents of https://gitlab.com/mengel1/custom-qm-policy as soon as the repo is created. Regards, Michael Engel

3 3

New repository request: demos/bazel-demos
by Leonardo Rossetti 23 Mar '26

23 Mar '26

Hello, I would like to request a new repository: *https://gitlab.com/CentOS/automotive/demos/bazel-demos <https://gitlab.com/CentOS/automotive/demos/bazel-demos>* This repository will host sample code to demonstrate how to use Bazel with our tooling and operating system. Regards, -- Leonardo Rossetti Principal Software Engineer, Red Hat <https://www.redhat.com> lrossett(a)redhat.com <https://www.redhat.com>

2 1

CentOS Bringup issue for J784S4 EVM board.
by Sanskruti Baburao Kadam 10 Mar '26

10 Mar '26

Hi, We are experiencing issues while booting the J784S4 EVM board using prebuilt images. We have attached the detailed build procedure followed, along with the error logs observed during the boot process of the J784S4 board, for your reference. Please share the recommended procedure to create a bootable SD card using the prebuilt images. Thanks and regards, Sanskruti K.

2 1

Custom kernel build fails: rsync: Argument list too long
by Sebastian Hetze 02 Mar '26

02 Mar '26

Hi *, when trying to build the centos-stream-9 main-automotive kernel for the x86_64 architecture as described in the automotive sig documentation <https://sigs.centos.org/automotive/building/building_an_os_image_that%20use…>, it fails. The failing command appears to be /usr/bin/make -s 'HOSTCFLAGS=-O2 -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -march=x86-64-v2 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection' 'HOSTLDFLAGS=-Wl,-z,relro -Wl,--as-needed -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 ' -j12 ARCH=x86_64 V=1 'TARGETS=bpf cgroup mm livepatch net net/forwarding net/mptcp netfilter tc-testing memfd drivers/net/bonding iommu cachestat drivers/net' SKIP_TARGETS= FORCE_TARGETS=1 INSTALL_PATH=/home/she/rpmbuild/BUILDROOT/kernel-automotive-5.14.0-570.518_at.el9iv.x86_64/usr/libexec/kselftests VMLINUX_H= DEFAULT_INSTALL_HDR_PATH=0 install with the error make[3]: Entering directory '/home/she/Workspace/centos-stream-9/redhat/rpm/BUILD/kernel-5.14.0-570.518_at.el9iv/linux-5.14.0-570.518_at.el9iv.x86_64/tools/testing/selftests/bpf' Auto-detecting system features: ... llvm: [ OFF ] make[3]: rsync: Argument list too long make[3]: *** [Makefile:768: test_progs-no_alu32-extras] Error 127 make[3]: Leaving directory '/home/she/Workspace/centos-stream-9/redhat/rpm/BUILD/kernel-5.14.0-570.518_at.el9iv/linux-5.14.0-570.518_at.el9iv.x86_64/tools/testing/selftests/bpf' make[2]: *** [Makefile:233: install] Error 2 This is the unmodified main-automotive branch of the current centos-stream-9 kernel on a current centos-stream-9 system. Setting ulimit -S -s unlimited for ARG_MAX 6291456 does not make any difference. It looks like the actual problem is not with the rsync command line. Any hint what is going wrong and how to proceed? Beste Grüße Sebastian Hetze -- Principal Software Engineer Red Hat GmbH. Niederlassung Berlin Leipziger Platz 16, 10117 Berlin Mobil: +49 173 8914205 E-Mail: she(a)redhat.com Registered seat: Werner von Siemens Ring 14, D-85630 Grasbrunn, Germany Commercial register: Amtsgericht Muenchen/Munich, HRB 153243,Managing Directors: Ryan Barnhart, Charles Cachera, Michael O'Neill, Amy Ross

3 2

Changing commit access for the Automotive SIG
by Jeffrey Osier-Mixon 02 Mar '26

02 Mar '26

Hi folks - we are paring down the number of inactive accounts who have commit access to the SIG repos. If you haven't committed, sent email, or otherwise interacted with the SIG in the past 3 months, we will be decommissioning your permission. If you feel this is in error, please get in touch and we can fix it. thanks Jeffrey "Jefro" Osier-Mixon | josiermi(a)redhat.com Distinguished Community Architect Automotive, Edge, & Hardware Enablement Communities Red Hat Open Source & AI Program Office Book a meeting: https://calendar.app.google/sMBa7Xe8CLSEUdGV9

2 1

Enforcing 2FA to the CentOS/automotive namespace
by Pierre-Yves Chibon 25 Feb '26

25 Feb '26

Good Morning Everyone, I would like to raise the topic of enforcing 2FA on the entire CentOS/Automotive namespace on gitlab: https://gitlab.com/CentOS/automotive/ This is something I can do, but before I click the button I'd like to ask: is anyone opposed to this? If not, I'll switch the configuration next week. Thanks in advance for your thoughts! Pierre

5 5

New repository request
by mengel＠redhat.com 23 Feb '26

23 Feb '26

Hi everyone, I would like to request a new repository creation: https://gitlab.com/CentOS/automotive/src/sysboot This repository will host a package creating system boot checks based on systemd by using simple unit drop-ins. This will, later on, also be used in [automotive-image-builder](https://gitlab.com/CentOS/automotive/src/automoti…. Regards, Michael Engel Senior Software Engineer, Red Hat https://www.redhat.com mengel(a)redhat.com https://www.redhat.com

2 3

Building an AUTOSD Image for TDA4 EVM
by sanskruti.bk＠mistralsolutions.com 19 Feb '26

19 Feb '26

I am experiencing issues while building an AUTOSD image for TDA4 EVM Board. I have attached the detailed build procedure followed, along with the error logs observed during the build process of the TDA4 EVM board, for your reference. Please share the recommended procedure to create a bootable SD card using the AUTOSD image. Website followed - https://docs.centos.org/automotive-sig-documentation/provisioning/flashing-… OS - CentOS Stream 10 (On virtual machine manager) Commands used - [sk@localhost automotive-image-builder]$ sudo ./bin/aib-dev build-deprecated \ --container \ --target tda4vm_sk \ --mode package \ --export image \ examples/simple.aib.yml . Output - usage: aib-dev [-h] [--version] [--verbose] {build-deprecated,build,list-distro,list-targets,list-rpms,download} ... aib-dev: error: unrecognized arguments: tda4vm_sk --mode package --export image examples/simple.aib.yml .

3 7

CI failure notifications?
by Pierre-Yves Chibon 26 Jan '26

26 Jan '26

Good Morning Everyone, In the sig-docs [1] repository we have a CI job that runs daily and builds, runs and checks a number of images [2]. When those builds/runs/checks fail there is usually a good reason that we should go and check. Currently I believe I'm the only one being notified about those failure. As part of https://gitlab.com/CentOS/automotive/sig-docs/-/merge_requests/441 I'd like this list to be notified, but I don't want to do this without asking before. So what do you all think? Is anyone against this? If not, then I'll go ahead with the change and if it starts to be too annoying/noisy we can always revisit later :) Looking forward for your feedback :) Pierre

1 1

2026

2025

2024

2023

2022

2021

automotive-sig