On Wed, Jan 13, 2021 at 08:37:30PM +0100, Wiktor Żelazny wrote: > Yeah, there may be a connection. Is --no-substitutes a way to avoid this > error? Yes, the problem is in the substituter so --no-substitutes will avoid it. You might spend a loooooong time building things but it depends on the specific package(s).