[tor-bugs] #32711 [Applications/GetTor]: Gitlab repository is full and can't be updated
Tor Bug Tracker & Wiki
blackhole at torproject.org
Wed Dec 11 01:49:29 UTC 2019
#32711: Gitlab repository is full and can't be updated
---------------------------------+------------------------
Reporter: cohosh | Owner: (none)
Type: defect | Status: new
Priority: Medium | Milestone:
Component: Applications/GetTor | Version:
Severity: Normal | Resolution:
Keywords: gitlab | Actual Points:
Parent ID: | Points:
Reviewer: | Sponsor:
---------------------------------+------------------------
Comment (by cohosh):
Even after we delete a branch, the files stick around in storage due to
our usage of
[https://docs.gitlab.com/ee/administration/lfs/manage_large_binaries_with_git_lfs.html
#git-lfs LFS].
After uploading about 5GB of files in a new test repository:
{{{
$ du -h
4.9G ./.git/lfs
}}}
There's no way to remove these files from the remote without deleting the
repository. See [https://help.github.com/en/github/managing-large-files
/removing-files-from-git-large-file-storage#git-lfs-objects-in-your-
repository this github guide to LFS]. So if we want to still use gitlab,
we should look into to the [https://docs.gitlab.com/ee/api/README.html
API] which might allow us to easily delete and create a new repository
from the command line.
This brings us to another issue: Gitlab repositories are capped at 9.8GB,
which is not enough space to store all the binaries we need. There's a few
options here:
- Prioritize locales for places that censor the other GetTor providers
(see #32716)
- Create more than one repository (perhaps one per platform?)
- Abandon GitLab for another platform (let's make sure the other providers
are reachable for people first)
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/32711#comment:1>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
More information about the tor-bugs
mailing list