Thema: package versions own 4.1 build vs OpenATV feeds server do not match

I don't understand what's going wrong.
I build some OpenATV 4.1 dreambox images, but if I do an update, always Packages get updated, this also happens with a completely fresh build image.
examples:

Upgrading enigma2-plugin-systemplugins-toolkit from 2.0+git1+8b03e94e23-r5.0 to 2.0+git1+5465b8d3da-r5.2 on root.
Upgrading enigma2-plugin-extensions-cutlisteditor from 3.0+git1+9606569e26-r12.0 to 3.0+git3+9606569e26-r11.0 on root.
Upgrading enigma2-plugin-extensions-dflash from 12.6+git0+7d176f437d-r0.1 to 12.6+git0+7d176f437d-r0.3 on root.

What is responsible for the r5.0 / r5.2 difference ?
Also the same question for git1 / git3

Zitat von arn354

You can't update your local build image with openatv feed.
Each buildsystem uses its own PR-database.

git0 - means first buildcycle of that package
git1 - means second buildcycle of that package
and so on.

So git0 on your fresh buildmachine "might" be the same like git34 on our buildserver.

Next question - are you sure you build from OE-A build-enviroment branch 2.2 ?
Because that would be openATV 4.1 - and i think the needed makefile for it is still not public.

I got the makefile link from Captain.