Package Details: megasync 5.2.1.0-1

Git Clone URL: https://aur.archlinux.org/megasync.git (read-only, click to copy)
Package Base: megasync
Description: Official MEGA desktop application for syncing with MEGA Cloud Drive
Upstream URL: https://github.com/meganz/MEGAsync/
Licenses: LicenseRef-Mega-Limited-Code-License
Submitter: son_link
Maintainer: dbermond
Last Packager: dbermond
Votes: 381
Popularity: 1.96
First Submitted: 2014-09-01 18:12 (UTC)
Last Updated: 2024-04-29 17:36 (UTC)

Latest Comments

1 2 3 4 5 6 .. 50 Next › Last »

FabioLolix commented on 2024-05-23 21:29 (UTC)

@dbermond time to re-add a pinned comments about the usual errors

dbermond commented on 2024-05-23 00:30 (UTC)

@rufusreal there is no issue. You missed the icu 75 rebuild and need to rebuild both libpdfium and megasync against icu 75. Remember that it's user responsibility to take care of the installed AUR packages and do the required rebuilds.

rufusreal commented on 2024-05-22 23:47 (UTC)

There are some issues with Megasync, I cannot open the app. Launching from terminal

megasync: error while loading shared libraries: libicuuc.so.74: cannot open shared object file: No such file or directory

agolovanov commented on 2024-05-02 08:25 (UTC)

@serafeimg, Please read how to install packages from AUR: https://wiki.archlinux.org/title/Arch_User_Repository and https://wiki.archlinux.org/title/AUR_helpers. The MEGAsync folder is a consequence of cloning the megasync git repo (https://github.com/meganz/MEGAsync.git) which is the source for this AUR package as defined in PKGBUILD.

Downloading the prebuilt binary is not a solution for this package because here it's built from source, it's just an alternative way of getting megasync. And downloading the binary by yourself is also not an optimal solution because it prevents automatic updates. If you want to use the megasync binary, it's better to use https://aur.archlinux.org/packages/megasync-bin which takes the binary from exactly the same source as you did but does this in a way which is better suited for Arch.

serafeimg commented on 2024-05-01 16:56 (UTC)

When I clone the repo with the command: git clone https://aur.archlinux.org/megasync.git

no file or folder with the name MEGAsync exist.

The solution for me was to download and install the package with: wget https://mega.nz/linux/repo/Arch_Extra/x86_64/megasync-x86_64.pkg.tar.zst && sudo pacman -U \"$PWD/megasync-x86_64.pkg.tar.zst\"

as instructed here: https://mega.io/desktop#download

agolovanov commented on 2024-04-30 07:38 (UTC) (edited on 2024-04-30 07:39 (UTC) by agolovanov)

With the latest update, I get the following error during installation/update:

==> Validating source files with sha256sums...
    MEGAsync ... NOT FOUND
    meganz-sdk ... Skipped
    010-megasync-libpdfium.patch ... Passed
    020-megasync-ffmpeg.patch ... Passed
==> ERROR: One or more files did not pass the validity check!

I guess the cause is that MEGAsync (obtained by cloning a git repo tag) is a folder, and it does not have a sha256 sum. Previously, it was marked to be skipped from the check, just like the magenz-sdk folder. What is the intended behavior here?

absinthium commented on 2024-04-10 03:32 (UTC)

@TheOmegaCarrot, in my case, I had to install qt5-quickcontrols2 and qt5-graphicaleffects which were not listed as dependencies. Afterward, everything worked fine.

jghodd commented on 2024-03-22 02:53 (UTC) (edited on 2024-03-22 02:54 (UTC) by jghodd)

As soon as the latest version came up it had Issue Detected with 67 files suddenly duplicated...? what's going on, and what;s changed, and how am I supposed to respond to it...

dbermond commented on 2024-03-05 21:53 (UTC)

@JPT48 Sorry, but Manjaro is not supported. Please seek help in your distribution's support channels. The package is building and running fine in Arch Linux. As @FabioLolix stated, the base-devel package is assumed to be installed when building Arch Linux packages. The Arch Wiki establishes that dependencies of base-devel should not be listed in PKGBUILDs.

JPT48 commented on 2024-03-05 10:36 (UTC)

@FabioLolix then this is a manjaro issue?

1 2 3 4 5 6 .. 50 Next › Last »