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/manife >>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. --------------------------------------------------------------------- Intel Finland Oy Registered Address: PL 281, 00181 Helsinki Business Identity Code: 0357606 - 4 Domiciled in Helsinki 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. _______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
