* Christian Hesse [2016-06-01 12:19:28 +0200]:

Florian Bruhin on Wed, 2016/06/01 12:10:

...

Hi,

whenever I push something to the AUR since some days (even a new repo with a single commit) I get:

error: The last gc run reported the following. Please correct the root cause and remove gc.log. Automatic cleanup will not be performed until the file is removed.

warning: There are too many unreachable loose objects; run 'git prune' to remove them.

It seems to be harmless (i.e. the package is uploaded anyways), but it's kind of confusing - it seems this is something wrong on the server, and not my local git repo?

No, it's your local repository. Just run:

git prune git gc

I did, and I'm still getting the same after pushing. This happening on a fresh repo with a single commit also wouldn't make any sense FWIW. Florian -- http://www.the-compiler.org | me@the-compiler.org (Mail/XMPP) GPG: 916E B0C8 FD55 A072 | http://the-compiler.org/pubkey.asc I love long mails! | http://email.is-not-s.ms/

On 01/06, Christian Hesse wrote:

Florian Bruhin on Wed, 2016/06/01 12:30:

...

* Christian Hesse [2016-06-01 12:19:28 +0200]:

...

Florian Bruhin on Wed, 2016/06/01 12:10:

...

Hi,

whenever I push something to the AUR since some days (even a new repo with a single commit) I get:

error: The last gc run reported the following. Please correct the root cause and remove gc.log. Automatic cleanup will not be performed until the file is removed.

warning: There are too many unreachable loose objects; run 'git prune' to remove them.

It seems to be harmless (i.e. the package is uploaded anyways), but it's kind of confusing - it seems this is something wrong on the server, and not my local git repo?

No, it's your local repository. Just run:

git prune git gc

I did, and I'm still getting the same after pushing.

This happening on a fresh repo with a single commit also wouldn't make any sense FWIW.

I've seen this myself but did not notice it happens over and over again for the same repository.

So yes, probably this is an issue with the remote repository. I think it is caused by the way we use git for AUR on the server. We do not have separate repositories per packages to share some objects.

Not sure if this is due to something we disabled in the config due to an earlier implementation issue, or if we just have to change the prune grace period that git-gc uses. Either way we'll have to wait for Lukas to do it. -- Sincerely, Johannes Löthberg PGP Key ID: 0x50FB9B273A9D0BB5 https://theos.kyriasis.com/~kyrias/

I just triggered a cleanup script to prune unreachable objects. The warning should be gone.

the warning returned for me today. g

On 6/9/16, G. Schlisio wrote:

...

I just triggered a cleanup script to prune unreachable objects. The warning should be gone.

the warning returned for me today. g

Same here. Horrible timing as I am about to go offline for 3 days. :( -- Eli Schwartz