On Wed, Sep 19, 2012 at 5:01 AM, Andrey Borzenkov <arvidjaar@gmail.com> wrote:

I am new to openSUSE packaging workflow so please bear with me.

When I branch some package, it gets release number based on revision of parent package; later release number is incremented with each commit/rebuild, so if I install branched package it will come newer than parent. Is it correct?

Now after I submit changes to parent package and it is accepted - will release number of parent package automatically compare newer than my local branch once it is available from official repository?

On other systems I had to locally extend release number to make sure it will update "upstream" package it is based on, but will be overwritten if upstream gets updated. How does it work in openSUSE?

Related question is for package version bump. If I update package branch to new version and submit it - is it ensure that package from official repository will come newer than my local build?

Thank you!

-andrey

In general the release number should be 0 (zero) in the specfile. OBS tracks the release number internally and increments it with each update/checkin. I find that the switch from my home package to the devel version normally requires me to "force" the update. For instance "zypper se -s libewf2" currently shows I have libewf2 from my home project: i | libewf2 | package | 0.0.0+20120813-45.1 | x86_64 | home:gregfreemyer:Tools-for-forensic-boot-cd v | libewf2 | package | 0.0.0+20120813-9.1 | x86_64 | security I know they are basically the same package, so to "downgrade" to the version in security I would do: sudo zypper in -f libewf2-0.0.0+20120813-9.1 HTH Greg -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org