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

Update to v7.10.0 #164

Closed
wants to merge 10 commits into from
Closed

Update to v7.10.0 #164

wants to merge 10 commits into from

Conversation

tier940
Copy link

@tier940 tier940 commented May 31, 2023

The arm and arm64 were successfully built + confirmed to be operational after incorporating the following modifications. Other builds did not pass.
#162 (comment)

If you want to know the build details and deliverables, please see below
https://github.com/tier940/ubiquitous-memory/pull/4/commits
https://github.com/tier940/ubiquitous-memory/releases/tag/v7.10.0

Copy link

@SKevo18 SKevo18 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you and yes please, there is no easy way to get arm64 version of Mattermost

Edit: turns out you can just do wget https://releases.mattermost.com/9.0.1/mattermost-9.0.1-linux-arm64.tar.gz

@kemenaran
Copy link
Collaborator

@tier940 the build is failing. When this repo's build script attempts to patch the Mattermost files, it fails with this error:

+ patch --directory=/build/go/src/github.com/mattermost/mattermost-server --strip=1 -t
can't find file to patch at input line 5
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/build/release.mk b/build/release.mk
|index faa027239..df40f0c68 100644
|--- a/build/release.mk
|+++ b/build/release.mk
--------------------------
No file to patch.  Skipping patch.
2 out of 2 hunks ignored
Error: Process completed with exit code 1.

Can you look if build/release.mk still needs to be patched – and if yes, port the patch to the new location?

@tier940 tier940 closed this Oct 17, 2023
@tier940
Copy link
Author

tier940 commented Oct 17, 2023

I forgot I left the PR open.

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

Successfully merging this pull request may close these issues.

3 participants