RDK Resources
[*RDK Preferred*]
Code Management Facility
RDK Forums
[RDK Conferences]
RDK Support
Archives
Papers & Presentations Archive
...
4. Apply the patch to the source file/files.
...
5. It should be applied successfully. Take In case of observing any failure when apply the patch to the source file/files then skip this step. If no failures observed then take a backup for the file/files got patched. For ex :
6. In case of observing any failure when apply the patch to the source file/files, then this may expects some other patch to be applied first. In such case,
a. Go to the full console logs and then search for "Repo Init".
Example:
Repo Init for - Project: ssh://gerrit.teamccp.com:29418/rdk/yocto_oe/manifests/cisco-intel-manifest Branch: 2003_sprint Manifest: ciscoxb3-3939B
b. Create another directory
$ mkdir cisco_intel_repo
$ cd cisco_intel_repo
c. Append .xml with manifest file in repo init command and Clone the repo
$ repo init -u ssh://gerrit.teamccp.com:29418/rdk/yocto_oe/manifests/cisco-intel-manifest -m ciscoxb3-3939B.xml -b 2003_sprint
$ repo sync -j4 --no-clone-bundle
d. grep with file name( in which patch applied failure observed) in meta-* layers, So that will find the other patch file which creates this file.
$ grep -irn "Filename" meta-*
e. Apply the patch file first, and then on top of that apply the second patch file, If no failures observed then take a backup for the file/files got patched. For ex :
$ cp source/Styles/xb3/code/index.php source/Styles/xb3/code/index_bk.php
...