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
Unsupported symlink found #6225
Comments
It's https://github.com/julian-klode/blog.jak-linux.org, the theme is included as a submodule https://github.com/julian-klode/ernest/tree/20d409d466cd1a150b6affdf2c6d3c6bead96a76 and it contains various symlinks in static/webfonts (to link to the fonts gotten via npm). These symlinks were resolved and then the real file put into the output as intended. |
We stopped supported symlinks from themes in a recent release. Mostly for security reasons, but we also added a powerful directory mount support that should be possible to replace those symlinks in a more portable and easier to reason about manner. You may want to ask further questions on https://discourse.gohugo.io/ |
@bep why don't give option, sometimes We known what we are doing. I just add symlinks to my static dir. ln -s $static/assets $ProjectRoot/assets |
This breaks the integration with some build systems that are relying on symlinks to sandbox the inputs (i.e. Bazel). This is not great :-( |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
I haven't built my blog in a while, but I'm getting a ton of failures now and can't proceed:
This used to work perfectly fine back in Jun 13.
The text was updated successfully, but these errors were encountered: