theypsilon / Update_All_MiSTer

All-in-one script for updating your MiSTer
GNU General Public License v3.0
607 stars 27 forks source link

Update_all script overwrites my setting in update.ini #38

Closed jayp76 closed 3 years ago

jayp76 commented 3 years ago

I have a custon config in update.ini. When i choose to use the Mister update in update_all, it overwrites my custom config with an empty file. If the i add my custom config again and start the updater, it still makes a full resinc, which i don't want, i wann only the cores that are defined in my custom config.

theypsilon commented 3 years ago

Thanks for the report @jayp76

I would like to ask you a few more questions.

Is this a long lasting issue, or you've noticed it only today? When did you start using Update All approximately?

jayp76 commented 3 years ago

I use the update_all script about 2 months, but used only for jotego and mame updates. This was the first time i used it with update script and update.ini.

theypsilon commented 3 years ago

I see. Could you please share the update_all.ini file? Maybe I can get some clues from there.

jayp76 commented 3 years ago

Here you are. Had to rename the file to upload it.

update_all.ini.txt

theypsilon commented 3 years ago

It doesn't seem to be strange at all. Could you please also share your update.ini and the log of a run where this problem happens? You will find the log from your latest run at /media/fat/Scripts/.cache/update_all/update_all.log

jayp76 commented 3 years ago

I don't have the original update.ini, since it was nuked by the updater. I can only attach the one i had to create new, to update the cores. Unfortunately i don't have the log file when the problem occured. It is overwritten by the last updates i made. I'll try to reproduce it. For now, here is the update.ini i currently use. update.ini.txt

theypsilon commented 3 years ago

Hey @jayp76 , did your update.ini file got overwritten again?

jayp76 commented 3 years ago

i have no time testing or using the MiSTer at the moment. If you like you can close the issue. If it occurs again i would open up a new issue.