Package Details: megasync 5.5.0.0-2

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.18
First Submitted: 2014-09-01 18:12 (UTC)
Last Updated: 2024-10-06 03:37 (UTC)

Latest Comments

« First ‹ Previous 1 .. 25 26 27 28 29 30 31 32 33 34 35 .. 52 Next › Last »

sekret commented on 2017-10-17 18:38 (UTC)

Hi, I just tried to build the package, including the patch of course. I still get In file included from control/CrashHandler.cpp:15:0: google_breakpad/client/linux/handler/exception_handler.h:192:21: error: field ‘context’ has incomplete type ‘google_breakpad::ucontext’ struct ucontext context; ^~~~~~~ google_breakpad/client/linux/handler/exception_handler.h:192:12: note: forward declaration of ‘struct google_breakpad::ucontext’ struct ucontext context; ^~~~~~~~ make[1]: *** [Makefile:5284: CrashHandler.o] Error 1 make[1]: Leaving directory '/build/megasync/src/MEGAsync/src/MEGASync' make: *** [Makefile:45: sub-MEGASync-make_first] Error 2 ==> ERROR: A failure occurred in build(). Aborting... Any ideas? That patch was supposed to fix this right?!

<deleted-account> commented on 2017-10-17 17:28 (UTC)

@zxioper Thanks for that patch! Your instructions worked perfectly. :) I hope the package gets properly updated soon.

bmbaker commented on 2017-10-16 09:42 (UTC)

thanks for the patch installation instructions, I will try it out tonight :-)

psltn commented on 2017-10-15 16:44 (UTC) (edited on 2017-12-03 19:19 (UTC) by psltn)

Hello, this error is occuring after upgrading libsodium from 1.0.14 to 1.0.15: $ megasync: error while loading shared libraries: libsodium.so.18: cannot open shared object file: No such file or directory

A temporary solution is to just downgrade the libsodium package or symlink libsodium.so.18 to libsodium.so.23: # ln -s /usr/lib/libsodium.so.23 /usr/lib/libsodium.so.18

famar commented on 2017-10-11 12:53 (UTC)

Official info on applying patches here https://wiki.archlinux.org/index.php/Patching_in_ABS#Applying_patches

zxioper commented on 2017-10-11 06:22 (UTC) (edited on 2017-10-12 06:30 (UTC) by zxioper)

How to apply the patch: 1) Download patch and put it, for example, to your home directory. 2) Start megasync installation ( yaourt -S megasync). 3) Type "Y" when you are asked about editing PKGBUILD. 4) Modify PKGBUILD file, adding lines to the begining of the section "build()": cd "${srcdir}/MEGAsync" cp ~/ucontext.patch ./ patch -p1 -i ./ucontext.patch 5) Save changes and continue installation.

bmbaker commented on 2017-10-07 11:32 (UTC)

hi there, im getting the same error google_breakpad/client/linux/handler/exception_handler.h:192:21: error: field ‘context’ has incomplete type ‘google_breakpad::ucontext’ but i don't know how to apply the patch you linked bellow. cheers BB

zxioper commented on 2017-09-18 11:34 (UTC) (edited on 2017-09-18 11:48 (UTC) by zxioper)

Hi there. It seems package can't be compiled since glibc was update to 2.26. I got error: google_breakpad/client/linux/handler/exception_handler.h:192:21: error: field ‘context’ has incomplete type ‘google_breakpad::ucontext’ I found out that 'ucontext' type is no longer available (see sys/ucontext.h), it was replaced with 'ucontext_t'. Replacing 'ucontext' to 'ucontext_t' in the next files: google_breakpad/client/linux/handler/exception_handler.cc google_breakpad/client/linux/handler/exception_handler.h google_breakpad/client/linux/minidump_writer/minidump_writer.cc solves the problem (at least for me). Patch: https://mega.nz/#!3lRGibxB!eO3eGZ-vYGqU6r7vCagrAGQVtLqxeP4hVrvijr-sRic

zeroflag commented on 2017-09-01 06:27 (UTC)

Hi Miquel, it miraculously works again. Most proly, a location related issue. That's why a stumbled upon the "new version" which is obviously a different one than the source you compile this package from. No worries then. Thanks a sorry for the noise.

migrev commented on 2017-08-28 14:19 (UTC)

Hi @psltn, that's a binary package that has nothing to do with the one compiled used the PKGBUILD of this one. Obviously, feel free to use either one, but as of now (and unless proven wrong), the one I'm mantaining works fine, follows the versioning scheme of the released source code and I actually have no idea on the differences of the two PKGBUILDs. Will take a look at it, anyway, to check if there are any improvments that can be useful to all of us. Thank you for your message.

« First ‹ Previous 1 .. 25 26 27 28 29 30 31 32 33 34 35 .. 52 Next › Last »