Re: What to do when upstream breaks configuration

2011-01-10 Thread Stephen Gallagher
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/10/2011 09:02 AM, Adam Williamson wrote: > On Mon, 2011-01-10 at 08:02 -0500, Stephen Gallagher wrote: > >> As a caveat, this is a project that always requires at least some manual >> intervention on upgrade, as individual sites need to have an

Re: What to do when upstream breaks configuration

2011-01-10 Thread Stephen Gallagher
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/10/2011 08:37 AM, Mat Booth wrote: > On 10 January 2011 13:02, Stephen Gallagher wrote: >> -BEGIN PGP SIGNED MESSAGE- >> Hash: SHA1 >> >> As a caveat, this is a project that always requires at least some manual >> intervention on upgrade

Re: What to do when upstream breaks configuration

2011-01-10 Thread Adam Williamson
On Mon, 2011-01-10 at 08:02 -0500, Stephen Gallagher wrote: > As a caveat, this is a project that always requires at least some manual > intervention on upgrade, as individual sites need to have an upgrade > script run on them. So end-users are used to taking some action. > Unfortunately, upstream

Re: What to do when upstream breaks configuration

2011-01-10 Thread Mat Booth
On 10 January 2011 13:02, Stephen Gallagher wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > As a caveat, this is a project that always requires at least some manual > intervention on upgrade, as individual sites need to have an upgrade > script run on them. So end-users are used to ta