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

Gitea create repository fails on Beaglebone (white) #12283

Closed
2 of 7 tasks
erdemoncel opened this issue Jul 20, 2020 · 1 comment
Closed
2 of 7 tasks

Gitea create repository fails on Beaglebone (white) #12283

erdemoncel opened this issue Jul 20, 2020 · 1 comment
Labels
issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented

Comments

@erdemoncel
Copy link

  • Gitea version (or commit ref):1.12.2
  • Git version: 2.20.1
  • Operating system: Debian GNU/Linux 10 (buster)
  • Processor model : ARMv7 Processor rev 2 (v7l)
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No but you may reproduce the bug at http://kotla.tk
    • Not relevant
  • Log gist:

2020/07/20 18:51:49 ...m.io/xorm/core/tx.go:36:BeginTx() [I] [SQL] BEGIN TRANSACTION [] - 2.208042ms
2020/07/20 18:51:49 ...sitory/repository.go:23:CreateRepository() [E] Rollback deleteRepository: repository does not exist [id: 1, uid: 1, owner_name: , name: ]
2020/07/20 18:51:49 routers/repo/repo.go:176:handleCreateError() [E] CreatePost: initRepository: git.InitRepository: fork/exec /usr/bin/git: cannot allocate memory

Description

I tried to install Gitea on Beaglebone white. As mentioned in the documentation I've downloaded the arm6 version of gitea. Everything worked fine until I tried to create a new repository. When I try to create an empty repository it gives a 500 error.
This device has only 256 MB DDR2 memory.

Screenshots

giteaerror

Gitea log

gitea.log

@stale
Copy link

stale bot commented Sep 20, 2020

This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.

@stale stale bot added the issue/stale label Sep 20, 2020
@lunny lunny added the issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented label Sep 20, 2020
@stale stale bot removed the issue/stale label Sep 20, 2020
@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 6, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented
Projects
None yet
Development

No branches or pull requests

3 participants