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
I can also see it now.
cheers!
mar77i
> I just triggered a cleanup script to prune unreachable objects. The
> warning should be gone.
the warning returned for me today.
g
signature.asc
Description: OpenPGP digital signature
On Wed, 01 Jun 2016 at 12:10:49, Florian Bruhin wrote:
> 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.
>
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:
> >
> >
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
* 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
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 b
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.