Package Details: megasync-bin 4.6.7-2

Git Clone URL: https://aur.archlinux.org/megasync-bin.git (read-only, click to copy)
Package Base: megasync-bin
Description: Easy automated syncing between your computers and your MEGA cloud drive
Upstream URL: https://mega.io
Licenses: custom
Conflicts: megasync
Provides: megasync
Submitter: rpanerai
Maintainer: rpanerai
Last Packager: rpanerai
Votes: 38
Popularity: 3.09
First Submitted: 2020-11-28 18:03 (UTC)
Last Updated: 2022-06-23 20:59 (UTC)

Latest Comments

PeterRies commented on 2022-06-23 19:57 (UTC)

version 4.6.7 is out with a security fix (see https://blog.mega.io/mega-security-update/ )

rpanerai commented on 2022-06-08 08:30 (UTC)

It seems that the last update of freeimage broke compatibility.

megasync: symbol lookup error: /usr/lib/libfreeimage.so.3: undefined symbol: TIFFFieldSetGetSize

I have modified the PKGBUILD to include the libfreeimage.so.3 provided by the original package. Please, update.

Neko-san commented on 2022-04-23 01:06 (UTC)

Why is it that the official package on their site gives a hard time about PGP keys? I've tried to use theirs but I've not had it to stop with that

ozon commented on 2022-03-13 22:29 (UTC)

You can edi the pkgbuild yourself to fix the issue :

git clone https://aur.archlinux.org/megasync-bin.git
cd megasync-bin

In the PKGBUILD file, change pkgver=4.6.5 and pkgrel=2 (or whatever the last version is, you can check it by looking at the file name here https://mega.io/linux/repo/Arch_Extra/x86_64/).

Then makepkg -si and it should work.

zeroconf commented on 2022-03-12 17:15 (UTC)

installation was not possible at March 11, 2022 with similar issue, like @adev had with older version below

michaldybczak commented on 2021-12-25 22:35 (UTC)

Thanks, this one works great. The non-bin version was a headache, mostly compile errors or dependency problems. Bin version is up-to-date, installs instantly and just works. Awesome!

adev commented on 2021-07-26 11:22 (UTC)


[Aur:1]  megasync-bin-4.4.0-3

  1 megasync-bin                     (Build Files Exist)
==> Packages to cleanBuild?
==> [N]one [A]ll [Ab]ort [I]nstalled [No]tInstalled or (1 2 3, 1-3, ^4)
==> 
:: PKGBUILD up to date, Skipping (1/1): megasync-bin
  1 megasync-bin                     (Build Files Exist)
==> Diffs to show?
==> [N]one [A]ll [Ab]ort [I]nstalled [No]tInstalled or (1 2 3, 1-3, ^4)
==> 
:: (1/1) Parsing SRCINFO: megasync-bin
==> Making package: megasync-bin 4.4.0-3 (Mon 26 Jul 2021 05:06:34 PM +0545)
==> Retrieving sources...
  -> Downloading megasync-4.4.0-3-x86_64.pkg.tar.zst...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:--  0:00:06 --:--:--     0
curl: (22) The requested URL returned error: 404
==> ERROR: Failure while downloading https://mega.io/linux/MEGAsync/Arch_Extra/x86_64/megasync-4.4.0-3-x86_64.pkg.tar.zst
    Aborting...
error downloading sources: megasync-bin

malch commented on 2021-06-30 03:24 (UTC)

Thank you for this time saver.

servimo commented on 2021-06-13 00:08 (UTC)

Nice found, thanks!

FabioLolix commented on 2021-05-10 18:11 (UTC)

@johnlinde I don't live for replying to you in seconds and I have other things to do.

I really care for a State of the Art packaging for the AUR. Updating packages, fixing them, improving mines and others, removing flaws & imperfections, streamlining and removing pointless parts, following packaging guidelines

johnlinde commented on 2021-05-10 17:40 (UTC)

No @FabioLolix, you are the keyboard lion responding only hours if not minutes after I slapped you in the face with my keyboard.

However, I will say this. I have found that the megasync-bin package does not save the downloads when I quit megasync, and then start it again, however, the regular one that compiles does. So, despite the morons like Fabio here, the reality is, the regular one does work better.

Keep up the good work Fabio! I'm sure someday you will get what you're looking for, which is some kind of respect I think...

FabioLolix commented on 2021-05-10 17:19 (UTC)

@johnlinde you're a real 'keyboard lion', account created today only to reply to me.

I'm gonna review as much as I want

johnlinde commented on 2021-05-10 15:40 (UTC)

@FabioLolix

Why don't you go find something more useful to do than try to go around and get people to take down the bin files? The people here on arch linux don't want to have to build the source from scratch every time, especially for a stupid little proprietary program like this. Furthermore, why don't you go on a campaign to stop all the other people who are doing with this other packages? Just type "bin" into the search engine. Make sure they're all following the rules little unelected police officer.

rpanerai commented on 2021-05-10 13:36 (UTC) (edited on 2021-05-10 13:36 (UTC) by rpanerai)

@FabioLolix: The way I interpret the rule is that an AUR entry should not just download and install a binary package generated by another PKGBUILD.

In this case, however, the original package installs a config file that modifies your inotify parameters and runs an install script that edits your /etc/pacman.conf by adding an external repository. I do not consider it acceptable for an Arch package to automatically reconfigure different core components of your setup upon installation. In fact, I am not aware of any Arch package that does anything remotely similar.

This package, on the contrary, provides the binaries for the client application without running any post-install action and, as such, is significantly different from the original one. The original package is merely used to extract precompiled binaries. By following your interpretation of the rule, extracting the binaries from the Ubuntu .deb would be fine. This would produce at best the same outcome (generating a package from the binaries shipped by mega.io) but it would potentially introduce compatibility issues (different dependencies, library versions, etc.).

FabioLolix commented on 2021-05-09 15:46 (UTC)

From https://wiki.archlinux.org/index.php/AUR_submission_guidelines#Rules_of_submission

"The AUR should not contain the binary tarball created by makepkg"

rpanerai commented on 2021-04-06 09:25 (UTC)

@FabioLolix: can you please be more specific about which rule on the AUR Submission Guidelines this PKGBUILD in your opinion violates and how?

FabioLolix commented on 2021-04-05 19:45 (UTC)

Hello, this kind of pkgbuild where the source is an already build Arch package are against submission rules

rpanerai commented on 2021-03-31 12:36 (UTC)

@mitchpk: I pushed an update with the new mega.io domain.

mitchpk commented on 2021-03-30 02:03 (UTC) (edited on 2021-03-30 02:33 (UTC) by mitchpk)

Hello. This package no longer installs on my University's network as the source link doesn't redirect to mega.io. However, it does install if I manually change the link in the PKGBUILD. MEGA has changed domains from mega.nz to mega.io which I believe has something to do with it.

rpanerai commented on 2020-12-28 14:23 (UTC)

@c3n21: Thank you for the suggestion! I've pushed an updated version.

c3n21 commented on 2020-12-27 11:37 (UTC)

I had to add provides=("megasync=$pkgver") to the PKGBUILD to make it recognizable by "nautilus-megasync", because it needs megasync>=2.9.8 as dep, without this I can't install it

rpanerai commented on 2020-11-30 21:41 (UTC)

@andrea_berling: Done!

andrea_berling commented on 2020-11-29 12:15 (UTC)

Hi. Could you please add "megasync" to the conflicts array in the PKGBUILD?