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

Sources (6)

Latest Comments

« First ‹ Previous 1 .. 39 40 41 42 43 44 45 46 47 48 49 .. 52 Next › Last »

sl1pkn07 commented on 2015-05-23 14:43 (UTC)

mkdir -p ${pkgdir}/usr/lib ln -s /usr/lib/libcrypto++.so ${pkgdir}/usr/lib/libcrypto++.so.10 ln -s /usr/lib/libcryptopp.so ${pkgdir}/usr/lib/libcryptopp.so.6 ln -s /usr/lib/libcrypto.so ${pkgdir}/usr/lib/libcrypto.so.10 ln -s /usr/lib/libssl.so.1.0.0 ${pkgdir}/usr/lib/libssl.so.10 in the pkgbuild and rm /usr/lib/libcrypto++.so.10 rn /usr/lib/libcryptopp.so.6 rm /usr/lib/libcrypto.so.10 rm /usr/lib/libssl.so.10 in .install not need anymore greetings

yan12125 commented on 2015-05-15 08:22 (UTC)

In megasync.install there's a typo: rn => rm

eherranzr commented on 2015-05-09 08:43 (UTC)

Getting the following error: /tmp/yaourt-tmp-emilio/aur-megasync/src tar (child): data.tar.gz: No se puede open: No existe el fichero o el directorio tar (child): Error is not recoverable: exiting now tar: Child returned status 2 tar: Error is not recoverable: exiting now

xstefen commented on 2015-05-08 20:58 (UTC)

The current md5sum for x86_64 is a96197054f4c4a9fbc74185704a34c94 for those who are trying to install right now

eherranzr commented on 2015-05-07 15:37 (UTC)

MadCat_X I get the following error using your PKGBUILD: /tmp/yaourt-tmp-emilio/aur-megasync/pkg/megasync no package supplied

MadCat_X commented on 2015-05-06 17:31 (UTC)

It's not just Arch, Fedora repository is broken (again) too. I have no idea what level of incompetence this takes but as far as I can tell they keep signing their packages with a wrong key. The funniest part is that sometimes they get it right, sometimes I have to skip the signature check to get the update. I reported this a while back and although they acknowledged the problem it doesn't look like they have done much about it. FWIW, if anybody wants the latest update, here's my PKGBUILD that uses the Fedora binaries instead of Debian ones. http://pastebin.com/t4f2C20U

a172 commented on 2015-05-05 21:59 (UTC)

Update on MEGA's Arch repos. It is severely busted. 1) The packages provided are actually empty. 2) The Arch_Extra folder does not have the public key available, although, it does seem to be present in other folders. 3) There is a version mismatch between the database and the actual files. There is a public key for the Debian 7/8 repos, but the signatures are not for the actual packages we are downloading. It is for the 'Release' text file which contains the checksums for the 'Packages' files, which contains the descriptions (including checksums) of the files in the repo. Since the public key is coming from the same source as the signatures, there PGP is only acting as a super complicated checksum. Of another checksum. Of the original checksum. All from the same source. So PGP is useless here. It does look like we can pull the checksum dynamically via shell script magic, though. This is a bit of an ugly example (the | grep | tail | cut could probably be done with a single sed/awk), but it does work (I only tested x86_64). http://sprunge.us/HBOV tl;dr The MEGA Arch repo is busted. Don't use any part of it. The files (and therefore the checksums) look like they change a lot, even without a version bump. We can do an ugly workaround by pulling the checksum dynamically from the debian repo provided. EDIT: Merged my wall of comments into 1 comment with only the relevant info. Also, I will keep on MEGA to try and fix their Arch repo, although I don't expect anything to change.

« First ‹ Previous 1 .. 39 40 41 42 43 44 45 46 47 48 49 .. 52 Next › Last »