[SM-Commit] GIT changes to master grimoire by George Sherwood (e054c02ae28f85718fe7e8ad28fffede7a79d6b8)

George Sherwood pilot at beernabeer.com
Sun Sep 2 22:39:01 EDT 2007


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Mon, 03 Sep 2007 00:41:55 +0200
Ladislav Hagara <ladislav.hagara at unob.cz> wrote:

> 
> > GIT changes to master grimoire by George Sherwood
> > <gsherwood at sourcemage.org>:
> >
> > New commits:
> > commit e054c02ae28f85718fe7e8ad28fffede7a79d6b8
> > Author: George Sherwood <gsherwood at sourcemage.org>
> > Commit: George Sherwood <gsherwood at sourcemage.org>
> >
> >     postgresql: updated broken pgcluster patch.  Something that
> > needs to be check on version updates.
> 
> Who should check it? Should we check all options? pgcluster patch
> isn't installed by default.
> Seems I was last updated postgresql to 8.2.4 on 2007-04-23. It was
> security fix so this went to the stable.
> I remember that that time pgcluster patch was not available for new
> postgresql.
> 

Whoever is updating it should check it.  This isn't the same as not
checking all options, but when we are providing a patch it should be
checked against updates.  Upstream should be checking that all the
options are correct.  If an option has changed then a bug will be
written.  If there isn't a patch available as you suggest happened then
the option should be commented out and a bug written until such time as
one is available. I don't think we should just leave it broken. 

George Sherwood
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)

iD8DBQFG23PFkVJnfkgKg60RAsI0AKCJNhdJFS8NNZ6CMpllhfQr5a0sAACfbA7e
3ejqC5KxQlfmTFTJNlINvtA=
=0Hf9
-----END PGP SIGNATURE-----


More information about the SM-Commit mailing list