Table of Contents
Returned Hugo’s theme to PaperMod
I changed Hugo’s theme again.
[Created a custom theme](http://localhost:1313/posts/2025-4/#%e5%80%8b%e4%ba%ba%e9%96%8b%e7%99%ba%e3%81%ab%e3%81%a4%e3%81%84%e3%8 1%a6) However, I wanted to automatically collect contributions, so I decided to use atinux/my-pull-requests.
The created version will be imported from this and Github’s API, so there is no need to operate it here.
That’s why I no longer needed the contribution categories in hugo-Passage, so I changed the blog to only manage blogs, and for that I changed the theme back to the original hugo-PaperMod.
Hugo’s build is fragile
So, when I went back and built with netlify, it failed.
Is it common for the build to fail when changing the theme? So I tried revising the version of Hugo defined on netlify, but the build did not pass at all.
The cause is the build image, not the version.
When searching for other causes of the error,
hugo: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by hugo)hugo: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by hugo)hugo: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by hugo)hugo: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by hugo)A log was left.
This is because the version of GLIBC (Linux standard library) installed in Netlify’s build environment is older than the version required by the Hugo binaries you are using.
That seems to be the case.
Indeed, when I changed the build image from Ubuntu Focal 20.04 to Ubuntu Noble 24.04 (default), the build was successful.
I don’t get it
But if you do that, you won’t understand the meaning of your success up until now.
It doesn’t make sense, but according to ChatGPT,
Netlify has a mechanism to cache previously used Hugo executable files to speed up the build.
That’s what he said.
In other words, until now, they may have continued to use Hugo when they first succeeded.
I don’t know when it is, and I don’t know what version it is.
1:59:22 AM: Failed to fetch cache, continuing with buildHowever, when I look at the log, the previous Hugo
It was written that the binary cache could not be used.
So, the solution was to change Ubuntu Noble 24.04 (default) in the build image.
I’m a little confused, so if anyone can explain it clearly, please let me know.
The next time I decide to change my theme, I think I’ll quit Hugo.