Comment 9 for bug 787864

Dear Dave!

Starting from the 2-nd point (signatures):
I meant that:
- I scheduled update in Automatic mode under user
- several days I checked if ClamTk performs the update - NO (old date in
GUI window)
- but if I did it manually in terminal (sudo freshclam) then I got fresh
signatures and then ClamTk saw them (reported them with fresh dates in
usual GIU window under user)
- so, I understood in a way that ClamTk under user has not enough rights
to start freshclam - THIS WAS the problem I meant
- then I switched update to Manual in ClamTk under user, BUT switched it
to Automatic in ClamTk under root
- so, now I see regularly equally fresh signatures dates in both ClamTk:
user's as well as root's

I didn't get what you wrote properly - this is like it should be or not?

> If you have automatic updates scheduled, the
> updates you run as a user will not be seen.

As for dependencies of the package...
I see quit simple way to check if the problems we discuss are in ClamTk
or not (to avoid you keep on thinking what's wrong in ClamTk especially
if everything is OK there :) ) :

- I could delete ClamTk together with some perl packages and those .pm
file I reported you about

- if you have proper .rpm packages with ClamTk then I would try to
install it and see which dependencies it requres

- either alone or with your help/advice I would install needed Perl
packages (or even better a perl repository from where all of them could
be installed automatically)

The aim is to check if the story with missing perl file will be repeated
or not after rpm will be satisfied with all dependencies (I'm not so
familiar with linux, but I believe that this is wrong if rpm reports OK,
but then something is missing).

If the problem with file will appear then lets fix it "somehow in a
right way", i.e. by installing one more perl package, but not by single
file copying.

And then we could see for sure if ClamTk works properly on SuSE SLED.
If yes - then you (or me - up to you) could report to SuSE about their
"wrong way" to resolve dependencies (I guess regarding perl modules
mostly).
If not - then you'd really have to think about what's wrong with ClamTk.

So, what do you think about?

Best regards,
Sergey

> Sergey,
>
> Here are the dependencies of the first clamtk package I saw on the link you provided:
> clamav >= 0.88
> clamav-db
> perl
> perl(LWP::UserAgent)
> perl(File::Find::Rule)
> perl(Date::Calc)
> perl(Gtk2)
> perl(Locale::gettext)
> perl(Net::DNS)
> zenity
> rpmlib(PayloadFilesHavePrefix) <= 4.0-1
> rpmlib(CompressedFileNames) <= 3.0.4-1
> /usr/bin/perl
> rpmlib(PayloadIsLzma) <= 4.4.2-1
>
> I'm not sure who is maintaining that version, but sending the maintainer this link might help him/her:
> http://clamtk.sourceforge.net/clamtk.spec
>
> Regarding the signature updates... can you hit Ctrl-W and tell me which
> option you have selected? If you have automatic updates scheduled, the
> updates you run as a user will not be seen.

> So, if you would like to
> update signatures yourself, you would need to select "Manual" (Вручную),
> and then you should see those updates.
>
> respectfully
> dave
>