On Wed, Jul 13, 2011 at 6:38 PM, Roger Leigh <[email protected]> wrote: > On Wed, Jul 13, 2011 at 06:28:53PM +0200, Thibaut VARENE wrote:
>> Well, given the lack of documentation, especially on upgrade process, >> and my previous experience with generally painful upgrades from >> version to version (0.60 entirely broke backward compatibility with >> 0.58 configs), I'm not exactly thrilled by the idea... ;P > > In theory, we should be completely backward compatible--we continue > to allow the use of older configuration variables in order to not > break compatibility with older formats. If you are seeing breakage, > I would appreciate knowing what's broken, so we can fix it. > > We have definitely made the config parser stricter though--it will now > error out where it would previously continue e.g. if you misnamed a > variable. And where we have removed configuration options, you might > well be required to comment out/remove them from your configuration. > But anything that's present in old and new versions should continue to > work. If it doesn't, I'll fix it. Well, from the top of my head problems were: - local config name changes (buildd.conf -> .builddrc) - removed/renamed config variables, which simply prevented sbuild/buildd to run until commented out / renamed. - config variable refactoring (the whole "@distributions" array was brand new in 0.60 and didn't work well (read: at all) with the good ol @take_from_dists(), and basically meant redoing entirely the buildd local configuration) <- this is what I call breaking backward compat, fwiw ;-) - upgrading schroot wasn't exactly a pleasant trip either HTH -- Thibaut VARENE http://www.parisc-linux.org/~varenet/ -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
