* Some Arch Linux build fixes
@ 2017-06-20 14:09 Anton Novikov
2017-06-21 3:05 ` Khem Raj
0 siblings, 1 reply; 4+ messages in thread
From: Anton Novikov @ 2017-06-20 14:09 UTC (permalink / raw)
To: yocto
Hi, and all have a nice day.
My company contributes to OpenBMC project, whose code has an
'import-layers/yocto-poky'
git subtree. I'm trying to build it on Arch Linux, which is a rolling
release distribution, and
has pretty recent package versions, which triggers some bugs, which I'm
fixing.
Patrick, an OpenBMC maintainer, sent me here, as the code in this folder
seems to be
synchronized with Yocto code. So somebody, please look at
https://github.com/openbmc/openbmc/pull/1817
and comment on it here. I want to either re-contribute the changes to
Yocto, or just maintain arch-fixes
branch of github.com/an146/openbmc and have someone else to adapt the
fixes to Yocto.
Thanks,
Anton
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: Some Arch Linux build fixes
2017-06-20 14:09 Some Arch Linux build fixes Anton Novikov
@ 2017-06-21 3:05 ` Khem Raj
2017-06-21 7:04 ` [yocto] " Anton Novikov
0 siblings, 1 reply; 4+ messages in thread
From: Khem Raj @ 2017-06-21 3:05 UTC (permalink / raw)
To: Anton Novikov; +Cc: yocto
On Tue, Jun 20, 2017 at 10:09 AM, Anton Novikov <a.novikov@yadro.com> wrote:
> Hi, and all have a nice day.
>
>
> My company contributes to OpenBMC project, whose code has an
> 'import-layers/yocto-poky'
>
> git subtree. I'm trying to build it on Arch Linux, which is a rolling
> release distribution, and
>
> has pretty recent package versions, which triggers some bugs, which I'm
> fixing.
>
>
> Patrick, an OpenBMC maintainer, sent me here, as the code in this folder
> seems to be
>
> synchronized with Yocto code. So somebody, please look at
> https://github.com/openbmc/openbmc/pull/1817
this are good fixes. Please send them to openembedded-core@ mailing list
for review and inclusion in branches they are required. Please be aware
that rolling releases are hard to use for a time based release like Yocto
since over period of time things will change unless you keep using master
of yocto. I would suggest to consider this fact.
>
> and comment on it here. I want to either re-contribute the changes to Yocto,
> or just maintain arch-fixes
>
> branch of github.com/an146/openbmc and have someone else to adapt the fixes
> to Yocto.
>
>
> Thanks,
>
> Anton
>
> --
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [yocto] Some Arch Linux build fixes
2017-06-21 3:05 ` Khem Raj
@ 2017-06-21 7:04 ` Anton Novikov
2017-06-21 7:27 ` Nicolas Dechesne
0 siblings, 1 reply; 4+ messages in thread
From: Anton Novikov @ 2017-06-21 7:04 UTC (permalink / raw)
To: openembedded-core
[-- Attachment #1: Type: text/plain, Size: 1801 bytes --]
Hi all,
people at yocto@yoctoproject.org sent me here.
Please review my commits and apply them or provide me with help to
do it myself.
Thanks,
Anton
-------- Forwarded Message --------
Subject: Re: [yocto] Some Arch Linux build fixes
Date: Tue, 20 Jun 2017 23:05:16 -0400
From: Khem Raj <raj.khem@gmail.com>
To: Anton Novikov <a.novikov@yadro.com>
CC: yocto@yoctoproject.org <yocto@yoctoproject.org>
On Tue, Jun 20, 2017 at 10:09 AM, Anton Novikov <a.novikov@yadro.com> wrote:
> Hi, and all have a nice day.
>
>
> My company contributes to OpenBMC project, whose code has an
> 'import-layers/yocto-poky'
>
> git subtree. I'm trying to build it on Arch Linux, which is a rolling
> release distribution, and
>
> has pretty recent package versions, which triggers some bugs, which I'm
> fixing.
>
>
> Patrick, an OpenBMC maintainer, sent me here, as the code in this folder
> seems to be
>
> synchronized with Yocto code. So somebody, please look at
> https://github.com/openbmc/openbmc/pull/1817
this are good fixes. Please send them to openembedded-core@ mailing list
for review and inclusion in branches they are required. Please be aware
that rolling releases are hard to use for a time based release like Yocto
since over period of time things will change unless you keep using master
of yocto. I would suggest to consider this fact.
>
> and comment on it here. I want to either re-contribute the changes to Yocto,
> or just maintain arch-fixes
>
> branch of github.com/an146/openbmc and have someone else to adapt the fixes
> to Yocto.
>
>
> Thanks,
>
> Anton
>
> --
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
[-- Attachment #2: Type: text/html, Size: 3753 bytes --]
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [yocto] Some Arch Linux build fixes
2017-06-21 7:04 ` [yocto] " Anton Novikov
@ 2017-06-21 7:27 ` Nicolas Dechesne
0 siblings, 0 replies; 4+ messages in thread
From: Nicolas Dechesne @ 2017-06-21 7:27 UTC (permalink / raw)
To: Anton Novikov; +Cc: Patches and discussions about the oe-core layer
hi,
On Wed, Jun 21, 2017 at 9:04 AM, Anton Novikov <a.novikov@yadro.com> wrote:
>
> Hi all,
>
> people at yocto@yoctoproject.org sent me here.
>
> Please review my commits and apply them or provide me with help to
>
> do it myself.
Patches need to be sent to the mailing list as inline patch, we wont'
do review on github.
please have a look at
http://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2017-06-21 7:27 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-06-20 14:09 Some Arch Linux build fixes Anton Novikov
2017-06-21 3:05 ` Khem Raj
2017-06-21 7:04 ` [yocto] " Anton Novikov
2017-06-21 7:27 ` Nicolas Dechesne
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.