User:Feri/bug3846
(→Plan) |
|||
| Line 7: | Line 7: | ||
2. Check out rev 1 of the [https://garage.maemo.org/svn/bugs bugs project] from garage | 2. Check out rev 1 of the [https://garage.maemo.org/svn/bugs bugs project] from garage | ||
| - | 3. Get the debian source package of Bugzilla 2.22-1, which was the version we started branching | + | 3. Get the debian source package of [http://packages.debian.org/source/oldstable/bugzilla Bugzilla 2.22-1], which was the version we started branching |
| - | 4. Get the diff between our rev 1 bugzilla and the upstream 2.22-1 | + | 4. Get the diff between our rev 1 bugzilla and the debian upstream 2.22-1 |
5. Analyze the diffs and see if there is any major patch that is not provided as a "debian patch" (dpatch) | 5. Analyze the diffs and see if there is any major patch that is not provided as a "debian patch" (dpatch) | ||
6. Take a break | 6. Take a break | ||
| - | |||
== DB schema diff == | == DB schema diff == | ||
Revision as of 09:36, 31 July 2009
Plan
1. Install vanilla Bugzilla 3.4 on test.maemo.org to see what new dependencies we will have to provide
2. Check the SQL schema diff between 3.4 and our own bugzilla
2. Check out rev 1 of the bugs project from garage
3. Get the debian source package of Bugzilla 2.22-1, which was the version we started branching
4. Get the diff between our rev 1 bugzilla and the debian upstream 2.22-1
5. Analyze the diffs and see if there is any major patch that is not provided as a "debian patch" (dpatch)
6. Take a break
DB schema diff
Bugzilla 3.4 has numerous diffs in the DB schema compared to 2.22. However bugzilla's checksetup.pl is able to handle the schema update on an existing database.
Analyzing Nokia patches
Luckily the most important Nokia changes are in forms of debian patch files. The outstanding parts can be quicly and easily applied by hand.