Package Details: megasync 5.4.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: 0.52
First Submitted: 2014-09-01 18:12 (UTC)
Last Updated: 2024-08-14 21:02 (UTC)

Sources (6)

Latest Comments

« First ‹ Previous 1 .. 20 21 22 23 24 25 26 27 28 29 30 .. 52 Next › Last »

kikadf commented on 2018-06-13 14:27 (UTC)

@pedrogabriel: do you have installed autoconf package?

pedrogabriel commented on 2018-06-13 13:53 (UTC)

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 (UTC)

@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 (UTC) (edited on 2018-06-02 18:22 (UTC) by kikadf)

@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 (UTC) (edited on 2018-06-01 23:05 (UTC) by FFY00)

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 :)

jfernandz commented on 2018-06-01 21:03 (UTC) (edited on 2018-06-01 21:09 (UTC) by jfernandz)

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?

CapSel commented on 2018-04-20 09:25 (UTC)

I've encountered a bug when using this package. Every time I try to select local directory (adding sync or selecting download directory) megasync crashes.

If you have same bug then you can follow these instructions from pm@mega.nz:

try to recompile removing this line of code in src/MEGASync/MegaApplication.cpp:

QApplication::setDesktopSettingsAware(false);

dresan commented on 2018-04-19 19:16 (UTC)

@kikadf, thanks for pointing me into the right direction. I'm currently rebuilding the package!

kikadf commented on 2018-04-17 13:33 (UTC)

@dresan, your fix is abuse the dependency structure. The correct way to fix the missing library problem is rebuild megasync with cryptoo++7.

dresan commented on 2018-04-17 06:47 (UTC)

Unable to launch Megasync due to a "missing library" libcryptopp.so.6. The current version is libcryptopp.so.7, ln -s /usr/lib/libcryptopp.so.7 /usr/lib/libcryptopp.so.6 seems to "fix" the problem.

« First ‹ Previous 1 .. 20 21 22 23 24 25 26 27 28 29 30 .. 52 Next › Last »