It's not clear to me why this is a bug; users shouldn't be driving the curtin in subiquity's snap themselves (right?), and the only evidence here is that that usecase breaks. Could you expand on what user-facing issue this is causing?
subiquity doesn't expose the curtin executable as an "app", so adding /snap/bin to PATH won't help. (Looking at the code, it will try using `which` before it tries constructing paths itself.)
The curtin binary being installed in /bin seems like a reasonable thing to support.
It's not clear to me why this is a bug; users shouldn't be driving the curtin in subiquity's snap themselves (right?), and the only evidence here is that that usecase breaks. Could you expand on what user-facing issue this is causing?
subiquity doesn't expose the curtin executable as an "app", so adding /snap/bin to PATH won't help. (Looking at the code, it will try using `which` before it tries constructing paths itself.)
The curtin binary being installed in /bin seems like a reasonable thing to support.