On 24.6.2014 16:23, Schaufler, Casey wrote:
I look at the package in question and see that what’s in IVI is very
different from what’s in Common. There is, it turns out, a **different**
problem in Common. I can fix Common, but that does nothing for IVI. I
keep getting pestered to fix IVI, but until it catches up there’s
nothing I can do. Further, other “unrelated” changes impact the
solution. How can I find the state of IVI without dredging the build
logs? The tree does not tell me.
I have the same issue, my packages are in "upstream" profile which is
supposed to end up first in Common (also takes a while, because they are
slow to accept submissions). And then eventually it is supposed to end
up in IVI.
Seems to take around one month for changes to propagate to IVI builds.
- Jussi
_______________________________________________
Dev mailing list
[email protected]
https://lists.tizen.org/listinfo/dev
