[yocto] YP 1.8 Bug Fix Cutoff is coming soon!

[Jolley, Stephen K]

All,

If you have an open bug targeting YP 1.8.   The cutoff for bug fixing for YP 
1.8 is coming up on 3/24/2015.   Please make your best effort to get your 
patches submitted to the mailing list before this date.   We will be doing our 
first release candidate right after the 24th and will only fixing bugs/issues 
which are found during testing and QA to insure we have a very stable release 
of YP 1.8 after this point.

If you have questions, please contact myself or Richard.

Thanks,

Stephen K. Jolley
Yocto Project Program Manager
INTEL, MS JF1-255, 2111 N.E. 25th Avenue, Hillsboro, OR 97124
*   Work Telephone:  (503) 712-0534
*Cell:(208) 244-4460
* Email: stephen.k.jol...@intel.com

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

[yocto] Kernel configuration fragments and defconfig from kernel source tree, not meta layer file

[Alex J Lennon]

Hi,

I've been looking into a request to have Yocto kernel configuration
fragment support in meta-raspberrypi with a defconfig which is pulled
from the kernel source tree for the configured machine.

My understanding is that Yocto expects the defconfig file to be supplied
in the meta-layer and then configured with SRC_URI += "file://defconfig"

We'd prefer not to maintain copies of defconfigs, instead using the true
default configuration from the kernel tree and allowing users to add
their own .cfg fragments to the SRC_URI via, say, .bbappends.

It's easy enough to _prepend() a function to copy the appropriate
defconfig from the kernel source to the working directory, but I am
having a problem as do_patch() in kernel-yocto.bbclass seems to require
a defconfig file from the layer itself via use of SRC_URI in find_sccs().

Any thoughts? Thanks,

Alex

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

Re: [yocto] YP 1.8 Bug Fix Cutoff is coming soon!

[Sona Sarmadi]

Hi,

The OpenSSL Project will repair a "high severity" security hole in updates  due 
Thursday (19th March), is it possible to include this as well?


-BEGIN PGP SIGNED MESSAGE-

Hash: SHA1





Forthcoming OpenSSL releases





The OpenSSL project team would like to announce the forthcoming release of 
OpenSSL versions 1.0.2a, 1.0.1m, 1.0.0r and 0.9.8zf.



These releases will be made available on 19th March. They will fix a number of 
security defects. The highest severity defect fixed by these releases is 
classified as "high" severity.



Yours



The OpenSSL Project Team

-BEGIN PGP SIGNATURE-

Version: GnuPG v1


From: openembedded-core-boun...@lists.openembedded.org 
[mailto:openembedded-core-boun...@lists.openembedded.org] On Behalf Of Jolley, 
Stephen K
Sent: den 17 mars 2015 18:39
To: OE-core; yocto
Cc: Purdie, Richard
Subject: [OE-core] YP 1.8 Bug Fix Cutoff is coming soon!
Importance: High

All,

If you have an open bug targeting YP 1.8.   The cutoff for bug fixing for YP 
1.8 is coming up on 3/24/2015.   Please make your best effort to get your 
patches submitted to the mailing list before this date.   We will be doing our 
first release candidate right after the 24th and will only fixing bugs/issues 
which are found during testing and QA to insure we have a very stable release 
of YP 1.8 after this point.

If you have questions, please contact myself or Richard.

Thanks,

Stephen K. Jolley
Yocto Project Program Manager
INTEL, MS JF1-255, 2111 N.E. 25th Avenue, Hillsboro, OR 97124
*   Work Telephone:  (503) 712-0534
*Cell:(208) 244-4460
* Email: 
stephen.k.jol...@intel.com

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

Re: [yocto] Kernel configuration fragments and defconfig from kernel source tree, not meta layer file

[Bruce Ashfield]

On Tue, Mar 17, 2015 at 1:57 PM, Alex J Lennon
 wrote:
> Hi,
>
> I've been looking into a request to have Yocto kernel configuration
> fragment support in meta-raspberrypi with a defconfig which is pulled
> from the kernel source tree for the configured machine.
>
> My understanding is that Yocto expects the defconfig file to be supplied
> in the meta-layer and then configured with SRC_URI += "file://defconfig"
>
> We'd prefer not to maintain copies of defconfigs, instead using the true
> default configuration from the kernel tree and allowing users to add
> their own .cfg fragments to the SRC_URI via, say, .bbappends.

