eglibc 2.13 upgrade

eglibc 2.13 upgrade

[Khem Raj]

Hi

I have eglibc 2.13 upgrade done locally and has been building fine for
all architectures. I have added 2.13 recipes and not
deleted the 2.12, This works ok except when setting the SRCREV. Since
we have a single file called
conf/distro/include/poky-default-revisions.inc to store this
information there can not be two SRCREV for two versions of same
package unless we move them to
recipes which is under work but not yet done. Thats one reason to hold
these patches. I can propose them if we are ok with
removing 2.12 recipes then it becomes straight forward

Opinions ?

-Khem

Re: eglibc 2.13 upgrade

[Koen Kooi]

Why not move those srcrevs into the recipe? IIRC these ones aren't affected by RPs concerns

Op 27 apr. 2011 om 18:21 heeft Khem Raj <raj.khem@gmail.com> het volgende geschreven:

> Hi
> 
> I have eglibc 2.13 upgrade done locally and has been building fine for
> all architectures. I have added 2.13 recipes and not
> deleted the 2.12, This works ok except when setting the SRCREV. Since
> we have a single file called
> conf/distro/include/poky-default-revisions.inc to store this
> information there can not be two SRCREV for two versions of same
> package unless we move them to
> recipes which is under work but not yet done. Thats one reason to hold
> these patches. I can propose them if we are ok with
> removing 2.12 recipes then it becomes straight forward
> 
> Opinions ?
> 
> -Khem
> 
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core

Re: eglibc 2.13 upgrade

[Khem Raj]

On Wed, Apr 27, 2011 at 9:44 AM, Koen Kooi <koen@dominion.thruhere.net> wrote:
> Why not move those srcrevs into the recipe? IIRC these ones aren't affected by RPs concerns

I am ok doing that but here
http://lists.linuxtogo.org/pipermail/openembedded-core/2011-April/001536.html

it seems we still need to investigate it before we start moving
SRCREVs to recipes.

>
> Op 27 apr. 2011 om 18:21 heeft Khem Raj <raj.khem@gmail.com> het volgende geschreven:
>
>> Hi
>>
>> I have eglibc 2.13 upgrade done locally and has been building fine for
>> all architectures. I have added 2.13 recipes and not
>> deleted the 2.12, This works ok except when setting the SRCREV. Since
>> we have a single file called
>> conf/distro/include/poky-default-revisions.inc to store this
>> information there can not be two SRCREV for two versions of same
>> package unless we move them to
>> recipes which is under work but not yet done. Thats one reason to hold
>> these patches. I can propose them if we are ok with
>> removing 2.12 recipes then it becomes straight forward
>>
>> Opinions ?
>>
>> -Khem
>>
>> _______________________________________________
>> Openembedded-core mailing list
>> Openembedded-core@lists.openembedded.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>

Re: eglibc 2.13 upgrade

[Saul Wold]

On 04/27/2011 01:13 PM, Khem Raj wrote:
> On Wed, Apr 27, 2011 at 9:44 AM, Koen Kooi<koen@dominion.thruhere.net>  wrote:
>> Why not move those srcrevs into the recipe? IIRC these ones aren't affected by RPs concerns
>
> I am ok doing that but here
> http://lists.linuxtogo.org/pipermail/openembedded-core/2011-April/001536.html
>
> it seems we still need to investigate it before we start moving
> SRCREVs to recipes.
>
We are days away from having this implemented (early next week is the 
plan right now). Once you see the big pull that moves SRCREVs, then you 
can go ahead with your upgrade.

Also creating a new recipe instead of moving the old one will cause a 
lose of history in git, we would prefer moves or create new / delete.

Sau!

>>
>> Op 27 apr. 2011 om 18:21 heeft Khem Raj<raj.khem@gmail.com>  het volgende geschreven:
>>
>>> Hi
>>>
>>> I have eglibc 2.13 upgrade done locally and has been building fine for
>>> all architectures. I have added 2.13 recipes and not
>>> deleted the 2.12, This works ok except when setting the SRCREV. Since
>>> we have a single file called
>>> conf/distro/include/poky-default-revisions.inc to store this
>>> information there can not be two SRCREV for two versions of same
>>> package unless we move them to
>>> recipes which is under work but not yet done. Thats one reason to hold
>>> these patches. I can propose them if we are ok with
>>> removing 2.12 recipes then it becomes straight forward
>>>
>>> Opinions ?
>>>
>>> -Khem
>>>
>>> _______________________________________________
>>> Openembedded-core mailing list
>>> Openembedded-core@lists.openembedded.org
>>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>>
>> _______________________________________________
>> Openembedded-core mailing list
>> Openembedded-core@lists.openembedded.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core

Re: eglibc 2.13 upgrade

[Khem Raj]

On Thu, Apr 28, 2011 at 3:03 PM, Saul Wold <sgw@linux.intel.com> wrote:
> On 04/27/2011 01:13 PM, Khem Raj wrote:
>>
>> On Wed, Apr 27, 2011 at 9:44 AM, Koen Kooi<koen@dominion.thruhere.net>
>>  wrote:
>>>
>>> Why not move those srcrevs into the recipe? IIRC these ones aren't
>>> affected by RPs concerns
>>
>> I am ok doing that but here
>>
>> http://lists.linuxtogo.org/pipermail/openembedded-core/2011-April/001536.html
>>
>> it seems we still need to investigate it before we start moving
>> SRCREVs to recipes.
>>
> We are days away from having this implemented (early next week is the plan
> right now). Once you see the big pull that moves SRCREVs, then you can go
> ahead with your upgrade.
>
> Also creating a new recipe instead of moving the old one will cause a lose
> of history in git, we would prefer moves or create new / delete.

