On Thu, 2011-07-07 at 02:39 +0800, Selbak, Rolla N wrote: > On 7/6/11 3:10 AM, "Li, Yan I" <[email protected]> wrote: > > >On Wed, 2011-07-06 at 16:07 +0800, Nashif, Anas wrote: > >> As long as you are using a link you should not worry about it, since > >> obs adds the build number from the origin to that of the destination > >> of the link, If you are not using links, then the proposed solution > >> below should also work. > >> > >Thanks. I'm importing an old package so I have to manually set the > >Release number. Didn't know such a good trick before. :) > > What are you doing specifically? I'm a bit worried about you changing the > release number, as the version/release in the .spec should be > corresponding to the version/release of the actual code you're packaging.
Release in spec should be corresponding to the release of actual code? I don't think so. Only the Version field should be corresponding to the actual code's version, and the Release is totally controlled by OBS and reflects the changes we made in OBS, mostly related to the changes of packaging, rather than the changes of the actual code from upstream. But please don't worry, my story is like this: I've pushed a package from devel:enterprise to Trunk:Testing so I don't have to maintain it in devel:enterprise any more. But that package is still missing from MeeGo 1.1 so I copypac-ed the package from devel:enterprise to devel:enterprise:1.1. Now I have to make sure the package in devel:enterprise:1.1 has a higher Release number than the old build from devel:enterprise or it won't install automatically on clients. > Here's a good reference btw: > > http://wiki.meego.com/Packaging/Guidelines#Version_and_Release -- Best regards, Li, Yan MeeGo Team, Opensource Technology Center, SSG, Intel Office tel.: +86-10-5751-1695 (inet: 8-751-1695) OpenPGP key: 5C6C31EF IRC: yanli on network irc.freenode.net _______________________________________________ MeeGo-packaging mailing list [email protected] http://lists.meego.com/listinfo/meego-packaging
