I am running SuSE 10.0 and I have a version of an rpm installed and I need that particular version to make a program function correctly, but now Yast Online Update is constantly telling me that a new security update is available for that package. When I open YOU it has the little green arrow/black arrow icon next to the package (which is for updating).

I can try clicking that icon to just get the checkmark (Keep) and I can right-click and select the lock icon (Protected -- do not modify) and accept that, but the status of YOU never changes and it keeps wanting me to update that package.

Anyway to tell it to tell it to forget about that package update permanently?

Can you not mark it taboo? You may have to do that in YaST and not YOU.

yes, you can select the patch and mark it as taboo. this is done in YOU. next update will list the marked patch but not install it by default.
there isn't way to not show the taboo-ed patch in the list yet. maybe someone here knows how to do that, if possible.

I just tried marking it as taboo in both YOU and YaST and it didn't work. Apparently since the package is already installed (just a lower version) it won't let me taboo it because taboo is just to tell it to never install a package that hasn't been installed yet. When I go to the list of updates and right click and taboo all of them in the list it taboos every one besides the one that I don't want to update.

Frustrating...

i am not aware of any workaround to disable certain update only.
howevr when your package in not in the database, YOU will not try to update it. it's as simple as you do not run suse.config...
here are steps but on your own risk...

1. make sure you have the rpm somewhere (of your version) mypkg-lowerversion.rpm
2. rpm -e myppkg
3. download mypkg-lowerversion in tarball format and install it

in case it breaks something, you simply install it back via your mypkg-lowerversion.rpm

please share here when it works. above method is not tested.

Shen,

Unfortunately, I don't have access to a tar or source version of the program. But it sounds like installing it this way so that it is not in the rpm database would solve the problem of YaST trying to update it each time.

Basically, what I have done is just ignore the one package and continue to update the necessary updates and leave that one as is (i.e. I'm just going to live with it for now). I'm planning on updating that machine to a newer version of SuSE anyways which, I think, would make the piece of software (at least this version) obsolete anyways.

If anyone tries Shen's solution or has any other solution, please post.

Thanks all!

PerfectStranger