Trouble recreating symlinks for ROM folders about retronas HOT 4 CLOSED

I am not sure I understand exactly the problem. Do you mean the folder have permissions that differ from expected? This should have been repaired as you rerun the playbook for MiSTer.

• roms/nintendo/nes should not be a folder, it should be a symlink
• roms/nintendo/famicom_disk i believe was something we identified as currently missing recently and needs correction.

Could you please clarify if all other symlinks created correctly for MiSTer?

from retronas.

Sorry for the confusion.

Due to the way I migrated my collection - I ended up messing up the permissions and had The following symlinks showing as having the wrong ownership and permission:
roms/nintendo/nes --> roms/nintendo/famicom
roms/nintendo/snes --> roms/nintendo/superfamicom (I misrembered the symlink that was at issue originally)

I'm fairly confident that roms/nintentdo/nes was a symlink pointing to roms/nintendo/famicom, and roms/nintendo/snes was also a symlink pointing to roms/nintendo/superfamicom but maybe I'm mistaken?

Eitherway, here were the steps I followed to correct this
1.) I deleted the symlinks expecting them to be regenerated when I ran the Samba for Mister option in the TUI.
2.) Confirmed that the target directory roms/nintendo/famicom exists with the right permissions (owned by my default user "retronas_user"
3.) Opened retronas and ran the Samba for Mister option from install things

Unfortunately, I ran that script, but the deleted items have not been regenerated and are still deleted

Is there a particular step I need to take to rerun the playbook beyond what I have done?

from retronas.

And disregard - after running it 4 times earlier today with no success, I just reran it again and the following symlinks regenerated:
roms/nintendo/nes --> roms/nintendo/famicom
roms/nintendo/snes --> roms/nintendo/superfamicom

Not sure why it didn't work earlier today and just worked now... but its resolved

Feel free to mark as closed unless you think there is something to learn from this except some weird user error on why they didn't regenerate when I ran the script earlier today.... of note the only thing I noticed that was different this time vs. the three times earlier today, was that this time when I opened the retronas TUI I got a message saying retronas had been updated required me to hit enter to confirm (I don't remember the exact message) before taking me to the TUI

from retronas.

sorry i had no chance to come back around to this yet, the message you saw said you could now run retronas at the cli instead of the long sudo /opt/retronas/retronas.sh

we have made no changes that space I am aware of so it is certainly odd, i will close thise for now and we can revisit if have more reports of the same.

thanks for the follow up

from retronas.