Hi Geoffroy--

Here's the command that works, sort of:

repo init -u ssh://[email protected]/scm/manifest -m
tizen_20130829.9-ivi-release-mbr-i586.manifest.xml


Except that we get a ways down on the sync and find the following error:

 * [new tag]         submit/tizen_2.0/20130215.191808 ->
submit/tizen_2.0/20130215.191808
 * [new tag]         submit/tizen_2.1/20130424.233300 ->
submit/tizen_2.1/20130424.233300
 * [new tag]         submit/tizen_2.1/20130514.054959 ->
submit/tizen_2.1/20130514.054959
remote: Counting objects: 76, done
remote: Finding sources: 100% (48/48)
remote: Total 260 (delta 9), reused 255 (delta 9)
Receiving objects: 100% (260/260), 100.86 KiB, done.
Resolving deltas: 100% (89/89), done.
>From ssh://review.tizen.org/platform/core/system/sys-assert
 * [new branch]      1.0_post   -> tizen-gerrit/1.0_post
 * [new branch]      2.0alpha   -> tizen-gerrit/2.0alpha
 * [new branch]      master     -> tizen-gerrit/master
 * [new branch]      tizen      -> tizen-gerrit/tizen
 * [new branch]      tizen_2.0  -> tizen-gerrit/tizen_2.0
 * [new branch]      tizen_2.1  -> tizen-gerrit/tizen_2.1
 * [new tag]         2.0_alpha  -> 2.0_alpha
 * [new tag]         2.0_release -> 2.0_release
 * [new tag]         2.1b_release -> 2.1b_release
 * [new tag]         accepted/tizen/20130520.101311 ->
accepted/tizen/20130520.101311
 * [new tag]         accepted/tizen/20130520.103002 ->
accepted/tizen/20130520.103002
 * [new tag]         accepted/tizen/20130604.172001 ->
accepted/tizen/20130604.172001
 * [new tag]         accepted/tizen/20130611.123358 ->
accepted/tizen/20130611.123358
 * [new tag]         accepted/tizen/20130628.202129 ->
accepted/tizen/20130628.202129
 * [new tag]         accepted/tizen/20130629.132108 ->
accepted/tizen/20130629.132108
 * [new tag]         accepted/tizen_2.0/20130215.203441 ->
accepted/tizen_2.0/20130215.203441
 * [new tag]         accepted/tizen_2.1/20130425.025152 ->
accepted/tizen_2.1/20130425.025152
 * [new tag]         submit/master/20120920.151114 ->
submit/master/20120920.151114
 * [new tag]         submit/tizen/20130517.015837 ->
submit/tizen/20130517.015837
 * [new tag]         submit/tizen/20130517.045233 ->
submit/tizen/20130517.045233
 * [new tag]         submit/tizen/20130604.095802 ->
submit/tizen/20130604.095802
 * [new tag]         submit/tizen/20130628.130547 ->
submit/tizen/20130628.130547
 * [new tag]         submit/tizen/20130628.202745 ->
submit/tizen/20130628.202745
 * [new tag]         submit/tizen/20130710.124819 ->
submit/tizen/20130710.124819
 * [new tag]         submit/tizen/20130815.013229 ->
submit/tizen/20130815.013229
 * [new tag]         submit/tizen_2.0/20130215.191808 ->
submit/tizen_2.0/20130215.191808
 * [new tag]         submit/tizen_2.1/20130424.233307 ->
submit/tizen_2.1/20130424.233307
fatal: Project not found: platform/core/telephony/libslp-tapi
fatal: The remote end hung up unexpectedly
fatal: Project not found: platform/core/telephony/libslp-tapi
fatal: The remote end hung up unexpectedly
error: Cannot fetch platform/core/telephony/libslp-tapi
phanchet@tizen-workstation:~/Tizen 3.0 M2 Aug$



I'll try commenting that line of the manifest out and try sync again.
 Should this package be there?

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 Wed, Sep 11, 2013 at 9:37 AM, VanCutsem, Geoffroy <
[email protected]> wrote:

>  Hi Paul,****
>
> ** **
>
> The exact git tags used to build an image are listed in the manifest.xml
> file that gets published with the image, so for the Tizen IVI 3.0-M2-Aug
> release it’s this file:****
>
>
> http://download.tizen.org/releases/milestone/tizen/ivi/tizen_20130829.9/images/ivi-release-mbr-i586/tizen_20130829.9-ivi-release-mbr-i586.manifest.xml
> ****
>
> ** **
>
> One thing I’ve put on my To-Do list is to write up a wiki page that would
> explain the following in details but here is some additional info (and I’ll
> let the Release Engineers correct me if/where I’m wrong):****
>
> - The ‘Creating a Tizen Platform Image from Scratch through Local Build’
> wiki page [1] is really tracking the latest commits in the Git tree. So
> it’s the latest and greatest at any point in time if the branch is under
> development (and as pointed out by Qiang earlier, it may even be ahead of
> what’s been submitted to OBS).****
>
> - For those who really want to settle (at least for some time) on a
> specific preview (which is really your case), then you should use the
> manifest.xml file that gets published along with that image. There are
> actually two manifest.xml files published:****
>
>                 1. Under builddata/manifests: that manifest includes a
> list of **all** packages that are available in the repository****
>
>                                 E.g.:
> http://download.tizen.org/releases/milestone/tizen/ivi/tizen_20130829.9/builddata/manifest/tizen_20130829.9_ia32.xml
> ****
>
>                 2. Under images/: tha tmanifest includes **only** the
> packages that are already installed in the image****
>
>                                 E.g.:
> http://download.tizen.org/releases/milestone/tizen/ivi/tizen_20130829.9/images/ivi-release-mbr-i586/tizen_20130829.9-ivi-release-mbr-i586.manifest.xml
> ****
>
> ** **
>
> These latter two manifest.xml files are affected by a couple of issues
> [2], I can send you a version I have manually fixed (not fully tested yet
> but happy to send them across all the same).****
>
> ** **
>
> The way I use these is as follows:****
>
> - Copy the manifest.xml file I want to use in .repo/manifests/****
>
> - repo init –m tizen_20130829.9-ivi-release-mbr-i586.manifest.xml****
>
> - repo sync****
>
> ** **
>
> Hope this helps,****
>
> Geoffroy****
>
> ** **
>
> [1]
> https://source.tizen.org/documentation/developer-guide/creating-tizen-platform-image-scratch-through-local-build
> ****
>
> [2] https://bugs.tizen.org/jira/browse/DEVT-91 and
> https://bugs.tizen.org/jira/browse/DEVT-92****
>
> ** **
>
> ** **
>
> *From:* [email protected] [mailto:[email protected]] *On
> Behalf Of *Hanchett, Paul
> *Sent:* Wednesday, September 11, 2013 6:03 PM
> *To:* [email protected]
> *Subject:* What git TAG was used to build the IVI M2 Aug release?****
>
> ** **
>
> We've been trying to build the tizen branch, but that is a constantly
> moving target as new commits occur.****
>
>
> 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****
>
> Intel Corporation NV/SA
> Kings Square, Veldkant 31
> 2550 Kontich
> RPM (Bruxelles) 0415.497.718.
> Citibank, Brussels, account 570/1031255/09
>
> This e-mail and any attachments may contain confidential material for the
> sole use of the intended recipient(s). Any review or distribution by others
> is strictly prohibited. If you are not the intended recipient, please
> contact the sender and delete all copies.
>
_______________________________________________
IVI mailing list
[email protected]
https://lists.tizen.org/listinfo/ivi

Reply via email to