Next step is: https://wiki.koha-community.org/wiki/Git_Splitting_and_Shrinking I have tried few months ago but almost burnt my CPU, we need a powerful machine to do that. I think some of us plan to work on that during the hackfest in Marseille. No need for me to explain the gitlab.com vs self-hosting, I am sure you know the answers already. Le jeu. 6 févr. 2020 à 03:40, <dcook@prosentient.com.au> a écrit :
I’ve been in touch with someone at Gitlab, and they pointed out that https://gitlab.com/gitlab-com/support-forum/issues/4590 is just a forum rather than a bug tracker per se. That said, I see Gitlab employees commenting on other “support-forum” issues like https://gitlab.com/gitlab-com/support-forum/issues/5165.
The information at https://about.gitlab.com/support/#differences-between-support-tickets-and-gi... is a bit confusing, as it seems to suggest free users can’t open tickets, but https://support.gitlab.com/hc/en-us has an option for free users to open tickets. I was also told that it was fine for free users to open tickets, although there is no SLA governing response times.
I suggest that we submit a new support ticket via https://support.gitlab.com/hc/en-us. If the number is shared with me, I’d be happy to try contacting Gitlab folk via side channels to see if they can prioritize it a bit.
Judging from https://docs.gitlab.com/ee/user/project/repository/reducing_the_repo_size_us... (and some things I’ve heard), it sounds like Gitlab might need to do cleanup work on their end. I don’t think rewriting history is the answer, but maybe they need to do some git garbage collection or do something else to “clean up its own internal state”.
That all being said, while we might solve this problem this once, I imagine it might happen again, so what would our long-term plan be?
Is there a reason we use Gitlab.com instead of self-hosting Gitlab?
David Cook
Systems Librarian
Prosentient Systems
72/330 Wattle St
Ultimo, NSW 2007
Australia
Office: 02 9212 0899
Direct: 02 8005 0595
From: Koha-devel <koha-devel-bounces@lists.koha-community.org> On Behalf Of Renvoize, Martin Sent: Thursday, 6 February 2020 5:17 AM To: Julian Maurice <julian.maurice@biblibre.com> Cc: koha-devel <koha-devel@lists.koha-community.org> Subject: Re: [Koha-devel] Koha mirror on gitlab.com not updated ?
Our repo is certainly a bit on the big side.. but I'm also disappointed in the lack of response from gitlab.
Perhaps we could clarify the issue title a little.. Its not clear from the title that we believe gitlab is estimating the size wrongly
On Wed, 5 Feb 2020, 2:47 pm Julian Maurice, <julian.maurice@biblibre.com> wrote:
I know there is a mirror on github but the koha-community organization there has only 4 repositories, including one which points to gitlab.com (kohadocs), and another that is not directly related to koha (perlweb). If we compare to gitlab.com where there are 17 repositories, I think we cannot say that we "moved" to github.
So, the situation is a little weird as almost all repositories are on gitlab, except for the main repository which is not updated correctly, so people have to go elsewhere (github or git.koha-community.org) to get koha
Hopefully gitlab will fix the issue. But what if they don't ? :/
Le 05/02/2020 à 10:00, Jonathan Druart a écrit :
Have you considered moving to github instead ? (github has a hard limit of 100GB per repository)
We moved from github to gitlab a couple of years ago ;)
Le 04/02/2020 à 16:29, Jonathan Druart a écrit :
I investigated that issue few months ago, and asked Chris what returned `du -sbh .git` on git.koha-community.org/koha: 2.8G .git So it's really weird that gitlab complains about that size (13GB) At that time (June 2019) the gitlab interface says "17Go, 7 over the limit of 10." So numbers look quite inconsistent.
See also the issue I opened on their bug tracker: https://gitlab.com/gitlab-com/support-forum/issues/4590
Le mar. 4 févr. 2020 à 15:28, Julian Maurice <julian.maurice@biblibre.com> a écrit :
Can we do something about that or should we consider the mirror on gitlab to be useless and never use it ?
Le 04/02/2020 à 14:59, Tomas Cohen Arazi a écrit :
Because of Koha's repo size.
El mar., 4 feb. 2020 a las 10:55, Julian Maurice (<julian.maurice@biblibre.com <mailto:julian.maurice@biblibre.com>>) escribió:
Hi all,
It seems the mirror on gitlab is not updated anymore. The last commit on master is
604c7b81 Bug 22816: OPAC detail holdings table should now look a bit better
which has been committed in May 2019
Does anyone know why ?
-- Julian Maurice BibLibre _______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org <mailto:Koha-devel@lists.koha-community.org> https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
-- Tomás Cohen Arazi Theke Solutions (http://theke.io <http://theke.io/>) ✆ +54 9351 3513384 GPG: B2F3C15F
-- Julian Maurice BibLibre _______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
-- Julian Maurice BibLibre
-- Julian Maurice BibLibre _______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/