"error: Following Packages Haven't Been Found On The Medium..

I'm not sure what's going on or what I did (nothing that I can think of) but I can't install downloaded RPMs through Yast anymore. Last night I tried installing Skype, which worked fine on a previous install of Suse, and it gave me the following error:

"ERROR: Following packages haven't been found on the medium: *insert package name here*"

I thought it was the rpm's fault, so I dismissed it. Then just now I tried installing SPCA5xx, a Suse 10.0 RPM, for my webcam and it gave me the same error. I then tried running the FrostWire rpm, which I installed before, and it did it again. The weird thing is that it doesn't say the package name properly. Like with SPCA5xx it says it's "spca5xxspca5xx". I'm not sure but I don't think that's correct.

Also, on a perhaps related note, FrostWire installed a couple weeks ago, but it doesn't actually open. The KMenu shortcut it made doesn't do anything. Anyone know why that might be? Running FrostWire under Run Command recognizes it (the KDE logo changes) but that doesn't work, either.

So, yeah.. somehow my Yast got broken :blink:

Help appreciated Thanks!

"ERROR: Following packages haven't been found on the medium: *insert package name here*"[/b]

Probably that you have refresh turned off on the repository and the packages have been updated so the version numbers no longer match.
Refresh the source and try again.

Eds

Nope, that didn't work >_< Although I will leave Refresh on from now on.

I'm talking about installing RPMs I downloaded off websites, though, not stuff you get through Yast. Like I got the Skype RPM from the official Skype website. To install RPMs I go into Konqueror and open the RPM, then go to Install Package with YaST. It's always worked great before.

*tries installing via Konsole* Okay, that worked... though it doesn't create a shortcut in the KMenu, which is kinda annoying. Also.. I got this strange message:

linux:/home/kalinda # rpm -i skype-1.2.0.18-suse.i586.rpm
warning: skype-1.2.0.18-suse.i586.rpm: V3 DSA signature: NOKEY, key ID d66b746e
linux:/home/kalinda #

At least it worked, though, so it's a temporary solution. Other then that, I suppose I can run the recovery on the DVD and see if that's helpful.

Thanks for your response

EDIT: Okay, the repair DVD did absolutely nothing to fix anything.. but it did, however, inform me that the "suse-release" thing I had installed was "Unnown" when I had it check installed programs. I don't know if that means anything, considering Suse boots just fine..

Anyway, I think I figured it out. I foolishly compiled the latest version of Expat a few days ago, whilst trying to get another program to work.. and I didn't remove the one I already had. So now I think I have two of them (Software Management doesn't seem to pick up compiled programs) and I don't know where it is... or how to remove it, as I think it's a ton of files.

Thinking back, I recall RPMs working before I installed it. So anyone know how to remove it? Or do you think installing an RPM I found of a newer version might fix everything?

Thanks!

EDIT 2: Right, finally removed the compiled expat (was easy, shouldn't have had to ask).. but it's still not working right. Now I'm totally lost and have no clue what could be wrong with it. I guess I could reinstall Yast.. but Im not sure how...

Yargh, I really don't wanna reinstall Suse again...

Mine does exactly the same thing for downloaded RPMs since my last online update, so I don't think it's anything you did wrong. I have been installing them from the command line under smart. For some reason AppArmor has appeared on my 10.0 system too (which I thought was a 10.1 thing), so I am thinking that maybe they are issuing the broken 10.1 version of YaST in the update.

I wonder if the YaST version can be rolled back. I would try but I would rather not risk breaking things as long as smart can do the job.

I have the same problem but have just walked around it. I've just been downloading the RPM and just choosing to install the software without YaST. I haven't had Suse for too long but don't think it had these problems prior to a recent update. I've also had problems with other YaST configured options like users, screensavers, and desktops.
*I just ran Online Update in YaSt and one of the updates ( yast2-online-update - yast2-online-update: Restart YOU in installation workflow. After applying libzypp patch during installation, online-update did not restarted, so there was not a chance to install any other patch. This update fixes the problem. ) It might be that certain updates were only partial or incorrectly applied and need to reinstalled. I just went thru the list of updates and installed or updated any patch that had been applied. After running Online Update in YaST my PC started running much smoother and most of my probs were resolved. Give it a shot!

Has anyone managed to fix their yast yet, I seem to be having same problem after recent update, tried the above but no success. I can however install rpms through cli.
Wouldnt mind getting yast back up and running, does anyone have any idea how to fix this?
tia

SOLVED!

For those who want the simplicity of installing downloaded rpms from Konqueror with "Install Package with YaST" ...

Downgrade kdebase3-SuSE to version 10.0-21

Z

SOLVED!
Downgrade kdebase3-SuSE to version 10.0-21[/b]

UPDATE!
-- kdebase3-SuSE 10.0-21.3 or 10.0-21.5 is the bad one.
-- kdebase3-SuSE 10.0-21.7 is the good one.

I upgraded to kdebase3-SuSE 10.0-21.7 this morning, and it worked fine installing two different rpm packages through Konqueror and "Install Package with YaST"

Z