Re: [yocto] [PATCH] buildset-config: build core-image-sato SDK

2013-07-02 Thread Flanagan, Elizabeth 
On Fri, Jun 28, 2013 at 9:01 AM, Trevor Woerner
 wrote:
> Just out of curiosity...
>
> On 27 June 2013 06:06, Ross Burton  wrote:
>>  buildset-config/nightly-arm.conf |2 ++
>>  buildset-config/nightly-fsl-arm.conf |2 ++
>>  buildset-config/nightly-fsl-ppc.conf |2 ++
>>  buildset-config/nightly-mips.conf|2 ++
>>  buildset-config/nightly-oecore.conf  |2 ++
>>  buildset-config/nightly-ppc.conf |2 ++
>>  buildset-config/nightly-x86-64.conf  |2 ++
>>  buildset-config/nightly-x86.conf |2 ++
>
>
> Against which repository do these apply?

These apply to the yocto-autobuilder eflanagan/yocto-autobuilder-refactor branch


-- 
Elizabeth Flanagan
Yocto Project
Build and Release
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] systemd configuration

2013-07-02 Thread Paul D. DeRocco 
I've switched to systemd, in a core-image-base build for an Atom
(Cedartrail), and it boots fine. Now I want to make my own daemon start up.
I'm new to systemd, and the way it seems to be set up is different from the
way the systemd docs say it is usually set up.

The docs say that systemd, when booting up, usually activates a target
called default.target, which is symlinked to either multi-user.target or
graphical.target. (It would be the former in this GUI-less system.) Then, if
I want to cause my daemon to be started, I would add a symlink to its
systemd unit file to the .wants directory associated with multi-user.target.

But I can't find these things. They're not in the trees under /etc/systemd
or /run/systemd. Oh, and when I do "systemctl list-unit-files", it shows
both default.target and multi-user.target as disabled.

What makes this difficult to figure out is that the tools I have for
perusing the target system are so primitive. There's no editor in the target
that I'm aware of, and I can't network into the system and use an external
editor to examine various files. So my question is this: is there someplace
in build/tmp on my build system where the full target file system exists as
a directory tree, so that I can pore through it and see how systemd is
really configured?

Or perhaps someone can just tell me what target gets activated on bootup,
where its .wants directory is, and what directory I should put my daemon's
unit file into.

-- 

Ciao,   Paul D. DeRocco
Paulmailto:pdero...@ix.netcom.com 
 

___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] systemd configuration

2013-07-02 Thread Paul Eggleton 
On Tuesday 02 July 2013 10:40:06 Paul D. DeRocco wrote:
> I've switched to systemd, in a core-image-base build for an Atom
> (Cedartrail), and it boots fine. Now I want to make my own daemon start up.
> I'm new to systemd, and the way it seems to be set up is different from the
> way the systemd docs say it is usually set up.
> 
> The docs say that systemd, when booting up, usually activates a target
> called default.target, which is symlinked to either multi-user.target or
> graphical.target. (It would be the former in this GUI-less system.) Then, if
> I want to cause my daemon to be started, I would add a symlink to its
> systemd unit file to the .wants directory associated with
> multi-user.target.
> 
> But I can't find these things. They're not in the trees under /etc/systemd
> or /run/systemd. Oh, and when I do "systemctl list-unit-files", it shows
> both default.target and multi-user.target as disabled.
> 
> What makes this difficult to figure out is that the tools I have for
> perusing the target system are so primitive. There's no editor in the target
> that I'm aware of

That's entirely up to what you put into your image. busybox should provide a 
very basic version of "vi" out of the box.

> , and I can't network into the system and use an external
> editor to examine various files. 

Again, that's up to what you enable in the image. You could use NFS for 
example.

> So my question is this: is there someplace
> in build/tmp on my build system where the full target file system exists as
> a directory tree, so that I can pore through it and see how systemd is
> really configured?

Sure, you can find in the "rootfs" subdirectory of the image's WORKDIR (which 
you can find out using:

 bitbake -e imagename | grep ^WORKDIR=

One way to look at this is to launch a devshell for the image:

 bitbake -c devshell imagename

In 1.4+ using a devshell has the advantage of showing you the correct 
permission/ownership of files within the root filesystem.

> Or perhaps someone can just tell me what target gets activated on bootup,
> where its .wants directory is, and what directory I should put my daemon's
> unit file into.

I'm sure someone more knowledgeable about systemd will pipe up with further 
information, but I would suggest looking at other recipes for examples. AFAICT 
systemd units for daemons should be installed into ${systemd_unitdir}/system.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [PATCH] buildset-config: build core-image-sato SDK

2013-07-02 Thread Flanagan, Elizabeth 
I'm going to pull these for now, but I'll probably end up doing this
significantly different when we settle on whatever solution (be it
LAYERVERSION or whatever) to identify build process breakage.