I would move if we decide that its an upgrade and we dont need
2.12 anymore othereise It will be created new along side 2.12 problem
with creating
new is that it carries lot of history from 2.12 but does not associate
with it directly
renaming/moving will atleast have that link but thats besides

>
> Sau!
>
>>>
>>> Op 27 apr. 2011 om 18:21 heeft Khem Raj<raj.khem@gmail.com>  het volgende
>>> geschreven:
>>>
>>>> Hi
>>>>
>>>> I have eglibc 2.13 upgrade done locally and has been building fine for
>>>> all architectures. I have added 2.13 recipes and not
>>>> deleted the 2.12, This works ok except when setting the SRCREV. Since
>>>> we have a single file called
>>>> conf/distro/include/poky-default-revisions.inc to store this
>>>> information there can not be two SRCREV for two versions of same
>>>> package unless we move them to
>>>> recipes which is under work but not yet done. Thats one reason to hold
>>>> these patches. I can propose them if we are ok with
>>>> removing 2.12 recipes then it becomes straight forward
>>>>
>>>> Opinions ?
>>>>
>>>> -Khem
>>>>
>>>> _______________________________________________
>>>> Openembedded-core mailing list
>>>> Openembedded-core@lists.openembedded.org
>>>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>>>
>>> _______________________________________________
>>> Openembedded-core mailing list
>>> Openembedded-core@lists.openembedded.org
>>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>>>
>>
>> _______________________________________________
>> Openembedded-core mailing list
>> Openembedded-core@lists.openembedded.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>

Re: eglibc 2.13 upgrade

[Khem Raj]

On Thu, Apr 28, 2011 at 3:30 PM, Khem Raj <raj.khem@gmail.com> wrote:
> On Thu, Apr 28, 2011 at 3:03 PM, Saul Wold <sgw@linux.intel.com> wrote:
>> On 04/27/2011 01:13 PM, Khem Raj wrote:
>>>
>>> On Wed, Apr 27, 2011 at 9:44 AM, Koen Kooi<koen@dominion.thruhere.net>
>>>  wrote:
>>>>
>>>> Why not move those srcrevs into the recipe? IIRC these ones aren't
>>>> affected by RPs concerns
>>>
>>> I am ok doing that but here
>>>
>>> http://lists.linuxtogo.org/pipermail/openembedded-core/2011-April/001536.html
>>>
>>> it seems we still need to investigate it before we start moving
>>> SRCREVs to recipes.
>>>
>> We are days away from having this implemented (early next week is the plan
>> right now). Once you see the big pull that moves SRCREVs, then you can go
>> ahead with your upgrade.
>>
>> Also creating a new recipe instead of moving the old one will cause a lose
>> of history in git, we would prefer moves or create new / delete.
>
> I would move if we decide that its an upgrade and we dont need
> 2.12 anymore othereise It will be created new along side 2.12 problem
> with creating
> new is that it carries lot of history from 2.12 but does not associate
> with it directly
> renaming/moving will atleast have that link but thats besides
>
>>
>> Sau!
>>
>>>>
>>>> Op 27 apr. 2011 om 18:21 heeft Khem Raj<raj.khem@gmail.com>  het volgende
>>>> geschreven:
>>>>
>>>>> Hi
>>>>>
>>>>> I have eglibc 2.13 upgrade done locally and has been building fine for
>>>>> all architectures. I have added 2.13 recipes and not
>>>>> deleted the 2.12, This works ok except when setting the SRCREV. Since
>>>>> we have a single file called
>>>>> conf/distro/include/poky-default-revisions.inc to store this
>>>>> information there can not be two SRCREV for two versions of same
>>>>> package unless we move them to
>>>>> recipes which is under work but not yet done. Thats one reason to hold
>>>>> these patches. I can propose them if we are ok with
>>>>> removing 2.12 recipes then it becomes straight forward
>>>>>
>>>>> Opinions ?
>>>>>

I have staged a contrib branch with eglibc 2.13 upgrade

its here

http://git.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=kraj/eglibc-2.13

(top 1 patch)

Please try it out and report any issues you see

Thanks

-Khem

Re: eglibc 2.13 upgrade

[Khem Raj]

On (28/04/11 15:03), Saul Wold wrote:
> On 04/27/2011 01:13 PM, Khem Raj wrote:
> >On Wed, Apr 27, 2011 at 9:44 AM, Koen Kooi<koen@dominion.thruhere.net>  wrote:
> >>Why not move those srcrevs into the recipe? IIRC these ones aren't affected by RPs concerns
> >
> >I am ok doing that but here
> >http://lists.linuxtogo.org/pipermail/openembedded-core/2011-April/001536.html
> >
> >it seems we still need to investigate it before we start moving
> >SRCREVs to recipes.
> >
> We are days away from having this implemented (early next week is
> the plan right now). Once you see the big pull that moves SRCREVs,
> then you can go ahead with your upgrade.

The SRCREV move happened today. I have updated the eglibc patch
accordingly and pushed it to contrib branch here. I have earlier
tested it on all arches this time I tested only on arm and it still
works fine. So please try it out in your configurations and let me know
if anything is needed.

branch is here

http://git.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=kraj/eglibc-2.13

Thanks

-Khem