$ yay -S megasync
:: There are 4 providers available for megasync:
:: Repository AUR
1) megasync 2) megasync-bin 3) megasync-git 4) megasync-nopdfium
Enter a number (default=1):
==> 2
:: Checking for conflicts...
:: Checking for inner conflicts...
[Aur:1] megasync-bin-4.6.3-4
1 megasync-bin (Build Files Exist)
==> Packages to cleanBuild?
==> [N]one [A]ll [Ab]ort [I]nstalled [No]tInstalled or (1 2 3, 1-3, ^4)
==>
:: PKGBUILD up to date, Skipping (1/0): megasync-bin
1 megasync-bin (Build Files Exist)
==> Diffs to show?
==> [N]one [A]ll [Ab]ort [I]nstalled [No]tInstalled or (1 2 3, 1-3, ^4)
==>
:: (1/1) Parsing SRCINFO: megasync-bin
==> Making package: megasync-bin 4.6.3-4 (Thursday 10 March 2022 07:16:27 PM)
==> Retrieving sources...
-> Downloading megasync-4.6.3-4-x86_64.pkg.tar.zst...
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (22) The requested URL returned error: 404
==> ERROR: Failure while downloading https://mega.io/linux/repo/Arch_Extra/x86_64/megasync-4.6.3-4-x86_64.pkg.tar.zst
Aborting...
-> error downloading sources: megasync-bin
context: exit status 1
==> Making package: megasync-bin 4.6.3-4 (Thursday 10 March 2022 07:16:29 PM)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
-> Downloading megasync-4.6.3-4-x86_64.pkg.tar.zst...
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (22) The requested URL returned error: 404
==> ERROR: Failure while downloading https://mega.io/linux/repo/Arch_Extra/x86_64/megasync-4.6.3-4-x86_64.pkg.tar.zst
Aborting...
-> error making: megasync-bin
What should I do ?
I0F
March 10, 2022, 2:07pm
2
You could edit the PKGBUILD so it points to the correct package version.
The current version on that address is megasync-4.6.5-2-x86_64.pkg.tar.zst .
The version inside the current PKGBUILD is 4.6.3. Change that to 4.6.5 and it should work. Also set pkgrel to 2. Someone correct me if I’m wrong.
The package also is marked out of date.
2 Likes
pebcak
March 10, 2022, 2:09pm
3
Alternatively, the following might work as well:
sudo pacman -U https://mega.io/linux/repo/Arch_Extra/x86_64/megasync-4.6.5-2-x86_64.pkg.tar.zst
1 Like
If I do that how will I update megaSYNC in the future ?
So far I just ran yay
and everything got updated including AUR packages.
Mega sync is part of the arch repo in extra. So it will update like everything else does.
Then why can’t I install megasync using pacman ?
$ sudo pacman -S megasync
[sudo] password for home:
error: target not found: megasync
I0F
March 10, 2022, 2:12pm
7
If I’m not mistaken it will update normally as soon as a new PKGBUILD is uploaded to the AUR.
@ricklinux is it? I can’t find it in the official repos.
1 Like
dalto
March 10, 2022, 2:15pm
8
Err…are you sure? It isn’t on my mirror…
Sorry, if i misinformed. I just saw @pebcak command and saw arch repo extra. My bad!
Edit: Your right it is an AUR package.
I really need megaSYNC. Can’t manage without it. I hope it gets fixed soon.
pebcak
March 10, 2022, 2:17pm
11
I guess you would check for the updates yourself and install them manually.
Perhaps the best approach is as per @I0F suggestion to edit the PKGBUILD.
Do none of them in the AUR work?
I0F
March 10, 2022, 2:20pm
13
As it seems it was flagged as “out-of-date” just today. I strongly believe it will be updated in one or two days. Maybe even today.
2 Likes
I read that the word “bin” means no need for compiling. I have always selected the bin for both megaSYNC and google-earth-pro.
This error is reported on the megasync-bin
AUR page . Also as suggested by @I0F it is marked out-of-date so probably for now you can install megsync
from AUR instead of the bin version.
1 Like
But that will be time consuming coz of compiling. I will just wait 2-3 days and try again.
I will keep trying and report back when successful.
pebcak
March 10, 2022, 2:38pm
19
You could also add their repo to your /etc/pacman.conf:
###REPO for MEGA###
[DEB_Arch_Extra]
SigLevel = Required TrustedOnly
Server = https://mega.nz/linux/repo/Arch_Extra/x86_64/
When prompted, import the signing key and locally sign it with:
sudo pacman-key --lsign-key B01C811880480C854C73EC7E1A664B787094A482
pacman -Ss megasync
DEB_Arch_Extra/dolphin-megasync 3.6.6-2
Extension for KDE based file managers to interact with Megasync
DEB_Arch_Extra/megasync 4.6.5-2
Easy automated syncing between your computers and your MEGA cloud drive
DEB_Arch_Extra/megasync-debug 4.6.5-2
Detached debugging symbols for megasync
DEB_Arch_Extra/nautilus-megasync 3.6.6-2
Easy automated syncing between your computers and your MEGA cloud drive
DEB_Arch_Extra/thunar-megasync 4.3.0-1
Extension for Thunar to interact with Megasync
1 Like
Adding their repo Vs Installing from AUR, which is better from a security angle ?
I0F
March 10, 2022, 2:40pm
21
In the end it does pretty much the same. I personally would wait for the AUR so I don’t have another repo inside pacman.conf, but if you need it now, this would probably be the easiest solution.