Hi Carl, Carl Dong <cont...@carldong.me> skribis:
> Yes! The patch actually fixed the problem when applied on top of > 5cf4b26d52bcea382d98fb4becce89be9ee37b55! [...] > Not sure what the next steps are for this, but I'd very much like to > understand where this went wrong. Perhaps we could write tests for this so it > doesn't happen in the future for releases. Yup, I understood when this could happen (if multiple inputs of a derivation are “fixed-output” derivations leading to the same output), wrote a test for that, and came up with a simpler fix in commit 268896444bed7b958add74b2e1e86ff802c5f5cb. Let me know if anything is amiss! Thanks for testing the patch, Ludo’.
