Required by (0)

Sources (2)

respiranto commented on 2017-08-05 23:17

To me, this does not really look like an error depiction. Though this is admittedly neither expected, nor what I get when building - which for me still works fine. Would you mind to post a little more context?

As a workaround, you could always (try to) build in a clean chroot [0].