Anyone who knows me, knows that I'd say I hate to see defconfigs
at all ;)

But back on topic, this is something I can change, it is simply that
when I first put together the linux-yocto kernel configuration steps,
that most defconfigs were actually out of tree, and not within the kernel
tree itself.

>
> It's easy enough to _prepend() a function to copy the appropriate
> defconfig from the kernel source to the working directory, but I am
> having a problem as do_patch() in kernel-yocto.bbclass seems to require
> a defconfig file from the layer itself via use of SRC_URI in find_sccs().
>
> Any thoughts? Thanks,

Pop an enhancement request into the yocto bugzilla and assign it to
me. I can take care of it from there.

But just to be clear, this will have to stay out of oe-core for a bit, since
it is past feature freeze for 1.8 and even bug fixes are cut off shortly.

Cheers,

Bruce

>
> Alex
>
> --
> ___
> 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] Kernel configuration fragments and defconfig from kernel source tree, not meta layer file

[Alex J Lennon]

On 17/03/2015 21:08, Bruce Ashfield wrote:
> On Tue, Mar 17, 2015 at 1:57 PM, Alex J Lennon
>  wrote:
>> Hi,
>>
>> I've been looking into a request to have Yocto kernel configuration
>> fragment support in meta-raspberrypi with a defconfig which is pulled
>> from the kernel source tree for the configured machine.
>>
>> My understanding is that Yocto expects the defconfig file to be supplied
>> in the meta-layer and then configured with SRC_URI += "file://defconfig"
>>
>> We'd prefer not to maintain copies of defconfigs, instead using the true
>> default configuration from the kernel tree and allowing users to add
>> their own .cfg fragments to the SRC_URI via, say, .bbappends.
> Anyone who knows me, knows that I'd say I hate to see defconfigs
> at all ;)

I'm interested to understand the background if it's not too boring a
revisit for you.

Perhaps we can take that offline. What's the problem from your perspective?

> But back on topic, this is something I can change, it is simply that
> when I first put together the linux-yocto kernel configuration steps,
> that most defconfigs were actually out of tree, and not within the kernel
> tree itself.
>
>> It's easy enough to _prepend() a function to copy the appropriate
>> defconfig from the kernel source to the working directory, but I am
>> having a problem as do_patch() in kernel-yocto.bbclass seems to require
>> a defconfig file from the layer itself via use of SRC_URI in find_sccs().
>>
>> Any thoughts? Thanks,
> Pop an enhancement request into the yocto bugzilla and assign it to
> me. I can take care of it from there.
>
> But just to be clear, this will have to stay out of oe-core for a bit, since
> it is past feature freeze for 1.8 and even bug fixes are cut off shortly.

Great. Will do thanks Bruce,

Regards,

Alex

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

Re: [yocto] Kernel configuration fragments and defconfig from kernel source tree, not meta layer file

[Andrei Gherzan]

On Tue, Mar 17, 2015 at 9:08 PM, Bruce Ashfield 
wrote:

> On Tue, Mar 17, 2015 at 1:57 PM, Alex J Lennon
>  wrote:
> > Hi,
> >
> > I've been looking into a request to have Yocto kernel configuration
> > fragment support in meta-raspberrypi with a defconfig which is pulled
> > from the kernel source tree for the configured machine.
> >
> > My understanding is that Yocto expects the defconfig file to be supplied
> > in the meta-layer and then configured with SRC_URI += "file://defconfig"
> >
> > We'd prefer not to maintain copies of defconfigs, instead using the true
> > default configuration from the kernel tree and allowing users to add
> > their own .cfg fragments to the SRC_URI via, say, .bbappends.
>
> Anyone who knows me, knows that I'd say I hate to see defconfigs
> at all ;)
>
> But back on topic, this is something I can change, it is simply that
> when I first put together the linux-yocto kernel configuration steps,
> that most defconfigs were actually out of tree, and not within the kernel
> tree itself.
>
> >
> > It's easy enough to _prepend() a function to copy the appropriate
> > defconfig from the kernel source to the working directory, but I am
> > having a problem as do_patch() in kernel-yocto.bbclass seems to require
> > a defconfig file from the layer itself via use of SRC_URI in find_sccs().
> >
> > Any thoughts? Thanks,
>
> Pop an enhancement request into the yocto bugzilla and assign it to
> me. I can take care of it from there.
>
> But just to be clear, this will have to stay out of oe-core for a bit,
> since
> it is past feature freeze for 1.8 and even bug fixes are cut off shortly.
>
>
There is absolutely no way we can have this for 1.8? It's a minor thing.
And would help us a lot.


