PR server question
I'm using a local PR server for my builds, working on my Linux kernel. When I run this sequence:
$ bitbake virtual/kernel -c devshell
... fiddle with some kernel sources
$ bitbake virtual/kernel -C compile; bitbake package-index
I notice that the package revision for 'kernel-image-*' goes up
by 3 on every iteration.Not that it makes much difference (or does it?), but does this make sense? Why does it not just increase by 1 since I've only actually rebuilt the package once?
Signature · 4 lines
------------------------------------------------------------ Gary Thomas | Consulting for the MLB Associates | Embedded world ------------------------------------------------------------
Quoted 11 lines · Gary Thomas
I'm using a local PR server for my builds, working on my Linux kernel. When I run this sequence:
$ bitbake virtual/kernel -c devshell ... fiddle with some kernel sources $ bitbake virtual/kernel -C compile; bitbake package-index I notice that the package revision for 'kernel-image-*' goes up by 3 on every iteration.Not that it makes much difference (or does it?), but does this make sense? Why does it not just increase by 1 since I've only actually rebuilt the package once?
I don't remember if it was resolved already, but before it was caused by qemuarm/qemux86/qemux86-64 using different SRCREVs so it was bumped 3 times every time it was parsed (and causing continual rebuilds for multi-machine builds).
Now the continual rebuilds should be fixed by PR server returning the same number to each MACHINE, but maybe there was something left.
Quoted 10 lines
Signature · 9 lines
-- ------------------------------------------------------------ Gary Thomas | Consulting for the MLB Associates | Embedded world ------------------------------------------------------------ _______________________________________________ yocto mailing list [email protected] https://lists.yoctoproject.org/listinfo/yocto
Signature · 1 line
Martin 'JaMa' Jansa jabber: [email protected]