Latest in my Update debacles - SuSe 10.2

[wesattexas]

The whole story is:
New to Linux. Over the last year or so I have installed (many times)
Suse 9.3 , 10 , 10.1 , 10.1r. All Clean Installs.
This install of Suse 10.2x64 AMD was the first good clean Install since 9.3
Software update application even worked for me first time right durring
the install,( a first since 9.3).
I thought I would add packman.unixheads.com/suse/10.2 as source.
Maybe a bad move: -
Unknown GnuPG Key
The file /var/tmp/TMPFile.n0RX9y
is digitally signed with the following unknown GnuPG key:
ID: 45A1D0671ABD1AFB
Fingerprint: F887 5B88 OD51 8B6B 8C53 0D13 45A1 D067 1ABD 1AFB
Name :PackMan Project (signing key) < packman@links2linux.de>

This means that a trust relationship to the creator of the file
cannot be established. Using the file may put the integrity
of your system at risk.
Use it anyway?
Yes - No
. . . . . . . . . . .
You can choose to import it into your keyring of trusted
public keys, meaning that you trust the owner of the key.
You should be sure that you can trust the owner and that
the key really belongs to that owner before importing it.
Import - Do Not Import
. . . . . . . . . . .

Well I thought since Suse went to this much trouble to warn me
I should verify the key first:
so I - NO..Abort..Stop..Quit..NO..Stop..Abort..etc..etc.. etc..
Quit Yast. - Oh! look I have software update(s) available.
Run Software Updater - like several successful times before:

. . . . . . . . . . .
Unresolved dependencies:

Updating perl-spamassassin-3.1.7-6.1.x86_64[System packages] to
perl-spamassassin-3.1.8-9.1.x86_64[SUSE-Linux-10.2-Updates]
Updating patch:spamassassin-2523-0.noarch[System packages] to
patch:spamassassin-3077-0.noarch[SUSE-Linux-10.2-Updates]
Establishing atom:perl-spamassassin-3.1.8-9.1.x86_64[SUSE-Linux-10.2-Updates]
There are no installable providers of perl-Archive-Tar for
perl-spamassassin-3.1.8-9.1.x86_64[SUSE-Linux-10.2-Updates]
perl-spamassassin-3.1.7-6.1.x86_64[System packages] provides
perl-spamassassin == 3.1.7-6.1, but is scheduled to be uninstalled.
perl-spamassassin-3.1.7-6.1.i586[SUSE-Linux-10.2-Updates] provides
perl-spamassassin == 3.1.7-6.1, but another version of that package is
already installed.
Can't satisfy requirement perl-spamassassin == 3.1.7 for
spamassassin-3.1.7-6.1.x86_64[System packages]
atom:spamassassin-3.1.8-9.1.x86_64[SUSE-Linux-10.2-Updates] needed by
patch:spamassassin-3077-0.noarch[SUSE-Linux-10.2-Updates]
Installing atom:spamassassin-3.1.8-9.1.x86_64[SUSE-Linux-10.2-Updates]
atom:perl-spamassassin-3.1.8-9.1.x86_64[SUSE-Linux-10.2-Updates] needed
by patch:spamassassin-3077-0.noarch[SUSE-Linux-10.2-Updates]
Installing atom:perl-spamassassin-3.1.8-9.1.x86_64[SUSE-Linux-10.2-Updates]
Establishing atom:perl-spamassassin-3.1.7-6.1.x86_64[System packages]
perl-spamassassin-3.1.8-9.1.i586[SUSE-Linux-10.2-Updates] provides
perl-spamassassin == 3.1.8-9.1, but it is uninstallable. Try installing
it on its own for more details.
perl-spamassassin-3.1.8-9.1.x86_64[SUSE-Linux-10.2-Updates] provides
perl-spamassassin == 3.1.8-9.1, but is scheduled to be uninstalled.
There are no installable providers of perl-spamassassin >= 3.1.8-9.1 for
atom:perl-spamassassin-3.1.8-9.1.x86_64[SUSE-Linux-10.2-Updates]
Updating spamassassin-3.1.7-6.1.x86_64[System packages] to
spamassassin-3.1.8-9.1.x86_64[SUSE-Linux-10.2-Updates]
spamassassin-3.1.8-9.1.x86_64[SUSE-Linux-10.2-Updates] needed by
perl-spamassassin-3.1.8-9.1.x86_64[SUSE-Linux-10.2-Updates]
Establishing atom:spamassassin-3.1.8-9.1.x86_64[SUSE-Linux-10.2-Updates]
perl-spamassassin-3.1.8-9.1.i586[SUSE-Linux-10.2-Updates] provides
perl-spamassassin == 3.1.8-9.1, but it is uninstallable. Try installing
it on its own for more details.
perl-spamassassin-3.1.8-9.1.x86_64[SUSE-Linux-10.2-Updates] provides
perl-spamassassin == 3.1.8-9.1, but is scheduled to be uninstalled.
There are no installable providers of perl-spamassassin == 3.1.8 for
spamassassin-3.1.8-9.1.x86_64[SUSE-Linux-10.2-Updates]
Establishing atom:spamassassin-3.1.7-6.1.x86_64[System packages]
. . . . . . . . . . .
seems like something about spamassassin!

Now, what I dont know, is this just some more of the much vaunted Novell methodology of system updates,
or have I ruined my computer by starting and not finishing the add of a source.
I saw th add process ' Creating Source ' copying..., copying..., copying...

So I went Back and finished the add of packman. Still no joy, on Software Updater.
I tried to do the update with out updating spamassassin. Still no joy.

Its all very Deja vu - all over again.

Still need Updater Help. Since it no longer works.
Am I the only one with this spamassassin problem or is (or will there be a fix soon)

Regards, Wes.

[gogalthorp]

Why don't you just remove spamassassin??

But before make sure that you are going to a good packman site. Last I looked the main US site lost its server and was running on a loaned server with much reduced bandwidth. I changed to the second on the list and my updates improved.

So first remove the packman site from your lists. Be sure you have a good site by naviagiting to it via a browser. The bad site has a notice up. Then add back a known good site.

Then accept the credentials even though there is a warning it is the site you wanted isn't it?

Simply truning off update for packman in installation sources may fix the problem for updating. Packman probably has a newer version but you confused things but tell the compter not to trust that site but it still is supposed to check the site for updates. Oops

Remember computers do what you tell them to do not what you met them to do.


If all else fails remove spamassassin and then if you still want it reinstall. I for one have never seen the use for it though it is installed here on my 10.1 installation. The spam filter in Thunderbird seems to do about as good a job as I can expect.