Paul Hi, https://source.tizen.org/documentation/developer-guide/creating-tizen-platform-image-scratch-through-local-build
Seems to suggest that a gbs build of the whole of Tizen is not possible due to gbs a) not handling cyclic dependencies and b) not supporting the use of the x86 acceleration packages. I'm not sure if you are hitting either of these limitations in your local build log. Other Tizen platform development documentation on gbs also talks about the workflow for contribution of 'individual packages' using git clone, gerrit and gbs not the whole stack. If you want to be sure that you can have a local copy of Tizen always available (so no dependency on download.tizen.org) have a look at obslight-fakeobs, this will allow you to keep a local copy of tizen snapshots and releases and use gbs to build against them. With regards to rebuilding Tizen from scratch are you planning to rebuild each release/snapshot/daily build? BR Martin On Mon, Aug 26, 2013 at 4:55 PM, Hanchett, Paul < [email protected]> wrote: > Hi Dawei- > > I wonder if I could ask a couple of questions about the Sanity Test? > > There's a group of us trying to recreate Tizen 3.0 (IVI) using the tool > chain and sources, but we aren't having much success. May I ask: > > 1. Are you doing a complete rebuild of the OS, or only the portions > changed since some milestone? If the latter, which milestone. When you do > the build, do you have to include the upstream build? If so, which > upstream are you using? > 2. What are you building on (Win32, Linux, 32bit, 64bit)? Do you > think it should make any difference to the build? > 3. Is there anyone who's an expert on the build process that you could > refer us to, so we can identify what's going wrong on our systems? > 4. Is there any one person or group that has taken responsibility for > the build process? I expect to be writing about it and would like an > authoritative contact to interact with. > > For what it's worth, the text below seems to be the first error reported > for a full build: > > info: building repo metadata ... > info: package dependency resolving ... > debug: Checking dependencies for capi-content-mime-type > debug: expansion error > debug: nothing provides cmake > debug: nothing provides pkgconfig(dlog) > debug: nothing provides pkgconfig(capi-base-common) > debug: nothing provides pkgconfig(xdgmime) > debug: nothing provides libsmack.so.1(LIBSMACK) needed by > rpm-security-plugin > debug: Checking dependencies for m4 > debug: expansion error > debug: nothing provides libsmack.so.1(LIBSMACK) needed by > rpm-security-plugin > debug: Checking dependencies for perl-gettext > debug: expansion error > debug: nothing provides libsmack.so.1(LIBSMACK) needed by > rpm-security-plugin > debug: Checking dependencies for capi-system-runtime-info > debug: expansion error > debug: nothing provides cmake > debug: nothing provides pkgconfig(dlog) > debug: nothing provides pkgconfig(vconf) > debug: nothing provides pkgconfig(capi-base-common) > debug: nothing provides libsmack.so.1(LIBSMACK) needed by > rpm-security-plugin > debug: Checking dependencies for org.tizen.image-viewer > debug: expansion error > debug: nothing provides pkgconfig(appcore-efl) > debug: nothing provides pkgconfig(elementary) > debug: nothing provides pkgconfig(edje) > debug: nothing provides pkgconfig(evas) > debug: nothing provides pkgconfig(ecore) > debug: nothing provides pkgconfig(ecore-x) > debug: nothing provides pkgconfig(ecore-input) > debug: nothing provides pkgconfig(bundle) > debug: nothing provides pkgconfig(sensor) > debug: nothing provides pkgconfig(ui-gadget-1) > debug: nothing provides pkgconfig(utilX) > debug: nothing provides pkgconfig(appsvc) > debug: nothing provides pkgconfig(vconf) > debug: nothing provides pkgconfig(dlog) > debug: nothing provides pkgconfig(capi-appfw-application) > debug: nothing provides cmake > debug: nothing provides edje-bin > debug: nothing provides embryo-bin > debug: nothing provides libsmack.so.1(LIBSMACK) needed by > rpm-security-plugin > > > Command line: > > gbs -v -d build -A i586 --include-all --upstream-branch > http://download.tizen.org/snapshots/tizen/ivi/tizen_20130822.11 > > > Thanks for any suggestions you can offer! > > Regards, > > Paul > > > > 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] > ------------------- > > Business Details: > Jaguar Land Rover Limited > Registered Office: Abbey Road, Whitley, Coventry CV3 4LF > Registered in England No: 1672070 > > > On Mon, Aug 26, 2013 at 2:30 AM, Wu, DaweiX <[email protected]> wrote: > >> *Key Messages* >> >> *---------------------* >> >> This build caught 2 regressions of wrt-launcher and PA . Only mbr image >> could boot to UI, EFI and EFI/mbr release images >> couldn’t(TIVI-1653<https://bugs.tizen.org/jira/browse/TIVI-1653>). >> So we used workaround to test on BB. **** >> >> *Issue Summary* >> >> *-----------------------* >> >> *Regression issues:* >> >> TIVI-1661 <https://bugs.tizen.org/jira/browse/TIVI-1661> [3.0][REG] No >> sound output when paplay an audio(from app user)** >> >> TIVI-1658 <https://bugs.tizen.org/jira/browse/TIVI-1658> [3.0] [REG] >> webapp launched fail by wrt-launcher**** >> >> *New issues* >> >> TIVI-1664 <https://bugs.tizen.org/jira/browse/TIVI-1664> [3.0] Integrate >> openavb in image** >> >> TIVI-1663 <https://bugs.tizen.org/jira/browse/TIVI-1663> [3.0] Integrate >> smartdevicelink(SDL) in image**** >> >> TIVI-1660 >> <https://bugs.tizen.org/jira/browse/TIVI-1660>[3.0]ico-uxf-homescreen >> package not integrated in image >> ** >> >> TIVI-1657 <https://bugs.tizen.org/jira/browse/TIVI-1657> [3.0] >> Characters in weston terminal are unable to be refreshed while terminal >> window size changed.**** >> >> *Reopen issues:* >> >> N/A**** >> >> *V*erify issu*es:* >> >> TIVI-1654 <https://bugs.tizen.org/jira/browse/TIVI-1654> [3.0] >> evolution-data-server not integrated into default image** >> >> *Key Issues:* >> >> TIVI-1661 <https://bugs.tizen.org/jira/browse/TIVI-1661> [3.0][REG] No >> sound output when paplay an audio(from app user)** >> >> TIVI-1660 >> <https://bugs.tizen.org/jira/browse/TIVI-1660>[3.0]ico-uxf-homescreen >> package not integrated in image >> ** >> >> TIVI-1658 <https://bugs.tizen.org/jira/browse/TIVI-1658> [3.0] [REG] >> webapp launched fail by wrt-launcher** >> >> TIVI-1653 <https://bugs.tizen.org/jira/browse/TIVI-1653> [3.0][REG] Home >> UI didn't start up in daily build >> 21030822.11 >> ** >> >> TIVI-1602 <https://bugs.tizen.org/jira/browse/TIVI-1602> WebGL context >> creation hangs when called from a web app** >> >> TIVI-1525 <https://bugs.tizen.org/jira/browse/TIVI-1525> Unable to >> display the dropdownlist** >> >> TIVI-1518 <https://bugs.tizen.org/jira/browse/TIVI-1518> [3.0] >> MediaPlayer crashed when switching audio to play >> **** >> >> * * >> >> *Workarounds:* >> >> **1. *** *Boot to UI on BB : chown -R app /home/app && reboot**** >> >> * * >> >> *Test Result:* >> >> ----------------------**** >> Image version**** >> >> 20130822.11**** >> >> 20130823.14**** >> Total test cases**** >> >> 41**** >> >> 41**** >> Passed**** >> >> 11**** >> >> 22**** >> Failed**** >> >> 1**** >> >> 6**** >> Blocked**** >> >> 29**** >> >> 13**** >> Run rate **** >> >> 29%**** >> >> 68%**** >> Pass rate of total**** >> >> 27%**** >> >> 54%**** >> Pass rate of executed**** >> >> 92%**** >> >> 79%**** >> >> ** ** >> >> For detail information, please refer to link below:**** >> >> https://qarpt.tizen.org/3.0/IVI/Sanity%20Test/Bay%20Trail/289**** >> >> *Test Environment***** >> >> *-----------------------***** >> >> *Image tested:* >> >> >> http://download.tizen.org/releases/daily/tizen/ivi/tizen_20130823.14/images/ivi-mbr-i586/ >> **** >> >> >> http://download.tizen.org/releases/daily/tizen/ivi/tizen_20130823.14/images/ivi-efi-i586/ >> **** >> >> *Hardware: * >> >> * *BB(Bios version:50.20) with CheLong touch monitor**** >> >> NDiS 166**** >> >> VTC7120 BK**** >> >> VTC7120 D1K**** >> >> *Note*: Since no WiFi/BT in BB ,WiFi /BT related cases are tested in >> NDiS166. And we used USB-Ethernet for network connection in BB.**** >> >> ** ** >> >> *Test Objective * >> >> *-----------------------***** >> >> Sanity test is a very brief run-through of the functionality of the >> entire Tizen IVI image, to assure that the basic health of the distribution >> and report major regressions at the earliest time. All the checkpoints in >> sanity test reflect the most important and basic functionality, stability >> and performance of the distribution. **** >> >> * * >> >> ** ** >> >> Best Regards**** >> >> Dawei **** >> >> _______________________________________________ >> IVI mailing list >> [email protected] >> https://lists.tizen.org/listinfo/ivi >> >> > > _______________________________________________ > IVI mailing list > [email protected] > https://lists.tizen.org/listinfo/ivi > >
_______________________________________________ IVI mailing list [email protected] https://lists.tizen.org/listinfo/ivi