-- 
*Andrei Gherzan*
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] Kernel configuration fragments and defconfig from kernel source tree, not meta layer file

[Ashfield, Bruce]

On Mar 17, 2015, at 4:04 PM, Andrei Gherzan 
mailto:and...@gherzan.ro>> wrote:



On Tue, Mar 17, 2015 at 9:08 PM, Bruce Ashfield 
mailto:bruce.ashfi...@gmail.com>> wrote:
On Tue, Mar 17, 2015 at 1:57 PM, Alex J Lennon
mailto:ajlen...@dynamicdevices.co.uk>> wrote:
> Hi,
>
> I've been looking into a request to have Yocto kernel configuration
> fragment support in meta-raspberrypi with a defconfig which is pulled
> from the kernel source tree for the configured machine.
>
> My understanding is that Yocto expects the defconfig file to be supplied
> in the meta-layer and then configured with SRC_URI += "file://defconfig"
>
> We'd prefer not to maintain copies of defconfigs, instead using the true
> default configuration from the kernel tree and allowing users to add
> their own .cfg fragments to the SRC_URI via, say, .bbappends.

Anyone who knows me, knows that I'd say I hate to see defconfigs
at all ;)

But back on topic, this is something I can change, it is simply that
when I first put together the linux-yocto kernel configuration steps,
that most defconfigs were actually out of tree, and not within the kernel
tree itself.

>
> It's easy enough to _prepend() a function to copy the appropriate
> defconfig from the kernel source to the working directory, but I am
> having a problem as do_patch() in kernel-yocto.bbclass seems to require
> a defconfig file from the layer itself via use of SRC_URI in find_sccs().
>
> Any thoughts? Thanks,

Pop an enhancement request into the yocto bugzilla and assign it to
me. I can take care of it from there.

But just to be clear, this will have to stay out of oe-core for a bit, since
it is past feature freeze for 1.8 and even bug fixes are cut off shortly.


There is absolutely no way we can have this for 1.8? It's a minor thing. And 
would help us a lot.


To do this right .. It isn't completely minor (not huge ... But not trivial). 
We'll be exposing / creating an interface for this to any number of recipes. 
I'd rather do it once, than to do it quickly and have to fix it three times. Or 
come up with something clunky.

Making a temporary copy of those defconfigs carries no risk to the release ... 
So we have to balance and consider that

That being said, I'll see what I can do and can log it in a bugzilla ... There 
are some tools only options (versus tools and recipes)

Bruce







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

[yocto] customising root file system by removing the unwanted commands and libraries

[Dilip Basavaraju]

Dear All,

I want to build an RFS, which I need to customize it by 
removing the unwanted packages and particular commands which is not used by me.

Please suggest me how to customize, or refer me for documents 
where I can read and understand completely all the details about customization.

For example:

/bin will have cat, ls, cd, lsmod, wc .

I want to remove wc and lsmod and minimize my RFS as much as 
possible.

Thanks in advance.

Thanks and regards
DILIP KUMAR B

L&T Technology Services Ltd

www.LntTechservices.com

This Email may contain confidential or privileged information for the intended 
recipient (s). If you are not the intended recipient, please do not use or 
disseminate the information, notify the sender and delete it from your system.
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] customising root file system by removing the unwanted commands and libraries

[Dilip Basavaraju]

Dear All,

I want to build an RFS, which I need to customize it by 
removing the unwanted packages and particular commands which is not used by me.

Please suggest me how to customize, or refer me for documents 
where I can read and understand completely all the details about customization.

For example:

/bin will have cat, ls, cd, lsmod, wc .

I want to remove wc and lsmod and minimize my RFS as much as 
possible.

Thanks in advance.

Thanks and regards
DILIP KUMAR B

L&T Technology Services Ltd

www.LntTechservices.com

This Email may contain confidential or privileged information for the intended 
recipient (s). If you are not the intended recipient, please do not use or 
disseminate the information, notify the sender and delete it from your system.
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto