All of lore.kernel.org
 help / color / mirror / Atom feed
* Need advice on tracking down "-dirty"
@ 2015-05-08  9:36 Spriggs, Jim
  2015-05-08 14:08 ` Bruce Ashfield
  0 siblings, 1 reply; 3+ messages in thread
From: Spriggs, Jim @ 2015-05-08  9:36 UTC (permalink / raw)
  To: yocto@yoctoproject.org; +Cc: Wilfert, Dennis, Weber, Markus

Hi Guys,

Using poky dizzy with meta-altera (from OE), and trying to implement a simple loadable kernel-module by following the method outlined  in Lab3 of  https://www.yoctoproject.org/sites/default/files/kernel-lab-1.6.pdf.

I'm doing an "rm -rf tmp" before starting "bitbake virtual/kernel  my-image-recipe".

The build seems to work just fine: the kernel-module-xxxx-1.0-r0.machine.rpm appears as expected under .../deploy/...

The package installation task fails, however, with:

    error: Can't install kernel-module-xxxx-1.0-r0@machine : no package provides kernel-3.15.0-00184-g5ae31a7

and indeed, the kernel packages available in .../deploy/... are:

    kernel-3.15-r1.machine.rpm
    kernel-3.15.0-00184-g5ae31a7-dirty-3.15-r1.machine.rpm
    kernel-dev-3.15-r1.machine.rpm
    kernel-image-3.15.0-00184-g5ae31a7-dirty-3.15-r1.machine.rpm


Yet "git status" reports "nothing to commit, w.d. clean" for both the main poky tree and the meta-altera sub-tree.

So I guess the n00b needs a clue about how to find out why and where the dirty-flag is getting set?

Thanks for listening!
--
jim spriggs

PS: the real names of module and machine have been redacted above to protect the guilty...
PPS: sorry about the company sig., I can't switch it off.


________________________________

RAYLASE AG
Argelsrieder Feld 2+4
82234 Wessling
Germany
Tel.: +49-(0)8153/88 98-0
Fax: +49-(0)8153/88 98-10
http://www.raylase.de

District Court Munich, HRB 131450

Board: Peter von Jan (CEO)

Supervisory Board: Dr. Ulrich Lohmann (Chairman)


Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail ist nicht gestattet.

This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden.

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

* Re: Need advice on tracking down "-dirty"
  2015-05-08  9:36 Need advice on tracking down "-dirty" Spriggs, Jim
@ 2015-05-08 14:08 ` Bruce Ashfield
  2015-05-09 10:18   ` Spriggs, Jim
  0 siblings, 1 reply; 3+ messages in thread
From: Bruce Ashfield @ 2015-05-08 14:08 UTC (permalink / raw)
  To: Spriggs, Jim, yocto@yoctoproject.org; +Cc: Wilfert, Dennis, Weber, Markus

On 2015-05-08 5:36 AM, Spriggs, Jim wrote:
> Hi Guys,
>
> Using poky dizzy with meta-altera (from OE), and trying to implement a simple loadable kernel-module by following the method outlined  in Lab3 of  https://www.yoctoproject.org/sites/default/files/kernel-lab-1.6.pdf.
>
> I'm doing an "rm -rf tmp" before starting "bitbake virtual/kernel  my-image-recipe".
>
> The build seems to work just fine: the kernel-module-xxxx-1.0-r0.machine.rpm appears as expected under .../deploy/...
>
> The package installation task fails, however, with:
>
>      error: Can't install kernel-module-xxxx-1.0-r0@machine : no package provides kernel-3.15.0-00184-g5ae31a7
>
> and indeed, the kernel packages available in .../deploy/... are:
>
>      kernel-3.15-r1.machine.rpm
>      kernel-3.15.0-00184-g5ae31a7-dirty-3.15-r1.machine.rpm
>      kernel-dev-3.15-r1.machine.rpm
>      kernel-image-3.15.0-00184-g5ae31a7-dirty-3.15-r1.machine.rpm
>
>
> Yet "git status" reports "nothing to commit, w.d. clean" for both the main poky tree and the meta-altera sub-tree.

By this, do you mean the kernel source tree ? Or the layers ?

I haven't looked at the kernel recipe you are using, but PV
and the git hash you have in those package names is coming from
the kernel source directory.

It is there that you'll likely find un-commited changes, and what
is triggering the -dirty flag to be captured.

Bruce

>
> So I guess the n00b needs a clue about how to find out why and where the dirty-flag is getting set?
>
> Thanks for listening!
> --
> jim spriggs
>
> PS: the real names of module and machine have been redacted above to protect the guilty...
> PPS: sorry about the company sig., I can't switch it off.
>
>
> ________________________________
>
> RAYLASE AG
> Argelsrieder Feld 2+4
> 82234 Wessling
> Germany
> Tel.: +49-(0)8153/88 98-0
> Fax: +49-(0)8153/88 98-10
> http://www.raylase.de
>
> District Court Munich, HRB 131450
>
> Board: Peter von Jan (CEO)
>
> Supervisory Board: Dr. Ulrich Lohmann (Chairman)
>
>
> Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail ist nicht gestattet.
>
> This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden.
>



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

* Re: Need advice on tracking down "-dirty"
  2015-05-08 14:08 ` Bruce Ashfield
