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

Filename change in Hugo 0.20.3 binaries #3385

Closed
bep opened this Issue Apr 24, 2017 · 3 comments

Comments

Projects
None yet
2 participants
@bep
Member

bep commented Apr 24, 2017

They are now prefixed with "v" ... and I did not notice it.

See goreleaser/goreleaser#210

@bep bep added the Bug label Apr 24, 2017

@bep bep changed the title from Filename change Hugo 0.23 binaries to Filename change in Hugo 0.23 binaries Apr 24, 2017

@bep bep self-assigned this Apr 24, 2017

@bep bep modified the milestones: v0.21, v0.20.4 Apr 24, 2017

@bep bep changed the title from Filename change in Hugo 0.23 binaries to Filename change in Hugo 0.20.3 binaries Apr 24, 2017

@bep bep closed this Apr 24, 2017

@ghost ghost referenced this issue Apr 25, 2017

Closed

spf13/hugo v0.20.4 released #5

@tombennet

This comment has been minimized.

Show comment
Hide comment
@tombennet

tombennet Apr 25, 2017

Contributor

Attempting to deploy 0.20.5 with Netlify throws an error due to the renamed binary, even with a cleared build cache - is this related to #3385? Apologies if not. Log below.

8:50:51 PM: Installing Hugo 0.20.5
8:50:53 PM: Cleaning up docker container
8:48:09 PM: Error running command: Build script returned non-zero exit code: 1
8:50:54 PM: Error running command: Build script returned non-zero exit code: 1
8:50:54 PM: Finished processing build request
8:50:53 PM: Error during Hugo 0.20.5 install: error renaming /opt/build/cache/.binrc/binaries/spf13/hugo/v0.20.5/binrc-302612769/hugo_0.20.5_linux_amd64/hugo_0.20.5_linux_amd64 to /opt/build/cache/.binrc/binaries/spf13/hugo/v0.20.5/hugo: rename /opt/build/cache/.binrc/binaries/spf13/hugo/v0.20.5/binrc-302612769/hugo_0.20.5_linux_amd64/hugo_0.20.5_linux_amd64 /opt/build/cache/.binrc/binaries/spf13/hugo/v0.20.5/hugo: no such file or directory

Contributor

tombennet commented Apr 25, 2017

Attempting to deploy 0.20.5 with Netlify throws an error due to the renamed binary, even with a cleared build cache - is this related to #3385? Apologies if not. Log below.

8:50:51 PM: Installing Hugo 0.20.5
8:50:53 PM: Cleaning up docker container
8:48:09 PM: Error running command: Build script returned non-zero exit code: 1
8:50:54 PM: Error running command: Build script returned non-zero exit code: 1
8:50:54 PM: Finished processing build request
8:50:53 PM: Error during Hugo 0.20.5 install: error renaming /opt/build/cache/.binrc/binaries/spf13/hugo/v0.20.5/binrc-302612769/hugo_0.20.5_linux_amd64/hugo_0.20.5_linux_amd64 to /opt/build/cache/.binrc/binaries/spf13/hugo/v0.20.5/hugo: rename /opt/build/cache/.binrc/binaries/spf13/hugo/v0.20.5/binrc-302612769/hugo_0.20.5_linux_amd64/hugo_0.20.5_linux_amd64 /opt/build/cache/.binrc/binaries/spf13/hugo/v0.20.5/hugo: no such file or directory

@bep

This comment has been minimized.

Show comment
Hide comment
@bep

bep Apr 25, 2017

Member

@tombennet I have notified Netlify about the change, but they haven't gotten to updating their script. I kind of did not think about this side effect, but we had to do this to get away from the unmaintained goxc as a build system. And it is much cleaner this way.

So from Hugo >= 0.20.3, the binary inside the archive is just named hugo (or hugo.exe on Windows.)

/cc @biilmann

Member

bep commented Apr 25, 2017

@tombennet I have notified Netlify about the change, but they haven't gotten to updating their script. I kind of did not think about this side effect, but we had to do this to get away from the unmaintained goxc as a build system. And it is much cleaner this way.

So from Hugo >= 0.20.3, the binary inside the archive is just named hugo (or hugo.exe on Windows.)

/cc @biilmann

@tombennet

This comment has been minimized.

Show comment
Hide comment
@tombennet

tombennet Apr 25, 2017

Contributor

Ok cool, makes sense. Thanks @bep @biilmann

Contributor

tombennet commented Apr 25, 2017

Ok cool, makes sense. Thanks @bep @biilmann

rrelmy added a commit to rrelmy/scoop that referenced this issue Apr 26, 2017

rrelmy added a commit to lukesampson/scoop that referenced this issue Apr 26, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment