Re: Calling all regressions

2009-03-12 Thread Bron Gondwana
Hi Simon, I was particularly interested in your feedback, since you're the most active package maintainer, and probably responsible for most of our long tail of users of the recent code. They're the people who are of most concern for things like configuration changes. Big sites tend to have

Re: Calling all regressions

2009-03-12 Thread Carson Gaspar
Bron Gondwana wrote: AAA+++ to cyr_conf! I'll write it up :) I think we want it to have the following spec: * cyr_conf - output all configuration variables and their current value * cyr_conf -C $file - as above with the following config file * cyr_conf -n $name - all configuration

Re: Calling all regressions

2009-03-12 Thread Bron Gondwana
On Thu, Mar 12, 2009 at 02:55:03AM -0700, Carson Gaspar wrote: Bron Gondwana wrote: AAA+++ to cyr_conf! I'll write it up :) I think we want it to have the following spec: * cyr_conf - output all configuration variables and their current value * cyr_conf -C $file - as above with

Re: Calling all regressions

2009-03-12 Thread Jorey Bump
Bron Gondwana wrote, at 03/12/2009 07:42 AM: On Thu, Mar 12, 2009 at 02:55:03AM -0700, Carson Gaspar wrote: Bron Gondwana wrote: AAA+++ to cyr_conf! I'll write it up :) I think we want it to have the following spec: * cyr_conf - output all configuration variables and their current value

Re: Calling all regressions

2009-03-12 Thread Simon Matter
AAA+++ to cyr_conf! I'll write it up :) I think we want it to have the following spec: * cyr_conf - output all configuration variables and their current value * cyr_conf -C $file - as above with the following config file * cyr_conf -n $name - all configuration variables for process $name

Re: Calling all regressions

2009-03-12 Thread Carson Gaspar
Bron Gondwana wrote: On Thu, Mar 12, 2009 at 02:55:03AM -0700, Carson Gaspar wrote: Bron Gondwana wrote: ... * cyr_conf -q - only show variables that are different than default ... Please include one of the most useful options that postconf has (postconf -n) - emit only those config

Re: Calling all regressions

2009-03-12 Thread Bron Gondwana
On Thu, Mar 12, 2009 at 02:04:17PM +0100, Simon Matter wrote: Yep, definitely. Store them all, and refuse to start unless: cyr_conf -C $oldfile is the same output as cyr_conf with the -C option passed to 'master'. Spit out an error message describing what's different and how to fix it.

Re: Calling all regressions

2009-03-12 Thread Simon Matter
On Thu, Mar 12, 2009 at 02:04:17PM +0100, Simon Matter wrote: Yep, definitely. Store them all, and refuse to start unless: cyr_conf -C $oldfile is the same output as cyr_conf with the -C option passed to 'master'. Spit out an error message describing what's different and how to fix it.

Re: Calling all regressions

2009-03-11 Thread Simon Matter
On Tue, Mar 10, 2009 at 01:33:00PM -0400, Wesley Craig wrote: On 10 Mar 2009, at 08:51, Michael Menge wrote: I think i should rephrase my question. Is there a way for cyrus to know that it was updated since the last time it did run, so it can do the things suggested by Bron. Perhaps

Calling all regressions

2009-03-10 Thread Bron Gondwana
I was looking through the bug tracker, and one of the items was skiplist issues in 2.2 - well, the ticket has morphed into that anyway. The question is - do we backport the skiplist bugfixes to Cyrus 2.2? For that matter, do we try to isolate just the actual bug fixes and backport them, or do

Re: Calling all regressions

2009-03-10 Thread Michael Menge
Quoting Bron Gondwana br...@fastmail.fm: Is there any good reason for a site to continue running 2.2 or even 2.1? Some Enterprise Distibutions still use 2.2.x as they maintain the same version for a very long time. E.g. Suse (SLES 10) uses Cyrus 2.2.12. These Distrutions patch the software

Re: Calling all regressions

2009-03-10 Thread Adam Tauno Williams
On Tue, 2009-03-10 at 12:07 +0100, Michael Menge wrote: Quoting Bron Gondwana br...@fastmail.fm: Is there any good reason for a site to continue running 2.2 or even 2.1? Some Enterprise Distibutions still use 2.2.x as they maintain the same version for a very long time. E.g. Suse (SLES 10)

Re: Calling all regressions

2009-03-10 Thread Michael Menge
Quoting Adam Tauno Williams a...@morrison-ind.com: On Tue, 2009-03-10 at 12:07 +0100, Michael Menge wrote: Quoting Bron Gondwana br...@fastmail.fm: Is there any good reason for a site to continue running 2.2 or even 2.1? Some Enterprise Distibutions still use 2.2.x as they maintain the same

Re: Calling all regressions

2009-03-10 Thread Wesley Craig
On 10 Mar 2009, at 08:51, Michael Menge wrote: Quoting Adam Tauno Williams a...@morrison-ind.com: Documentation is pretty miserable; best source for changes is either http://cyrusimap.web.cmu.edu/imapd/changes.html or to read the CVS commit maillist

Re: Calling all regressions

2009-03-10 Thread Bron Gondwana
On Tue, Mar 10, 2009 at 01:33:00PM -0400, Wesley Craig wrote: On 10 Mar 2009, at 08:51, Michael Menge wrote: I think i should rephrase my question. Is there a way for cyrus to know that it was updated since the last time it did run, so it can do the things suggested by Bron. Perhaps