Cargo gives precedence to configs without .toml suffix

[a-ovchinnikov]

As per https://doc.rust-lang.org/cargo/reference/config.html :

Note: Cargo also reads config files without the .toml extension, such as .cargo/config. Support for the .toml extension was added in version 1.39 and is the preferred form. If both files exist, Cargo will use the file without the extension.

There exist older projects that seem to rely on this feature. As a measure of precaution the alternative config should be renamed prior to running prefetch.

[eskultety]

Looking at the linked PR in the affected project I'm unclear what the real problem is as no error log snippet was provided either here or in the linked PR. Can you shed some more light on this please?

[a-ovchinnikov]

When someone uses pre-1.39 cargo config our generated settings will be ignored, this was observed in the linked project. The correct solution to the problem is to stop relying on conventions that were made obsolete in 2019. At the same time Hermeto could double-check if someone is still clinging to the past and either issue a warning or simply move the config.