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

Unable to build mmc-utils #867

Open
Eeems opened this issue May 29, 2024 · 0 comments · Fixed by #878
Open

Unable to build mmc-utils #867

Eeems opened this issue May 29, 2024 · 0 comments · Fixed by #878
Labels
bug Something isn't working packages Add or improve packages of the repository

Comments

@Eeems
Copy link
Member

Eeems commented May 29, 2024

Describe the issue
git.kernel.org is now returning a 403 error when trying to download the source files

To Reproduce
Steps to reproduce the behaviour:

  1. Attempt to build mmc-utils
  2. Get the following error: Unexpected status code while fetching source file 'https://git.kernel.org/pub/scm/utils/mmc/mmc-utils.git/snapshot/mmc-utils-7769a4d7abe339ce273c13a203394a79a11fcff9.tar.gz', got 403

Expected behaviour
It should not error.

Upstream issue
N/A

Screenshots
N/A

System information:

  • toltecctl status output: N/A
  • Package: mmc-utils 1.0-0

Additional context
I've tried manually downloading the tar.gz file, and I also get a 403, even though the link is available on the web interface.

Likely the workaround would be to change the recipe to use git to checkout the repository at the correct commit instead. The wireguard package should have an example of how to do that.

@Eeems Eeems added bug Something isn't working packages Add or improve packages of the repository labels May 29, 2024
This was linked to pull requests Jun 2, 2024
@Eeems Eeems removed a link to a pull request Jun 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working packages Add or improve packages of the repository
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant