-
Notifications
You must be signed in to change notification settings - Fork 358
Remove dependency on git #3684
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
pipx
git clone (selinux is disabled on boot already)
zppy
|
You are trying to build something that requires at least specific git version of mkosi, I think, systemd I assume, since that's probably the only project using this feature out there at this point, so you must run mkosi from a git checkout. Can you provide the debug output for the run from a git checkout with the SELinux problem? |
@eadwu mkosi does not have a required dependency on git, using mkosi from within the systemd repository does have a required dependency on git as long as we're using features that are not in a released version so that we can ensure the mkosi version is sufficiently new and can show a proper error if it isn't. Please run mkosi from git for now when using it in the systemd repository. Hopefully at some point in the future we won't have to rely on unreleased features in the systemd repo anymore and can drop the git requirement. As for the other selinux error, can you tell us a bit more about your setup? Specifically, the output of |
Got it, I see, error message confused me. mkosi commit 8235ddb
SELinux is disabled on boot with
It appears to work after |
This also fails with permission denied errors so let's skip it on zfs as well. Fixes systemd#3684
mkosi commit the issue has been seen with
mkosi 26~devel
Used host distribution
Fedora 41
Used target distribution
N/A
Linux kernel version used
6.13.9-200.fc41.x86_64
CPU architectures issue was seen on
x86_64
Unexpected behaviour you saw
Installed with README.md provided instructions
Used mkosi config
mkosi output
The text was updated successfully, but these errors were encountered: