Everytime I try to add or remove a repository from YaST2 I get this error:
http://img11.imageshack.us/img11/1271/up1x.gif](http://img11.imageshack.us/i/up1x.gif/)
Does anyone know how to fix this annoying problem ?
Thanks for your help! 
try rebuilding the database,might help
Andy
What command should I run from console ? http://fc05.deviantart.com/fs41/f/2009/014/4/0/___confusion____by_forestsofazarath.gif
Hi. Try
rpm --rebuilddb
Thanks for your help.
Unfortunately it didn’t work this time. I’m still receiving the same annoying message. >:(
Anything else I can try…
You can try to add a repository with zypper. e.g.:
zypper ar http://bla.bla anyname
If it fails there should at least be some useful output. Maybe you can also rebuild the zypper database but I don’t know if or how this may work. Good luck!
This is the list of repos I have for now:
http://img11.imageshack.us/img11/7965/up1u.gif](http://img11.imageshack.us/i/up1u.gif/)
I guess I managed to locate the problem…
I have disabled the repos I don’t want to use anymore and have tried to delete them, but everytime I try to delete them, I got the window posted @ the 1st. post.
However yast is allowing me to add more repos, the only problem are those stubborn repos (the ones highlighted).
When I try to delete them, the warning window appears.
Is there an alternative way to get rid of them not using YaST2 ???
Open a terminal and you may as well become su and do:
zypper lr
In that note the alias for the repo’s you want to delete
then:
zypper rr (alias)
eg:
zypper rr videolan-vlc
Is there an alternative way to get rid of them not using YaST2 ???
You can use zypper. You’ll need to be root first. To list repos (by number, alia, and url):
zypper lr --details
Now, say you have a repo #9 that you wish to remove. Then you can do:
zypper rr 9
@deano_ferrari
I’m not sure 10.3 supports all the zypper commands eg: --details
I seem to recall someone else having trouble with this, but I may be wrong?!
Well, I’m not sure what to answer. But repositories which are not enabled should not have any influence on your package management. You can try to remove them with “zypper rr RepositoryName”.
There’s smart package management activated in your repositories. Did you try to remove the unwanted repositories with smart? And just for curiosity, why do you have packman-usa and packman-ger enabled?
Unlike 11.1, in 10.3 there’s a zypper database in “/var/cache/zypp/zypp.db”. See what happens, when you delete it (better rename to have a backup) and then “zypper refresh” your database.
wow. after pressing preview I see a lot of traffic here 
@deano_ferrari
I’m not sure 10.3 supports all the zypper commands eg: --details
I seem to recall someone else having trouble with this, but I may be wrong?!
No, you’re right about this. Sorry, didn’t check OS version before posting. :X
Thank you to all of you guys. Specially to you “caf4926” your command got rid of those repos.
Dixie7:~ # zypper rr KDE_4_-_Qt_4.4
* Cleaning repository 'KDE 4 - Qt 4.4' cache
* Removing repository 'KDE_4_-_Qt_4.4'
Unexpected exception.
Record not found in the cache
Please file a bug report about this.
See http://en.opensuse.org/Zypper#Troubleshooting for instructions.
Dixie7:~ # zypper rr "VideoLan Repository"
* Cleaning repository 'VideoLan Repository' cache
* Removing repository 'VideoLan Repository'
Repository VideoLan Repository has been removed.
Dixie7:~ # zypper rr "KDE_4_-_Playground"
* Cleaning repository 'KDE 4 - Playground' cache
* Removing repository 'KDE_4_-_Playground'
Unexpected exception.
Record not found in the cache
Please file a bug report about this.
See http://en.opensuse.org/Zypper#Troubleshooting for instructions.
Even when apparently it didn’t made the cleaning smootly to all. As it said there was a bug.
I first tried to remove them “by the #”, but it didn’t work. So I tried by their alias, and this time they were deleted.
Well 2 be honest, just for “redundancy”, in case one of them becomes unavailable, the other hopefully will be there offering the files needed. 
10x ag4in for your help!
Good to know we sorted it for you. Thanks for letting us know.