-
Notifications
You must be signed in to change notification settings - Fork 87
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
new package(tur-on-device): awscli #863
Conversation
Kapral67
commented
Feb 29, 2024
•
edited
Loading
edited
- workflow will probably fail unless Call entrypoint on docker-exec #849 gets merged
arm/aarch64
i686/x86_64
|
tur-on-device/awscli/build.sh
Outdated
} | ||
|
||
termux_step_get_source() { | ||
local tarball |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why not use GitHub to fetch source? Using GitHub will make it easy to enable auto-update.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was thinking about that but I wasn't sure how the auto updates would work given that they simultaneously track 1.x and 2.x updates in the same repo with tags. If we can somehow force the auto updater to only look at 2.x tags that might be better.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actually this is not a problem. If the tag does not meet the increment conditions, the auto-update script will not update checksum for it.
c62dc13
to
37e6059
Compare
actions still not pulling latest built image from termux-user-repoistory/termux-docker so dns resolution is failing |
I don't think this is going to be able to compile in github actions. Every workflow seems to fail with an error that I am unable to reproduce locally |