Update ... On Friday 11 October 2013 14:43:17 Jan-Simon Möller wrote: > Hi JF.Ding, > > thanks for your reply. > > On Friday 11 October 2013 20:04:53 Jian-feng Ding wrote: > > > This works for a snapshot, true. How about the tip ? > > > > It's the clue to figure out which git is being used in OBS (and then > > repos/images). So for 'tip', just looking for the latest snapshot. > > Well and this is what I want. Mapping back from what OBS builds to the git. > Reproducible and unique. > Right now what I can see is: > > * git-obs-mapping provides general rules like branch "tizen" in all git > repos goes into "Tizen" in OBS. Fine. > > * Not all git branches have a branch "tizen" and "master". "master" should > be an alias to tizen IMHO for simplicity.
Ok, we seem to match on the tag "submit/tizen" . Then we should have a "tizen"-branch always point to the latest tag in all repos. Currently this is not the case. For the releases, this is mostly true (tizen_2.x) . It is just not consistent over all repos! For osp-* and tizen.org.* we do not match the name in git with the name in obs. Can we fix this somehow ? > * In OBS some specfiles have a VCS tag. Which holds this information. BUT > not all packages have this tag. The most relevant have. So I'm just confused about: Look at package acl in "Tizen" , "Tizen:Mobile" , "Tizen:IVI" . Actually they should match, but they don't. Tizen : submit/tizen/20130904.094408 Tizen:Mobile : submit/tizen/20130912.073703 Tizen:IVI : submit/tizen/20130912.073703 Why is "Tizen" older ? Do we no longer use "Tizen" as base layer for Mobile and IVI ? /me confused. Best, JS _______________________________________________ General mailing list [email protected] https://lists.tizen.org/listinfo/general
