Cyrus 2.1 and 2.2 init scripts

[Benjamin Seidenberg]

Ross Boylan wrote:
> On Mon, 2006-10-16 at 20:57 +0000, Ross Boylan wrote:
>   
>> On Mon, 2006-10-16 at 17:41 -0300, Henrique de Moraes Holschuh wrote:
>>     
>>> On Mon, 16 Oct 2006, Ross Boylan wrote:
>>>       
>>>> Since 2.1 and 2.2 basically do the same thing, invoking cyrmaster, I'm
>>>> not sure this is a problem, but it looks odd.
>>>>         
>>> The problem is that the executables are named the same.  We can fix this
>>> only by adding a sentinel file to *both* packages and testing for that file.
>>> It must be a non-conffile.
>>>
>>>       
>>>> Is this behavior intended, have I misunderstood something, or is this
>>>> worth filing a bug about?
>>>>         
>>> I'd say it is worth a bug report, yes.  The fix required for both packages
>>> is trivial.  We can either add a new sentinel file to /usr/lib/cyrus, or we
>>> can grep for a proper version for PACKAGE_VERSION in
>>> /usr/lib/cyrus/cyrus-hardwired-config.txt if that file is still there in
>>> 2.2.
>>>       
>> OK.  I'll wait to see if there's any other discussion before filing a
>> bug.
>>
>> I'm not sure there's any fix for people like me who have already removed
>> 2.1; obviously I'm not going to get updated files or init scripts for
>> the 2.1 package.  Maybe a NEWS item would be appropriate?
>>
>> For now, I stuck exit 0 at the top of init.d/cyrus21
>>     
>
> I was going to say I could just purge 2.1, but now that I think about
> it, would that take the current /etc/cyrus.conf and /etc/imapd.conf with
> it?  If that's a risk, that might be a separate, and bigger, problem.
>
>   
I don't think so. They ought to now be marked as being owned by cyrus 
2.2.  Do a dpkg -S /etc/<whatever> to be sure.