Am 23.02.2019 um 03:33 schrieb Voytek Eymont via dovecot <dovecot@dovecot.org>:



On Sat, February 23, 2019 10:41 am, Gerald Galster via dovecot wrote:



you can't install it yet because dovecot-2.3.4-2.x86_64 is not shown,
probably due to the priority protection plugin:

-> 226 packages excluded due to repository priority protections


Try disabling it, see:


https://serverfault.com/questions/312472/what-does-that-mean-packages-exc
luded-due-to-repository-priority-protections
<https://serverfault.com/questions/312472/what-does-that-mean-packages-ex
cluded-due-to-repository-priority-protections>

Afterwards you should see all dovecot packages and can install version
2.3.4 again


Gerald,

thank you again

in meanwhile, I've tried specifying repo as in 'yum --enablerepo..',
perhaps I din't do it correctly as got errors, BUT, following your
advise/link, disabling r-p-p, now I see:

# yum install  dovecot dovecot-devel dovecot-mysql dovecot-pigeonhole
Loaded plugins: fastestmirror, langpacks
Loading mirror speeds from cached hostfile
* base: mirror.nsw.coloau.com.au
* epel: mirror.nsw.coloau.com.au
* extras: mirror.ventraip.net.au
* remi-safe: remi.conetix.com.au
* updates: mirror.nsw.coloau.com.au
Resolving Dependencies
--> Running transaction check
---> Package dovecot.x86_64 2:2.3.4.1-1 will be installed
---> Package dovecot-devel.x86_64 2:2.3.4.1-1 will be installed
---> Package dovecot-mysql.x86_64 2:2.3.4.1-1 will be installed
---> Package dovecot-pigeonhole.x86_64 2:2.3.4.1-1 will be installed
--> Finished Dependency Resolution

Dependencies Resolved

================================================================================
Package                Arch       Version         Repository             
Size
================================================================================
Installing:
dovecot                x86_64     2:2.3.4.1-1     dovecot-2.3-latest    
4.4 M
dovecot-devel          x86_64     2:2.3.4.1-1     dovecot-2.3-latest    
475 k
dovecot-mysql          x86_64     2:2.3.4.1-1     dovecot-2.3-latest     
92 k
dovecot-pigeonhole     x86_64     2:2.3.4.1-1     dovecot-2.3-latest    
704 k

Transaction Summary
================================================================================
Install  4 Packages

Total download size: 5.6 M
Installed size: 18 M
Is this ok [y/d/N]:


so I guess I'm good to hit 'y'

and:

Running transaction check
Running transaction test
Transaction test succeeded
Running transaction
 Installing : 2:dovecot-2.3.4.1-1.x86_64                                 
1/4
 Installing : 2:dovecot-devel-2.3.4.1-1.x86_64                           
2/4
 Installing : 2:dovecot-mysql-2.3.4.1-1.x86_64                           
3/4
 Installing : 2:dovecot-pigeonhole-2.3.4.1-1.x86_64                      
4/4
 Verifying  : 2:dovecot-devel-2.3.4.1-1.x86_64                           
1/4
 Verifying  : 2:dovecot-mysql-2.3.4.1-1.x86_64                           
2/4
 Verifying  : 2:dovecot-pigeonhole-2.3.4.1-1.x86_64                      
3/4
 Verifying  : 2:dovecot-2.3.4.1-1.x86_64                                 
4/4

Installed:
 dovecot.x86_64 2:2.3.4.1-1           dovecot-devel.x86_64 2:2.3.4.1-1
 dovecot-mysql.x86_64 2:2.3.4.1-1     dovecot-pigeonhole.x86_64 2:2.3.4.1-1

Complete!
[root@c7 ~]# dovecot --version
2.3.4.1 (3c0b8769e)


thanks again!
(I should've read the install screen properly in the first place, and,
should've noticed I was installing NOT from dovecot...)


just thinking... now that I installed OK, should I revert the priority
protection to '1', if I don't, will it bite me elsewhere, any thought ?

I've never used it. When you install/update, yum shows which repository the package belongs to.
This has been sufficient so far.

https://wiki.centos.org/PackageManagement/Yum/Priorities  / 7. A Cautionary Note:

# Note: The upstream maintainer of yum, Seth Vidal, had the following to say about
# 'yum priorities' in September 2009

# Gosh, I hope people do not set up yum priorities. There are so many things about
# priorities that make me cringe all over. It could just be that it reminds me of
# apt 'pinning' and that makes me want to hurl.

# The primary concern is that priorities is heavy handed over removing packages
# from the transaction set. It makes it difficult to readily determine what packages
# are being ignored and why. Even so, it is very flexible and can be extremely useful
# to provide the largest available list of packages.

Best regards
Gerald