On Feb 22, 2020, at 07:43, Gerben Wierda wrote:
> On 22 Feb 2020, at 14:31, Rainer Müller wrote:
>
>> On 22.02.20 12:41, Gerben Wierda wrote:
>>> port dovecot is now installing dovecot 2
>>> port dovecot2 is now installing dovecot 1
>>
>> No, there is no Dovecot 1.x i the ports tree any more.
> On 22 Feb 2020, at 14:31, Rainer Müller wrote:
>
> On 22.02.20 12:41, Gerben Wierda wrote:
>> port dovecot is now installing dovecot 2
>> port dovecot2 is now installing dovecot 1
>
> No, there is no Dovecot 1.x i the ports tree any more.
>
> dovecot2 is a port that has been marked as
On 22.02.20 12:41, Gerben Wierda wrote:
> port dovecot is now installing dovecot 2
> port dovecot2 is now installing dovecot 1
No, there is no Dovecot 1.x i the ports tree any more.
dovecot2 is a port that has been marked as replaced_by dovecot. As the
epoch was increased, it will be considered
Just do:
port uninstall dovecot2 dovecot2-sieve
port clean --all dovecot2 dovecot2-sieve
port install dovecot +solr +…
port install dovecot-sieve
A strong downvote to anything named “dovecot3” when and if version 3 ever
appears. At that time dovecot version 2 will be obsolete, which is how we
Follow-up suggestion:
Clone port dovecot2 to a new port dovecot1 now
Whenever dovecot major release 3 appears:
Clone the existing dovecot to new port dovecot2
Update dovecot port to dovecot 3
Is there a mechanism in MacPorts to block automatic update activations when new
versions of software
port dovecot is now installing dovecot 2
port dovecot2 is now installing dovecot 1
The change breaks ‘port update outdated’ as the existence of a dovecot2 install
will prevent the installation of dovecot which now has become a dependency for
other ports instead of dovecot2. dovecot2-sive is
