Re: Calling all regressions

> 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

Re: Calling all regressions

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 fi

Re: Calling all regressions

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

> 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 $

Re: Calling all regressions

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 thei

Re: Calling all regressions

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 ab

Re: Calling all regressions

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

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 mo

Re: Calling all regressions

> 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

Re: Calling all regressions

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. >

Re: Calling all regressions

On 10 Mar 2009, at 08:51, Michael Menge wrote: > Quoting Adam Tauno Williams : >> Documentation is pretty miserable; best source for changes is either >> or to read the CVS >> commit maillist >>

Re: Calling all regressions

Quoting Adam Tauno Williams : On Tue, 2009-03-10 at 12:07 +0100, Michael Menge wrote: Quoting Bron Gondwana : > 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

Re: Calling all regressions

On Tue, 2009-03-10 at 12:07 +0100, Michael Menge wrote: > Quoting Bron Gondwana : > > 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.

Re: Calling all regressions

Quoting Bron Gondwana : 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 with own patches an