Hi Brendan,
I can definitely confirm this, as I have been dealing with this on and
off for a couple of years now due to the window managers I use.
Would you like to file a bug on this or check if there are / have been
bugreports about this before? I'm not sure what the best way to
proceed could
> Perhaps you simply don't have enough garbage available for the collector
> to collect? If you ask for 5 GiB, your system has 3 GiB free, and there
> is only 1 GiB of garbage, the best the collector can do is collect all
> the garbage (1 GiB) and leave you with just 4 GiB of free space.
Sorry fo
Pierre Neidhardt writes:
> Thanks for mentioning this. I'm very confused by the documentation however:
>
> ‘--gc-keep-outputs[=yes|no]’
> Tell whether the garbage collector (GC) must keep outputs of live
> derivations.
>
> When set to “yes”, the GC will keep the outputs of any liv
Fantastic review!
Thank you so much for this: very clear, very thorough, it scattered all
remaining confusions! I thumb up for a blog post! :D
While I had understood most of it, I was completely ignorant of the separation
between the .drv closure and the output closure. It all makes much more se
Pierre Neidhardt writes:
> Thanks for mentioning this. I'm very confused by the documentation however:
>
> ‘--gc-keep-outputs[=yes|no]’
> Tell whether the garbage collector (GC) must keep outputs of live
> derivations.
>
> When set to “yes”, the GC will keep the outputs of any liv
