Adding 'build-id' to Build Image

Adding 'build-id' to Build Image

[Leo Schwab]

We'd like to have the system images we build to contain a build id, or
at least a pile of information inside the image itself that lets us
identify which build is being run/tested.  Indeed, the information
'bitbake' kicks out just as it starts a build is exactly the sort of
thing we'd like sitting in a file in the image somewhere.

I turned on the 'buildhistory' feature in conf/local.conf which, among
other things, generates a 'build-id' file.  However, it doesn't place
it in the image, but in an entirely separate directory hierarchy.

Surely this sort of thing has been done before.  Is there an existing
recipe I can use, or will I have to cobble together a custom recipe
out of buildhistory_get_layers() or get_layers_branch_rev()?

Thanks,
Schwab

Re: Adding 'build-id' to Build Image

[Philip Balister]

On 09/08/2014 07:08 PM, Leo Schwab wrote:
> We'd like to have the system images we build to contain a build id, or
> at least a pile of information inside the image itself that lets us
> identify which build is being run/tested.  Indeed, the information
> 'bitbake' kicks out just as it starts a build is exactly the sort of
> thing we'd like sitting in a file in the image somewhere.
> 
> I turned on the 'buildhistory' feature in conf/local.conf which, among
> other things, generates a 'build-id' file.  However, it doesn't place
> it in the image, but in an entirely separate directory hierarchy.
> 
> Surely this sort of thing has been done before.  Is there an existing
> recipe I can use, or will I have to cobble together a custom recipe
> out of buildhistory_get_layers() or get_layers_branch_rev()?

I was asking the same question yesterday. I have a hacky solution for my
immediate need, but I'd like a long term solution along these lines also.

Should we add this to bugzilla and see if we can get it done for 1.8? (I
think I ahve the version number right)

Philip


> 
> Thanks,
> Schwab
> 

Re: Adding 'build-id' to Build Image

[Paul Eggleton]

On Tuesday 09 September 2014 15:03:39 Philip Balister wrote:
> On 09/08/2014 07:08 PM, Leo Schwab wrote:
> > We'd like to have the system images we build to contain a build id, or
> > at least a pile of information inside the image itself that lets us
> > identify which build is being run/tested.  Indeed, the information
> > 'bitbake' kicks out just as it starts a build is exactly the sort of
> > thing we'd like sitting in a file in the image somewhere.
> > 
> > I turned on the 'buildhistory' feature in conf/local.conf which, among
> > other things, generates a 'build-id' file.  However, it doesn't place
> > it in the image, but in an entirely separate directory hierarchy.
> > 
> > Surely this sort of thing has been done before.  Is there an existing
> > recipe I can use, or will I have to cobble together a custom recipe
> > out of buildhistory_get_layers() or get_layers_branch_rev()?
> 
> I was asking the same question yesterday. I have a hacky solution for my
> immediate need, but I'd like a long term solution along these lines also.
> 
> Should we add this to bugzilla and see if we can get it done for 1.8? (I
> think I ahve the version number right)

Yes, please add this to the bugzilla. This has also come up before several 
times, we should just do it (and bonus points if someone wants to send a patch 
;).

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre

Populate /var/lib/opkg/status

[Dag Björklund]

Hello,
How do I populate /var/lib/opkg/status so that all .ipk packages that 
Yocto has installed for me are seen if I e.g. say 'opkg list-installed'?

This, so that if I later install some new packages with dependencies to 
sw that is infact in my rootfs, but opkg is unaware of, I won't get 
failed dependencies from opkg.
Yes I can do 'opkg install --force-depend' but that is not so nice.

Thanks,
    Dag

Re: Populate /var/lib/opkg/status

[Burton, Ross]

On 10 September 2014 12:20, Dag Björklund <dag@iki.fi> wrote:
> How do I populate /var/lib/opkg/status so that all .ipk packages that Yocto
> has installed for me are seen if I e.g. say 'opkg list-installed'?

The IMAGE_FEATURE "package-management" controls whether images have
this data preserved, so you probably need to add that to your image.

Ross

Re: Populate /var/lib/opkg/status

[Dag Björklund]

On 10.09.2014 14:50, Burton, Ross wrote:
> On 10 September 2014 12:20, Dag Björklund <dag@iki.fi> wrote:
>> How do I populate /var/lib/opkg/status so that all .ipk packages that Yocto
>> has installed for me are seen if I e.g. say 'opkg list-installed'?
> The IMAGE_FEATURE "package-management" controls whether images have
> this data preserved, so you probably need to add that to your image.
>
> Ross
Thanks, found this in the documentation now as well. Unfortunately I 
don't see a difference.
Should I find a /var/lib/opkg/status file after adding the feature and 
building?

Dag

Re: Populate /var/lib/opkg/status

[Burton, Ross]

On 12 September 2014 06:36, Dag Björklund <dag@iki.fi> wrote:
> Thanks, found this in the documentation now as well. Unfortunately I don't
> see a difference.
> Should I find a /var/lib/opkg/status file after adding the feature and
> building?

Yes, assuming that you've told bitbake to use opkg and not dpkg or rpm
(PACKAGE_CLASSES).

Ross

Re: Adding 'build-id' to Build Image

[Philip Balister]

I added https://bugzilla.yoctoproject.org/show_bug.cgi?id=6770

Sorry no patch yet :)

Philip

On 09/10/2014 12:38 AM, Paul Eggleton wrote:
> On Tuesday 09 September 2014 15:03:39 Philip Balister wrote:
>> On 09/08/2014 07:08 PM, Leo Schwab wrote:
>>> We'd like to have the system images we build to contain a build id, or
>>> at least a pile of information inside the image itself that lets us
>>> identify which build is being run/tested.  Indeed, the information
>>> 'bitbake' kicks out just as it starts a build is exactly the sort of
>>> thing we'd like sitting in a file in the image somewhere.
>>>
>>> I turned on the 'buildhistory' feature in conf/local.conf which, among
>>> other things, generates a 'build-id' file.  However, it doesn't place
>>> it in the image, but in an entirely separate directory hierarchy.
>>>
>>> Surely this sort of thing has been done before.  Is there an existing
>>> recipe I can use, or will I have to cobble together a custom recipe
>>> out of buildhistory_get_layers() or get_layers_branch_rev()?
>>
>> I was asking the same question yesterday. I have a hacky solution for my
>> immediate need, but I'd like a long term solution along these lines also.
>>
>> Should we add this to bugzilla and see if we can get it done for 1.8? (I
>> think I ahve the version number right)
> 
> Yes, please add this to the bugzilla. This has also come up before several 
> times, we should just do it (and bonus points if someone wants to send a patch 
> ;).
> 
> Cheers,
> Paul
> 

Re: Adding 'build-id' to Build Image

[Douglas Geiger]

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

I've attached a build_info.inc that I've used in some of my image to the
issue - comments welcome.
Currently I include a build timestamp, and the names and version info on
all the layers used in the build and put it in /etc/build

 Doug

On Fri, Sep 26, 2014 at 1:09 PM, Philip Balister <philip@balister.org>
wrote:

> I added https://bugzilla.yoctoproject.org/show_bug.cgi?id=6770
>
> Sorry no patch yet :)
>
> Philip
>
> On 09/10/2014 12:38 AM, Paul Eggleton wrote:
> > On Tuesday 09 September 2014 15:03:39 Philip Balister wrote:
> >> On 09/08/2014 07:08 PM, Leo Schwab wrote:
> >>> We'd like to have the system images we build to contain a build id, or
> >>> at least a pile of information inside the image itself that lets us
> >>> identify which build is being run/tested.  Indeed, the information
> >>> 'bitbake' kicks out just as it starts a build is exactly the sort of
> >>> thing we'd like sitting in a file in the image somewhere.
> >>>
> >>> I turned on the 'buildhistory' feature in conf/local.conf which, among
> >>> other things, generates a 'build-id' file.  However, it doesn't place
> >>> it in the image, but in an entirely separate directory hierarchy.
> >>>
> >>> Surely this sort of thing has been done before.  Is there an existing
> >>> recipe I can use, or will I have to cobble together a custom recipe
> >>> out of buildhistory_get_layers() or get_layers_branch_rev()?
> >>
> >> I was asking the same question yesterday. I have a hacky solution for my
> >> immediate need, but I'd like a long term solution along these lines
> also.
> >>
> >> Should we add this to bugzilla and see if we can get it done for 1.8? (I
> >> think I ahve the version number right)
> >
> > Yes, please add this to the bugzilla. This has also come up before
> several
> > times, we should just do it (and bonus points if someone wants to send a
> patch
> > ;).
> >
> > Cheers,
> > Paul
> >
> --
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>



-- 
Doug Geiger
doug.geiger@bioradiation.net

[-- Attachment #2: Type: text/html, Size: 3204 bytes --]

Re: Adding 'build-id' to Build Image

[Douglas Geiger]

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

FWIW: most of that file is based off a discussion from back in 2012 - I
think Marc Ferland posted a similar file to the list.

On Fri, Sep 26, 2014 at 1:55 PM, Douglas Geiger <
doug.geiger@bioradiation.net> wrote:

> I've attached a build_info.inc that I've used in some of my image to the
> issue - comments welcome.
> Currently I include a build timestamp, and the names and version info on
> all the layers used in the build and put it in /etc/build
>
>  Doug
>
> On Fri, Sep 26, 2014 at 1:09 PM, Philip Balister <philip@balister.org>
> wrote:
>
>> I added https://bugzilla.yoctoproject.org/show_bug.cgi?id=6770
>>
>> Sorry no patch yet :)
>>
>> Philip
>>
>> On 09/10/2014 12:38 AM, Paul Eggleton wrote:
>> > On Tuesday 09 September 2014 15:03:39 Philip Balister wrote:
>> >> On 09/08/2014 07:08 PM, Leo Schwab wrote:
>> >>> We'd like to have the system images we build to contain a build id, or
>> >>> at least a pile of information inside the image itself that lets us
>> >>> identify which build is being run/tested.  Indeed, the information
>> >>> 'bitbake' kicks out just as it starts a build is exactly the sort of
>> >>> thing we'd like sitting in a file in the image somewhere.
>> >>>
>> >>> I turned on the 'buildhistory' feature in conf/local.conf which, among
>> >>> other things, generates a 'build-id' file.  However, it doesn't place
>> >>> it in the image, but in an entirely separate directory hierarchy.
>> >>>
>> >>> Surely this sort of thing has been done before.  Is there an existing
>> >>> recipe I can use, or will I have to cobble together a custom recipe
>> >>> out of buildhistory_get_layers() or get_layers_branch_rev()?
>> >>
>> >> I was asking the same question yesterday. I have a hacky solution for
>> my
>> >> immediate need, but I'd like a long term solution along these lines
>> also.
>> >>
>> >> Should we add this to bugzilla and see if we can get it done for 1.8?
>> (I
>> >> think I ahve the version number right)
>> >
>> > Yes, please add this to the bugzilla. This has also come up before
>> several
>> > times, we should just do it (and bonus points if someone wants to send
>> a patch
>> > ;).
>> >
>> > Cheers,
>> > Paul
>> >
>> --
>> _______________________________________________
>> yocto mailing list
>> yocto@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto
>>
>
>
>
> --
> Doug Geiger
> doug.geiger@bioradiation.net
>



-- 
Doug Geiger
doug.geiger@bioradiation.net

[-- Attachment #2: Type: text/html, Size: 3917 bytes --]