All of lore.kernel.org
 help / color / mirror / Atom feed
* PR server question
@ 2014-01-08 12:00 Gary Thomas
  2014-01-08 12:43 ` Martin Jansa
  0 siblings, 1 reply; 2+ messages in thread
From: Gary Thomas @ 2014-01-08 12:00 UTC (permalink / raw)
  To: Yocto Project

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?

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------


^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: PR server question
  2014-01-08 12:00 PR server question Gary Thomas
@ 2014-01-08 12:43 ` Martin Jansa
  0 siblings, 0 replies; 2+ messages in thread
From: Martin Jansa @ 2014-01-08 12:43 UTC (permalink / raw)
  To: Gary Thomas; +Cc: Yocto Project

[-- Attachment #1: Type: text/plain, Size: 1422 bytes --]

On Wed, Jan 08, 2014 at 05:00:12AM -0700, Gary Thomas wrote:
> 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.

> 
> -- 
> ------------------------------------------------------------
> Gary Thomas                 |  Consulting for the
> MLB Associates              |    Embedded world
> ------------------------------------------------------------
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2014-01-08 12:42 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-01-08 12:00 PR server question Gary Thomas
2014-01-08 12:43 ` Martin Jansa

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.