Just opened a ticket at mega. Just in case somebody comes across this error.
❯ megasync
megasync: error while loading shared libraries: libicuuc.so.73: cannot open shared object file: No such file or directory
You can either downgrade the icu package or switch to a command-line sync solution like rclone. If you’re using megasync-bin, it was flagged out-of-date this morning.
1 Like
I’ll wait 'til megasync gets an update. If it takes too long I’ll downgrade. It happened on my test machine fortunately 
But thanks anyway 
General question
How will i come to know if any of my installed packages has been flagged in AUR
If I recall, these Mega/icu dependencies can take weeks to get worked out, given past track records.
One may be able to use nix or distrobox and install megasync under those facilities, essentially isolating mega from the operating system.
If you rebuild megasync with the new version of icu, won’t that work?
1 Like
You can either use yay or go to page for your AUR package
For example
$ yay -Ss megasync-bin
aur/megasync-bin 4.11.0-3 (+14 3.49) (Out-of-date: 2023-12-17)
Easy automated syncing between your computers and your MEGA cloud drive
will need to try this. I used the bin package due to faster updates. downgrade icu gave me dependecy errors. I’ll buid from sources and report
Maybe. If an interface changed, you’ll have to make code changes to get a successful build.
I am not familiar with Mega’s desktop application but don’t they provide own pacman repo for it?
Yeah, they did at one point, but might have let that go. Their desktop download page for Arch suggests a wget of a pkg.tar.zst file that one uses a second command to pacman -U and install it.
Given Arch’s icu package changed over the weekend, Mega may need some time to turn this around.
using megasync instead of megasync-bin worked. took some time but dependency issue solved.
You might want to close that issue you opened on the Megasync github project since this is not a problem of Megasync.
Glad my suggestion in post #6 worked and you reported the solution in post #12. 
1 Like
Ticket at megasync closed with comment.
I added a comment in the AUR megasync-bin instead.
I just downloaded the latest package from their site and if you extract it there is an .install file with a post-install function (?) which apparently imports a pacman key and add a repo to pacman.conf.
make sure that you have done the Getting Started part - especially the correct setting of MAKEFLAGS in /etc/makepkg.conf to your systems thread count. If you have not done that, doing so will drastically speed up the build time.
the -bin PKGBUILD actually takes the package from that repo
1 Like
Yes, it does.
The point was you could perhaps “bypass” AUR and go directly to the “source” if the PKGBUILD is not timely updated? As an option.
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.