Search Criteria
Package Details: megasync 5.5.0.0-2
Package Actions
| 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) |
Dependencies (26)
- c-ares (c-ares-gitAUR)
- crypto++ (crypto++-gitAUR)
- curl (curl-quiche-gitAUR, curl-http3-ngtcp2AUR, curl-gitAUR, curl-c-aresAUR)
- ffmpeg (ffmpeg-intel-full-gitAUR, ffmpeg-nvcodec-11-1-gitAUR, ffmpeg-ffplayoutAUR, ffmpeg-decklinkAUR, ffmpeg-fullAUR, ffmpeg-amd-fullAUR, ffmpeg-headlessAUR, ffmpeg-full-gitAUR, ffmpeg-libfdk_aacAUR, ffmpeg-obsAUR, ffmpeg-gitAUR, ffmpeg-amd-full-gitAUR, ffmpeg-cudaAUR)
- freeimage
- hicolor-icon-theme (hicolor-icon-theme-gitAUR)
- icu (icu-gitAUR)
- libmediainfo (libmediainfo-gitAUR)
- libpdfium (pdfium-binariesAUR, pdfium-binaries-v8AUR, libpdfium-nojsAUR)
- libsodium (libsodium-gitAUR, libsodium-1.0.18AUR)
- libuv (libuv-gitAUR)
- libxcb (libxcb-gitAUR)
- libzen (libzen-gitAUR)
- openssl (openssl-gitAUR, openssl-staticAUR)
- qt5-base (qt5-base-gitAUR, qt5-base-headlessAUR)
- qt5-declarative (qt5-declarative-gitAUR)
- qt5-graphicaleffects (qt5-graphicaleffects-gitAUR)
- qt5-quickcontrols (qt5-quickcontrols-gitAUR)
- qt5-quickcontrols2 (qt5-quickcontrols2-gitAUR)
- qt5-svg (qt5-svg-gitAUR)
- qt5-x11extras
- sqlite (sqlite-fossilAUR)
- zlib (zlib-ng-compat-gitAUR, zlib-gitAUR, zlib-ng-compatAUR)
- cmake (cmake-gitAUR) (make)
- git (git-gitAUR, git-glAUR) (make)
- qt5-tools (make)
Latest Comments
« First ‹ Previous 1 .. 3 4 5 6 7 8 9 10 11 12 13 .. 52 Next › Last »
Sylvain_07 commented on 2022-11-03 20:03 (UTC)
/usr/bin/ld : avertissement : libicuuc.so.71, requis par /usr/lib/gcc/x86_64-pc-linux-gnu/12.2.0/../../../../lib/libpdfium.so, non trouvé (essayez avec -rpath ou -rpath-link) /usr/bin/ld : /usr/lib/gcc/x86_64-pc-linux-gnu/12.2.0/../../../../lib/libpdfium.so : référence indéfinie vers « u_isalpha_71 » /usr/bin/ld : /usr/lib/gcc/x86_64-pc-linux-gnu/12.2.0/../../../../lib/libpdfium.so : référence indéfinie vers « u_isspace_71 » /usr/bin/ld : /usr/lib/gcc/x86_64-pc-linux-gnu/12.2.0/../../../../lib/libpdfium.so : référence indéfinie vers « u_tolower_71 » /usr/bin/ld : /usr/lib/gcc/x86_64-pc-linux-gnu/12.2.0/../../../../lib/libpdfium.so : référence indéfinie vers « u_isalnum_71 » /usr/bin/ld : /usr/lib/gcc/x86_64-pc-linux-gnu/12.2.0/../../../../lib/libpdfium.so : référence indéfinie vers « u_toupper_71 » collect2: erreur: ld a retourné le statut de sortie 1 make[1]: [Makefile:1270 : megasync] Erreur 1 make[1] : on quitte le répertoire « /home/sylvain-sa/.cache/yay/megasync/src/MEGAsync/src/MEGASync » make: [Makefile:47 : sub-MEGASync-make_first] Erreur 2 ==> ERREUR : Une erreur s’est produite dans build().
jghodd commented on 2022-10-25 18:19 (UTC) (edited on 2022-10-25 23:17 (UTC) by jghodd)
Just a heads-up that version 4.6.8.0-2 requires icu71 even though the current version of icu is 72 on 64-bit systems.
Edit: the type narrowing issue in fs.cpp still exists and kills an i686 build, so the patch I posted below is still needed.
Edit2: if you're getting a build error re icu71, you need to rebuild libpdfium against the latest version of icu. that resolves the build issue.
MrSelfDestruct commented on 2022-10-22 14:30 (UTC)
The build of this package is now broken as of modern git versions due to the patches for CVE-2022-39253 (you can read more here: https://vielmetti.typepad.com/logbook/2022/10/git-security-fixes-lead-to-fatal-transport-file-not-allowed-error-in-ci-systems-cve-2022-39253.html)
As a workaround, it is possible to run this command and then build the megasync package: git config --global protocol.file.allow
I'm not as familiar with PKGBUILDs, but there should be some way for the maintainers of this package to fix this issue upstream, but the workaround exists for the time being for anyone who needs it.
jghodd commented on 2022-10-12 00:16 (UTC) (edited on 2022-10-12 18:09 (UTC) by jghodd)
am getting an error on the i686 build. i was able to create a patch to allow the build to complete, but due to the context of the "fix", i'm not 100% comfortable that there wouldn't be negative ripple effects. the error is one of narrowing in posix/fs.cpp - a 32-bit hex value is being assigned to an int via a #define. the patch, which i'll post, allows the build not to fail, but i'd feel more comfortable if someone more familiar with the code base could give it a thumbs-up or thumbs-down, or even code in a fix for 32-bit platforms.
please let me know if this does or does not pass the smell test.
edit: i've changed the cast to __fsword_t so that it matches the type of statfs.f_type because the only way these two constants are used are in a switch statement where they're compared to a statfs.f_type variable. tracking back through the include files, statfs.f_type is a __fsword_t which is #def'd to different types depending on the platform (32-bit vs 64-bit). so now the patch looks like this:
if anyone sees a problem with this, please let me know. what concerns me is that these 2 values would set the sign bit of a 32-bit int. but at least that would also hold true of the statfs.f_type value they're being compared against, which makes it more consistent, and it resolves the narrowing error.
pescepalla commented on 2022-09-15 07:38 (UTC)
Please add qt5-wayland as an optional dependency for those of us who use wayland.
killua99 commented on 2022-09-08 04:50 (UTC)
I just bumped the version, for my github fork, this package still doesn't install without issues
kikadf commented on 2022-05-30 16:00 (UTC)
@attila123: cmst is not a megasync dependency, it is an inedependent package. The megasync upgrade was fine (just a reinstall, not built the package) in your output. I don't know paru, maybe you upgraded all AUR packages, not only megasync, and you had a problem with the megyasync independent cmst package.
attila123 commented on 2022-05-30 14:56 (UTC)
When upgrading megasync (with paru), for some reason there was some problem with cmst. So I manually upgraded cmst (went fine), then reinstalled megasync just to make sure. The mystical problem with cmst was:
« First ‹ Previous 1 .. 3 4 5 6 7 8 9 10 11 12 13 .. 52 Next › Last »