Closed miabbott closed 9 months ago
We can't control what is in the symlink beforehand. I mean, I guess it's usually the correct thing, but would it be safer to just override it always?
We can't control what is in the symlink beforehand. I mean, I guess it's usually the correct thing, but would it be safer to just override it always?
Sure, I'll modify the patch to copy any old version to <file>.old
and create the new symlink.
Sure, I'll modify the patch to copy any old version to
<file>.old
and create the new symlink.
Eh, it doesn't make sense to copy an old version of the symlink...I'll just force create it
I switched my custom ublue image from using "ublue-os/silverblue-nvidia" to "ublue-os/bazzite-gnome-nvidia" and received the following error when the build action kicked off:
ln: failed to create symbolic link '/usr/etc/profile.d/ublue-firstboot.sh': File exists
The yafti module should be the only thing creating this symlink, so it should be safe to use the
-f
flag to force creating it.