v7.15beta broke backup file naming

[t0mm13b]

@infabo The real question to be asked is: why do you need them?

Furthermore, modern file systems have no inherent problems storing spaces and neither does NFS. You can easily mount NFS shares that include spaces. The “spaces” issue is primarily a legacy shell scripting problem which is why the ‘noclobber’ option was invented.

What has noclobber got to do with “legacy shell scripting problem” or spaces in filename?
Hint: it has nothing to do with spaces in the filename.

To truly understand the fundamental issue of breaking compatibility, you need experience with mission critical support systems for backup, version control and monitoring. One problem that many might not be aware of is that since Mikrotik isn’t a major player in the enterprise sector, ready-made support for ROS is often lacking and must be developed in-house. Changes that break compatibility force unnecessary spending on consultants and internal rework, redirecting resources away from more productive work.

Hobbyists or people working with smaller setups often lack this insight.

To be fair, MT did state the obvious, that’s on you relying on using spaces in filenames.

What’s new in 7.15beta4 (2024-Mar-04 08:04):

*) console - replace reserved characters to backup and certificate export file names with underscores;