Package Details: megasync 5.10.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: 380
Popularity: 0.77
First Submitted: 2014-09-01 18:12 (UTC)
Last Updated: 2025-04-03 17:02 (UTC)

Latest Comments

« First ‹ Previous 1 .. 46 47 48 49 50 51 52 53 Next › Last »

matthias.lisin commented on 2014-10-07 02:35 (UTC)

@jancici Rename the file and try uploading it again. Had such an issue months ago uploading images via Web (Chrome/Firefox with/without extension). Probably not client related.

jancici commented on 2014-10-06 20:45 (UTC)

if I am uploading one big file cca 200MB client is working okay if I am uploading cca 60photos total size cca 350MB client freez at photo 18, after restart app, again it freeze at 18. what do you think?

n1k9 commented on 2014-10-04 13:23 (UTC)

MEGAsync 1.0.33 is available now. Old versions are removed. The installer doesn't work.

hepha commented on 2014-09-28 06:51 (UTC)

Import the new link has BUG recommended to keep 1.0.30

matthias.lisin commented on 2014-09-20 00:15 (UTC)

MEGAsync 1.0.30 is available now. In case you always want to retrieve the latest available version, you can use this URL: https://mega.co.nz/linux/MEGAsync/Debian_7.0/amd64/megasync-Debian_7.0_amd64.deb

son_link commented on 2014-09-11 17:53 (UTC)

@ValHue a veces me pasa lo mismo, tengo que usar Google Translator XD

<deleted-account> commented on 2014-09-11 17:48 (UTC)

@otto06217 When I have to use a package from another distro because I can not access the source, I usually look at her guts. And in the case of nautilus-megasync within deb file in control.tar.gz I find the control file with the following: Depends: libatk1.0-0 (> = 1.12.4), libc6 (> = 2.4), libcairo-gobject2 (> = 1.10.0), libcairo2 (> = 1.2.4), libgcc1 (> = 1: 4.1. 1) libgdk-pixbuf2.0-0 (> = 2.22.0), libglib2.0-0 (> = 2.16.0), libgtk-3-0 (> = 3.0.0), libnautilus-extension1a (> = 2.91), libpango1.0-0 (> = 1.14.0), libstdc ++ 6 (> = 4.1.1), megasync I think what, if debian have not been wrong, nautilus-megasync has megasync dependence. I like the irony, but "Something is rotten in the state of Denmark." I do not get it. Best regards from Spain. PD:sorry for my English, translated by google.

otto06217 commented on 2014-09-11 14:18 (UTC)

@ValHue You said: I propose another solution and not break anything, why not rename /usr/bin/megasync from megatools package to /usr/bin/megasync-cli I say to you this is not an option. And by the way: Regarding nautilus-megasync I couldn't after an exhaustive code review recognise any dependencies to megasync itself. Megasync consists of many of third software, e.g. curl 7.32 and sodium 0.5. I'm starting to worry. AFAIK nautilus-mega doesn't and megatools as well. Something is rotten in the state of Denmark. I'm not amused, trust me.

otto06217 commented on 2014-09-11 13:09 (UTC)

@ValHue Many thanks for your comment. :-) The problem is MEGA was drawing back the opportunity to obtain the sources without authentication. http://build.developers.mega.co.nz:82/MEGASync/Fedora_20/src/ IMHO That's a strange behavior.

<deleted-account> commented on 2014-09-09 18:50 (UTC)

@otto06217: - Do that would break the dependency of nautilus-megasync. Son_link has already scored that conflicts with megatools. I propose another solution and not break anything, why not rename /usr/bin/megasync from megatools package to /usr/bin/megasync-cli? >>Why no source build? Sources are here: - Why is it necessary to authenticate? ;-) >>I'm a Ubuntu Packager, sorry for that. - Nobody is perfect.

« First ‹ Previous 1 .. 46 47 48 49 50 51 52 53 Next › Last »