GBS build process contains the following steps:
1. Export source code to tarball.
2. resolve dependencies
3. Start building based on dependencies
4. show build results, which may contains the following three types of error
  - Export error: this should be fixed in source. There're about 8 packages 
have these error, we are driving to fix them. Here's the bug: 
https://bugs.tizen.org/jira/browse/TIVI-1829

  - build dependencies error (Expansion error): This is caused by some 
dependencies can't be found from remote repo and local pre-built repo.
  - rpm build error: There're many types of error, need analyze case by case.

So, for your case, it occurs in the first step (Export), so you can wait and 
let gbs continue, gbs will report the full build results.
Ncurses export issue has been fixed last month by this commit:

Refs: accepted/tizen/20130912.195247-1-gfc238d7
Author:     Anas Nashif <[email protected]>
AuthorDate: Sun Sep 15 02:43:07 2013 -0400
Commit:     Anas Nashif <[email protected]>
CommitDate: Sun Sep 15 02:43:22 2013 -0400

    remove remaining undefined macro for abi

    also remove unused code

    Change-Id: I5e96e3aad0dc647fa7d410e5854b0e518248fbdb
    Signed-off-by: Anas Nashif <[email protected]>
---
packaging/ncurses.spec |    7 +------
1 file changed, 1 insertion(+), 6 deletions(-)




Thanks
Qiang


From: [email protected] [mailto:[email protected]] On 
Behalf Of Hanchett, Paul
Sent: Thursday, August 22, 2013 5:06 AM
To: [email protected]; UM-PD-Engineering-Electrical-Infotainment-Portland
Subject: How to report error during gbs (re)build

A previous build failed ("nothing provides libsmack").  Tried to repeat the 
command, but I get this error:

administrator@tizen-SDK-2:~/Tizen_3-0$ gbs build -A i586
info: generate repositories ...
info: start building packages from: /home/administrator/Tizen_3-0 (git)
info: prepare sources...
info: start export source from: 
/home/administrator/Tizen_3-0/platform/upstream/ncurses ...
warning: pristine-tar and upstream branches exist in remote branches, you can 
checkout them to enable upstream tarball and patch-generation
error: types must match
error: /tmp/gbp2_g94G:83: bad %if condition
error: RPM error while parsing spec: can't parse specfile

error: <gbs>Failed to export packaging files from git tree
info: retrieving repo metadata...

So this looks like there must be an error in some (source) file.  How would you 
pinpoint the cause?

Thanks,

Paul Hanchett

-------------------
Infotainment Engineer
MSX on behalf of Jaguar Land Rover
One World Trade Center, 121 Southwest Salmon Street, 11th Floor, Portland, 
Oregon, 97204

Email: [email protected]<mailto:[email protected]>
-------------------

Business Details:
Jaguar Land Rover Limited
Registered Office: Abbey Road, Whitley, Coventry CV3 4LF
Registered in England No: 1672070
_______________________________________________
IVI mailing list
[email protected]
https://lists.tizen.org/listinfo/ivi

Reply via email to