Dear Rui, The steps are executed successfully except the following
sudo apt-get update shows the below error "W: GPG error: http://download.opensuse.org Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 85753AA5EEFEFDE9" sudo apt-get upgrade shows Errors were encountered while processing: /var/cache/apt/archives/jenkins_1.579_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) Is it ok to ignore the above errors. Will these affect the GBS build functionality? Thanks & Regards Jinil P On Wednesday 10 September 2014 12:22 PM, Jinil P. wrote: > Dear Rui, > > Still it is showing the same error. > > Thanks & Regards > Jinil P > > > On Wednesday 10 September 2014 12:10 PM, Lv, RuiX wrote: >> Then please follow section 2.1 in this page to add appropriate repo. >> https://source.tizen.org/documentation/developer-guide/getting-started-guide/installing-development-tools >> >> Rui >> >> -----Original Message----- >> From: Jinil P. [mailto:jini...@nestgroup.net] >> Sent: Wednesday, September 10, 2014 2:31 PM >> To: Lv, RuiX; Li, JinjingX >> Cc: Anoop Babu; ivi@lists.tizen.org >> Subject: Re: Expansion error while GBS build >> >> Dear Rui, >> >> The version which I am using is Ubuntu 12.04 >> >> Thanks & Regards >> Jinil P >> >> >> On Wednesday 10 September 2014 11:57 AM, Lv, RuiX wrote: >>> Which Linux distribution are you working on? >>> " sudo apt-get update " is for Ubuntu, whereas the error displayed " >>> W: GPG error: http://download.opensuse.org ..." is related to openSUSE. >>> >>> Rui >>> >>> -----Original Message----- >>> From: IVI [mailto:ivi-boun...@lists.tizen.org] On Behalf Of Jinil P. >>> Sent: Wednesday, September 10, 2014 2:13 PM >>> To: Li, JinjingX >>> Cc: Anoop Babu; ivi@lists.tizen.org >>> Subject: Re: Expansion error while GBS build >>> >>> Dear Li, >>> >>> Thank you for the support. >>> >>> I followed the steps mentioned in the below link for reinstalling GBS >>> after removing existing GBS by executing sudo apt-get remove gbs >>> https://developer.tizen.org/dev-guide/2.2.0/org.tizen.platform.develop >>> ment/html/platform_dev_env/gbs_installation.htm >>> >>> But after executing the step sudo apt-get update terminal shows the >>> below error >>> "W: GPG error: http://download.opensuse.org Release: The following >>> signatures couldn't be verified because the public key is not available: >>> NO_PUBKEY 85753AA5EEFEFDE9" >>> >>> Could you please help to resolve this error. >>> >>> Thanks & Regards >>> Jinil P >>> >>> >>> On Friday 05 September 2014 01:26 PM, Li, JinjingX wrote: >>>> Hi Jinil >>>> >>>> You could find depanneur path with command "which depanneur". >>>> >>>> In your situation, you'd better reinstall gbs on your side after cleaning >>>> installed gbs and its dependences. >>>> >>>> >>>> Thanks >>>> Li Jinjing >>>> >>>> -----Original Message----- >>>> From: Jinil P. [mailto:jini...@nestgroup.net] >>>> Sent: Friday, September 05, 2014 1:44 PM >>>> To: Li, JinjingX >>>> Cc: Anoop Babu; ivi@lists.tizen.org >>>> Subject: Re: Expansion error while GBS build >>>> >>>> Dear Li, >>>> >>>> I didn't find these files in local root and in GBS-ROOT. >>>> Should I install any package to get these files. >>>> >>>> Thank you for your support. >>>> >>>> >>>> Thanks & Regards >>>> Jinil P >>>> >>>> >>>> >>>> On Thursday 04 September 2014 06:35 PM, Li, JinjingX wrote: >>>>> Hi Jinil >>>>> >>>>> It is ok with your .gbs.conf file. Could you please check whether there >>>>> is getchangetarget script under dir /usr/lib/build/? >>>>> >>>>> I suggested you to add Required:cmake and Requried: cmake-x86-arm in >>>>> build.conf, which won't affect calling the /usr/lib/build/getchangetarget >>>>> in depanneur. >>>>> >>>>> The direct resolve method is reinstall gbs after clean it and the >>>>> dependences thoroughly. >>>>> >>>>> The path of 'depanneur' is /usr/bin/depanneur. >>>>> >>>>> Thanks >>>>> Li Jinjing >>>>> >>>>> -----Original Message----- >>>>> From: Jinil P. [mailto:jini...@nestgroup.net] >>>>> Sent: Thursday, September 04, 2014 4:37 PM >>>>> To: Li, JinjingX >>>>> Cc: Anoop Babu; ivi@lists.tizen.org >>>>> Subject: Re: Expansion error while GBS build >>>>> >>>>> Dear Li, >>>>> >>>>> Thank you for the reply. >>>>> >>>>> Could you please mention the path of 'depanneur'. >>>>> I not able to find it in the source path. >>>>> After giving build with the below mentioned steps the build is getting >>>>> aborted. >>>>> The build log and GBS conf are attached with this mail. >>>>> Could you please help to sort out this issue. >>>>> >>>>> Thanks for your support. >>>>> >>>>> Thanks & Regards >>>>> Jinil P >>>>> >>>>> On Thursday 04 September 2014 12:14 AM, Li, JinjingX wrote: >>>>>> Hi Jinil >>>>>> >>>>>> Sorry for replying a little late, let me analyze the issues you met and >>>>>> also I met : >>>>>> >>>>>> 1. For the package framework/web/wrt, the revision >>>>>> "2.0_release-0-g0ea9212" in git tree has been removed, so commented it >>>>>> out in manifest is right. >>>>>> 2. For the build hang issue, I add the resolve way in the attachment >>>>>> doc: add cmake in build.conf and add libcurl-x86-arm for cmake in >>>>>> prebuilt/toolchain-arm. >>>>>> 3. Comment out the code " push @args, "--debug"; " in depanneur, where >>>>>> is about 1409 line. >>>>>> >>>>>> BTW, this tizen repo is too old, perhaps gbs couldn't do the full >>>>>> feature's support, packages are outdated there. >>>>>> Now tizen3.0 common supports gbs build armv7l, you could use it. >>>>>> >>>>>> Thanks >>>>>> Li Jinjing >>>>>> >>>>>> -----Original Message----- >>>>>> From: Jinil P. [mailto:jini...@nestgroup.net] >>>>>> Sent: Monday, September 01, 2014 3:55 PM >>>>>> To: Li, JinjingX >>>>>> Cc: Anoop Babu; ivi@lists.tizen.org >>>>>> Subject: Re: Expansion error while GBS build >>>>>> >>>>>> Dear Li, >>>>>> >>>>>> Thank you for the reply. >>>>>> >>>>>> Yes we are trying to create the tizen2.0_ivi arm image. >>>>>> Yes it will be a great help if you could help to analyze the build >>>>>> failure. >>>>>> >>>>>> Thank you for your support. >>>>>> >>>>>> Thanks & Regards >>>>>> Jinil P >>>>>> >>>>>> On Monday 01 September 2014 01:11 PM, Li, JinjingX wrote: >>>>>>> Hi Jinil >>>>>>> >>>>>>> I have got your email, I am reproducing the issue you met. >>>>>>> You will create tizen2.0_ivi arm image to use, right? >>>>>>> >>>>>>> I think there must be some build failed packages based on manifest from >>>>>>> the repo you are using, because this repo is outdated, long time >>>>>>> inactive. >>>>>>> >>>>>>> We can help to analyzing the build failed reason, if needed. >>>>>>> >>>>>>> >>>>>>> Thanks >>>>>>> Li Jinjing >>>>>>> >>>>>>> -----Original Message----- >>>>>>> From: Jinil P. [mailto:jini...@nestgroup.net] >>>>>>> Sent: Friday, August 29, 2014 9:49 PM >>>>>>> To: Li, JinjingX >>>>>>> Cc: Anoop Babu; ivi@lists.tizen.org >>>>>>> Subject: Re: Expansion error while GBS build >>>>>>> >>>>>>> Dear Li, >>>>>>> >>>>>>> After following the procedure mentioned in the earlier mails ( the >>>>>>> doc >>>>>>> attachment) the build is getting hang after rpm build of around 300+ >>>>>>> packages. >>>>>>> Could you please help to resolve this issue. >>>>>>> >>>>>>> The required logs are attached with this mail. >>>>>>> >>>>>>> Thank you for your support. >>>>>>> >>>>>>> Thanks & Regards >>>>>>> Jinil P >>>>>>> >>>>>>> >>>>>>> On Thursday 28 August 2014 06:39 PM, Jinil P. wrote: >>>>>>>> Dear Li, >>>>>>>> >>>>>>>> Thank you for the reply. >>>>>>>> >>>>>>>> After doing the "repo sync -j 32" I was getting a error saying >>>>>>>> "Syncing work tree: 78% (575/736) error: in `sync -j 32`: >>>>>>>> revision >>>>>>>> 2.0_release-0-g0ea9212 in framework/web/wrt not found" >>>>>>>> But after commenting out the "toolchains" and "path : >>>>>>>> framework/web/wrt revision : 2.0_release-0-g0ea9212" in "projects.xml" >>>>>>>> the build is going on. Some of the packages like >>>>>>>> "avahi-0.6.30-18", "bluez-4.101_19-19"... etc are getting failed >>>>>>>> but the build is not yet aborted. >>>>>>>> Could you please tell me whether the build is going in right >>>>>>>> direction or not.? >>>>>>>> >>>>>>>> The sync error log and modified projects.xml(line nos :- 577,634 >>>>>>>> to >>>>>>>> 728) are attached with this mail. >>>>>>>> >>>>>>>> Thanks in advance. >>>>>>>> >>>>>>>> Thanks & Regards >>>>>>>> Jinil P >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> On Tuesday 26 August 2014 09:43 PM, Li, JinjingX wrote: >>>>>>>>> little in the attached document with red font, please follow it to do >>>>>>>>> gbs build. >>>>>>>>> If meet other issues, ask me. >>>>>>>>> >>>>>>>>> Thanks >>>>>>>>> Li Jinjing >>>>>>> ________________________________ >>>>>>> >>>>>>> Confidentiality Statement / Disclaimer : This message and any >>>>>>> attachments is intended for the sole use of the intended recipient. It >>>>>>> may contain confidential information. Any unauthorized use, >>>>>>> dissemination or modification is strictly prohibited. If you are not >>>>>>> the intended recipient, please notify the sender immediately then >>>>>>> delete it from all your systems, and do not copy, use or print. >>>>>>> Internet communications are not secure and it is the responsibility of >>>>>>> the recipient to make sure that it is virus/malicious code exempt. >>>>>>> >>>>>>> The company/sender cannot be responsible for any unauthorized >>>>>>> alterations or modifications made to the contents. If you require any >>>>>>> form of confirmation of the contents, please contact the >>>>>>> company/sender. The company/sender is not liable for any errors or >>>>>>> omissions in the content of this message. >>>>>>> >>>>>>> ________________________________ >>>>>>> >>>>>> ________________________________ >>>>>> >>>>>> Confidentiality Statement / Disclaimer : This message and any >>>>>> attachments is intended for the sole use of the intended recipient. It >>>>>> may contain confidential information. Any unauthorized use, >>>>>> dissemination or modification is strictly prohibited. If you are not the >>>>>> intended recipient, please notify the sender immediately then delete it >>>>>> from all your systems, and do not copy, use or print. Internet >>>>>> communications are not secure and it is the responsibility of the >>>>>> recipient to make sure that it is virus/malicious code exempt. >>>>>> >>>>>> The company/sender cannot be responsible for any unauthorized >>>>>> alterations or modifications made to the contents. If you require any >>>>>> form of confirmation of the contents, please contact the company/sender. >>>>>> The company/sender is not liable for any errors or omissions in the >>>>>> content of this message. >>>>>> >>>>>> ________________________________ >>>>>> >>>>> ________________________________ >>>>> >>>>> Confidentiality Statement / Disclaimer : This message and any attachments >>>>> is intended for the sole use of the intended recipient. It may contain >>>>> confidential information. Any unauthorized use, dissemination or >>>>> modification is strictly prohibited. If you are not the intended >>>>> recipient, please notify the sender immediately then delete it from all >>>>> your systems, and do not copy, use or print. Internet communications are >>>>> not secure and it is the responsibility of the recipient to make sure >>>>> that it is virus/malicious code exempt. >>>>> >>>>> The company/sender cannot be responsible for any unauthorized alterations >>>>> or modifications made to the contents. If you require any form of >>>>> confirmation of the contents, please contact the company/sender. The >>>>> company/sender is not liable for any errors or omissions in the content >>>>> of this message. >>>>> >>>>> ________________________________ >>>>> >>>> ________________________________ >>>> >>>> Confidentiality Statement / Disclaimer : This message and any attachments >>>> is intended for the sole use of the intended recipient. It may contain >>>> confidential information. Any unauthorized use, dissemination or >>>> modification is strictly prohibited. If you are not the intended >>>> recipient, please notify the sender immediately then delete it from all >>>> your systems, and do not copy, use or print. Internet communications are >>>> not secure and it is the responsibility of the recipient to make sure that >>>> it is virus/malicious code exempt. >>>> >>>> The company/sender cannot be responsible for any unauthorized alterations >>>> or modifications made to the contents. If you require any form of >>>> confirmation of the contents, please contact the company/sender. The >>>> company/sender is not liable for any errors or omissions in the content of >>>> this message. >>>> >>>> ________________________________ >>>> >>> ________________________________ >>> >>> Confidentiality Statement / Disclaimer : This message and any attachments >>> is intended for the sole use of the intended recipient. It may contain >>> confidential information. Any unauthorized use, dissemination or >>> modification is strictly prohibited. If you are not the intended recipient, >>> please notify the sender immediately then delete it from all your systems, >>> and do not copy, use or print. Internet communications are not secure and >>> it is the responsibility of the recipient to make sure that it is >>> virus/malicious code exempt. >>> >>> The company/sender cannot be responsible for any unauthorized alterations >>> or modifications made to the contents. If you require any form of >>> confirmation of the contents, please contact the company/sender. The >>> company/sender is not liable for any errors or omissions in the content of >>> this message. >>> >>> ________________________________ >>> _______________________________________________ >>> IVI mailing list >>> IVI@lists.tizen.org >>> https://lists.tizen.org/listinfo/ivi >>> >> ________________________________ >> >> Confidentiality Statement / Disclaimer : This message and any attachments is >> intended for the sole use of the intended recipient. It may contain >> confidential information. Any unauthorized use, dissemination or >> modification is strictly prohibited. If you are not the intended recipient, >> please notify the sender immediately then delete it from all your systems, >> and do not copy, use or print. Internet communications are not secure and it >> is the responsibility of the recipient to make sure that it is >> virus/malicious code exempt. >> >> The company/sender cannot be responsible for any unauthorized alterations or >> modifications made to the contents. If you require any form of confirmation >> of the contents, please contact the company/sender. The company/sender is >> not liable for any errors or omissions in the content of this message. >> >> ________________________________ >> > ________________________________ > > Confidentiality Statement / Disclaimer : This message and any attachments is > intended for the sole use of the intended recipient. It may contain > confidential information. Any unauthorized use, dissemination or modification > is strictly prohibited. If you are not the intended recipient, please notify > the sender immediately then delete it from all your systems, and do not copy, > use or print. Internet communications are not secure and it is the > responsibility of the recipient to make sure that it is virus/malicious code > exempt. > > The company/sender cannot be responsible for any unauthorized alterations or > modifications made to the contents. If you require any form of confirmation > of the contents, please contact the company/sender. The company/sender is not > liable for any errors or omissions in the content of this message. > > ________________________________ > _______________________________________________ > IVI mailing list > IVI@lists.tizen.org > https://lists.tizen.org/listinfo/ivi > ________________________________ Confidentiality Statement / Disclaimer : This message and any attachments is intended for the sole use of the intended recipient. It may contain confidential information. Any unauthorized use, dissemination or modification is strictly prohibited. If you are not the intended recipient, please notify the sender immediately then delete it from all your systems, and do not copy, use or print. Internet communications are not secure and it is the responsibility of the recipient to make sure that it is virus/malicious code exempt. The company/sender cannot be responsible for any unauthorized alterations or modifications made to the contents. If you require any form of confirmation of the contents, please contact the company/sender. The company/sender is not liable for any errors or omissions in the content of this message. ________________________________ _______________________________________________ IVI mailing list IVI@lists.tizen.org https://lists.tizen.org/listinfo/ivi