@ 2015-05-09 10:18   ` Spriggs, Jim
  0 siblings, 0 replies; 3+ messages in thread
From: Spriggs, Jim @ 2015-05-09 10:18 UTC (permalink / raw)
  To: Bruce Ashfield, yocto@yoctoproject.org; +Cc: Wilfert, Dennis, Weber, Markus

Hi Bruce, List

@Bruce: many thanks indeed for your prompt reply and very helpful clue!

It turns out "-dirty" has nothing directly to do with my own recipe at all.

It appears as soon as I specify 'KERNEL_PROVIDER = "linux-altera"' in local.conf, instead of allowing the meta-altera layer's default (which is "linux-altera-ltsi") to go through.
"linux-altera" currently pulls in kernel version 3.15, whereas "linux-altera-ltsi" pulls in 3.10.

I'm using "git clone https://github.com/kraj/meta-altera" to get the altera layer.

Can anyone suggest why 3.15 should (apparently) be "dirty" straight out of the repo?
Is this actually expected behaviour?
Alternatively, what it is that I'm failing to understand about the whole yocto/bitbake mechanism?

Many thanks for your collective patience....
--
jim
________________________________________
From: Bruce Ashfield [bruce.ashfield@windriver.com]
Sent: 08 May 2015 16:08
To: Spriggs, Jim; yocto@yoctoproject.org
Cc: Wilfert, Dennis; Weber, Markus
Subject: Re: [yocto] Need advice on tracking down "-dirty"

On 2015-05-08 5:36 AM, Spriggs, Jim wrote:
> Hi Guys,
>
> Using poky dizzy with meta-altera (from OE), and trying to implement a simple loadable kernel-module by following the method outlined  in Lab3 of  https://www.yoctoproject.org/sites/default/files/kernel-lab-1.6.pdf.
>
> I'm doing an "rm -rf tmp" before starting "bitbake virtual/kernel  my-image-recipe".
>
> The build seems to work just fine: the kernel-module-xxxx-1.0-r0.machine.rpm appears as expected under .../deploy/...
>
> The package installation task fails, however, with:
>
>      error: Can't install kernel-module-xxxx-1.0-r0@machine : no package provides kernel-3.15.0-00184-g5ae31a7
>
> and indeed, the kernel packages available in .../deploy/... are:
>
>      kernel-3.15-r1.machine.rpm
>      kernel-3.15.0-00184-g5ae31a7-dirty-3.15-r1.machine.rpm
>      kernel-dev-3.15-r1.machine.rpm
>      kernel-image-3.15.0-00184-g5ae31a7-dirty-3.15-r1.machine.rpm
>
>
> Yet "git status" reports "nothing to commit, w.d. clean" for both the main poky tree and the meta-altera sub-tree.

By this, do you mean the kernel source tree ? Or the layers ?

I haven't looked at the kernel recipe you are using, but PV
and the git hash you have in those package names is coming from
the kernel source directory.

It is there that you'll likely find un-commited changes, and what
is triggering the -dirty flag to be captured.

Bruce

>
> So I guess the n00b needs a clue about how to find out why and where the dirty-flag is getting set?
>
> Thanks for listening!
> --
> jim spriggs
>
> PS: the real names of module and machine have been redacted above to protect the guilty...
> PPS: sorry about the company sig., I can't switch it off.
>
>
> ________________________________
>
> RAYLASE AG
> Argelsrieder Feld 2+4
> 82234 Wessling
> Germany
> Tel.: +49-(0)8153/88 98-0
> Fax: +49-(0)8153/88 98-10
> http://www.raylase.de
>
> District Court Munich, HRB 131450
>
> Board: Peter von Jan (CEO)
>
> Supervisory Board: Dr. Ulrich Lohmann (Chairman)
>
>
> Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail ist nicht gestattet.
>
> This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden.
>


________________________________

RAYLASE AG
Argelsrieder Feld 2+4
82234 Wessling
Germany
Tel.: +49-(0)8153/88 98-0
Fax: +49-(0)8153/88 98-10
http://www.raylase.de

District Court Munich, HRB 131450

Board: Peter von Jan (CEO)

Supervisory Board: Dr. Ulrich Lohmann (Chairman)


Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail ist nicht gestattet.

This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden.


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

end of thread, other threads:[~2015-05-09 10:18 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2015-05-08  9:36 Need advice on tracking down "-dirty" Spriggs, Jim
2015-05-08 14:08 ` Bruce Ashfield
2015-05-09 10:18   ` Spriggs, Jim

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.