Yes, it's right. Developers just confirmed it's has been fixed and deployed already. But this affected package has not been updated after that.
thanks - jf.ding On Tue, Nov 19, 2013 at 01:09:02AM +0800, Kanevskiy, Alexander wrote: > On 18/11/13 18:58 , "Lynch, Rusty" <[email protected]> wrote: > > >Packages that have more then one spec file will not include the VCS > >data. I'm not saying this is the way it should be, but an observation > >of mine from a long time ago. > > Rusty, that is a bug that should be fixed by now. > I remember to see that in gbs and backend release notes (0.19 from October > release if memory serves me well). > Probably for some of those linked packages there were no updates recently. > > > > > --rusty > > > >On Mon, 2013-11-18 at 16:26 +0000, Kanevskiy, Alexander wrote: > >> On 18/11/13 17:17 , "Jian-feng Ding" <[email protected]> wrote: > >> > >> > >> For cases like python-libxml2 it means that package was done during > >> bootstrap period, and afterwards there was no updates. > >> Once maintainer of that package submits new version, it will have proper > >> VCS tag and will be marked in manifest. > >> > >> For cases as python-rpm, it was a fix in backend code that suppose to > >> update VCS tag in all “slave” packages. > >> In case if you’re building packages locally, it should be not a problem, > >> as gbs will try to build all *.spec files available in git tree (so it > >>is > >> enough to mention only main package in manifest) > >> > >> > >> >1. the rpm files without VCS mean they are submitted by the regular > >>work > >> >process. Possible it's for some quick solution of new packages, but it > >> >need to be fixed soon. > >> >2. In Tizen, some packages are just link package of others. E.g. the > >> >'python-rpm' is linked from rpm, and they share the same git tree. So > >>you > >> >cannot find the corresponding git in manifest. > >> > > >> >For other cases, it should be a real issue, please submit JIRA ticket > >>to > >> >report it. > >> > > >> >thanks > >> >- jf.ding > >> > > >> >On Mon, Nov 18, 2013 at 04:47:36PM +0100, Ronan Le Martret wrote: > >> >> Hi all, > >> >> I see two problems in the repo manifest files of Tizen projects. > >> >> > >> >> 1) Some packages do not provides VCS, which mean that we do not > >>have > >> >>a > >> >> pointer to the source code (problem is indicated in the manifest see > >> >>below > >> >> (a) ). > >> >> 2) Some packages are missing in the manifest (b). > >> >> > >> >> (a) > >> >> As you can seen at the end of the manifest files . > >> >> "<!-- Source packages without VCS infomation: --> > >> >> <!-- > >> >> <project name="python-libxml2-2.8.0-3.16.i686.rpm" > >> >> path="unknown/python-libxml2-2.8.0-3.16.i686.rpm" > >> >>revision="2.8.0-3.16"/> > >> >> --> > >> >> ..." > >> >> > >> >> > >> >> (b) Some packages are missing. > >> >> I'm find a missing package (but perhaps, there are more than one). > >> >> Package "python-rpm", is present in the IVI repository but not in > >>the > >> >>repo > >> >> manifest file. > >> >> > >> >> > >> >> The two problems have the same consequences, we can't rebuild those > >> >> packages from git source with local tools (gbs) or in a private OBS. > >> >> > >> >> Sample project: > >> >> ivi > >> >> Manifest: > >> >> > >> >> > >> > >>>>http://download.tizen.org/snapshots/tizen/ivi/ivi/latest/builddata/mani > >>>>fe > >> >>st/ > >> >> > >>______________________________________________________________________ > >> >> > >> >> Q: > >> >> Does somebody know where is the source code of the tools which > >>generate > >> >>the > >> >> repo manifest files? > >> >> > >> >> I would be happy to check if I can offer a correction would the > >>source > >> >> code available. > >> >> > >> >> Regards, > >> >> -- > >> >> Ronan Le Martret > >> >> Intel Open Source Technology Center > >> > > >> >> _______________________________________________ > >> >> Dev mailing list > >> >> [email protected] > >> >> https://lists.tizen.org/listinfo/dev > >> > > >> >_______________________________________________ > >> >Dev mailing list > >> >[email protected] > >> >https://lists.tizen.org/listinfo/dev > >> > > >> > >> > > > > > > > > > -- > Best regards, Alexander Kanevskiy. > > > _______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