-b


On Tue, Jul 2, 2013 at 8:28 AM, Flanagan, Elizabeth
 wrote:
> On Fri, Jun 28, 2013 at 9:01 AM, Trevor Woerner
>  wrote:
>> Just out of curiosity...
>>
>> On 27 June 2013 06:06, Ross Burton  wrote:
>>>  buildset-config/nightly-arm.conf |2 ++
>>>  buildset-config/nightly-fsl-arm.conf |2 ++
>>>  buildset-config/nightly-fsl-ppc.conf |2 ++
>>>  buildset-config/nightly-mips.conf|2 ++
>>>  buildset-config/nightly-oecore.conf  |2 ++
>>>  buildset-config/nightly-ppc.conf |2 ++
>>>  buildset-config/nightly-x86-64.conf  |2 ++
>>>  buildset-config/nightly-x86.conf |2 ++
>>
>>
>> Against which repository do these apply?
>
> These apply to the yocto-autobuilder eflanagan/yocto-autobuilder-refactor 
> branch

We've moved the old yocto-autobuilder master to old-master and the
refactor branch is now master. I will be working from master from now
on (except for private branches, etc)

>
>
> --
> Elizabeth Flanagan
> Yocto Project
> Build and Release



-- 
Elizabeth Flanagan
Yocto Project
Build and Release
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Minutes: Yocto Project Technical Team Meeting - Tuesday, July 02, 2013 8:00 AM-9:00 AM (UTC-08:00) Pacific Time (US & Canada).

2013-07-02 Thread Liu, Song 
Attendees:
Nitin, Matthew Weigel,  Dave, Eren, Mark, Saul, ScottR, Denys, Corneliu, Ross, 
Belen, Paul, TomZ, MichaelH, AlexG, LaurentiuP, MihaiL, Beth, Song

Agenda:

* Opens collection - 5 min (Song)
* Yocto 1.5 status - 10 min (Song/team)
  https://wiki.yoctoproject.org/wiki/Yocto_Project_v1.5_Status
  - Feature development:
. 1584/3867, security feature. They are in a layer. Mostly done, will be 
released separately.
. 4267: Fenrus updater, Ionut Radu. Stability issues, reconsidering 
priority or target milestone. Any technical questions, please let Saul know.
. 3169: Shuku implementation, Ross. It's in progress, not yet ready. Hope 
to close in a couple of weeks.
. 4753: Need to document buildtools-tarball. Just about to complete. 
Waiting for url from Beth. Beth has it ready, sending
  - Bug fix: Bug number is down, we fixed more bugs last week. Thanks to 
Richard/Saul and the team, please keep the good work up.

* Yocto Project 1.5 QA plan review - 20 min (AlexG/MihaiL)
  https://wiki.yoctoproject.org/wiki/1.5_Overall_Test_Plan
  - Please take a look at the test cases in testopia, especially those in your 
area or areas you have concerns. Make sure we have enough coverage.
* SWAT team rotation: Radu M -> Ioana
* Opens - 10 min
* Team Sharing - 15 min
  - Saul: M2 freeze happened on last Sunday. Master pull will happen this 
morning. Will start RC1 build after that.
  - Beth: Build failure emails gone out. Format changed, making it easier. 
Trimming unnecessary info. Changed the milestone release process. We do not 
create branches, we create tags. Will be out until 13th, Michael will cover for 
Beth.
  - Eren: working on a project, hamradio, for 3 month until Sep. Just create 
the layer, if you are interested, please send emails to me. I may also 
contribute to security things too.



___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [yocto-docs][PATCH] dev-manual: referencing bugzilla issues

2013-07-02 Thread Saul Wold 

On 07/01/2013 08:35 AM, Trevor Woerner wrote:

On 1 July 2013 02:37, Rifenbark, Scott M  wrote:

I got a hold of Saul and confirmed that you are right.  I have been entering 
these strings incorrectly for a good while now.  I have applied your patch to 
the tip of the yocto-docs repository and republished in our development area 
for the manuals.



Just to complete this, and I apologize for missing the thread,

Yes, the correct format is [YOCTO #] where  is the Yocto Project 
Bugzilla Bug #.


Sau!



Great! Thank _you_ :-)
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto



___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] [PATCH] buildset-config: build core-image-sato SDK

2013-07-02 Thread Flanagan, Elizabeth 
Actually, I'm going to revert this commit out of master. The
autobuilder doesn't start up when it is applied.

I don't have time to look at why right now, but I'll take a look when
I get back.

-b

On Tue, Jul 2, 2013 at 3:59 PM, Flanagan, Elizabeth
 wrote:
