[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Phpgroupware-developers] PHPGW - SECURITY WARNING ALL BRANCHES
From: |
Chris Weiss |
Subject: |
Re: [Phpgroupware-developers] PHPGW - SECURITY WARNING ALL BRANCHES |
Date: |
Fri, 04 Jul 2003 15:39:19 +0000 |
>I've tried and check what is necessary to apply to correct these bugs,
>and made a diff against 0.9.14.003, and there seems to be more than
>juste security patches...
>
>Is there any details ChangeLog, and specific detail of patches that may
>be necessary to correct only the security issues (and maybe links to
>bugs numbers, etc.) ?
the other changes are bug fixes, there is a strict policy of "no new features in
stable branches".
>
>For instance if applying a patch is easier than simply deploying a
>complete new version, that may be more convenient for some...
Since this needs no database changes applying a patch would be more difficult
than
running a CVS update, which by default does patches on CVS diffs against your
installed version and will never overwrite a change you made unless it's older
and
in conflict with a bug fix.
If you've made changes to the source it's easiest to do a cvs update -dP, but
beware
that cvs handle conflicts in an odd manner sometimes. It's not unusual (from my
experience) for cvs do things like:
>>>>>>>>>>>>>>>> cvs stamp
old conflicting code
<<<<<<<<<<<<<<<< cvs stamp
new code
which causes php parse errors. When you run the update look for files updated
with
M (merge) instead of P (patch) and keep in mind they may need edited.