flatpak update nuked the config

[Goury]

Describe the bug

Subj.
I've spent some time tuning my instance of dosbox-x and it all was gone after another update.

Steps to reproduce the behaviour

1. Do nothing, flatpak updates are automated
2. Just run the dosbox-x
3. Be disappointed

Expected behavior

Retain the configuration.
If changes are required, do a migration, don't just nuke the whole config.

What operating system(s) this bug have occurred on?

Ubuntu 22.04

What version(s) of DOSBox-X have this bug?

2025.02.01

Used configuration

Output log

Additional information

No response

Have you checked that no similar bug report(s) exist?

• I have searched and didn't find any similar bug report.

Code of Conduct & Contributing Guidelines

• I agree to follow the code of conduct and the contributing guidelines.

[FredBezies]

As far as I know - and I've been using dosbox-x since its 0.8x.y time - nothing is lost.

When you upgrade Dosbox-X, for example from 2025.01.01 to 2025.02.01 a new config file is generated in ./config/dosbox-x

Configuration file for 2025.01.01 is called dosbox-x-2025.01.01.conf. The on for 2025.02.01 is dosbox-x-2025.02.01.conf

Just verify you have both files. And to get back your configuration, just rename dosbox-x-2025.01.01.conf to dosbox-x-2025.02.01.conf.

[Goury]

Yes, but I still consider this a bug.
At the very least, dosbox-x should check if there's an older config and prompt to use it instead of not even caring.

For a good example, look how blender does it.