Zypper Looks For Repomd.xml In Wrong Directory So I Can't Update SuSE 11.0

ThisGuyIKnow · 09-25-2008, 11:58 AM

I have a fresh, no-GUI-or-desktop installation of SuSE 11.0. I was very happy to see the zmd/rug crap is gone!

Zypper seems mostly better, but I am having problems with my update repository only; my other ones are all fine.

When running "zypper lu" I get:

Code:

Error building the cache database:
File /var/cache/zypp/raw/UPDATESiTDNoy/repodata/repomd.xml.key doesn't contain public key data
Warning: Disabling repository 'UPDATES' because of the above error.
Reading installed packages...
Patches

No updates found.

I'm not sure why the UPDATES directory has "iTDNoy" appended to it in the error message. I have verified that /var/cache/zypp/raw/UPDATES exists (but has nothing in it) but /var/cache/zypp/raw/UPDATESiTDNoy does not. My other repos in /var/cache/zypp/raw/ have the appropriate stuff in them.

I have tried removing this repository and adding it again. No dice. I do get slightly different results depending on what I name the update repository.

When re-adding the update repository with the original name I got:

Code:

SE-11.0-Updates
shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory
Adding repository 'openSUSE-11.0-Updates' [done]
Repository 'openSUSE-11.0-Updates' successfully added
Enabled: Yes
Autorefresh: No
URI: http://download.opensuse.org/update/11.0

When re-adding the update repository with a new name (UPDATES) I got:

Code:

Adding repository 'UPDATES' [done]
Repository 'UPDATES' successfully added
Enabled: Yes
Autorefresh: No
URI: http://download.opensuse.org/update/11.0/

I have Googled for a while now and found others with the same or similar problems... just no solutions. I wish SuSE would finally get a good packaging system working with their OS. Maybe I'll finally try out the Smart packaging system.

I will keep on truck'n on my own, but would appreciate anyone's suggestions/help on this. Updates are kinda important!

- Gavin

ThisGuyIKnow · 09-27-2008, 01:27 PM

After trying many different things, beating my head against the wall, more Googling, crying (well no, but almost felt like it!

) and repeating, I finally found the issue was because I didn't have gpg installed. Installing gpg made the problem go away completely.

I was in Yast last week deleting unnecessary packages and it's more than a little possible that I wasn't careful enough and deleted gpg, but then again I *thought* I had this problem before I did that. Hmmmm...

Anyways, hope this thread helps someone else as "clumsy" as me with the same problem.

- Gavin