After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 685288 - git head org.gnome.evolution.spamassassin.gschema.xml missing spamc-binary and spamd-binary keys -- evolution fails to start
git head org.gnome.evolution.spamassassin.gschema.xml missing spamc-binary an...
Status: RESOLVED NOTABUG
Product: evolution
Classification: Applications
Component: Mailer
3.8.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2012-10-02 13:50 UTC by Reid Thompson
Modified: 2013-09-13 01:08 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
fails to start missing spamc-binary -- backtrace (73.09 KB, text/plain)
2012-10-02 13:50 UTC, Reid Thompson
Details
fails to start due to missing spamd-binary (after I add a dummy spamc-binary tag to the schema and recompile schema) (72.38 KB, text/plain)
2012-10-02 13:53 UTC, Reid Thompson
Details

Description Reid Thompson 2012-10-02 13:50:49 UTC
Created attachment 225588 [details]
fails to start missing spamc-binary -- backtrace

git head org.gnome.evolution.spamassassin.gschema.xml missing spamc-binary and spamd-binary keys -- evolution fails to start
Comment 1 Reid Thompson 2012-10-02 13:53:12 UTC
Created attachment 225589 [details]
fails to start due to missing spamd-binary (after I add a dummy spamc-binary tag to the schema and recompile schema)

pls ignore the 
"(evolution:31270): GLib-GIO-CRITICAL **: g_settings_bind: property 'spamc-binary' on class 'ESpamAssassin' has type 'gchararray' which is not compatible with type 'b' of key 'spamc-binary' on schema 'org.gnome.evolution.spamassassin'
"
I fixed that when i added the dummy spamd-binary tag.  Evolution then started up and ran
Comment 2 Dan Vrátil 2012-10-02 14:03:41 UTC
If you disabled spamassassin in the last build, the spamassassin module is probably still installed in the install dir from the previous install, so Evolution finds it, loads it and is confused :)

Try clearing your build root/install dir and building Evo again.
Comment 3 Reid Thompson 2012-10-02 16:47:43 UTC
ok -- completely cleaned build area and
mv /opt/evo/ opt/evo.old
rebuilt
restarted evo with no problem

thanks

just wondering - how is going to work re distro's -- if distro builds with spamassasin and/or bogofilter, but user doesn't want/removes spamassassin or bogo from their system
Comment 4 Dan Vrátil 2012-10-02 21:42:42 UTC
Usually package manager can do diff of files provided by previous package and files provided by current update and remove files that are not present in the current update - or more simply, removes the old package with all it's files and installs the new package
Comment 5 Matthew Barnes 2012-10-03 02:30:52 UTC
(In reply to comment #3)
> just wondering - how is going to work re distro's -- if distro builds with
> spamassasin and/or bogofilter, but user doesn't want/removes spamassassin or
> bogo from their system

It's the distro's reposibility to ensure the package requirements are complete.  If Evolution's SpamAssassin module is installed, then the spamassassin package is a requirement.  If Evolution's Bogofilter module is installed, then the bogofilter package is a requirement.  Many distros can split this into subpackages like evolution-spamassassin and evolution-bogofilter which shield the additional requirements from the main evolution package.

Failing that, the user will see an error message about the missing filtering software with each and every incoming message.