-
-
Notifications
You must be signed in to change notification settings - Fork 49
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
Homebrew installation issues on mac m1 #151
Comments
Hey @LucasLombardo! This is a good catch, it's nice to know that removing Line 28 in fa474a4
Go added native m1 support in v1.16, so we should be able to add This could be the same issue @Valexr was experiencing in #141 |
So it looks like trying to build with plenti/.github/workflows/release.yml Line 22 in e1a6189
|
I just tried building with Error message
Right from the OSXCross README:
Right from our OSXCross-Target README we used I can rebuild with a newer SDK but it's a pain on Ubuntu 20 because of the newer version of |
@jimafisk Thanks for looking into it, I wouldn't be surprised if the other installation methods offered would have also worked so not necessarily a big deal. Just wanted to give you a heads up. |
I appreciate you flagging it to me and debugging to figure out what the issue was @LucasLombardo! I use linux so I don't always catch these things, but I imagine a lot of other folks would run into the same issue. I updated the SDK in osxcross-target from Reran build https://github.com/plentico/plenti/runs/2281823775 which failed with a new error: Error message
This might have to do with the fact that I'm building the target on Ubuntu 20.04 now. I could bump our CI from 18.04 to 20.04, but I'll have to add a step to install an outdated version of libssl: plentico/osxcross-target#1 (comment) |
New failure: https://github.com/plentico/plenti/runs/2282087718 Snapcraft login error
Sounds like Not sure if bumping the OS to Ubuntu 20.04 from 18.04 is causing the issue... |
I can't find much support for this snapcraft login issue, at least we're not the only ones https://twitter.com/dosco/status/1378055663792705536 |
This is interesting, we use click and added a new option (boolean) which seems to be causing issues with the way you are feeding the auth data. While I figure out what is going on with click, can you see if |
Thanks for taking a look @sergiusens! I just ran another build with the updated login command, but it seems to have the same |
This was more of a simpler issue to fix than I thought, but still a 🤦 moment canonical/snapcraft#3493 Renaming the env var should do it for now, will try to get this fix released by tomorrow in a patch release. Sorry for the troubles. |
No worries @sergiusens, thanks for the quick fix! Renaming the env var on my end now as a test, will follow up if I have any issues! Thanks! |
@sergiusens that worked! Thanks again! The remain breakage is unrelated: https://github.com/plentico/plenti/runs/2283581048 |
This might not be possible in v8go at the moment: rogchap/v8go#54 |
FYI I just installed plenti via Homebrew on my Mac mini M1 and it worked for the first time because previous tries failed. But when looking at the version it has installed it is not the latest. I wonder does Homebrew take a few days to update its packages?
Cheers, |
Oh interesting, thanks for testing this out @jamestagal. I honestly wasn't sure if this would work on M1 or not, so it's great to have more data points. Some day I'd like to remove our cgo dependency so we could open up the releases to a vast number of different devices. For getting the newest Plenti version, does something like |
Hi @jimafisk
So the version is showing V.0.5.5 while V0.5.8 is installed? How can I know which version I have because I don't believe I have the latest version installed? |
I wasn't able to install plenti initially through homebrew following instructions from the readme on a mac with m1 processor.
After running
brew tap plentico/homebrew-plenti
I got the error below.Looking at the homebrew-plenti repo I saw there was a check for if you are on intel before installing. Forking that file and removing the check worked for me and it installed / created a new site OK. Fork I used.
The text was updated successfully, but these errors were encountered: