It looks like cargo now accepts both these paths for overriding its behaviour.
However, %cargo_prep only overrides the first file. If upstream uses the second one, cargo will get confused and do weird things.
We should properly clean up both these two files in %cargo_prep before writing our own configuration.
How does cargo get confused? I thought the one without the extension was supposed to take precedence for backwards compatibility.
I think you're right, because the build problem turned out to be caused by a different issue in the end, I just forgot to close this ticket.
Metadata Update from @decathorpe: - Issue close_status updated to: Invalid - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.