54d53e8439
We're no longer using legacy network scripts to bring up networking. We're using NetworkManager and now in F33+ networkmanager will even default to writing out new configuration as NM keyfiles in /etc/NetworkManager/system-connections/. We don't need to lay down a networking config for eth0. Either cloud-init will do that for us or NetworkManager will default to DHCP anyway. We also don't need to populate /etc/hosts as that will get done on boot too with the same content we were writing there already.
fedora-kickstarts
This project is used to manage the Fedora kickstart files used in composing Fedora release images.
The master branch is used by rawhide and each release branch is used by that release.
All changes should be made via the PR workflow.
This project is packaged in Fedora as the spin-kickstarts package allowing users to see and modify the kickstart files for their local needs.
Maintainers for each image are listed in the maintainers.toml file.
To make a release
git clone ssh://git@pagure.io/fedora-kickstarts.git fedora-kickstarts
cd fedora-kickstarts
# If you need a specific branch other than master:
git checkout BRANCHNAME
# No tag has been added yet tag HEAD with
git tag VERSION
git push --tags
make
# Publish the released tar ball
make publish
# Clean up the generated files:
make clean
Build logs
To see build logs go to
https://koji.fedoraproject.org/koji
"Packages" tab, and filter by Fedora-Workstation-Live for example.
Technical info about the officialy released images can be found at
https://kojipkgs.fedoraproject.org/compose/
bug reports
Bugs should be reported to the spin-kickstarts bugzilla component:
https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&component=spin-kickstarts