-
|
Hi All, I migrate form a Intel based Mac to M1 based with TimeMachine. Yeap, it's not a good move... The error (The operation couldn’t be completed. (RsyncUI.FilesError<RsyncUI.LocationErrorReason> error 1.)) pop-up when I start RsyncUI & while I'm trying to save configuration. I then remove the RsyncUI and then uninstall Homebrew & all apps. And reinstall all of those again as well as update a new M1 based path with the follow: export PATH="/opt/homebrew/bin:$PATH" However, the same error still comes up. I guess that some of the env or "settings" are still using the Intel based env & unable to update by my reinstallation. Can anyone guide me to resolve this problem? Thanks & regards, Danny |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 3 replies
-
|
Hi, it is difficult to say why this happens. RsyncUI should automatically pick of the correct path for rsync. The first time you start, RsyncUI utilizes default rsync as part of macOS. The error is from a third party code (Files), it might be that RsyncUI is not allowed to write files within your home catalog?.. I suggest you try RsyncOSX (install by brew - |
Beta Was this translation helpful? Give feedback.
-
|
It might also be that RsyncUI does not find rsync..The error indicates rsync is not found. You might also try to use default version of rsync within RsyncUI (do not tick on Rsync v3.x in settings) /// Error thrown by location operations - such as find, move, copy and delete. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks Thomas! |
Beta Was this translation helpful? Give feedback.
-
|
I have the same issue but this did not resolve it for me. from env this is what I have set: Thank you Michael |
Beta Was this translation helpful? Give feedback.
-
|
Homebrew seems to be installed by default values and should be picked up by
RsyncUI. Please check my comment on your issue, I need more info to assist
what causes the problem ..
All the best,
Thomas
man. 20. mai 2024 kl. 19:20 skrev Michael Dweck ***@***.***>:
… I have the same issue but this did not resolve it for me. from env this is
what I have set:
HOMEBREW_PREFIX=/opt/homebrew
HOMEBREW_CELLAR=/opt/homebrew/Cellar
HOMEBREW_REPOSITORY=/opt/homebrew
MANPATH=/opt/homebrew/share/man::
INFOPATH=/opt/homebrew/share/info:
Thank you Michael
—
Reply to this email directly, view it on GitHub
<#10 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AFLDNTCLMY27E2DUSOGDKX3ZDIWFLAVCNFSM5V7UHVXKU5DIOJSWCZC7NNSXTOKENFZWG5LTONUW63SDN5WW2ZLOOQ5TSNBZHEYDOOA>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
Hi, it is difficult to say why this happens. RsyncUI should automatically pick of the correct path for rsync. The first time you start, RsyncUI utilizes default rsync as part of macOS. The error is from a third party code (Files), it might be that RsyncUI is not allowed to write files within your home catalog?..
I suggest you try RsyncOSX (install by brew -
brew install --cask rsyncosx). Add a task in RsyncOSX and RsyncUI should pick it up..