Skip to content
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

Check rasberry build #5101

Closed
bep opened this issue Aug 20, 2018 · 6 comments · Fixed by #5102
Closed

Check rasberry build #5101

bep opened this issue Aug 20, 2018 · 6 comments · Fixed by #5102

Comments

@bep
Copy link
Member

bep commented Aug 20, 2018

See https://discourse.gohugo.io/t/error-installing-47-on-raspbian/13663

dpkg: error processing archive ./hugo_0.47_Linux-ARM.deb (--install):
package architecture (armel) does not match system (armhf)

In Hugo 0.47 we updated Goreleaser to 0.79 (from something very old, but the config should be more or less the same, see: 2014834

Does the above ring any bells, @caarlos0 ?

@caarlos0
Copy link
Contributor

hm... maybe a bug on nfpm...

will take a look, sorry about the issue :/

@bep bep changed the title Check Check rasberry build Aug 20, 2018
@caarlos0
Copy link
Contributor

Yeah, I think the package was arm v6 (goreleaser default), so, on build, we just need to set goarm to 7.

@caarlos0
Copy link
Contributor

not sure why this is broken only now though... 6 has been the default since the start as far as I remember

@caarlos0
Copy link
Contributor

#5102 should fix it.

Is the idea to build for arm6 as well?

if so, we also need to change the name templates...

@caarlos0
Copy link
Contributor

caarlos0 commented Aug 20, 2018

not sure why this is broken only now though... 6 has been the default since the start as far as I remember

maybe GOARM was set as an external environment variable before? (if so, maybe this is a bug on goreleaser indeed - it shouldn't accept those external environment variables).

EDIT: or was a bug before at least

@github-actions
Copy link

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 27, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants