-
Notifications
You must be signed in to change notification settings - Fork 322
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
Improve absolute symlink handling #2536
Comments
Can you add a gist or so with the full logs when running with --debug? |
Do you have any mkosi scripts that are used with your configuration? I cannot reproduce this error locally with the information you've provided. I'm assuming that You can verify this by adding |
So I added It is a symlink: /boot -> /srv/boot. I verified in our postinstall script that we create this symlink since However, at |
@zjackwang Please realize that I lost a lot of time investigating this because you omitted this information. Next time you should add crucial information like this in your original report. To fix this, don't use absolute symlinks, use relative symlinks. |
mkdir
cannot create destination directory
So we should probably add a |
Apologies for the omitted information. Confirmed relative symlinks allowed the build to succeed. |
Getting this error as using the
Bootloader=systemd-boot
option attempts to install the UKI into /boot/EFI/Linux. Not sure what's going on since the python version is 3.10, and according to https://docs.python.org/3/library/pathlib.html#pathlib.Path.mkdir, the mkdir command in the code should behave likemkdir -p
.Here is my full config:
The build succeeds if I use
Bootloader=uki
as that installs the UKI to/efi/EFI/BOOT
, which was successfully created.The text was updated successfully, but these errors were encountered: