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

Use github as provider for appdata-screenshots #254

Merged
merged 5 commits into from
May 17, 2023
Merged

Conversation

fabiscafe
Copy link
Contributor

Today someone was unable to build the AUR pkg of tuba. While testing this at work, I faces something similar. At my workplace imgur is blocked, so the appdata check at the end of the build process failed, because it's unable to reach the screenshots.

This PR changes the provider from imgur to githubusercontent.com, that is the official github domain. It's very unlikely that github and githubusercontent.com are blocked/not reachable at the same time. So the build should always work or fail for that single reason instead of 2 points or error.

I have tried to build tuba via my own github repo. This worked (even at work 🥂 ) and switched over to the original repo after that. Of course this will fail to build until the screenshots are merged.

@GeopJr
Copy link
Owner

GeopJr commented May 16, 2023

Thanks! I understand that the screenshots being hosted on an external service are causing issues but at the same time I don't think the repo is the best place to store them.

Tootle had them in the repo and looking at the sizes in history, they are the main reason cloning is ~5mb

image

Perhaps I should "host" them in another repo, git-lfs or another service maybe?

@fabiscafe
Copy link
Contributor Author

That's a question, hm. 😅 An own repo, or branch could be an option. I sadly don't know about git-lfs. A different service would maybe hit the same problem, that it might not be reachable for the user who tries to build tuba.

@GeopJr
Copy link
Owner

GeopJr commented May 17, 2023

I switched to lfs on 5fb5d51

Thanks, merging!

@GeopJr GeopJr merged commit e4e8ba9 into GeopJr:main May 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants