Sorry if this sounds like another post but I have read lots of them and have not found solve for my problem yet. Since my 12.1->12.2 DVD upgrade:
if I try to update from YAST I get: There was an error in the repository initialization. |]Valid metadata not found at specific URL(s) History: -File /var/tmp/TmpFile.gbTMdE doesn’t contain public key data
if I try to update from zypper I get (strangely enough, one repo seems to almost work (and I think I’ve even applied 6 updates from it), but the other three do not):
Repository ‘openSUSE-12.2-Non-Oss’ is up to date.
Retrieving repository ‘openSUSE-12.2-Oss’ metadata …[error]
Repository ‘openSUSE-12.2-Oss’ is invalid.
|] Valid metadata not found at specified URL(s)
Please check if the URIs defined for this repository are pointing to a valid repository.
Skipping repository ‘openSUSE-12.2-Oss’ because of the above error.
Retrieving repository ‘openSUSE-12.2-Update’ metadata …[error]
Repository ‘openSUSE-12.2-Update’ is invalid.
|] Valid metadata not found at specified URL(s)
Please check if the URIs defined for this repository are pointing to a valid repository.
Skipping repository ‘openSUSE-12.2-Update’ because of the above error.
Retrieving repository ‘openSUSE-12.2-Update-Non-Oss’ metadata …[error]
Repository ‘openSUSE-12.2-Update-Non-Oss’ is invalid.
|] Valid metadata not found at specified URL(s)
Please check if the URIs defined for this repository are pointing to a valid repository.
Skipping repository ‘openSUSE-12.2-Update-Non-Oss’ because of the above error.
Some of the repositories have not been refreshed because of an error.
I have tried (not necessarily in the order listed here) (if I can even remember all the things I’ve tried here):
removing and replacing repositories (including with other sites from the mirrors list site)
using the --no-gpg-checks option
zypper ref, ref --force, and clean -a, a number of times
downloading rpm’s and reinstalling zypper and gpg2
My zypper lr -d looks like this (have tried the URL(s) with and without the slashes on the end:
| Alias | Name | Enabled | Refresh | Priority | Type | URI | Service
One of the posts I’ve read talked about deleting things in /var/cache/zypp, but I can’t remember it exactly and I’ve been hesitant about how much I can safely delete from there.
I cannot think of anything else to try. If anyone has solved this and has gotten their updates working, any help is appreciated!!! Signed, “exhausted”
People will probably not respond to your queries in these forums if you don’t post terminal output within “code” tags. Use the “#” menu in advanced post editor.
Thanks, vazhavandan
I also read caf4926’s tutorial on how to do the code tags
Was a little bit unsure because wanted to show you output of both commands (after su, of course) that you recommended, and tried putting them both between same set of code tags.
Here’s what I got from zypper clean --all and zypper ref -f. Thanks again.
All repositories have been cleaned up.
Forcing raw metadata refreshRetrieving repository 'openSUSE-12.2-Non-Oss' metadata ------------------------------------\]
File 'content' from repository 'openSUSE-12.2-Non-Oss' is signed with an unknown key ''. Continue? [yes/no] (no): yes
Retrieving repository 'openSUSE-12.2-Non-Oss' metadata .................................[done]
Forcing building of repository cache
Building repository 'openSUSE-12.2-Non-Oss' cache ......................................[done]
Forcing raw metadata refresh
Retrieving repository 'openSUSE-12.2-Oss' metadata ....................................[error]
Repository 'openSUSE-12.2-Oss' is invalid.
|] Valid metadata not found at specified URL(s)
Please check if the URIs defined for this repository are pointing to a valid repository.
Skipping repository 'openSUSE-12.2-Oss' because of the above error.
Forcing raw metadata refresh
Retrieving repository 'openSUSE-12.2-Update' metadata .................................[error]
Repository 'openSUSE-12.2-Update' is invalid.
|] Valid metadata not found at specified URL(s)
Please check if the URIs defined for this repository are pointing to a valid repository.
Skipping repository 'openSUSE-12.2-Update' because of the above error.
Forcing raw metadata refresh
Retrieving repository 'openSUSE-12.2-Update-Non-Oss' metadata .........................[error]
Repository 'openSUSE-12.2-Update-Non-Oss' is invalid.
|] Valid metadata not found at specified URL(s)
Please check if the URIs defined for this repository are pointing to a valid repository.
Skipping repository 'openSUSE-12.2-Update-Non-Oss' because of the above error.
Some of the repositories have not been refreshed because of an error.
Also do this for debug repos and source repos(disable and stop auto refresh)
zypper mr -d -R 1 2 3 6
Do this for oss,non-oss,update,update-non-oss(enable and auto refresh)
zypper mr -e -r 4 5 7 8
Although I’d be surprised you’d have this problem with the core repos, whenever I see this error I fire up a web browser with the repodata URI.
You can then compare the URI of working repos to modify the malfunctioning URI.
Not sure if you somehow imported corrupted or incorrect GPG keys, whether you might have to mark those invalid or hopefully you can simply authorize new keys when prompted.
Replying to overall thread here; thanks to all who have offered suggestions so far; Would still like to get YAST or zypper updates going, did clearing out of tmp and cache directories as described here and also all of the zypper clean and mr commands; zypper ref -f still gives the same output as I have put in the code box before. I did notice something interesting which is that after you run the zypper ref -f after clearing out the cache directory, you see this when you look at the cache directories: the one for non-oss has things in it (the repo that I was able to get 6 updates to work with), the others are all empty. I wonder what this means?:
linux:/var/cache/zypp/raw # cd repo-non-osslinux:/var/cache/zypp/raw/repo-non-oss # ls -al
total 16
drwxr-xr-x 4 root root 248 Mar 11 22:59 .
drwxr-xr-x 6 root root 176 Mar 11 22:59 ..
-rw-r--r-- 1 root root 2591 Mar 11 22:59 content
-rw-r--r-- 1 root root 481 Mar 11 22:59 content.asc
-rw-r--r-- 1 root root 673 Mar 11 22:59 gpg-pubkey-307e3d54-4be01a65.asc
-rw-r--r-- 1 root root 1059 Mar 11 22:59 gpg-pubkey-3dbdc284-4be1884d.asc
drwxr-xr-x 2 root root 72 Mar 11 22:59 media.1
drwxr-xr-x 3 root root 72 Mar 11 22:59 suse
linux:/var/cache/zypp/raw/repo-non-oss # cd ../repo-oss
linux:/var/cache/zypp/raw/repo-oss # ls -al
total 0
drwxr-xr-x 2 root root 48 Mar 11 22:59 .
drwxr-xr-x 6 root root 176 Mar 11 22:59 ..
linux:/var/cache/zypp/raw/repo-oss # cd ../repo-update
linux:/var/cache/zypp/raw/repo-update # ls -al
total 0
drwxr-xr-x 2 root root 48 Mar 11 22:59 .
drwxr-xr-x 6 root root 176 Mar 11 22:59 ..
linux:/var/cache/zypp/raw/repo-update # cd ../repo-update-non-oss
linux:/var/cache/zypp/raw/repo-update-non-oss # ls -al
total 0
drwxr-xr-x 2 root root 48 Mar 11 22:59 .
drwxr-xr-x 6 root root 176 Mar 11 22:59 ..
linux:/var/cache/zypp/raw/repo-update-non-oss #
I found that yesterday the repos are non responsive probably due to heavy activity . I think they are creating lot of packages for 12.3 release. I couldn’t refresh repos yesterday. I dod have a slow internet though
i don’t think we have https repos. you can disable all repos using zypper (zypper mr --disable --all)
open YaST. delete the repo keys from YaST.Close YaST. Then do zypper ref -f in terminal .
I remember seeing a button on the YAST repositories maintenance screen that was called “GPG Keys…”. I’ve gone into this button several times and have never found anything in there. Am I supposed to have anything (like keys?) stored in there?
Is there any way that I can do some kind of “brute force” download of the repo and/or key information back into my system by using, for example, my web browser, to get things re-synchronized (if that’s the problem)?
That screen should have always have some keys . The situation you are facing is very unique
The force sync process is “zypper ref -f” after “zypper clean --all”.
Tried several attempts at downloading key files from the download.opensuse.org sites themselves but never could get the add function in the yast2 repo screen to accept any of it as a valid gpg key.
Even tried mounting my downloaded install/upgrade DVD again and re-installing zypper, gpg2, and yast2 from there.
Still get the “valid metadata not found” and “Repository ‘(name)’ is invalid” messages from zypper ref -f, and when attempting to do Online Update in yast I get the message like “/var/tmp/TmpFile.aiq0AW doesn’t contain public key data” (when you go into /var/tmp and look for such a file, it isn’t even there).
Somewhere I came across someone saying that instead of using download.opensuse.org, you could go to another repo site for the same things?
Or is there a way to get patches and/or updates by doing something different altogether from yast and/or zypper? (Like getting rpm to somehow get my updates for me? Or like the way that in the Microsoft world people can go to a site like windowsupdate.microsoft.com and run their updates through their web browser?)
that would be a great idea. use this to find your nearest and best mirror openSUSE Download Mirrors - Overview
You may export your existing repos into a .repo file . These files are readable by any text editor.
zypper lr --export /home/<profileName>/repos/foo.repo
after export remove existing repos
you can do
zypper rr 1 2 3 4 5...
finally before adding repos from mirrors remove any leftover gpg repo keys in YaST
Also did we try and disable ipv6 on your machine. Does your ISP support IPV6? If not this mess may be due to it
On 2013-03-14 04:46, slcro wrote:
> Still get the “valid metadata not found” and “Repository ‘(name)’ is
> invalid” messages from zypper ref -f, and when attempting to do Online
> Update in yast I get the message like “/var/tmp/TmpFile.aiq0AW doesn’t
> contain public key data” (when you go into /var/tmp and look for such a
> file, it isn’t even there).
Maybe you have defined a repo pointing to a temporary space that is no
longer there, and of course has no key (it may happen with one click
installs). Check the repo list to see if that is the case and remove the
repo.
Besides zypper commands, the repo list is stored at
“/etc/zypp/repos.d/”, where you can remove the offending directory.
–
Cheers / Saludos,
Carlos E. R.
(from 11.4, with Evergreen, x86_64 “Celadon” (Minas Tirith))
This still looks “as per recommended spec” to me, unless I’m not seeing something. I exported my repos to a file in my own home folder, and was getting ready to delete them out and add some new ones, one by one, from another URL (although I haven’t been having much success with this so far).
I was thinking about how when I try to do Online Update in yast, I was getting those errors about this or that /var/tmp file saying that it “doesn’t contain public key data”, and being one who likes to try lots of “list” commands when I have a problem (it can’t hurt, right?), I tried the following and got the following errors (didn’t get the scroll bar on this code block):
linux:/home/stevec # gpg2 --list-public-keys
gpg: Fatal: libgcrypt is too old (need 1.4.0, have 1.2.4)
linux:/home/stevec # gpg2 --list-secret-keys
gpg: Fatal: libgcrypt is too old (need 1.4.0, have 1.2.4)
linux:/home/stevec # gpg2 --list-sigs
gpg: Fatal: libgcrypt is too old (need 1.4.0, have 1.2.4)
I tried downloading the closest thing I could find for this for i586 OpenSuSE 12.2, which was a file called libgcrypt11-1.5.0-9.2.2.i586.rpm, and did a rpm --install --force on it, but this did not do any good, still get the same errors as above. (I had already previously done the same rpm command with a downloaded libzypp-11.6.2-2.1.2.i586.rpm) .
Also, everything I’ve been doing in the last day or so has been with the IPv6 shut off from Yast>Network Devices>Network Settings>Global Options (assuming that all I needed to do was uncheck this panel’s “Enable IPv6” box and re-boot)…
Still wondering about the “[LEFT]Fatal: libgcrypt is too old (need 1.4.0, have 1.2.4)” when asking gpg2 to list my public keys, but went ahead with the following, trying to pull repos from the Linux Foundation in Portland, Oregon:
[/LEFT]
linux:~ # zypper rr 5 6 7 8 9
Removing repository 'openSUSE-12.2-Non-Oss' ............................................[done]
Repository 'openSUSE-12.2-Non-Oss' has been removed.
Removing repository 'openSUSE-12.2-Oss' ................................................[done]
Repository 'openSUSE-12.2-Oss' has been removed.
Removing repository 'openSUSE-12.2-Source' .............................................[done]
Repository 'openSUSE-12.2-Source' has been removed.
Removing repository 'openSUSE-12.2-Update' .............................................[done]
Repository 'openSUSE-12.2-Update' has been removed.
Removing repository 'openSUSE-12.2-Update-Non-Oss' .....................................[done]
Repository 'openSUSE-12.2-Update-Non-Oss' has been removed.
linux:~ # zypper ar -c -n 'openSUSE-12.2-Non-Oss' http://suse.mobile-central.org/distribution/12.2/repo/non-oss/ repo-non-oss
Adding repository 'openSUSE-12.2-Non-Oss' ..............................................[done]
Repository 'openSUSE-12.2-Non-Oss' successfully added
Enabled: Yes
Autorefresh: No
GPG check: Yes
URI: http://suse.mobile-central.org/distribution/12.2/repo/non-oss/
linux:~ # zypper ar -c -n 'openSUSE-12.2-Oss' http://suse.mobile-central.org/distribution/12.2/repo/oss/ repo-oss
Adding repository 'openSUSE-12.2-Oss' ..................................................[done]
Repository 'openSUSE-12.2-Oss' successfully added
Enabled: Yes
Autorefresh: No
GPG check: Yes
URI: http://suse.mobile-central.org/distribution/12.2/repo/oss/
linux:~ # zypper ar -c -n 'openSUSE-12.2-Source' http://suse.mobile-central.org/source/distribution/12.2/repo/oss/ repo-source
Adding repository 'openSUSE-12.2-Source' ...............................................[done]
Repository 'openSUSE-12.2-Source' successfully added
Enabled: Yes
Autorefresh: No
GPG check: Yes
URI: http://suse.mobile-central.org/source/distribution/12.2/repo/oss/
linux:~ # zypper ar -c -n 'openSUSE-12.2-Update' http://suse.mobile-central.org/update/12.2/ repo-update
Adding repository 'openSUSE-12.2-Update' ...............................................[done]
Repository 'openSUSE-12.2-Update' successfully added
Enabled: Yes
Autorefresh: No
GPG check: Yes
URI: http://suse.mobile-central.org/update/12.2/
linux:~ # zypper ar -c -n 'openSUSE-12.2-Update-Non-Oss' http://suse.mobile-central.org/update/12.2-non-oss/ repo-update-non-oss
Adding repository 'openSUSE-12.2-Update-Non-Oss' .......................................[done]
Repository 'openSUSE-12.2-Update-Non-Oss' successfully added
Enabled: Yes
Autorefresh: No
GPG check: Yes
URI: http://suse.mobile-central.org/update/12.2-non-oss/
linux:~ # zypper lr -d
# | Alias | Name | Enabled | Refresh | Priority | Type | URI | Service
--+---------------------------+------------------------------------+---------+---------+----------+--------+-------------------------------------------------------------------+--------
1 | openSUSE_12.2-1.6 | openSUSE 12.2-1.6 | Yes | No | 99 | yast2 | dvd:///?devices=/dev/sr0 |
2 | repo-debug | openSUSE-12.2-Debug | No | No | 99 | yast2 | http://download.opensuse.org/debug/distribution/12.2/repo/oss/ |
3 | repo-debug-update | openSUSE-12.2-Update-Debug | No | No | 99 | NONE | http://download.opensuse.org/debug/update/12.2/ |
4 | repo-debug-update-non-oss | openSUSE-12.2-Update-Debug-Non-Oss | No | No | 99 | NONE | http://download.opensuse.org/debug/update/12.2-non-oss/ |
5 | repo-non-oss | openSUSE-12.2-Non-Oss | Yes | No | 99 | yast2 | http://suse.mobile-central.org/distribution/12.2/repo/non-oss/ |
6 | repo-oss | openSUSE-12.2-Oss | Yes | No | 99 | yast2 | http://suse.mobile-central.org/distribution/12.2/repo/oss/ |
7 | repo-source | openSUSE-12.2-Source | Yes | No | 99 | yast2 | http://suse.mobile-central.org/source/distribution/12.2/repo/oss/ |
8 | repo-update | openSUSE-12.2-Update | Yes | No | 99 | rpm-md | http://suse.mobile-central.org/update/12.2/ |
9 | repo-update-non-oss | openSUSE-12.2-Update-Non-Oss | Yes | No | 99 | rpm-md | http://suse.mobile-central.org/update/12.2-non-oss/ |
[LEFT]
(Did 5 6 7 8 and 9 because the first one was my mounted install DVD and the next three were the debug ones that I figured I wasn’t using anyway, if that assumption is OK (?))
Then tried to refresh and see if updates would work, no success, and went ahead with the zypper clean all and refresh force sequence again:
[/LEFT]
linux:~ # zypper ref
Retrieving repository 'openSUSE-12.2-Non-Oss' metadata ------------------------------------\]
File 'content' from repository 'openSUSE-12.2-Non-Oss' is signed with an unknown key ''. Continue? [yes/no] (no): yes
Retrieving repository 'openSUSE-12.2-Non-Oss' metadata .................................[done]
Building repository 'openSUSE-12.2-Non-Oss' cache ......................................[done]
Retrieving repository 'openSUSE-12.2-Oss' metadata ....................................[error]
Repository 'openSUSE-12.2-Oss' is invalid.
|] Valid metadata not found at specified URL(s)
Please check if the URIs defined for this repository are pointing to a valid repository.
Skipping repository 'openSUSE-12.2-Oss' because of the above error.
Retrieving repository 'openSUSE-12.2-Source' metadata -------------------------------------/]
File 'content' from repository 'openSUSE-12.2-Source' is signed with an unknown key ''. Continue? [yes/no] (no): yes
Retrieving repository 'openSUSE-12.2-Source' metadata ..................................[done]
Building repository 'openSUSE-12.2-Source' cache .......................................[done]
Retrieving repository 'openSUSE-12.2-Update' metadata .................................[error]
Repository 'openSUSE-12.2-Update' is invalid.
|] Valid metadata not found at specified URL(s)
Please check if the URIs defined for this repository are pointing to a valid repository.
Skipping repository 'openSUSE-12.2-Update' because of the above error.
Retrieving repository 'openSUSE-12.2-Update-Non-Oss' metadata .........................[error]
Repository 'openSUSE-12.2-Update-Non-Oss' is invalid.
|] Valid metadata not found at specified URL(s)
Please check if the URIs defined for this repository are pointing to a valid repository.
Skipping repository 'openSUSE-12.2-Update-Non-Oss' because of the above error.
Some of the repositories have not been refreshed because of an error.
linux:~ # zypper list-updates
Error building the cache:
|] Valid metadata not found at specified URL(s)
Warning: Disabling repository 'openSUSE-12.2-Oss' because of the above error.
Error building the cache:
|] Valid metadata not found at specified URL(s)
Warning: Disabling repository 'openSUSE-12.2-Update' because of the above error.
Error building the cache:
|] Valid metadata not found at specified URL(s)
Warning: Disabling repository 'openSUSE-12.2-Update-Non-Oss' because of the above error.
Loading repository data...
Reading installed packages...
No updates found.
linux:~ # zypper clean --all
All repositories have been cleaned up.
linux:~ # zypper ref -f
Forcing raw metadata refresh
Retrieving repository 'openSUSE 12.2-1.6' metadata .....................................[done]
Forcing building of repository cache
Building repository 'openSUSE 12.2-1.6' cache ..........................................[done]
Forcing raw metadata refresh
Retrieving repository 'openSUSE-12.2-Non-Oss' metadata -------------------------------------]
File 'content' from repository 'openSUSE-12.2-Non-Oss' is signed with an unknown key ''. Continue? [yes/no] (no): yes
Retrieving repository 'openSUSE-12.2-Non-Oss' metadata .................................[done]
Forcing building of repository cache
Building repository 'openSUSE-12.2-Non-Oss' cache ......................................[done]
Forcing raw metadata refresh
Retrieving repository 'openSUSE-12.2-Oss' metadata ....................................[error]
Repository 'openSUSE-12.2-Oss' is invalid.
|] Valid metadata not found at specified URL(s)
Please check if the URIs defined for this repository are pointing to a valid repository.
Skipping repository 'openSUSE-12.2-Oss' because of the above error.
Forcing raw metadata refresh
Retrieving repository 'openSUSE-12.2-Source' metadata -------------------------------------|]
File 'content' from repository 'openSUSE-12.2-Source' is signed with an unknown key ''. Continue? [yes/no] (no): yes
Retrieving repository 'openSUSE-12.2-Source' metadata ..................................[done]
Forcing building of repository cache
Building repository 'openSUSE-12.2-Source' cache .......................................[done]
Forcing raw metadata refresh
Retrieving repository 'openSUSE-12.2-Update' metadata .................................[error]
Repository 'openSUSE-12.2-Update' is invalid.
|] Valid metadata not found at specified URL(s)
Please check if the URIs defined for this repository are pointing to a valid repository.
Skipping repository 'openSUSE-12.2-Update' because of the above error.
Forcing raw metadata refresh
Retrieving repository 'openSUSE-12.2-Update-Non-Oss' metadata .........................[error]
Repository 'openSUSE-12.2-Update-Non-Oss' is invalid.
|] Valid metadata not found at specified URL(s)
Please check if the URIs defined for this repository are pointing to a valid repository.
Skipping repository 'openSUSE-12.2-Update-Non-Oss' because of the above error.
Some of the repositories have not been refreshed because of an error.
[LEFT]
Also tried refresh force again, with “-s” to refresh services:
[/LEFT]
linux:~ # zypper ref -f -s
All services have been refreshed.
Forcing raw metadata refresh
Retrieving repository 'openSUSE 12.2-1.6' metadata .....................................[done]
Forcing building of repository cache
Building repository 'openSUSE 12.2-1.6' cache ..........................................[done]
Forcing raw metadata refresh
Retrieving repository 'openSUSE-12.2-Non-Oss' metadata -------------------------------------]
File 'content' from repository 'openSUSE-12.2-Non-Oss' is signed with an unknown key ''. Continue? [yes/no] (no): yes
Retrieving repository 'openSUSE-12.2-Non-Oss' metadata .................................[done]
Forcing building of repository cache
Building repository 'openSUSE-12.2-Non-Oss' cache ......................................[done]
Forcing raw metadata refresh
Retrieving repository 'openSUSE-12.2-Oss' metadata ....................................[error]
Repository 'openSUSE-12.2-Oss' is invalid.
|] Valid metadata not found at specified URL(s)
Please check if the URIs defined for this repository are pointing to a valid repository.
Skipping repository 'openSUSE-12.2-Oss' because of the above error.
Forcing raw metadata refresh
Retrieving repository 'openSUSE-12.2-Source' metadata -------------------------------------\]
File 'content' from repository 'openSUSE-12.2-Source' is signed with an unknown key ''. Continue? [yes/no] (no): yes
Retrieving repository 'openSUSE-12.2-Source' metadata ..................................[done]
Forcing building of repository cache
Building repository 'openSUSE-12.2-Source' cache .......................................[done]
Forcing raw metadata refresh
Retrieving repository 'openSUSE-12.2-Update' metadata .................................[error]
Repository 'openSUSE-12.2-Update' is invalid.
|] Valid metadata not found at specified URL(s)
Please check if the URIs defined for this repository are pointing to a valid repository.
Skipping repository 'openSUSE-12.2-Update' because of the above error.
Forcing raw metadata refresh
Retrieving repository 'openSUSE-12.2-Update-Non-Oss' metadata .........................[error]
Repository 'openSUSE-12.2-Update-Non-Oss' is invalid.
|] Valid metadata not found at specified URL(s)
Please check if the URIs defined for this repository are pointing to a valid repository.
Skipping repository 'openSUSE-12.2-Update-Non-Oss' because of the above error.
Some of the repositories have not been refreshed because of an error.
I think it’s enabled but not autorefresh; I’ll check again; I think I may have been unsuccessful trying to install libgcrypt from the DVD once but will try again and post back.
What’s weird about this is that if I look in /var/cache/zypp, it seems that I have stuff for the DVD, repo-non-oss, and source repos, but not for the others (the same ones where they at least seem to fire up without erroring out when I do repo force refresh (except for complaining about an unrecognized key, which they let me work around)).
linux:/var/cache/zypp/solv # ls -al -R
.:
total 0
drwxr-xr-x 6 root root 176 Mar 16 22:20 .
drwxr-xr-x 5 root root 120 Jul 15 2012 ..
drwxr-xr-x 2 root root 96 Mar 16 22:17 @System
drwxr-xr-x 2 root root 96 Mar 16 22:20 openSUSE_12.2-1.6
drwxr-xr-x 2 root root 96 Mar 16 22:20 repo-non-oss
drwxr-xr-x 2 root root 96 Mar 16 22:20 repo-source
./@System:
total 4396
drwxr-xr-x 2 root root 96 Mar 16 22:17 .
drwxr-xr-x 6 root root 176 Mar 16 22:20 ..
-rw-r--r-- 1 root root 53 Mar 16 22:17 cookie
-rw-r--r-- 1 root root 4491208 Mar 16 22:17 solv
./openSUSE_12.2-1.6:
total 3263
drwxr-xr-x 2 root root 96 Mar 16 22:20 .
drwxr-xr-x 6 root root 176 Mar 16 22:20 ..
-rw-r--r-- 1 root root 53 Mar 16 22:20 cookie
-rw-r--r-- 1 root root 3331464 Mar 16 22:20 solv
./repo-non-oss:
total 84
drwxr-xr-x 2 root root 96 Mar 16 22:20 .
drwxr-xr-x 6 root root 176 Mar 16 22:20 ..
-rw-r--r-- 1 root root 53 Mar 16 22:20 cookie
-rw-r--r-- 1 root root 81695 Mar 16 22:20 solv
./repo-source:
total 1546
drwxr-xr-x 2 root root 96 Mar 16 22:20 .
drwxr-xr-x 6 root root 176 Mar 16 22:20 ..
-rw-r--r-- 1 root root 53 Mar 16 22:20 cookie
-rw-r--r-- 1 root root 1574176 Mar 16 22:20 solv
It’s like some of the repos work but not others (could it be a problem with the keys for some but not others?). Thanks again, will try that libgcrypt reinstall again and re-post.
Signed, “exhausted”