The missing file 'autogen.sh' is supposed to be included in one of the patches This is caused by patches have not been generated correctly. Build Err Message: chmod: cannot access 'autogen.sh': No such file or directory.Here we take the typical error below as an example: TIVI-3232 Incorrect upstream branch is configured in.$ pristine-tar -m 'update pristine-tar branch ' commit gdb-7.5.1.tar.bz2 Update pristine-tar branch by committing required tarball.Generation efficiency because it was outdated and could NOT provide required In this case, pristine-tar branch, on the contrary, reduced the tarball The consistency only if pristine-tar branch is up-to-date. This designĬan enormously increase the tarball generation efficiency as well as enhancing

Upstream tag to HEAD, and generates tarball from pristine-tar branch. When both tag and pristine-tar branch exit, gbs-export generates patches from Info: gdb-7.5.1.tar.bz2 does not exist, creating from 'upstream/7.5.1' Please file a bug report.Įrror: Couldn't checkout 'gdb-7.5.1.tar.bz2': /usr/bin/pristine-tar returned 2 Pristine-tar: Failed to reproduce original tarball. Xdelta1: expected from file (/tmp/pristine-tar.wBpiV2MRcf/recreatetarball) of length 169574400 bytes Xdelta1: expected from file (/tmp/pristine-tar.qrG7qz1zdh/recreatetarball) of length 169574400 bytes Info: Generating patches from git (upstream/7.5.1.HEAD)

Info: tracking branch: origin/pristine-tar -> pristine-tar Info: tracking branch: origin/upstream -> upstream home/xiaoqiang/fixtures/fake/packaging/fake-2.0-1 Info: package files have been exported to: Info: fake-2.0.tbz2 does not exist, creating from 'upstream/2.0' Pristine-tar: git show refs/heads/pristine-tar:fake-2.0.lta failedĮrror: Couldn't checkout 'fake-2.0.tbz2': it exited with 128 Info: Generating patches from git (upstream/2.0.HEAD)įatal: Path 'fake-2.0.lta' does not exist in 'refs/heads/pristine-tar' Pristine-tar branch can NOT provide required version of tarball.Pristine-tar branch contains broken tarball.An example of modification is shown below: gbs.conf to correct it, refer to `Incorrect Upstream` section. Note: The downside of this solution is: upstream branch, if exists, will be untrackable.įor errors caused by tag being added in incorrect upstream branch or having version issue, modify.Reset the upstream branch as none by modifying gbs.conf, that is, make the package native.We have the following two ways to fix this: When tag is not ancestor of current HEAD, GBS will display the second error When required tag is missing, GBS will display the first error mesage and exit. Generation, therefore, tags must be added for GBS to use as boundary of tarballīased on the working mechanism, GBS can smoothly perform packaging only when the Also, check the upstream tag format.įor non-native packages, the packaging process covers tarball creation and patch Update your upstream branch and/or fix the spec file. GBS tried this as you have upstream branch in you git tree. Info: Generating patches from git (.HEAD)Įrror: Start commit '' not an ancestor of end commit 'HEAD'Įrror: Generating upstream tarball and/or generating patches failed. Remove or rename the upstream branch (change the package to native)Įrror: Failed to export packaging files from git tree Update your upstream branch and/or fix the spec file.Ģ. GBS tried this as you have upstream branch in you git tree.ġ. Info: tracking branch: tizen-gerrit/upstream -> upstreamĮrror: Generating upstream tarball and/or generating patches failed. Tag is reachable but in reverse direction. Tag is NOT reachable at all for the current HEAD. The commit with tag is NOT ancester of current HEAD.This type of error covers the following scenarios: This section studies typical JIRA bugs to showcase the following three types of If errors still remain, return to step-01 otherwise, exit. If no build error appears after rebuild, go to step-03.Ĥ. If no export error appears after rebuild, go to step-02.Ģ. Fix all export errors and then go to step-04. When analyzing a local-full build report, the following basic workflow should be kept in mind:ġ. Local-full-build errors can be classified into three categories: This document provides information about how to analyze local-full-build errors, including the following:

Git rebase invalid upstream