Okay, I am re-downloading from the Gerrit sources, although I'm still quite unclear as to which sources are supposed to be used.
For any package I see, if there is no "tizen" branch does that mean it is out of date? Or does a package with tizen2.2, for instance, still something that 3.0 uses? I am still terribly unclear on that. On 20 August 2013 11:04, Graydon, Tracy <[email protected]> wrote: > By the way, Steven, your .gbs.conf looks fine (from previous email). Given > the version number of the package showing in your build logs, I don't > think you are building the tizen branch. > > If you do a git branch -a and it does show "* tizen", then there is > probably something whacked with your local project. Re-cloning would be a > good bet at that point. But I would wager a guess you are actually on some > other branch than the tizen branch. > > Tracy > > > On 8/19/13 10:00 PM, "Ylinen, Mikko" <[email protected]> wrote: > > >Hi, > > > >On Tue, Aug 20, 2013 at 1:52 AM, Maurer, Steven > ><[email protected]> wrote: > >> The same problem happened. This is the tail of the output I got: > >> > >> warning: build failed, Leaving the logs in > >> > >>/home/smaurer/GBS-ROOT/local/repos/tizen_3.0_m2_jul/i586/logs/fail/org.ti > >>zen.volume-0.2.4-1/log > >> info: updating local repo > >> error: *** Error Summary *** > >> === the following packages failed to build due to missing build > >>dependencies > >> (1) === > >> wrt-setting: > >> nothing provides pkgconfig(ace) > >> nothing provides pkgconfig(ace-dao-rw) > > > >As Tracy suggests, please check your branch. > > > >It should look like this (for apps/core/preloaded/volume-app): > >$ git branch -a > >* tizen > > remotes/origin/1.0_post > > remotes/origin/2.0alpha > > remotes/origin/HEAD -> origin/tizen > > remotes/origin/master > > remotes/origin/tizen > > remotes/origin/tizen_2.0 > > remotes/origin/tizen_2.1 > > > >I tried gbs build and it also works fine ("tizen" branch has version > >0.2.8) > >$ gbs build -A i586 --skip-conf-repos -R > > > http://download.tizen.org/releases/daily/tizen/ivi/latest/repos/ivi/ia32/p > >ackages/ > >-C > > > >The lesson here is: Git branch and the repo URL MUST be in sync. > > > >If you say, "I want to build for Tizen 3.0", it means > >1) you've checked out "tizen" branch from the git project > >2) you are using "tizen" release repo URLs (e.g., > > > http://download.tizen.org/releases/daily/tizen/ivi/latest/repos/ivi/ia32/p > >ackages/) > > > >if 1) and 2) are out of sync, you'll easily face dependency issues > > > >-- Mikko > >_______________________________________________ > >IVI mailing list > >[email protected] > >https://lists.tizen.org/listinfo/ivi > > -- Kind Regards Steven Maurer ------------------- 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]
_______________________________________________ IVI mailing list [email protected] https://lists.tizen.org/listinfo/ivi