> I'm going to pull these for now, but I'll probably end up doing this
> significantly different when we settle on whatever solution (be it
> LAYERVERSION or whatever) to identify build process breakage.
>
> -b
>
>
> On Tue, Jul 2, 2013 at 8:28 AM, Flanagan, Elizabeth
>  wrote:
>> On Fri, Jun 28, 2013 at 9:01 AM, Trevor Woerner
>>  wrote:
>>> Just out of curiosity...
>>>
>>> On 27 June 2013 06:06, Ross Burton  wrote:
  buildset-config/nightly-arm.conf |2 ++
  buildset-config/nightly-fsl-arm.conf |2 ++
  buildset-config/nightly-fsl-ppc.conf |2 ++
  buildset-config/nightly-mips.conf|2 ++
  buildset-config/nightly-oecore.conf  |2 ++
  buildset-config/nightly-ppc.conf |2 ++
  buildset-config/nightly-x86-64.conf  |2 ++
  buildset-config/nightly-x86.conf |2 ++
>>>
>>>
>>> Against which repository do these apply?
>>
>> These apply to the yocto-autobuilder eflanagan/yocto-autobuilder-refactor 
>> branch
>
> We've moved the old yocto-autobuilder master to old-master and the
> refactor branch is now master. I will be working from master from now
> on (except for private branches, etc)
>
>>
>>
>> --
>> Elizabeth Flanagan
>> Yocto Project
>> Build and Release
>
>
>
> --
> Elizabeth Flanagan
> Yocto Project
> Build and Release



-- 
Elizabeth Flanagan
Yocto Project
Build and Release
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] poky-extras

2013-07-02 Thread Bruce Ashfield 
On Mon, Jul 1, 2013 at 1:33 AM, Michael Halstead
 wrote:
> I can change the name shortly. Is there any reason to keep a read-only
> copy available at the current location temporarily?

It can't hurt, but I also can't think of a really compelling reason that it is
absolutely required. By the name alone, we can be sure that nothing
core to a build uses it, or fetches it, and that anyone with a copy can
continue to use their local copy under the current name .. until they
track down the new repo name.

Cheers,

Bruce

>
> Michael Halstead
> Yocto Project / Sys Admin
>
> On 06/30/2013 10:19 PM, Rifenbark, Scott M wrote:
>> Hi,
>>
>> I updated the dev-manual section that tells the user what is in this repo 
>> and shows an example of cloning it.  Nothing changes except for the name, 
>> which I switched to 'meta-yocto-kernel-extras'.  To me, it appears that the 
>> contents of the repo still contain the kernel BitBake append files that you 
>> edit to point to your locally modified kernel source files as described in 
>> the text.  Within the entire YP documentation set, this little area is the 
>> only reference to the old 'poky-extras' repo.  Here is the link to see the 
>> changes - 
>> http://www.yoctoproject.org/docs/1.5/dev-manual/dev-manual.html#meta-yocto-kernel-extras-repo.
>>
>> I am assuming that the name of the repo will indeed be changed to 
>> 'meta-yocto-kernel-extras'.  If I don't hear from anyone, I will assume 
>> everything is good.
>>
>> Thanks,
>> Scott
>>
>>> -Original Message-
>>> From: Hart, Darren
>>> Sent: Friday, June 28, 2013 10:08 PM
>>> To: Richard Purdie
>>> Cc: Bruce Ashfield; Rifenbark, Scott M; yocto; Michael Halstead
>>> Subject: Re: poky-extras
>>>
>>> On Fri, 2013-06-28 at 14:56 +0100, Richard Purdie wrote:
 On Fri, 2013-06-28 at 09:40 -0400, Bruce Ashfield wrote:
> On 13-06-28 09:22 AM, Rifenbark, Scott M wrote:
>> All I need is the name to make some initial changes.
> Personally, I'm fine with 'meta-yocto-kernel'. Naming things is
> never easy, so I won't agonize over whether or not an "extras"
> should be on the end. But the name should be clear that it isn't
> the main yocto kernel, it's just a few crappy bbappends that make
> working with it locally easier for some :)
>
> So my only counter proposal is: meta-yocto-kernel-extras
>
> I'm going to de-crapify the bbappends so they are more useful, and
> have started on that work, but haven't finished it yet.
 No strong feelings here. I just wiped out meta-linaro from there
>>> (hoping
 Darren won't mind) and that checksums.ini file.
>>> That's fine, I was just thinking about that last week when I saw Linaro
>>> has a meta-linaro. That's where it belongs, so buh-bye. :-)
>>>
>>> --
>>> Darren Hart
>>> Intel Open Source Technology Center
>>> Yocto Project - Technical Lead - Linux Kernel
>
>
>
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>



--
"Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end"
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] poky-extras

