Thanks for that insight, jf ding.  :-)

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 Fri, Sep 6, 2013 at 5:25 AM, Jian-feng Ding <[email protected]>wrote:

> Hi, Steven
>
> For current tizen-3.0 code base, the code quality is still not good enough
> to
> enable the local full build. For our development testings, we need some
> hacks
> to workaround the existing issues, but the final solution is to patch all
> the
> packages with problems. Our developers are working on a summary of all the
> issues found in current tizen-3.0 packages, in about 5 categaries and more
> thank 100 packages(though some issues will not block the build), and will
> continue work with others to speed up the fixings together.
>
> thanks
> - jf.ding
>
> On Thu, Sep 05, 2013 at 09:49:05AM -0700, Maurer, Steven wrote:
> > Hi everyone,
> >
> > Okay, one more trip on the merry-go-round. Because the documentation
> > changed in
> >
> https://source.tizen.org/documentation/developer-guide/creating-tizen-platform-image-scratch-through-local-build
> ,
> > I re-downloaded into a fresh directory using these commands:
> >
> > *% repo init -u review.tizen.org:/scm/manifest -b tizen -m ivi.xml
> > *
> > *% repo sync -m ivi.xml*
> >
> > Then changed the local .gbs.conf file to this (note the use of the
> > daily/tizen url now):
> >
> > [general]
> > tmpdir=/var/tmp/
> > profile = profile.tizen3.0
> > editor = vim
> > packaging_branch = tizen
> > work_dir=.
> > user = smaurer
> > passwdx = <redacted>
> >
> > [obs.tizen]
> > url = https://api.tizen.org
> >
> > [repo.tizen3.0_x86]
> > url=${work_dir}/pre-built/toolchain-x86/
> >
> > [repo.tizen3.0_ivi]
> > url=*http://download.tizen.org/releases/daily/tizen/ivi/latest/*
> >
> > [profile.tizen3.0]
> > obs = obs.tizen
> > repos=repo.tizen3.0_x86,repo.tizen3.0_ivi
> > buildconf=${work_dir}/scm/meta/build-config/build.conf
> >
> ------------------------------------------------------------------------------------------------------------------------------------------------------------
> >
> >
> > I then ran this command:
> >
> > *% gbs build -A i586
> --exclude=gcc,cmake,filesystem,aul,libmm-sound,libtool
> > > gbsbuild.out*
> >
> > This partially succeeded but mostly failed. And all the things that
> > succeeded appear to be vanilla linux. None of the tizen sources
> succeeded.
> >
> > The failures, listed in ~/GBS-ROOT/local/repos/tizen3.0/i586/logs/fail,
> > appear to look mostly like this:
> >
> > [    0s] Memory limit set to 2037888KB
> > [    0s] Using
> > BUILD_ROOT=/home/smaurer/GBS-ROOT/local/BUILD-ROOTS/scratch.i586.1
> > [    0s] Using BUILD_ARCH=i686:i586:i486:i386:noarch
> > [    0s]
> > [    0s]
> > [    0s] tizen-SDK-2 started "build acl.spec" at Thu Sep  5 16:28:46 UTC
> > 2013.
> > [    0s]
> > [    0s]
> > [    0s] processing specfile
> > /home/smaurer/GBS-ROOT/local/sources/tizen3.0/acl-2.2.51-0/acl.spec ...
> > [    0s] init_buildsystem --configdir /var/tmp/smaurer-gbs --cachedir
> > /home/smaurer/GBS-ROOT/local/cache --repository
> > /home/smaurer/GBS-ROOT/local/repos/tizen3.0/i586/RPMS --repository
> > /home/smaurer/git2/pre-built/toolchain-x86/ --repository
> >
> http://download.tizen.org/releases/daily/tizen/ivi/latest/repos/ivi/ia32/packages--clean
> > /home/smaurer/GBS-ROOT/local/sources/tizen3.0/acl-2.2.51-0/acl.spec
> > ...
> > [    0s] initializing
> > /home/smaurer/GBS-ROOT/local/BUILD-ROOTS/scratch.i586.1/.srcfiles.cache
> ...
> > [    0s] /usr/lib/build/createrpmdeps
> > /home/smaurer/GBS-ROOT/local/repos/tizen3.0/i586/RPMS
> > [    0s] /usr/lib/build/createrepomddeps
> > /home/smaurer/git2/pre-built/toolchain-x86/
> > [    1s] /usr/lib/build/createrepomddeps
> > --cachedir=/home/smaurer/GBS-ROOT/local/cache
> >
> http://download.tizen.org/releases/daily/tizen/ivi/latest/repos/ivi/ia32/packages
> > [    2s] expanding package dependencies...
> > [    3s] [1/2] downloading
> >
> http://download.tizen.org/releases/daily/tizen/ivi/latest/repos/ivi/ia32/packages/i686/glibc-locale-2.17-4.6.i686.rpm.
> ..
> > [    4s] Could not stat tmpfile
> >
> '/home/smaurer/GBS-ROOT/local/cache/0cca4ce1752580229c4256e2194fb1e7/tmp/glibc-locale-2.17-4.6.i686.rpm-28920':
> > No such file or directory at /usr/share/perl5/LWP/UserAgent.pm line 897.
> >
> > ...although some look like this:
> >
> > [    0s] Memory limit set to 2037888KB
> > [    0s] Using
> > BUILD_ROOT=/home/smaurer/GBS-ROOT/local/BUILD-ROOTS/scratch.i586.1
> > [    0s] Using BUILD_ARCH=i686:i586:i486:i386:noarch
> > [    0s]
> > [    0s]
> > [    0s] tizen-SDK-2 started "build alsa-lib.spec" at Thu Sep  5 16:24:08
> > UTC 2013.
> > [    0s]
> > [    0s]
> > [    0s] processing specfile
> >
> /home/smaurer/GBS-ROOT/local/sources/tizen3.0/alsa-lib-1.0.25-1/alsa-lib.spec
> > ...
> > [    0s] init_buildsystem --configdir /var/tmp/smaurer-gbs --cachedir
> > /home/smaurer/GBS-ROOT/local/cache --repository
> > /home/smaurer/GBS-ROOT/local/repos/tizen3.0/i586/RPMS --repository
> > /home/smaurer/git2/pre-built/toolchain-x86/ --repository
> >
> http://download.tizen.org/releases/daily/tizen/ivi/latest/repos/ivi/ia32/packages--clean
> >
> /home/smaurer/GBS-ROOT/local/sources/tizen3.0/alsa-lib-1.0.25-1/alsa-lib.spec
> > ...
> > [    0s] initializing
> > /home/smaurer/GBS-ROOT/local/BUILD-ROOTS/scratch.i586.1/.srcfiles.cache
> ...
> > [    0s] /usr/lib/build/createrpmdeps
> > /home/smaurer/GBS-ROOT/local/repos/tizen3.0/i586/RPMS
> > [    1s] /usr/lib/build/createrepomddeps
> > /home/smaurer/git2/pre-built/toolchain-x86/
> > [    1s] /usr/lib/build/createrepomddeps
> > --cachedir=/home/smaurer/GBS-ROOT/local/cache
> >
> http://download.tizen.org/releases/daily/tizen/ivi/latest/repos/ivi/ia32/packages
> > [    2s] expanding package dependencies...
> > [    2s] [1/1] downloading
> >
> http://download.tizen.org/releases/daily/tizen/ivi/latest/repos/ivi/ia32/packages/i686/glibc-locale-2.17-4.6.i686.rpm.
> ..
> > [    5s] RPM version 4.9.1.1
> > [    5s] Copyright (C) 1998-2002 - Red Hat, Inc.
> > [    5s] This program may be freely redistributed under the terms of the
> > GNU GPL
> > [    5s]
> > [    5s] Usage: rpm2 [-afgpcdlsiv?] [-a|--all] [-f|--file] [-g|--group]
> > [    5s]         [-p|--package] [--pkgid] [--hdrid] [--triggeredby]
> > [--whatrequires]
> > [    5s]         [--whatprovides] [--nomanifest] [-c|--configfiles]
> > [-d|--docfiles]
> > [    5s]         [--dump] [-l|--list] [--queryformat=QUERYFORMAT]
> > [-s|--state]
> > [    5s]         [--nofiledigest] [--nofiles] [--nodeps] [--noscript]
> > [--allfiles]
> > [    5s]         [--allmatches] [--badreloc] [-e|--erase=<package>+]
> > [--excludedocs]
> > [    5s]         [--excludepath=<path>] [--force] [--force-debian]
> > [    5s]         [-F|--freshen=<packagefile>+] [-h|--hash] [--ignorearch]
> > [    5s]         [--ignoreos] [--ignoresize] [-i|--install] [--justdb]
> > [--nodeps]
> > [    5s]         [--nofiledigest] [--nocontexts] [--noorder]
> [--noscripts]
> > [    5s]         [--notriggers] [--nocollections] [--oldpackage]
> [--percent]
> > [    5s]         [--prefix=<dir>] [--relocate=<old>=<new>]
> [--replacefiles]
> > [    5s]         [--replacepkgs] [--test] [-U|--upgrade=<packagefile>+]
> > [    5s]         [-D|--define='MACRO EXPR'] [-E|--eval='EXPR']
> > [--macros=<FILE:...>]
> > [    5s]         [--nodigest] [--nosignature] [--rcfile=<FILE:...>]
> > [-r|--root=ROOT]
> > [    5s]         [--dbpath=DIRECTORY] [--querytags] [--showrc] [--quiet]
> > [    5s]         [-v|--verbose] [--version] [-?|--help] [--usage]
> > [    5s] rpm verify failed
> >
> >
> > This actually happened a few days ago, and I've been trying every sort of
> > permutation to try to get something to build (not specifying the manifest
> > on the repo sync command was the latest).
> > No dice. In facer, the latest builds seems to have actually gone
> backwards,
> > and everything is giving these warnings now.
> >
> > If anyone knows why these sorts of errors occur, I'd be very grateful
> for a
> > few pointers.
> >
> > Steven Maurer
> >
> >
> >
> > On 2 September 2013 22:33, venkat <[email protected]> wrote:
> >
> > >  Thanks Paul.
> > > We will try the latest version instead of 3.0 M2.
> > >
> > > On Tuesday 03 September 2013 06:54 AM, Hanchett, Paul wrote:
> > >
> > >  Hi Venkat--
> > >
> > >  From the errors you're seeing, I'd wonder if somehow the sources are
> not
> > > in sync with the build process.  It looks to me like you've gotten a
> bit
> > > farther than we have so far... I'm away from the company computer, but
> I
> > > think that we've fallen back to using 'latest' vs 'snapshot' branches
> for
> > > our builds.
> > >
> > >  Steve Maurer could tell you more, he's in the thick of it.
> > >
> > >  Sorry that I don't have an *answer* for you.  :-(
> > >
> > >  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, Sep 2, 2013 at 6:20 AM, venkat <[email protected]>
> wrote:
> > >
> > >>  Hi Geoffroy,
> > >>
> > >> While building 3.0 M2 packages,  we are able to build most of the
> > >> upstream packages except some. I have attached logs for libcap and
> smack
> > >> packages. Can you please let me know what is the issue?
> > >>
> > >> We are using Ubuntu 12.04.
> > >>
> > >> Regards,
> > >> Venkat
> > >>
> > >>
> > >> On Thursday 29 August 2013 03:07 PM, VanCutsem, Geoffroy wrote:
> > >>
> > >>  Hi Venkat,
> > >>
> > >>
> > >>
> > >> libtapi -  Can I use the same tag (that exists in the manifest?
> > >>
> > >> [Geoffroy] Yes
> > >> wrt     - What should be the tag to be used?
> > >>
> > >> [Geoffroy] Replace the ‘revision’ tag by this one: *
> > >>
> submit/tizen/20130716.222709-0-ga8cd04578ff0ff57ef5e1a8ad3c1c261df9a1d43*
> > >>
> > >>
> > >>
> > >> I’ve also attached that very manifest file with the modifications in
> for
> > >> your convenience.
> > >>
> > >>
> > >>
> > >> Thanks,
> > >>
> > >> Geoffroy
> > >>
> > >>
> > >>
> > >> *From:* venkat [mailto:[email protected]<
> [email protected]>]
> > >>
> > >> *Sent:* Thursday, August 29, 2013 11:31 AM
> > >> *To:* VanCutsem, Geoffroy
> > >> *Cc:* [email protected]
> > >> *Subject:* Re: Building Tizen IVI 3.0 locally with gbs
> > >>
> > >>
> > >>
> > >> Hi Geoffroy,
> > >>
> > >> I am using this manifest.xml
> > >>
> > >>
> http://download.tizen.org/releases/milestone/tizen/ivi/tizen_20130729.2/images/ivi-release-mbr-i586/tizen_20130729.2-ivi-release-mbr-i586.manifest.xml
> > >>
> > >> libtapi -  Can I use the same tag (that exists in the manifest?
> > >> wrt     - What should be the tag to be used?
> > >>
> > >> On Thursday 29 August 2013 02:44 PM, VanCutsem, Geoffroy wrote:
> > >>
> > >> Hi Venkat,
> > >>
> > >>
> > >>
> > >> These are known issues which I have reported to our team already:
> > >>
> > >> - libslp-tapi: this package was recently renamed to libtapi but the
> > >> manifest file has not yet been updated. I expect this to be done
> shortly
> > >> and in the meantime you can manually change that in the manifest file.
> > >>
> > >> - wrt: some of the git history/previous commits got partly lost which
> > >> means the repo tool can’t find the original tag anymore. This will be
> fixed
> > >> the next time there is a new commit made to this project. Are you
> using the
> > >> latest manifest from scm/manifest or a specific one (like I do below)?
> > >>
> > >>
> > >>
> > >> Geoffroy
> > >>
> > >>
> > >>
> > >> *From:* venkat [mailto:[email protected]<
> [email protected]>]
> > >>
> > >> *Sent:* Thursday, August 29, 2013 9:00 AM
> > >> *To:* [email protected]
> > >> *Cc:* VanCutsem, Geoffroy
> > >> *Subject:* Re: Building Tizen IVI 3.0 locally with gbs
> > >>
> > >>
> > >>
> > >> One more package can't be found "wrt".
> > >>
> > >> On Thursday 29 August 2013 12:07 PM, venkat wrote:
> > >>
> > >> Hi Geoffroy,
> > >>
> > >> We are able to sync all the repo packages except  libslp-tapi. Can you
> > >> let me know how to clone this (Tizen IVI 3.0 M2)? We are getting teh
> > >> following error.
> > >>
> > >> fatal: Project not found: platform/core/telephony/libslp-tapi
> > >> fatal: The remote end hung up unexpectedly
> > >>
> > >> Regards,
> > >> Venkat
> > >>
> > >>
> > >>  On Wednesday 28 August 2013 02:40 PM, VanCutsem, Geoffroy wrote:
> > >>
> > >> Hi Paul,
> > >>
> > >>
> > >>
> > >> The instructions on the wiki are a little too generic and we need to
> > >> enhance these to also cover the use cases which are of interest to
> you,
> > >> i.e. the ability to rebuild from sources a complete image locally
> using
> > >> gbs, keeping in mind that that image will in most cases not be the
> very
> > >> latest daily release. I’ll put this on my ‘To-Do’ list along with
> Tomasz’
> > >> feedback that a wiki page on how to create a package from scratch for
> Tizen
> > >> IVI would be useful.
> > >>
> > >>
> > >>
> > >> Regarding the manifest files, there are still a few glitches in these,
> > >> even in the one I’ve pointed at below (i.e. the libslp-tapi and wrt
> > >> packages failed to be cloned when I tried it our yesterday and if you
> look
> > >> at the bottom of the manifest file you’ll notice that it failed to
> > >> understand where three of the packages came from). We’ve only recently
> > >> introduced these so it’s not, as expected, perfect yet. You testing
> these
> > >> is actually also very useful to highlight some of the gaps or
> problems that
> > >> we may miss.
> > >>
> > >>
> > >>
> > >> Cheers,
> > >>
> > >> Geoffroy
> > >>
> > >>
> > >>
> > >> *From:* Hanchett, Paul [mailto:[email protected]<
> [email protected]>]
> > >>
> > >> *Sent:* Tuesday, August 27, 2013 7:12 PM
> > >> *To:* VanCutsem, Geoffroy; Steven Maurer
> > >> *Cc:* [email protected]
> > >> *Subject:* Re: Building Tizen IVI 3.0 locally with gbs
> > >>
> > >>
> > >>
> > >> Geoffroy--
> > >>
> > >>
> > >>
> > >> Hard to fault your logic; basically you're saying the instructions in
> the
> > >> article have gotten stale and need to be updated for the present
> project
> > >> set-- Right?
> > >>
> > >>
> > >>
> > >> 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 Tue, Aug 27, 2013 at 10:08 AM, VanCutsem, Geoffroy <
> > >> [email protected]> wrote:
> > >>
> > >> Hi all, Paul,
> > >>
> > >>
> > >>
> > >> There were various threads about this topic but instead of replying to
> > >> one I just decided to start (yet) a new one.
> > >>
> > >>
> > >>
> > >> I went through the wiki page that is used as a starting point for the
> > >> exercise of trying to recompile Tizen IVI locally from sources using
> GBS:
> > >>
> https://source.tizen.org/documentation/developer-guide/creating-tizen-platform-image-scratch-through-local-build
> > >>
> > >>
> > >>
> > >> Although I have not gone through the entire exercise myself yet, the
> very
> > >> first thing that looked a little awkward to me is that the manifest
> file
> > >> that is referenced (i.e.
> > >>
> https://review.tizen.org/git/?p=scm/manifest.git;a=tree;h=refs/heads/tizen;hb=refs/heads/tizen
> )
> > >> does not seem to match the list of packages that we actually use in
> Tizen
> > >> IVI 3.0… there are packages in there that we do **not** use in IVI and
> > >> also some others that we do but are not listed in there. I believe a
> better
> > >> starting point may actually be to use the manifest file that gets
> published
> > >> along with a particular image (and so you can also decide which image
> you
> > >> want to rebuild from scratch). As an example, the manifest for the
> Tizen
> > >> IVI 3.0-M2-Jul release can be found here:
> > >>
> http://download.tizen.org/releases/milestone/tizen/ivi/tizen_20130729.2/images/ivi-release-mbr-i586/tizen_20130729.2-ivi-release-mbr-i586.manifest.xml
> > >>
> > >>
> > >>
> > >> So I think at a minimum, we should use that file by copying it in the
> > >> .repo/manifests folder and initialise the system using this: ‘repo
> init –m
> > >> tizen_20130729.2-ivi-release-mbr-i586.manifest.xml’
> > >>
> > >>
> > >>
> > >> Like I said, I haven’t gone through the entire exercise yet but
> hopefully
> > >> I will get around to try this out shortly and I will report back to
> the
> > >> list if I have any more success.
> > >>
> > >>
> > >>
> > >> Cheers,
> > >>
> > >> Geoffroy
> > >>
> > >>
> > >>
> > >> 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
> > >>
> > >>
> > >>
> > >> 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
> > >>
> > >>
> > >>
> > >>
> > >>  --
> > >>
> > >> Regards,
> > >>
> > >> Venkat
> > >>
> > >>
> > >>
> > >>
> > >>  --
> > >>
> > >> Regards,
> > >>
> > >> Venkat
> > >>
> > >>
> > >>
> > >>
> > >>  --
> > >>
> > >> Regards,
> > >>
> > >> Venkat
> > >>
> > >>  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.
> > >>
> > >>
> > >>
> > >>  --
> > >>
> > >> Regards,
> > >>
> > >> Venkat
> > >>
> > >>  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.
> > >>
> > >>
> > >>   --
> > >> Regards,
> > >> Venkat
> > >>
> > >>
> > >> _______________________________________________
> > >> IVI mailing list
> > >> [email protected]
> > >> https://lists.tizen.org/listinfo/ivi
> > >>
> > >>
> > >
> > > --
> > > Regards,
> > > Venkat
> > >
> > >
> > > _______________________________________________
> > > 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]
> > -------------------
> >
> > Business Details:
> > Jaguar Land Rover Limited
> > Registered Office: Abbey Road, Whitley, Coventry CV3 4LF
> > Registered in England No: 1672070
> >
> >
> >
> > This e-mail and any attachments contain confidential information for a
> > specific individual and purpose.  The information is private and
> privileged
> > and intended solely for the use of the individual to whom it is
> addressed.
> > If you are not the intended recipient, please e-mail us immediately.  We
> > apologise for any inconvenience caused but you are hereby notified that
> any
> > disclosure, copying or distribution or the taking of any action in
> reliance
> > on the information contained herein is strictly prohibited.
> >
> > This e-mail does not constitute an order for goods or services unless
> > accompanied by an official purchase order.
>
> > _______________________________________________
> > 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

Reply via email to