Fedora-coreos-config build failure

If using:

cosa init --force --branch stable https://github.com/coreos/fedora-coreos-config

followed by:

cosa fetch --update-lockfile --with-cosa-overrides

Fetch will fail:

rpm-ostree version: 2025.7
No previous commit for fedora/x86_64/coreos/stable
Enabled rpm-md repositories: fedora-coreos-pool
Updating metadata for 'fedora-coreos-pool'...done
Importing rpm-md...done
rpm-md repo 'fedora-coreos-pool'; generated: 2025-04-09T21:14:38Z solvables: 71364
error: Installing packages: Packages not found: NetworkManager, NetworkManager-cloud-setup, NetworkManager-team, NetworkManager-tui, WALinuxAgent-udev, aardvark-dns, acl, adcli, afterburn, afterburn-dracut, amd-gpu-firmware, amd-ucode-firmware, attr, audit, azure-vm-utils, bash-color-prompt, bash-completion, bind-utils, bootc, bootupd, bsdtar, btrfs-progs, bzip2, catatonit, chrony, cifs-utils, clevis, clevis-dracut, clevis-luks, clevis-systemd, cloud-utils-growpart, console-login-helper-messages-issuegen, console-login-helper-messages-motdgen, console-login-helper-messages-profile, containerd, coreos-installer, coreos-installer-bootinfra, coreutils, criu, criu-libs, crun, crun-wasm, cryptsetup, curl, device-mapper-multipath, dnsmasq, dracut-network, e2fsprogs, efibootmgr, fedora-release-coreos, fedora-repos-archive, fedora-repos-ostree, file, fuse-overlayfs, fuse-sshfs, fwupd, git-core, gnupg2, google-compute-engine-guest-configs-udev, grub2, grub2-efi-x64, gzip, hostname, intel-gpu-firmware, ipcalc, iproute, iproute-tc, iptables, iptables-legacy, iptables-nft, iptables-services, irqbalance, iscsi-initiator-utils, jq, kbd, kdump-utils, kernel, kexec-tools, less, libsss_sudo, linux-firmware, logrotate, lsof, lvm2, makedumpfile, mdadm, microcode_ctl, moby-engine, nano, nano-default-editor, ncurses, net-tools, netavark, nfs-utils-coreos, nftables, nmstate, nss-altfiles, nvidia-gpu-firmware, nvme-cli, openssh-clients, openssh-server, openssl, passt, pciutils, podman, polkit, qed-firmware, rpm-ostree, rsync, runc, selinux-policy-targeted, sg3_utils, shadow-utils, shim, skopeo, slirp4netns, socat, ssh-key-dir, sssd-ad, sssd-client, sssd-ipa, sssd-krb5, sssd-ldap, stalld, sudo, systemd, systemd-container, systemd-resolved, tar, teamd, toolbox, tzdata, vim-minimal, wasmedge-rt, which, wireguard-tools, xfsprogs, xz, zram-generator, zstd
failed to execute cmd-fetch: exit status 1

Is there another step or something that needs to be done if using --branch stable for the config?

Thanks.

If you’re trying to update the lockfile you’d most likely be best served by trying to update and build the testing-devel branch instead of a production stream.

Ahh!

I understand I think.

–update-lockfile reaches out to gather the latest RPM versions, which is not the same sets of RPM versions as what’s in the stable branch lock files.

Thanks for the clarification.

1 Like