Re: 回复: Re: Tizen Build Issues

2014-02-17 Thread Thiago Macieira
Em seg 17 fev 2014, às 16:12:41, hello tizen escreveu: > Okay,let me try again. I want do fully rebuild of tizen source code. > download.tizen.org is not what I want to use to get the job done. Neither > gbs. Is there any other solution available? Please dont sell me > gbs+download.tizen.org again,

Re: how to test a rpm on ivi? (seem security related)

2014-02-17 Thread Ylinen, Mikko
On Tue, Feb 18, 2014 at 3:47 AM, Zhao, Halley wrote: > I don't have SMACK manifest file yet, how to add it? > Thanks > See any other package (.manifest and .spec) as an example. https://wiki.tizen.org/wiki/Security:SmackThreeDomainModel#The_Default_Floor_Domain_Manifest_File ___

RE: how to test a rpm on ivi? (seem security related)

2014-02-17 Thread Zhao, Halley
Thanks Ning. It works. I installed these packages in Weston terminal (instead of ctrl+alt+Fn); then it works. Thanks From: Wang, Ning W Sent: Tuesday, February 18, 2014 8:33 AM To: Zhao, Halley; ivi@lists.tizen.org Subject: RE: how to test a rpm on ivi? (seem security related) Halley, You can

RE: how to test a rpm on ivi? (seem security related)

2014-02-17 Thread Zhao, Halley
I don't have SMACK manifest file yet, how to add it? Thanks From: Ylinen, Mikko [mailto:mikko.yli...@intel.com] Sent: Monday, February 17, 2014 7:21 PM To: Zhao, Halley Cc: ivi@lists.tizen.org Subject: Re: how to test a rpm on ivi? (seem security related) On Mon, Feb 17, 2014 at 12:18 PM, Zhao

RE: how to test a rpm on ivi? (seem security related)

2014-02-17 Thread Wang, Ning W
Halley, You can try installing the rpm in weston terminal. Thanks, Ning From: ivi-boun...@lists.tizen.org [mailto:ivi-boun...@lists.tizen.org] On Behalf Of Zhao, Halley Sent: Monday, February 17, 2014 6:19 PM To: ivi@lists.tizen.org Subject: how to test a rpm on ivi? (seem security related) wh

回复: Re: Tizen Build Issues

2014-02-17 Thread hello tizen
Okay,let me try again. I want do fully rebuild of tizen source code. download.tizen.org is not what I want to use to get the job done. Neither gbs. Is there any other solution available? Please dont sell me gbs+download.tizen.org again, please. The combination sucked too much human+machines hou

Re: Tizen 2.2 Build Issues

2014-02-17 Thread Thiago Macieira
Em seg 17 fev 2014, às 04:15:26, hello tizen escreveu: > -2.You seemed to have mis-understood what I asked. Again, let me try again, > I‘m looking for a solution to rebuild all released package from Its > released git head and tag(no download.tizen.org). Is Gbs capable of doing > that? If not, why

回复: RE: 回复: Re: 回复: Re: Tizen 2.2 Build Issues

2014-02-17 Thread hello tizen
-2.You seemed to have mis-understood what I asked. Again, let me try again, I‘m looking for a solution to rebuild all released package from Its released git head and tag(no download.tizen.org). Is Gbs capable of doing that? If not, why do you waste your time in pointing people to somthing that w

Re: network interfaces not detected on nexcom vtc6200

2014-02-17 Thread Ylinen, Mikko
On Sun, Feb 16, 2014 at 9:40 PM, mouton maximilien wrote: > > > > I think this is a matter of missing driver. Is there any way to get them? > > If you know the linux kernel driver for your networking hardware, you can easily rebuild a kernel for yourself with the help of [1]. -- Mikko [1] https:

Re: how to test a rpm on ivi? (seem security related)

2014-02-17 Thread Ylinen, Mikko
On Mon, Feb 17, 2014 at 12:18 PM, Zhao, Halley wrote: > > > what's the correct way to deploy a new rpm for test? > > > > After update some packages and pass 'gbs build', > > I installed these rpm package on device by 'rpm -ivh -nodeps -force > libva-1.2.1-0.i686.rpm'. > > > > However, in weston te

how to test a rpm on ivi? (seem security related)

2014-02-17 Thread Zhao, Halley
what's the correct way to deploy a new rpm for test? After update some packages and pass 'gbs build', I installed these rpm package on device by 'rpm -ivh -nodeps -force libva-1.2.1-0.i686.rpm'. However, in weston terminal, the corresponding libs becomes invisible to 'app' user, then app fail