Hi guys,
Please correct me if I am adding repos to dovecot correctly. I hope I am
doing it correctly


Step 1. Add the following repos to the following file
/etc/apt/sources.list.

deb http://xi.rename-it.nl/debian/pool/stable-auto/dovecot-2.2/ trusty
universe
deb-src http://xi.rename-it.nl/debian/pool/stable-auto/dovecot-2.2/ trusty
universe

Step 2. apt-get update

Step 3. apt-get build-dep dovecot-2.2

Step 4. apt-get -b source -t trusty dovecot-2.2

I hope the process listed above is correct and that if I execute it I wont
end up in a mess.
Please comment.
Thanks
Kevin


On Wed, Jan 28, 2015 at 11:02 PM, Kevin Laurie <superinterstel...@gmail.com>
wrote:

> Dear Thomas,
> From what I have read is that I cannot automatically install dovecot, I
> would need to add the repos to my repo list and then use pining to install
> the latest version. Kindly advise if I am on correct track?
>
> Thanks
> Kevin
>
>
>
>
> On Wed, Jan 28, 2015 at 10:08 PM, Kevin Laurie <
> superinterstel...@gmail.com> wrote:
>
>> Dear Thomas,
>> Could you advise(or provide a link to) for a safe way to upgrade the
>> Dovecot version.
>> I am a little worried about testing and making trial-and-error approach
>> as it could be risky.
>> Appreciate if you could help with this. I have been trying to address
>> this "slow search" issue for a while with very limited success(I was trying
>> to implement FTS also), so I will appreciate if you could support.
>> Apologies for my noobness.
>> Thank You
>> Kevin
>>
>>
>> Do you have much ideas on how to upgrade dovecot. I am little worried
>> about upgrading dovecot as there could be risks to data.
>> I am trying to upgrade from  2.2.9 to 2.2.15 or Dovecot-EE.
>>
>>
>> On Wed, Jan 28, 2015 at 9:16 PM, Thomas Leuxner <t...@leuxner.net> wrote:
>>
>>> * superinterstel...@gmail.com <superinterstel...@gmail.com> 2015.01.28
>>> 12:07:
>>>
>>> > Do you think I should try 2.2.15? Or stick to EE?
>>>
>>> This is in the repo. My version just has *all* the latest changes
>>> applied which sometime can be untested.
>>>
>>
>>
>

Reply via email to