Arch Linux

Hi,

several Arch users experience issues with Evolution. I don't, so I can't report those bugs.
However, when those users sent requests to the Evolution mailing list, I noticed that they reported the wrong version.

I don't know why not the official releases from upstream are packaged, however, if you package commits from git, then build with
-DVERSION_SUBSTRING="+gitXXXXXX" \
-DVERSION_COMMENT="+gitXXXXXX"
, without doing so "evolution -v" does show another version then actually was build and packaged.

From the mailing list:

"[snip] the detailed Arch versions are shown below. Maybe those commits are ok, however, at least the Arch versions aren't simply

[rocketmouse@archlinux ~]$ evolution -v
evolution 3.24.2

they are 3.24.1+git:

[rocketmouse@archlinux ~]$ grep _commit /var/abs/extra/evolution/PKGBUILD
_commit=fc6d11eb4aab2cb44a6f63ea540d14138d278605 # gnome-3-24 [snip]"
- https://mail.gnome.org/archives/evolution-list/2017-April/msg00120.html

"[snip] You surely do not have 3.24.2, that had not been released yet. The way the Arch maintainer does his/her duty leads only to confusion for users and nothing else. It's a very wrong approach, from my point of view. The packager should use
-DVERSION_SUBSTRING="+gitXXXXXX", eventually
-DVERSION_COMMENT="+gitXXXXXX", (though none of this is shown in Help->About (I'm changing it for the next release), only in `evolution --version`) during the build (pass to cmake command) and skip the commit where the version is bumped just after the previous release, then everything will make sense and not be confusing. [snip]"
- https://mail.gnome.org/archives/evolution-list/2017-April/msg00128.html

Steps to reproduce:

[rocketmouse@archlinux ~]$ pacman -Si evolution{,-ews,-data-server,-bogofilter,-spamassassin}|grep Ve
Version : 3.24.1+6+gfc6d11eb4a-1
Version : 3.24.1-1
Version : 3.24.1+5+g98589a27b-2
Version : 3.24.1+6+gfc6d11eb4a-1
Version : 3.24.1+6+gfc6d11eb4a-1
[rocketmouse@archlinux ~]$ evolution -v
evolution 3.24.2

Regards,
Ralf