On 4/10/2024 10:04 PM, Adrien Monteleone wrote:
The distro does not matter. (with perhaps some caveats concerning dependencies) While you technically can jump from 2.6.21 to 5.6 (current version), that isn't officially supported, nor recommended. See the Wiki FAQ about upgrading procedures from one major version to another. (In this case, you are upgrading from one major version to one THREE versions later.)

The recommended and safest path would be:
2.6.21 -> 3.11 -> 4.14 -> 5.6
keeping a backup/copy of your data file at each stage and running 'Actions > Check & Repair > Check & Repair All' upon first opening your file after each upgrade.

Based on my decades in the cypher mines:

a) Be Prepared to follow the recommended and safest path

b) But given the number of steps, I would think it worth while to conduct an experiment to see if you couldn't just jump all the way. It's just a matter of first making a backup of the data  AND also a backup of the program directory (make a renamed copy of the directory -- quick to back-off by renaming back. IF the jump all the way from 2.3.21 works (you've tested opening the books and entered some test transactions, run all the reports you usually do, etc.). If it worked, you can delete the program backup and rename back the data back-up (unless you used real data not yet entered for testing)

     If it didn't work, a bridge too far, you haven;t lost a great deal. Revert to the step by step method.

Michael D Novack

PS -- this is really a test of the developer's prowess since ideally they would have managed to maintain backwards data compatibility. The issue is being able to open an OLD back-up if/when necessary << say to see something that has been removed from current books >>





_______________________________________________
gnucash-user mailing list
gnucash-user@gnucash.org
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
-----
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.

Reply via email to