Retrieving repository ‘MEGAsync’ metadata …[error]Repository ‘MEGAsync’ is invalid.
[MEGAsync|http://mega.nz/linux/MEGAsync/openSUSE_Leap_42.1/] Valid metadata not found at specified URL
Please check if the URIs defined for this repository are pointing to a valid repository.
Skipping repository ‘MEGAsync’ because of the above error.
File /var/tmp/TmpFile.IiyI09 doesn’t contain public key data
Please check if the URIs defined for this repository are pointing to a valid repository.
Skipping repository ‘MEGAsync’ because of the above error.
Already tried “zypper clean”/“zpper -v clean”/“zypperclean --all”/ “rpmdb–rebuilddb” ,cleaning /var/tmp and restarting system, nothing seems to work. I don’t know why only i get this Error when other users seems to have it working fine in Leap.
File /var/tmp/TmpFile.IiyI09 doesn’t contain public key data
There’s nothing you can do about the above error, it’s the fault of the people who set up the repo.
But you have a couple of options…
First, delete your non-working Megasync repo
zypper rm MEGAsyn
Then, Option 1 - Install the repo without doing the security check
zypper ar -f -G http://mega.nz/linux/MEGAsync/openSUSE_Leap_42.1/ MEGAsync
Option 2 Install just the packages without installing the repo
The repo is tiny, in fact it looks like you only need one package and an optional second package if you want Gnome Nautilus integration.
Run the following from a root console
zypper in https://mega.nz/linux/MEGAsync/openSUSE_Leap_42.1/x86_64/megasync-2.9.5-1.1.x86_64.rpm
And, if you want the Nautilus integration
zypper in https://mega.nz/linux/MEGAsync/openSUSE_Leap_42.1/x86_64/nautilus-megasync-2.9.5-1.1.x86_64.rpm
So any idea why only i get that error ? I have asked others over IRC using Leap to check and they said its running fine without errors and when i contacted the Mega developers they also said its running fine when they checked it for Leap in a VM.
A FYI
When running Argon (and other bleeding edge versions of LEAP),
You’re not running a standard version of your distro and a bleeding edge version is actually <likely> to have unresolved bugs, and this might be one of them. Could be that Argon is trying the very latest and maybe proposed versions of repos and the test code may not contain backwards compatible code to support older versions.
Only the Desktop Environment which is KDE is bleeding edge from Argon repos, the core system is Leap and still as stable as Leap. And i also have other stable DEs installed along side
sudo zypper ar -f -n Megasync http://mega.nz/linux/MEGAsync/openSUSE_Leap_42.1/ Megasync
[sudo] wachtwoord voor root:
Bron 'Megasync' toevoegen ...........................................................................................................................[gereed]
Installatiebron 'Megasync' is met succes toegevoegd:
Ingeschakeld : Ja
Autovernieuwen : Ja
GPG-controle : Ja
Prioriteit : 99
URI : http://mega.nz/linux/MEGAsync/openSUSE_Leap_42.1/
glosscomputer@knurpht:~> sudo zypper ref
Installatiebron 'Chrome' is actueel.
Installatiebron 'KDExtra' is actueel.
Installatiebron 'Knurpht' is actueel.
Ophalen van metadata uit installatiebron 'Megasync' ------------------------------------------------------------------------------------------------------|]
**Een nieuwe handtekening voor een installatiebron of pakket is ontvangen:**
Installatiebron: Megasync
Sleutelnaam: MegaLimited <support@mega.co.nz>
Vingerafdruk van sleutel: 8F208FBF 12FEE766 AA32AEAF 03C3AD3A 7F068E5D
Sleutel aangemaakt: za 07 nov 2015 10:12:33 CET
Sleutel verloopt op: di 04 nov 2025 10:12:33 CET
Rpm-naam: gpg-pubkey-7f068e5d-563dc081
Wilt u de sleutel verwerpen, tijdelijk vertrouwen of altijd vertrouwen? **[v/t/a/? alle opties tonen] (v): **t
Ophalen van metadata uit installatiebron 'Megasync' .................................................................................................[gereed]
Cache van bron 'Megasync' bouwen ....................................................................................................................[gereed]
Installatiebron 'NVIDIA' is actueel.
Installatiebron 'Packman' is actueel.
Installatiebron 'TWoss' is actueel.
Installatiebron 'TWnonoss' is actueel.
Installatiebron 'TWup' is actueel.
Alle installatiebronnen zijn vernieuwd.
It’s in dutch, but as you can see it works fine adding the repo to my Tumbleweed install ( and removing it immediately afterwards ). Same on my Leap install.
I contacted Mega related this issue and exchanged few emails sending the information they asked for and this was final advise they gave me, looks like even they are not sure where the problem is:
Dear MEGA user,
Our developers advised:
Possible response to the user:
Everything seems ok, the repository, the connectivity.
Some people have reported similar issues with other repositories related to problems with `zypper`
Some claim to have it solved by reinstalling a failing gpg2:
```zypper in --force gpg2```
Some others report success deleting /var/cache/zypp/raw/<REPONAME> :
```rm -r /var/cache/zypp/raw/MEGAsync*```
Doing a
```zypper -vvv clean -a```
and
```zypper -vvv refresh```
later will check for success.
Some suggest to reinstall zypper (that's not recommended).
Also, ensure that
```rpm -q gpg-pubkey --qf '%{name}-%{version}-%{release} --> %{summary}
'```
Contains:
```gpg-pubkey-7f068e5d-563dc081 --> gpg(MegaLimited <[EMAIL="support@mega.co.nz"]support@mega.co.nz[/EMAIL]>)```
Anyway, in the worst case scenario, you can manually delete mega repository:
```rm /etc/zypp/repos.d/megasync.repo```
to avoid further error messages.
In this case, your megasync application won't be updated. We would recommend you to regularly check for updates (at `[https://mega.nz/#sync`](https://mega.nz/#sync)) to keep on with the latest features.