-
-
Notifications
You must be signed in to change notification settings - Fork 7.7k
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
Debian build is broken #8141
Comments
I will have a look at it (I esp. appreciate the example repo). The only related change in 0.80 was a upgrade from Esbuild 0.8.15 to 0.8.17. I do have some (I think) pretty good tests in this area (also a manual repo), so I'm a little surprised. A side not is that I tried to pull in the lates ESBuild (he works fast), and that broke my test repo. |
I cannot reproduce your issue (on MacOS, but I don't see how that can differ) -- the error you get looks like the error I get when I pull in the latest esbuild. |
@raoulb,
It's interesting to me that your version string is different from mine. I downloaded the tar.gz extended releases from GH. Where are you getting your hugo binaries? Can you try the ones in the tar.gz on GH? |
OK, then I guess that the version @raoulb is built without the versioning of Go Modules. Which I hope means that he built it himself? |
I use the official packages from Debian |
Cc: @anthonyfok |
Oh, interesting and kind of good news.
Ok. I tried the both versions for the
and
Now I could try the |
Oh, good point. Maybe the Debian package builds against an own, 'external' version of ESBuild. At least this is what I see here with the build time dependency:
if I'm reading this correctly. |
Ok, the package |
We've pinned esbuild at v0.8.17, but the esbuild package from Debian is v0.8.28. |
Tested the latest esbuild and can confirm that it fails to build your test site with the error message in the OP: |
Last update 😄 The test site in the OP starts failing with esbuild v0.8.21. If I change the import path to |
@moorereason this issue is not about ESBuild (which is a known issue -- we had a buildbot PR that luckily failed in test some weeks ago). This is about the broken Debian build. |
Dear all, @raoulb, Thank you for reporting the issue, especially timely because Debian 11 (bullseye) will go into freezing soon, and it is good that you let us know of the issue now instead of later. @bep and @moorereason, thank you both for your excellent investigative work. Indeed, it was my laziness and oversight when updating Debian's copy of esbuild to a too-new version that led to this issue. Now that @moorereason has found out which version of esbuild (v0.8.21) has the behaviour change, I can start looking into a fix for my Debian build later today. Thank you @moorereason for saving me a lot of time. |
@anthonyfok are you somehow running with different versions of the dependencies in the Debian build (I assume because they're shared by others?)? Do the tests pass? |
Hi @bep, sorry for the late reply.
Yes. I had stupidly upgraded golang-github-evanw-esbuild from 0.8.15-1 to 0.8.28-1. Usually, I follow the versions listed in Hugo's go.mod quite strictly, but this last time, I was not able to upgrade to 0.8.17 directly with the usual command because there had been too many newer esbuild releases that 0.8.17 got pushed from https://github.com/evanw/esbuild/releases to the "Next" page, and the pattern matching in debian/watch file did not work. There are ways around that, but I either forgot how or got too lazy, and decided to just go ahead and package 0.8.28, and that's how I got the Debian package into trouble.
At the moment, golang-github-evanw-esbuild-dev is not used by other packages. Hugo is currently the only Debian package that depends on it.
Yes, they do, but the Debian build isn't running all the tests, but
See https://buildd.debian.org/status/fetch.php?pkg=hugo&arch=amd64&ver=0.80.0-1&stamp=1609753546&raw=0 for the full build (and test) log. I have decided to fix the bug by including a local copy of esbuild 0.8.17 into the Hugo Debian package for the time being. The fix will appear in hugo_0.80.0-2 soon. |
Any plans on making it work with the latest ESBuild? |
Hello @raoulb and all: Here is an update:
hugo (0.80.0-3) unstable; urgency=medium
-- Anthony Fok foka@debian.org Wed, 27 Jan 2021 06:21:10 -0700 hugo (0.80.0-2) unstable; urgency=medium
-- Anthony Fok foka@debian.org Sat, 16 Jan 2021 04:28:36 -0700 @raoulb, thank you again for reporting this issue. I believe the issue is resolved in the Debian package hugo_0.80.0-2, and made a bit more futureproof in 0.80.0-3, hence I'm closing this issue. |
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. |
What version of Hugo are you using (
hugo version
)?Does this issue reproduce with the latest release?
Yes.
Issues
Javascript building/bundling fails with sources and dependencies all in
assets/js
. Here is a minimal example I constructed based on the test project linked in the Hugo documentation.With Hugo 0.80.0 the build fails:
While with Hugo 0.79.1 it works as expected:
If this is not a regression but intended new behaviour, then the documentation might need further clarification.
BTW: Calling
esbuild
manually works on the same sources:The text was updated successfully, but these errors were encountered: