Hi, Jay On Wednesday, October 29, 2014 at 11:09 AM, Jay D Bhatt wrote:
> Hi, > > I had downloaded the march source code using below xml file, here the version > of murphy code is 0.0.49.2-1: > http://download.tizen.org/releases/milestone/tizen/ivi/tizen_20140422.1/builddata/manifest/ > > But when I look at rpm packages for march at below path , here the version of > murphy code is 0.0.49.2-3.1: > http://download.tizen.org/releases/milestone/tizen/ivi/tizen_20140422.1/repos/ivi/ia32/packages/i686/ > > So, I think that source code is different for both versions. Then I extract > and compare source rpm for both version and I find many files changed ( i.e > more than 117 files in total ). > > > Should not be. I have checked the content of the manifest and src.rpm, they are pointing to the same git commit revision. - In manifest.xml: <project name="profile/ivi/murphy" path="profile/ivi/murphy" revision="b917854329ce4f56b4a4481ddf90451bf2829ed3”/> - Inside the src.rpm: http://download.tizen.org/releases/milestone/tizen/ivi/tizen_20140422.1/repos/ivi/source/murphy-0.0.49.2-3.1.src.rpm, the %{VCS} tag is the same revision. (you can just download the rpm file, and query by ‘rpm -qp --%{VCS} abc.rpm) The file changes you have noticed might be from the packaging actions. But the source code themselves should have no difference. > > As, Philippe said, I can extract source code from source rpm, but here again > I cannot build it using gbs build, since it does not have .git related > folders in source rpms. > > Is there any way to do gbs build after extracting source rpm? or is there any > way to get source code of murphy with specific version number 0.0.49.2-3.1 > through git clone or gbs clone, so that I can do gbs build for murphy for > version 0.0.49.2-3.1 ? > > > Once you have used `git clone` to clone the git tree to your local machine, all of the files and revisions are in your machine already. The following problem is you need only to `git checkout` to specific revision, e.g. the b917854329ce4f56b4a4481ddf90451bf2829ed3 for murphy. And then run `gbs build` inside this local git directory. Thanks - jf.ding > > > Thanks, > Jay > > From: Ylinen, Mikko [mailto:mikko.yli...@intel.com] > Sent: 28 October 2014 21:57 > To: Jay D Bhatt > Cc: ivi@lists.tizen.org (mailto:ivi@lists.tizen.org) > Subject: Re: Unable to download specific version of source code > > > Hi, > > I want to download murphy source code for version murphy-0.0.49.2-3.1, but > when I do git clone I get murphy-0.0.49.2-1. > > > > They are the same (0.0.49.2). The difference comes from the RPM release > counter. > > > > rpm -qp --qf '%{NAME} has version %{VERSION}\n' <your_murphy_rpm>.rpm > > > > > > > > > > (I made an assumption that the RPM you downloaded is from the same release > directory you got the manifest.xml to do repo sync) > > > > > > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~Disclaimer~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > Information contained and transmitted by this e-mail is confidential and > proprietary to IGATE and its affiliates and is intended for use only by the > recipient. If you are not the intended recipient, you are hereby notified > that any dissemination, distribution, copying or use of this e-mail is > strictly prohibited and you are requested to delete this e-mail immediately > and notify the originator or mailad...@igate.com > (mailto:mailad...@igate.com). IGATE does not enter into any agreement with > any party by e-mail. Any views expressed by an individual do not necessarily > reflect the view of IGATE. IGATE is not responsible for the consequences of > any actions taken on the basis of information provided, through this email. > The contents of an attachment to this e-mail may contain software viruses, > which could damage your own computer system. While IGATE has taken every > reasonable precaution to minimise this risk, we cannot accept liability for > any damage which you sustain as a result of software viruses. You should > carry out your own virus checks before opening an attachment. To know more > about IGATE please visit www.igate.com (http://www.igate.com). > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > _______________________________________________ > IVI mailing list > IVI@lists.tizen.org (mailto:IVI@lists.tizen.org) > https://lists.tizen.org/listinfo/ivi > >
_______________________________________________ IVI mailing list IVI@lists.tizen.org https://lists.tizen.org/listinfo/ivi
