how to solve : Dovecot version mismatch: Master is v2.1.7, lmtp is v2.2.13
Hello again dovecot list ;)
I've recently upgraded my dovecot version from 2.1.7 to 2.2.13. both versions where installed from source.
I upgraded why attempting to get lmtp working. I ultimately just coped the executable lmtp to the location that dovecot was expecting it to be in. but then the above error appeared.
However when I get the info from dovecot I get the following...
$ dovecot -n # 2.2.13: /usr/local/etc/dovecot/dovecot.conf
so there seems to be an issue somewhere.
I should note that I had copied my previous /conf.d/ files and then copied them back after the update.
I guess that I have missed a switch during the build, or need to modify a line in the config somewhere that tells what the version is, but that doesn't explain why the dovecot -n returns the correct info, but the error reports something different.
I am considering inserting the version_ignore=yes config option, but where should I insert it ?
Thanks in advance.
David
-- Tel:
- 33 6 50 14 39 34
email: david.myers.24j74@gmail.com
Addres: 22 Rue de L'Eglise 77700 Coupvray. 77700 France
Am 22.09.2014 um 12:32 schrieb Dave Myers:
Hello again dovecot list ;)
I've recently upgraded my dovecot version from 2.1.7 to 2.2.13. both versions where installed from source.
I upgraded why attempting to get lmtp working. I ultimately just coped the executable lmtp to the location that dovecot was expecting it to be in. but then the above error appeared.
why do you copy files around?
if you update a software then make it complete and not copy random files around - installing from source would in general be better done by build packages because they care about obsoleted files and so on
However when I get the info from dovecot I get the following...
$ dovecot -n # 2.2.13: /usr/local/etc/dovecot/dovecot.conf
so there seems to be an issue somewhere.
I should note that I had copied my previous /conf.d/ files and then copied them back after the update.
I guess that I have missed a switch during the build, or need to modify a line in the config somewhere that tells what the version is, but that doesn't explain why the dovecot -n returns the correct info, but the error reports something different.
I am considering inserting the version_ignore=yes config option, but where should I insert it?
no, you should make sure that you have only one version installed on your system and no old craft staying around
@Reindl.
I copied my conf.d folder as I deleted all the dovecot files in etc/dovecot use/etc/dovecot etc ... ...
When I installed the new 2.2.13 version it didn't seem to want to put the lmtp executable into the location that dovecot was expecting ? So I found the file and copied it to where it was expected to be.
I then copied my old (backed up) conf.d bact to etc/dovecot/conf.d/ Performed a restart of dovecot, and got the above error.
Quite simple really. But where else does dovecot store files, so as I can get all the errant files.
David. On 22 Sep 2014 12:37, "Reindl Harald" h.reindl@thelounge.net wrote:
Hello again dovecot list ;)
I've recently upgraded my dovecot version from 2.1.7 to 2.2.13. both versions where installed from source.
I upgraded why attempting to get lmtp working. I ultimately just coped
Am 22.09.2014 um 12:32 schrieb Dave Myers: the executable lmtp to the location that
dovecot was expecting it to be in. but then the above error appeared.
why do you copy files around?
if you update a software then make it complete and not copy random files around - installing from source would in general be better done by build packages because they care about obsoleted files and so on
However when I get the info from dovecot I get the following...
$ dovecot -n # 2.2.13: /usr/local/etc/dovecot/dovecot.conf
so there seems to be an issue somewhere.
I should note that I had copied my previous /conf.d/ files and then copied them back after the update.
I guess that I have missed a switch during the build, or need to modify a line in the config somewhere that tells what the version is, but that doesn't explain why the dovecot -n returns the correct info, but the error reports something different.
I am considering inserting the version_ignore=yes config option, but where should I insert it?
no, you should make sure that you have only one version installed on your system and no old craft staying around
Am 22.09.2014 um 13:44 schrieb David Myers:
@Reindl.
I copied my conf.d folder as I deleted all the dovecot files in etc/dovecot use/etc/dovecot etc ... ...
When I installed the new 2.2.13 version it didn't seem to want to put the lmtp executable into the location that dovecot was expecting ? So I found the file and copied it to where it was expected to be.
and there started your mistake
just test builds somewhere and realize if it comes to "so i found the file and copied it" something went terrible wrong - that's why you build usually *packages* - rpmbuild complains as long you have not listed all files in the %files section or if there are listed ones no longer built
for a clean upgrade you need to replace *every* file and in doubt get rid of orphans - just build packages or use a virtual machine with a snapshot to try as long you know what lives where
I then copied my old (backed up) conf.d bact to etc/dovecot/conf.d/ Performed a restart of dovecot, and got the above error.
Quite simple really. But where else does dovecot store files, so as I can get all the errant files.
/usr/bin/ /usr/lib64/dovecot /usr/libexec/ /var/lib/dovecot
David. On 22 Sep 2014 12:37, "Reindl Harald" h.reindl@thelounge.net wrote:
Hello again dovecot list ;)
I've recently upgraded my dovecot version from 2.1.7 to 2.2.13. both versions where installed from source.
I upgraded why attempting to get lmtp working. I ultimately just coped
Am 22.09.2014 um 12:32 schrieb Dave Myers: the executable lmtp to the location that
dovecot was expecting it to be in. but then the above error appeared.
why do you copy files around?
if you update a software then make it complete and not copy random files around - installing from source would in general be better done by build packages because they care about obsoleted files and so on
However when I get the info from dovecot I get the following...
$ dovecot -n # 2.2.13: /usr/local/etc/dovecot/dovecot.conf
so there seems to be an issue somewhere.
I should note that I had copied my previous /conf.d/ files and then copied them back after the update.
I guess that I have missed a switch during the build, or need to modify a line in the config somewhere that tells what the version is, but that doesn't explain why the dovecot -n returns the correct info, but the error reports something different.
I am considering inserting the version_ignore=yes config option, but where should I insert it?
no, you should make sure that you have only one version installed on your system and no old craft staying around
participants (3)
-
Dave Myers
-
David Myers
-
Reindl Harald