This reverts commit 57e13a1b8970c2e15d0c310aa871e4737781a23f. I noticed that systemd-logind was causing problems in our containers after a container rebuild of the f32 base image was published about 5 days ago. I found that an issue[0] had been filed about the problem, but that bug was reported against Rawhide (f33). I then found that systemd had been removed from the f32 base image after f32 was released. This causes problems for users who expect stability out of Fedora releases - changing the default package set means that a container build that works one day can break the next. In our case, the problem wasn't so much that systemd was removed, but that the unit masks were removed. This causes some components of systemd to be unable to function in a container, and puts a burden on users to identify the problem. https://pagure.io/releng/issue/9603 [0] https://bugzilla.redhat.com/show_bug.cgi?id=1841139
…
…
…
…
…
…
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.
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
bug reports
Bugs should be reported to the spin-kickstarts bugzilla component:
https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&component=spin-kickstarts
Description
Languages
Python
58.3%
JavaScript
33%
Makefile
8.7%