Package Details: megasync 4.2.0-1

Git Clone URL: https://aur.archlinux.org/megasync.git (read-only)
Package Base: megasync
Description: Easy automated syncing between your computers and your MEGA cloud drive
Upstream URL: https://github.com/meganz/MEGAsync
Licenses: custom:MEGA LIMITED CODE REVIEW LICENCE
Submitter: son_link
Maintainer: Kozeid
Last Packager: Kozeid
Votes: 321
Popularity: 5.513498
First Submitted: 2014-09-01 18:12
Last Updated: 2019-06-25 14:37

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 ... Next › Last »

JotEs commented on 2018-08-17 10:11

Mir wird seit einigen Tagen angeboten: Pakete (1) megasync-3.6.7-1 Aber: Fehler: Konnte Datei 'megasync-3.6.7-1-x86_64.pkg.tar.xz' nicht von mega.nz übertragen : HTTP server doesn't seem to support byte ranges. Cannot resume. Warnung: Konnte einige Dateien nicht übertragen Fehler: Konnte den Vorgang nicht durchführen (Fehler in der Bibliothek für Downloads) Fehler sind aufgetreten, keine Pakete wurden aktualisiert.

kikadf commented on 2018-08-05 10:38

@erayerdin, autoconf and automake is part of the base packages as well.

erayerdin commented on 2018-08-02 09:09

autoconf installed, yet there is still one error:

autoreconf: running: aclocal -I m4 --output=aclocal.m4t Can't exec "aclocal": No such file or directory at /usr/share/autoconf/Autom4te/FileUtils.pm line 326. autoreconf: failed to run aclocal: No such file or directory

For those who get this error, install autoconf and automake. It builds successfully.

simona commented on 2018-06-20 20:11

Wayland support for tray?

kikadf commented on 2018-06-13 14:27

@pedrogabriel: do you have installed autoconf package?

pedrogabriel commented on 2018-06-13 13:53

The package does not build.

==> Iniciando build()... ./autogen.sh: linha 2: autoreconf: comando não encontrado ==> ERRO: Uma falha ocorreu em build(). Abortando... Error making: megasync

kikadf commented on 2018-06-02 18:32

@wyre: I can't help. Try to make a lib32-crypto++ package, and use this as dependency. Linking doesn't work.

kikadf commented on 2018-06-02 18:21

@FFY00: I use the latest release as source, not from tarball, but from git tag. It is not a -git package. I use this method, because need the mega-sdk source to the build, what is a submodule in the megasync git repo, so this is the easiest way to get the whole source. Altough I don't like this, because the megasync source is the latest release, but the mega-sdk source is not. I will try to find a good solution to use the latest mega-sdk release as source.

FFY00 commented on 2018-06-01 23:05

You are using the git repository as a source. Normal packages, and by normal I mean non -git or other vcs, should have a valid checksum. Since this is released on github, you can just use the automatically generated .tar.gz release file as a source.

You can check out this sample PKGBUILD: https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=limesuite

Info about -git packages: https://wiki.archlinux.org/index.php/Arch_User_Repository#What_is_the_difference_between_foo_and_foo-git_packages.3F

Thanks for your time :)

wyre commented on 2018-06-01 21:03

I'm trying build the 32bit version on my 64bit system following this guide

https://wiki.archlinux.org/index.php/makepkg#Build_32-bit_packages_on_a_64-bit_system

but I'm having crypo++ libs issues

checking for main in -lcryptopp... no
configure: error: Could not find libcryptopp

Of course I've got installed crypto++ 7 version.

I think this is happening because I haven't got

libcryptopp.so
libcryptopp.so.7
libcryptopp.so.7.0.0

libraries inside /usr/lib32 folder, there is no lib32-crypto++ version? Could I fix this issue doing a symlink?