2013-07-02 Thread Bruce Ashfield 
On Mon, Jul 1, 2013 at 1:28 PM, Darren Hart  wrote:
> On Mon, 2013-07-01 at 07:46 +0100, Richard Purdie wrote:
>> On Sun, 2013-06-30 at 23:18 -0700, Michael Halstead wrote:
>> > On 06/30/2013 10:44 PM, Darren Hart wrote:
>> > > On Sun, 2013-06-30 at 22:33 -0700, Michael Halstead wrote:
>> > > > I can change the name shortly. Is there any reason to keep a read-only
>> > > > copy available at the current location temporarily?
>> > > Not really. Unless Bruce is using it in some automated scripts that need
>> > > to be updated.
>> > >
>> >
>> > The name has been changed. Shall we update the description or is
>> > "Supplementary metadata layers to extend the Poky core" still
>> > appropriate?
>>
>> We can change it to something like "Supplementary linux-yocto kernel
>> development metadata" unless Bruce has any better description.
>
> Bruce is out this week with limited email access. He isn't terribly
> picky on naming and that description should work as good as any.

Yup, and apparently my access when it comes back .. makes me
read email in random order!

The description and resolution are all fine with me.

Bruce

>
> --
> Darren Hart
> Intel Open Source Technology Center
> Yocto Project - Technical Lead - Linux Kernel
>
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto



--
"Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end"
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Yocto Project 1.5_M2.rc1 build underway

2013-07-02 Thread Michael Halstead 
The Yocto Project 1.5_M2.rc1 build is underway. As tasks complete
artifacts will start appearing at:

http://autobuilder.yoctoproject.org/pub/nightly/20130703-1

pokyeaa5df34af42b6a37f6506847d0f3ef6ba0d298a 

meta-fsl-armdaf582c93a7283fb0af3b25fe2ada48f4c9985c4 

meta-fsl-ppcb889029dca03fcb7e55c671aa5006fe8be1eefb0 

meta-intel  e0d6134ed2e2687ff9f2ee77701666447842bf33 

meta-minnow 286a72ba3f5e29432be1dd77127de5bdc2d988c3 

 
meta-qt3b73552fb998fd30a01dbee5a172e432a16078222 

eclipse-pokye35dfd79e3970f88a8273125890a54f75f108b97 

 

Please begin QA as soon as possible. Thank you.

-- 
Michael Halstead
Yocto Project / Sys Admin



smime.p7s
Description: S/MIME Cryptographic Signature
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Yocto Project 1.5_M2.rc1 build underway

2013-07-02 Thread Flanagan, Elizabeth 
I'm going to have to restart this build. A slight issue on the
autobuilder this afternoon that I didn't catch is causing it to fail.
I'll have it restarted momentarily and will resend out the hashes.

-b

On Tue, Jul 2, 2013 at 7:44 PM, Michael Halstead
 wrote:
> The Yocto Project 1.5_M2.rc1 build is underway. As tasks complete artifacts
> will start appearing at:
>
> http://autobuilder.yoctoproject.org/pub/nightly/20130703-1
>
> poky  eaa5df34af42b6a37f6506847d0f3ef6ba0d298a
> meta-fsl-arm  daf582c93a7283fb0af3b25fe2ada48f4c9985c4
> meta-fsl-ppc  b889029dca03fcb7e55c671aa5006fe8be1eefb0
> meta-intele0d6134ed2e2687ff9f2ee77701666447842bf33
> meta-minnow   286a72ba3f5e29432be1dd77127de5bdc2d988c3
> meta-qt3  b73552fb998fd30a01dbee5a172e432a16078222
> eclipse-poky  e35dfd79e3970f88a8273125890a54f75f108b97
>
> Please begin QA as soon as possible. Thank you.
>
> --
> Michael Halstead
> Yocto Project / Sys Admin
>
>
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>



-- 
Elizabeth Flanagan
Yocto Project
Build and Release
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Yocto Project 1.5_M2.rc1 build underway, again

2013-07-02 Thread Michael Halstead 

After correcting some configuration errors the Yocto Project 1.5_M2.rc1
build is underway again. As tasks complete artifacts will start
appearing at their new location:

http://autobuilder.yoctoproject.org/pub/nightly/20130703-2

pokyeaa5df34af42b6a37f6506847d0f3ef6ba0d298a 

meta-fsl-armdaf582c93a7283fb0af3b25fe2ada48f4c9985c4 

meta-fsl-ppcb889029dca03fcb7e55c671aa5006fe8be1eefb0 

meta-intel  e0d6134ed2e2687ff9f2ee77701666447842bf33 

meta-minnow 286a72ba3f5e29432be1dd77127de5bdc2d988c3 

 
meta-qt3b73552fb998fd30a01dbee5a172e432a16078222 

eclipse-pokye35dfd79e3970f88a8273125890a54f75f108b97 

 

Please begin QA as soon as possible. Thank you.

-- 
Michael Halstead
Yocto Project / Sys Admin



smime.p7s
Description: S/MIME Cryptographic Signature
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto