> i've been able to build by `INHERIT_remove`ing "uninative", but this
> feels like a hack.
>
> so i'm wondering: what could cause a reparse error when `uninative` is
> enabled?
i think i've tracked down the error:
`uninative_event_enable` extends `PATH`, but only if `UNINATIVE_LOADER`
points to
hi all,
i'm currently running into an issue of non-deterministic metadata: my
packages build fine when building the package itself, but i'm getting a
metadata mismatch when building as dependency of an image:
> ERROR: When reparsing
>
