Package naming "exceptions" in Yocto

Package naming "exceptions" in Yocto

[Reshetova, Elena]

[-- Attachment #1.1: Type: text/plain, Size: 733 bytes --]

Hi,

 

I have a small question about "exceptional" names of packages in yocto/OE.
Kernel package is being one example with the name "linux-yocto" vs.
traditional "linux_kernel". 

Are there more such yocto-specific packages (of course excluding FW and
other bsp-related packages)? A look over the package list didn't reveal any,
but I wanted to double check. 

 

The reason I am asking is that in case when we try to determine the package
CVEs against the NVD database, in these particular exception cases, we
probably want to check not only "linux-yocto", but also "linux_kernel" open
package CVEs with regards to specified version to make sure we cover as much
as we can. 

 

Best Regards,
Elena.

 


[-- Attachment #1.2: Type: text/html, Size: 2950 bytes --]

[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 7586 bytes --]

Re: Package naming "exceptions" in Yocto

[Philip Balister]

Please note there is a security page on the wiki:

https://wiki.yoctoproject.org/wiki/Security

and there is a security list at:

yocto-security@yoctoproject.org

The list isn't very active, but it should be copied on all security
discussions. If you are interested you should be subscribed to this list.

If I hadn't read the email, I wouldn't have realized this was about
security issues.

Philip

On 01/14/2016 02:43 AM, Reshetova, Elena wrote:
> Hi,
> 
>  
> 
> I have a small question about "exceptional" names of packages in yocto/OE.
> Kernel package is being one example with the name "linux-yocto" vs.
> traditional "linux_kernel". 
> 
> Are there more such yocto-specific packages (of course excluding FW and
> other bsp-related packages)? A look over the package list didn't reveal any,
> but I wanted to double check. 
> 
>  
> 
> The reason I am asking is that in case when we try to determine the package
> CVEs against the NVD database, in these particular exception cases, we
> probably want to check not only "linux-yocto", but also "linux_kernel" open
> package CVEs with regards to specified version to make sure we cover as much
> as we can. 
> 
>  
> 
> Best Regards,
> Elena.
> 
>  
> 
> 
> 
> 

Re: Package naming "exceptions" in Yocto

[Reshetova, Elena]

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

>Please note there is a security page on the wiki:

>https://wiki.yoctoproject.org/wiki/Security

>and there is a security list at:

>yocto-security@yoctoproject.org

>The list isn't very active, but it should be copied on all security
discussions. If you are interested you should be subscribed to this list.

>If I hadn't read the email, I wouldn't have realized this was about
security issues.

Well, security is just an example use-case, but the question is generic,
that's why I asked on yocto list. 

Best Regards,
Elena.

On 01/14/2016 02:43 AM, Reshetova, Elena wrote:
> Hi,
> 
>  
> 
> I have a small question about "exceptional" names of packages in yocto/OE.
> Kernel package is being one example with the name "linux-yocto" vs.
> traditional "linux_kernel". 
> 
> Are there more such yocto-specific packages (of course excluding FW 
> and other bsp-related packages)? A look over the package list didn't 
> reveal any, but I wanted to double check.
> 
>  
> 
> The reason I am asking is that in case when we try to determine the 
> package CVEs against the NVD database, in these particular exception 
> cases, we probably want to check not only "linux-yocto", but also 
> "linux_kernel" open package CVEs with regards to specified version to 
> make sure we cover as much as we can.
> 
>  
> 
> Best Regards,
> Elena.
> 
>  
> 
> 
> 
> 

[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 7586 bytes --]

Re: Package naming "exceptions" in Yocto

[akuster]

On 01/13/2016 11:43 PM, Reshetova, Elena wrote:
> Hi,
> 
>  
> 
> I have a small question about "exceptional" names of packages in yocto/OE.
> Kernel package is being one example with the name "linux-yocto" vs.
> traditional "linux_kernel". 

Since you ask about "Yocto" naming in the Poky distribution I have the
following comments:

The Reference to "Yocto" should only be in terms of the project. The
Soures you refer to in support of the "Poky" distro.
> 
> Are there more such yocto-specific packages (of course excluding FW and
> other bsp-related packages)? A look over the package list didn't reveal any,
> but I wanted to double check. 

The Yocto project should not have any specific packages. Its "Poky". In
fact in the last OEDAME it was decided to rename the meta-yocto* layers
to meta-poky*.  I was hoping would have been changed by now.

People are saying "Yocto linux" which is wrong. Its the Yocto Project
which has a test distro named "Poky".

Just ask Phil B.


> 
>  
> 
> The reason I am asking is that in case when we try to determine the package
> CVEs against the NVD database, in these particular exception cases, we
> probably want to check not only "linux-yocto", but also "linux_kernel" open
> package CVEs with regards to specified version to make sure we cover as much
> as we can. 

There may be a need to have a mapping for upstream names to packages
named within OE. They may not all be 1:1. Or in the case of someone
outside the project runs this in there distro they can.

regards,
Armin

> 
>  
> 
> Best Regards,
> Elena.
> 
>  
> 
> 
> 
> 

Re: Package naming "exceptions" in Yocto

[Khem Raj]

[-- Attachment #1.1: Type: text/plain, Size: 1656 bytes --]

Elena

> On Jan 13, 2016, at 11:43 PM, Reshetova, Elena <elena.reshetova@intel.com> wrote:
> 
> Hi,
> 
> I have a small question about “exceptional” names of packages in yocto/OE. Kernel package is being one example with the name “linux-yocto” vs.  traditional “linux_kernel”.


This just happens to be that Yocto project maintain a reference kernel and its called linux-yocto just following the naming conventions that are in use for kernel trees ( linux-<feature> ) e.g. linux-stable and so on
OE infra provides virtuals that we use to have pluggable kernels or other packages e.g. virtual/kernel for kernel and there are other packages which are using this mechanism too.

> Are there more such yocto-specific packages (of course excluding FW and other bsp-related packages)? A look over the package list didn’t reveal any, but I wanted to double check.
> 

yocto project does have more tools e.g. cross-prelink etc. there is no general naming convention of something-yocto for packages that project maintains
just check git.yoctoproject.org for number of components.

> The reason I am asking is that in case when we try to determine the package CVEs against the NVD database, in these particular exception cases, we probably want to check not only “linux-yocto”, but also “linux_kernel” open package CVEs with regards to specified version to make sure we cover as much as we can.

it probably is a general problem for end users since they may not use linux-yocto to provide the kernel on system but some other name but in the end they are kernels. may be some tooling to encode this in recipe would be good.

[-- Attachment #1.2: Type: text/html, Size: 4694 bytes --]

[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 211 bytes --]

Re: Package naming "exceptions" in Yocto

[Paul Eggleton]

Hi Elena,

On Thu, 14 Jan 2016 07:43:19 Reshetova, Elena wrote:
> I have a small question about "exceptional" names of packages in yocto/OE.
> Kernel package is being one example with the name "linux-yocto" vs.
> traditional "linux_kernel".
> 
> Are there more such yocto-specific packages (of course excluding FW and
> other bsp-related packages)? A look over the package list didn't reveal any,
> but I wanted to double check.
> 
> The reason I am asking is that in case when we try to determine the package
> CVEs against the NVD database, in these particular exception cases, we
> probably want to check not only "linux-yocto", but also "linux_kernel" open
> package CVEs with regards to specified version to make sure we cover as much
> as we can.

FYI we do have meta/conf/distro/include/distro_alias.inc which sets 
DISTRO_PN_ALIAS for each recipe, which is intended to help map to the names 
used in other distros. Will that work?

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre

Re: Package naming "exceptions" in Yocto

[Reshetova, Elena]

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

> FYI we do have meta/conf/distro/include/distro_alias.inc which sets
DISTRO_PN_ALIAS for each recipe, which is intended to help map to the names
used in other distros. Will that work?

Yes, I think this is exactly what I was hoping to find! Great that you
already have smth line this in place :)
 Just one question: how is this value supposed to be fetched in a class? I
could not find any usage example through the code. Is it set for each
package automatically or do I need to enable smth?

Best Regards,
Elena.

[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 7586 bytes --]

Re: Package naming "exceptions" in Yocto

[Paul Eggleton]

On Mon, 18 Jan 2016 11:14:31 Reshetova, Elena wrote:
> > FYI we do have meta/conf/distro/include/distro_alias.inc which sets
> 
> DISTRO_PN_ALIAS for each recipe, which is intended to help map to the names
> used in other distros. Will that work?
> 
> Yes, I think this is exactly what I was hoping to find! Great that you
> already have smth line this in place :)
>  Just one question: how is this value supposed to be fetched in a class? I
> could not find any usage example through the code. Is it set for each
> package automatically or do I need to enable smth?

create_distro_packages_list() in meta/lib/oe/distro_check.py is the only 
existing code that reads those values that I'm aware of, but that may not be 
in the form that you need it.

One thing you'll definitely need to do is to actually include the file in your 
configuration i.e.:

require conf/distro/include/distro_alias.inc

After that you should just be able to access DISTRO_PN_ALIAS like any other 
recipe-specific variable provided you're doing so in the context of a recipe 
(e.g. within a task for the recipe you wish to query the value for).

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre

Re: Package naming "exceptions" in Yocto

[Reshetova, Elena]

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

>One thing you'll definitely need to do is to actually include the file in
your configuration i.e.:

>require conf/distro/include/distro_alias.inc

This is what I was missing obviously since I stupidly assumed it is included
by default.  Thank you very much. Now I get the information I need :)

Best Regards,
Elena.

[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 7586 bytes --]