[Angstrom-devel] Strategies for freezing and building Angstrom offline?
Hi all,
First off, thanks a lot for the Angstrom effort, it's a great distro and
we're committing to use it on BeagleBone Blacks to manage our automated
test rack at work.
We are trying to figure out the best way to capture a full Angstrom
codebase snapshot so that we can iterate locally on it and make private
changes. I see that invoking "bitbake virtual/kernel" performs an update
before doing a build, so our current strategy is failing.
My naive first attempt to capture Angstrom was to pull it down and do a
full build as per the instructions on the Angstrom site. After confirming
that this gave me a good output image, I deleted the entire /build
directory, and then recursively deleted the .git metadata ("find . -type d
-name ".git" -exec rm -rf {}\;"). I committed the results to our local
private git repository.
When our build slave machine tries to sync and build, it gives us this:
MACHINE=beaglebone ./oebb.sh bitbake console-image
col: write error
grotty: ():25092:fatal error: output error
WARNING
WARNING: bitbake is using a different uri
'g...@git.mycompany.com:hardware/bbb-angstrom.git' than configured in
layers.txt 'git://github.com/openembedded/bitbake.git'
WARNING: Changing uri to: 'git://github.com/openembedded/bitbake.git'
WARNING
Fetching origin
This makes sense, because the conf/layers.txt file references all of
the subprojects on the public github.
Can I tell bitbake to use the local versions? Do I need to host each
subproject on our internal git and point layers.txt towards that? Is
what I'm doing sensible? :)
All advice, comments, flames welcome, and thanks for taking the time
to read this.
Best Regards,
Charles Nicholson
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] Strategies for freezing and building Angstrom offline?
Have a look at using:
BB_NO_NETWORK = "1"
in your local.conf. This will deny bitbake all access to the network and
will effectively freeze your build.
However, issuing a bitbake command usually won't fetch new sources
unless the underlying recipes have changed; so this should really be
what you try to tackle; the BB_NO_NETWORK is a bit of a workaround which
isn't really designed for this purpose.
Cheers,
Jack.
On 28/06/2013 19:21, Charles Nicholson wrote:
Hi all,
First off, thanks a lot for the Angstrom effort, it's a great distro and
we're committing to use it on BeagleBone Blacks to manage our automated
test rack at work.
We are trying to figure out the best way to capture a full Angstrom
codebase snapshot so that we can iterate locally on it and make private
changes. I see that invoking "bitbake virtual/kernel" performs an update
before doing a build, so our current strategy is failing.
My naive first attempt to capture Angstrom was to pull it down and do a
full build as per the instructions on the Angstrom site. After confirming
that this gave me a good output image, I deleted the entire /build
directory, and then recursively deleted the .git metadata ("find . -type d
-name ".git" -exec rm -rf {}\;"). I committed the results to our local
private git repository.
When our build slave machine tries to sync and build, it gives us this:
MACHINE=beaglebone ./oebb.sh bitbake console-image
col: write error
grotty: ():25092:fatal error: output error
WARNING
WARNING: bitbake is using a different uri
'g...@git.mycompany.com:hardware/bbb-angstrom.git' than configured in
layers.txt 'git://github.com/openembedded/bitbake.git'
WARNING: Changing uri to: 'git://github.com/openembedded/bitbake.git'
WARNING
Fetching origin
This makes sense, because the conf/layers.txt file references all of
the subprojects on the public github.
Can I tell bitbake to use the local versions? Do I need to host each
subproject on our internal git and point layers.txt towards that? Is
what I'm doing sensible? :)
All advice, comments, flames welcome, and thanks for taking the time
to read this.
Best Regards,
Charles Nicholson
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
--
Jack Mitchell (j...@embed.me.uk)
Embedded Systems Engineer
http://www.embed.me.uk
--
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] Strategies for freezing and building Angstrom offline?
On Jun 28, 2013, at 11:21 AM, Charles Nicholson
wrote:
> Hi all,
>
> First off, thanks a lot for the Angstrom effort, it's a great distro and
> we're committing to use it on BeagleBone Blacks to manage our automated
> test rack at work.
>
> We are trying to figure out the best way to capture a full Angstrom
> codebase snapshot so that we can iterate locally on it and make private
> changes. I see that invoking "bitbake virtual/kernel" performs an update
> before doing a build, so our current strategy is failing.
bitbake -cfetchall
will download the needed sources and then you can add BB_NO_NETWORK = "1"
to you local.conf from thereon it will not access web anymore
>
> My naive first attempt to capture Angstrom was to pull it down and do a
> full build as per the instructions on the Angstrom site. After confirming
> that this gave me a good output image, I deleted the entire /build
> directory, and then recursively deleted the .git metadata ("find . -type d
> -name ".git" -exec rm -rf {}\;"). I committed the results to our local
> private git repository.
>
> When our build slave machine tries to sync and build, it gives us this:
>
> MACHINE=beaglebone ./oebb.sh bitbake console-image
dont se oebb.sh wrapper to run builds once you have create the sandbox.
using oebb.sh config then
source ~/.oe/angstrom-* in your shell and after that issue normal bitbake
commands
directly
bitbake sytemd-image and so on
and once everything works for you. Contributions are welcome
> col: write error
> grotty: ():25092:fatal error: output error
> WARNING
> WARNING: bitbake is using a different uri
> 'g...@git.mycompany.com:hardware/bbb-angstrom.git' than configured in
> layers.txt 'git://github.com/openembedded/bitbake.git'
> WARNING: Changing uri to: 'git://github.com/openembedded/bitbake.git'
> WARNING
> Fetching origin
>
>
> This makes sense, because the conf/layers.txt file references all of
> the subprojects on the public github.
>
>
> Can I tell bitbake to use the local versions? Do I need to host each
> subproject on our internal git and point layers.txt towards that? Is
> what I'm doing sensible? :)
>
>
> All advice, comments, flames welcome, and thanks for taking the time
> to read this.
>
>
> Best Regards,
>
> Charles Nicholson
> ___
> Angstrom-distro-devel mailing list
> Angstrom-distro-devel@linuxtogo.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] Strategies for freezing and building Angstrom offline?
Thanks everyone for the quick response. Once we get things working, I'd be
happy to contribute a page to the wiki about how to freeze and build
Angstrom locally without further updates, if people think that would be
helpful.
(BTW, the build machine in question has no access to the outside internet,
which might also be contributing to the errors I'm seeing? All git
commands against github etc. fail...)
Best, and thanks again,
Charles
On Sat, Jun 29, 2013 at 7:17 AM, Khem Raj wrote:
>
> On Jun 28, 2013, at 11:21 AM, Charles Nicholson <
> charles.nichol...@gmail.com> wrote:
>
> > Hi all,
> >
> > First off, thanks a lot for the Angstrom effort, it's a great distro and
> > we're committing to use it on BeagleBone Blacks to manage our automated
> > test rack at work.
> >
> > We are trying to figure out the best way to capture a full Angstrom
> > codebase snapshot so that we can iterate locally on it and make private
> > changes. I see that invoking "bitbake virtual/kernel" performs an update
> > before doing a build, so our current strategy is failing.
>
> bitbake -cfetchall
> will download the needed sources and then you can add BB_NO_NETWORK = "1"
> to you local.conf from thereon it will not access web anymore
>
> >
> > My naive first attempt to capture Angstrom was to pull it down and do a
> > full build as per the instructions on the Angstrom site. After
> confirming
> > that this gave me a good output image, I deleted the entire /build
> > directory, and then recursively deleted the .git metadata ("find . -type
> d
> > -name ".git" -exec rm -rf {}\;"). I committed the results to our local
> > private git repository.
> >
> > When our build slave machine tries to sync and build, it gives us this:
> >
> > MACHINE=beaglebone ./oebb.sh bitbake console-image
>
>
> dont se oebb.sh wrapper to run builds once you have create the sandbox.
> using oebb.sh config then
>
> source ~/.oe/angstrom-* in your shell and after that issue normal bitbake
> commands
> directly
>
> bitbake sytemd-image and so on
>
> and once everything works for you. Contributions are welcome
>
> > col: write error
> > grotty: ():25092:fatal error: output
> error
> > WARNING
> > WARNING: bitbake is using a different uri
> > 'g...@git.mycompany.com:hardware/bbb-angstrom.git' than configured in
> > layers.txt 'git://github.com/openembedded/bitbake.git'
> > WARNING: Changing uri to: 'git://github.com/openembedded/bitbake.git'
> > WARNING
> > Fetching origin
> >
> >
> > This makes sense, because the conf/layers.txt file references all of
> > the subprojects on the public github.
> >
> >
> > Can I tell bitbake to use the local versions? Do I need to host each
> > subproject on our internal git and point layers.txt towards that? Is
> > what I'm doing sensible? :)
> >
> >
> > All advice, comments, flames welcome, and thanks for taking the time
> > to read this.
> >
> >
> > Best Regards,
> >
> > Charles Nicholson
> > ___
> > Angstrom-distro-devel mailing list
> > Angstrom-distro-devel@linuxtogo.org
> >
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
>
>
> ___
> Angstrom-distro-devel mailing list
> Angstrom-distro-devel@linuxtogo.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
>
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] Strategies for freezing and building Angstrom offline?
On Jun 29, 2013, at 11:17 AM, Charles Nicholson
wrote:
> Thanks everyone for the quick response. Once we get things working, I'd be
> happy to contribute a page to the wiki about how to freeze and build
> Angstrom locally without further updates, if people think that would be
> helpful.
>
> (BTW, the build machine in question has no access to the outside internet,
> which might also be contributing to the errors I'm seeing? All git
> commands against github etc. fail…)
We strive to make it such that it doesn't have to enquire once you download. So
when you see that some recipe is
trying to query the sources from www you should check if it has
SRCREV set to a hardcoded git SHA sometimes it might have tagnames or AUTOREV
assigned to SRCREV
that will need to be changed to specific git commit SHAs
So that can be your first contribution.
>
> Best, and thanks again,
> Charles
>
>
> On Sat, Jun 29, 2013 at 7:17 AM, Khem Raj wrote:
>
>>
>> On Jun 28, 2013, at 11:21 AM, Charles Nicholson <
>> charles.nichol...@gmail.com> wrote:
>>
>>> Hi all,
>>>
>>> First off, thanks a lot for the Angstrom effort, it's a great distro and
>>> we're committing to use it on BeagleBone Blacks to manage our automated
>>> test rack at work.
>>>
>>> We are trying to figure out the best way to capture a full Angstrom
>>> codebase snapshot so that we can iterate locally on it and make private
>>> changes. I see that invoking "bitbake virtual/kernel" performs an update
>>> before doing a build, so our current strategy is failing.
>>
>> bitbake -cfetchall
>> will download the needed sources and then you can add BB_NO_NETWORK = "1"
>> to you local.conf from thereon it will not access web anymore
>>
>>>
>>> My naive first attempt to capture Angstrom was to pull it down and do a
>>> full build as per the instructions on the Angstrom site. After
>> confirming
>>> that this gave me a good output image, I deleted the entire /build
>>> directory, and then recursively deleted the .git metadata ("find . -type
>> d
>>> -name ".git" -exec rm -rf {}\;"). I committed the results to our local
>>> private git repository.
>>>
>>> When our build slave machine tries to sync and build, it gives us this:
>>>
>>> MACHINE=beaglebone ./oebb.sh bitbake console-image
>>
>>
>> dont se oebb.sh wrapper to run builds once you have create the sandbox.
>> using oebb.sh config then
>>
>> source ~/.oe/angstrom-* in your shell and after that issue normal bitbake
>> commands
>> directly
>>
>> bitbake sytemd-image and so on
>>
>> and once everything works for you. Contributions are welcome
>>
>>> col: write error
>>> grotty: ():25092:fatal error: output
>> error
>>> WARNING
>>> WARNING: bitbake is using a different uri
>>> 'g...@git.mycompany.com:hardware/bbb-angstrom.git' than configured in
>>> layers.txt 'git://github.com/openembedded/bitbake.git'
>>> WARNING: Changing uri to: 'git://github.com/openembedded/bitbake.git'
>>> WARNING
>>> Fetching origin
>>>
>>>
>>> This makes sense, because the conf/layers.txt file references all of
>>> the subprojects on the public github.
>>>
>>>
>>> Can I tell bitbake to use the local versions? Do I need to host each
>>> subproject on our internal git and point layers.txt towards that? Is
>>> what I'm doing sensible? :)
>>>
>>>
>>> All advice, comments, flames welcome, and thanks for taking the time
>>> to read this.
>>>
>>>
>>> Best Regards,
>>>
>>> Charles Nicholson
>>> ___
>>> Angstrom-distro-devel mailing list
>>> Angstrom-distro-devel@linuxtogo.org
>>>
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
>>
>>
>> ___
>> Angstrom-distro-devel mailing list
>> Angstrom-distro-devel@linuxtogo.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
>>
> ___
> Angstrom-distro-devel mailing list
> Angstrom-distro-devel@linuxtogo.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
___
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
Re: [Angstrom-devel] Strategies for freezing and building Angstrom offline?
Op 28 jun. 2013, om 20:21 heeft Charles Nicholson het volgende geschreven: > Hi all, > > First off, thanks a lot for the Angstrom effort, it's a great distro and > we're committing to use it on BeagleBone Blacks to manage our automated > test rack at work. > > We are trying to figure out the best way to capture a full Angstrom > codebase snapshot so that we can iterate locally on it and make private > changes. I see that invoking "bitbake virtual/kernel" performs an update > before doing a build, so our current strategy is failing. To clear: bitbake virtual/kernel will NOT do any update, but ./oebb.sh bitbake virtual/kerne will do an update before the build. If you want to lock down all the metadata, have a look at 'oebb.sh info': [koen@rrMBP v2012.12]$ ./oebb.sh info Showing contents of /build/v2012.12/sources/info.txt: bitbake,git://github.com/openembedded/bitbake.git,master,7e3a99949358f4362876df5a82f8aeaae72c3c97 meta-angstrom,git://github.com/Angstrom-distribution/meta-angstrom,angstrom-v2012.12-yocto1.3,26a3bd2ac4cabf7d5eda8bd88b7bf81af44a3891 meta-openembedded,git://github.com/Angstrom-distribution/meta-oe.git,angstrom-staging-yocto1.3,7ad77f0f74bf9a47c975a15304d9b8f6d8bad5f9 meta-beagleboard,git://github.com/beagleboard/meta-beagleboard.git,master,ebdab447c18766464e610d12c3e96ac2cd069b58 meta-ti,git://github.com/Angstrom-distribution/meta-ti.git,angstrom-staging-yocto1.3,8e888ab8dd4ac846d95eabf8981ecd6dc218138d meta-ettus,git://github.com/balister/meta-ettus.git,master,5a6a642f6707dc42a5210dbbf01d2bdfd869d4b0 meta-efikamx,git://github.com/kraj/meta-efikamx.git,master,07f2a5c777b4f866985735303bc6d696592760a9 meta-nslu2,git://github.com/kraj/meta-nslu2.git,master,8948458fe3ec2b3c713b2a13a87123b64e22b0d9 meta-smartphone,http://git.shr-project.org/repo/meta-smartphone.git,danny,924338ee2d44987da71088da31e1cd31d3a9dfa9 meta-intel,git://git.yoctoproject.org/meta-intel,danny,ecc6695a14a8843acdba38c91c139b873343b393 meta-xilinx,git://git.yoctoproject.org/meta-xilinx,master,d196fa93c7ff5e080d4c44e2b83aed472f32b2c7 meta-openpandora,git://github.com/openpandora/meta-openpandora.git,master,bdd973321efabf9da4ac7bbc5e18ecab257841a3 meta-raspberrypi,git://github.com/djwillis/meta-raspberrypi.git,danny,1ad98cf651054982c1a69576c1663285f0090034 meta-handheld,git://git.openembedded.org/meta-handheld,danny,d641e71a7c09cd24c72e690ad1981e49da612bcd meta-opie,git://github.com/bluelightning/meta-opie.git,master,c242efc6ca55772a88602f1f8f94dff697b38430 meta-java,git://github.com/woglinde/meta-java.git,master,75dee76c7cfbf1418e5c581f50bb57b3282013f7 meta-browser,git://github.com/OSSystems/meta-browser.git,danny,de6eb680c0efe0df9ed12526380a10d3aab4359a meta-mono,git://git.yoctoproject.org/meta-mono.git,master,adf47f078dbf788a80ff1398a15a4fd5a334d320 meta-kde,git://gitorious.org/openembedded-core-layers/meta-kde.git,master,316d9c27e72cfebc7618268f8766624ee3f5e18e meta-linaro,git://git.linaro.org/openembedded/meta-linaro.git,danny,d0558fa4304592622423582f8b464e1c22cfe6f1 meta-minnow,git://git.yoctoproject.org/meta-minnow,danny,9e2d60ecccae4c2f0a677f95b92553ab7bde1bca meta-allwinner,git://github.com/naguirre/meta-allwinner.git,danny,3603ce61c075d2f6a23dbe0bd71ee604f7eb24ea meta-ros,git://github.com/bmwcarit/meta-ros.git,master,7e2cd2c0952ee35e30c8e3f9dc57f277d58419b8 openembedded-core,git://github.com/Angstrom-distribution/oe-core.git,angstrom-staging-yocto1.3,1255516812a3faa09dba04f59970b172de863b5a you can replace layers.txt with info.txt and all metadata will be fixed to the current revisions. regards, Koen ___ Angstrom-distro-devel mailing list Angstrom-distro-devel@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel
