Re: [yocto] [tsc] [qa-build-notification] QA notification for completed autobuilder build (yocto-5.0.rc2)

[Denys Dmytriyenko]

On Thu, Apr 18, 2024 at 11:49:26AM +0100, Richard Purdie wrote:
> On Thu, 2024-04-18 at 10:45 +, Ross Burton wrote:
> > On 18 Apr 2024, at 09:11, Richard Purdie 
> >  wrote:
> > > For the purposes of history, the issue is in curl 8.7.0 and 8.7.1 was
> > > just a single bug fix. There is a fix in git master branch for the curl
> > > issue and curl themselves also have a fix in master as yet unreleased.
> > > I've backported the patch to git for now, we can drop it when we
> > > upgrade things.
> > 
> > As the underlying issue is in curl and has been fixed in master:
> > 
> > https://github.com/curl/curl/commit/721941aadf4adf4f6aeb3f4c0ab489bb89610c36
> > 
> > I think we should apply this instead.  The issue is a curl regression, we 
> > just saw it first in git.
> > 
> > I lean towards this being a release blocker and think we should respin.
> 
> Much as I would prefer not to, I agree. 
> 
> We should abandon rc2 and build an rc3. I'd like to keep the
> dunfell/kirkstone builds for after rc3 goes through QA though. We
> should be able to build rc3 quite quickly.

I believe 5.0 is still "within" the schedule, right?

What about dunfell and kirkstone minor releases? I know their builds are being 
delayed by 5.0 taking up AB. But are they already behind the schedule? If not, 
then 5.0 rc3 should definitely get prioritized.

-- 
Denys

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#62963): https://lists.yoctoproject.org/g/yocto/message/62963
Mute This Topic: https://lists.yoctoproject.org/mt/105575131/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] [tsc] [qa-build-notification] QA notification for completed autobuilder build (yocto-5.0.rc2)

[Denys Dmytriyenko]

On Wed, Apr 17, 2024 at 11:36:27AM +, Ross Burton wrote:
> On 17 Apr 2024, at 09:50, Richard Purdie via lists.yoctoproject.org 
>  wrote:
> > For b), updating buildtools should resolve it, I thought I had done
> > that but there were a lot of moving pieces so I must not have got the
> > latest.
> > 
> > I'm proposing we do but this into QA as I'd not block release on these
> > issues. I've done my best to get this into as good a shape as we can.
> 
> Agreed.  Can we do a build in the meantime of the specific job that failed 
> so we can verify the buildtools/pip issue is resolved?

Sounds reasonable.

-- 
Denys

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#62952): https://lists.yoctoproject.org/g/yocto/message/62952
Mute This Topic: https://lists.yoctoproject.org/mt/105575131/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] Canceled: OpenEmbedded Happy Hour November 29

[Denys Dmytriyenko]

There will be no OE Happy Hour on November 29 due to the ongoing Yocto Project 
Summit[1] this week and the OpenEmbedded Developers Meeting[2] on Friday.

[1] https://summit.yoctoproject.org/yocto-project-summit-2023-11/
[2] https://www.openembedded.org/wiki/OEDvM_2023.12

Best regards,
Denys Dmytriyenko
OpenEmbedded Board of Directors

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#61770): https://lists.yoctoproject.org/g/yocto/message/61770
Mute This Topic: https://lists.yoctoproject.org/mt/102861584/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] [RFC][meta-yocto][PATCH] poky.conf: re-enable TCLIBCAPPEND

[Denys Dmytriyenko]

Back in 2011[0] TCLIBCAPPEND was disabled due to:

"Poky doesn't support parallel builds of libc at this point"

Since then musl, newlib and baremetal support were added along with ability
to build them together in multiconfig environments. Some BSPs are actively
using multiconfigs to build baremetal components for modern heterogeneous
SoCs.

To enable such broad use cases for Poky (the reference Yocto distribution)
and many derivative distributions based on Poky, lets re-enable TCLIBCAPPEND
to isolate dissonant TMPDIRs from each other and possible collisions.

[0] 
https://git.yoctoproject.org/meta-yocto/commit/?id=5e121094c6024d8113ab0922b40ccc8a45215277

[YOCTO #15273]

Signed-off-by: Denys Dmytriyenko 
---
This may not be the right fix for #15273, but the change is good on its
own and it avoids the race condition reported in that bugzilla entry.
It also helps with other observed collisions in a combined TMPDIR, such
as nativesdk builds for incompatible multiconfigs, etc.

 meta-poky/conf/distro/poky.conf | 2 --
 1 file changed, 2 deletions(-)

diff --git a/meta-poky/conf/distro/poky.conf b/meta-poky/conf/distro/poky.conf
index e742666..742a64a 100644
--- a/meta-poky/conf/distro/poky.conf
+++ b/meta-poky/conf/distro/poky.conf
@@ -28,8 +28,6 @@ SDKPATHINSTALL = "/opt/${DISTRO}/${SDK_VERSION}"
 DISTRO_EXTRA_RDEPENDS += "${POKY_DEFAULT_EXTRA_RDEPENDS}"
 DISTRO_EXTRA_RRECOMMENDS += "${POKY_DEFAULT_EXTRA_RRECOMMENDS}"
 
-TCLIBCAPPEND = ""
-
 PACKAGE_CLASSES ?= "package_rpm"
 
 SANITY_TESTED_DISTROS ?= " \
-- 
2.25.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#61640): https://lists.yoctoproject.org/g/yocto/message/61640
Mute This Topic: https://lists.yoctoproject.org/mt/102470944/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] OpenEmbedded Happy Hour October 25 9pm/2100 UTC

[Denys Dmytriyenko]

All,

You are cordially invited to the next OpenEmbedded Happy Hour on October 25 
for Asia/Pacific timezones @ 2100/9pm UTC (5pm ET / 2pm PT):

https://www.openembedded.org/wiki/Calendar
https://www.openembedded.org/wiki/Happy_Hours
https://www.timeanddate.com/worldclock/fixedtime.html?msg=OpenEmbedded+Happy+Hour+October+25&iso=20231025T21

Best regards,
Denys Dmytriyenko
OpenEmbedded Board of Directors

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#61475): https://lists.yoctoproject.org/g/yocto/message/61475
Mute This Topic: https://lists.yoctoproject.org/mt/102173052/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] OpenEmbedded Happy Hour September 27 5pm/1700 UTC

[Denys Dmytriyenko]

All,

A friendly reminder - our regular monthly OpenEmbedded Happy Hour is coming 
up in 3 days, on September 27 for Europe/Americas timezones @ 1700/5pm UTC 
(1pm ET/10am PT)

https://www.openembedded.org/wiki/Calendar
https://www.openembedded.org/wiki/Happy_Hours
https://www.timeanddate.com/worldclock/fixedtime.html?msg=OpenEmbedded+Happy+Hour+September+27&iso=20230927T17

Since there were multiple confusions with time conversions to different 
timezones lately, please note the last link above, that's been provided 
for years, pointing to the actual event and allowing you to look up exact 
time for your location.

Best regards,
Denys Dmytriyenko
OpenEmbedded Board of Directors

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#61092): https://lists.yoctoproject.org/g/yocto/message/61092
Mute This Topic: https://lists.yoctoproject.org/mt/101562457/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] OpenEmbedded Happy Hour August 30 9pm/2100 UTC

[Denys Dmytriyenko]

All,

You are cordially invited to the next OpenEmbedded Happy Hour on August 30 
for Asia/Pacific timezones @ 2100/9pm UTC (5pm ET / 2pm PT):

https://www.openembedded.org/wiki/Calendar
https://www.openembedded.org/wiki/Happy_Hours
https://www.timeanddate.com/worldclock/fixedtime.html?msg=OpenEmbedded+Happy+Hour+August+30&iso=20230830T21

-- 
Regards,
Denys Dmytriyenko 
PGP: 0x420902729A92C964 - https://denix.org/0x420902729A92C964
Fingerprint: 25FC E4A5 8A72 2F69 1186  6D76 4209 0272 9A92 C964

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#60917): https://lists.yoctoproject.org/g/yocto/message/60917
Mute This Topic: https://lists.yoctoproject.org/mt/101042130/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] OpenEmbedded Happy Hour July 26 5pm/1700 UTC

[Denys Dmytriyenko]

In less than a day, tomorrow, we hope to see everyone at OE Happy Hour.


On Wed, Jul 19, 2023 at 06:07:04PM -0400, Denys Dmytriyenko wrote:
> All,
> 
> A friendly reminder - our regular monthly OpenEmbedded Happy Hour is 1 week 
> away, on July 26 for Europe/Americas timezones @ 1700/5pm UTC (1pm ET/10am PT)
> 
> https://www.openembedded.org/wiki/Calendar
> https://www.openembedded.org/wiki/Happy_Hours
> https://www.timeanddate.com/worldclock/fixedtime.html?msg=OpenEmbedded+Happy+Hour+July+26&iso=20230726T17

-- 
Regards,
Denys Dmytriyenko 
PGP: 0x420902729A92C964 - https://denix.org/0x420902729A92C964
Fingerprint: 25FC E4A5 8A72 2F69 1186  6D76 4209 0272 9A92 C964

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#60651): https://lists.yoctoproject.org/g/yocto/message/60651
Mute This Topic: https://lists.yoctoproject.org/mt/100245303/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] OpenEmbedded Happy Hour July 26 5pm/1700 UTC

[Denys Dmytriyenko]

All,

A friendly reminder - our regular monthly OpenEmbedded Happy Hour is 1 week 
away, on July 26 for Europe/Americas timezones @ 1700/5pm UTC (1pm ET/10am PT)

https://www.openembedded.org/wiki/Calendar
https://www.openembedded.org/wiki/Happy_Hours
https://www.timeanddate.com/worldclock/fixedtime.html?msg=OpenEmbedded+Happy+Hour+July+26&iso=20230726T17

-- 
Regards,
Denys Dmytriyenko 
PGP: 0x420902729A92C964 - https://denix.org/0x420902729A92C964
Fingerprint: 25FC E4A5 8A72 2F69 1186  6D76 4209 0272 9A92 C964

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#60616): https://lists.yoctoproject.org/g/yocto/message/60616
Mute This Topic: https://lists.yoctoproject.org/mt/100245303/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] Canceled: OpenEmbedded Happy Hour June 28

[Denys Dmytriyenko]

All,

Due to the coinciding Embedded Open Source Summit (EOSS) in Prague, the OE 
Board has decided to cancel our regular Happy Hour on June 28. The next Happy 
Hour is scheduled for July 26 - see you all then. Thank you.

-- 
Regards,
Denys Dmytriyenko 
PGP: 0x420902729A92C964 - https://denix.org/0x420902729A92C964
Fingerprint: 25FC E4A5 8A72 2F69 1186  6D76 4209 0272 9A92 C964

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#60427): https://lists.yoctoproject.org/g/yocto/message/60427
Mute This Topic: https://lists.yoctoproject.org/mt/99759471/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] OpenEmbedded Happy Hour May 31 5pm/1700 UTC

[Denys Dmytriyenko]

All,

Sorry for short notice - our regular OpenEmbedded Happy Hour is today, May 31 
for Europe/Americas timezones @ 1700/5pm UTC (1pm ET/10am PT)

https://www.openembedded.org/wiki/Calendar
https://www.openembedded.org/wiki/Happy_Hours
https://www.timeanddate.com/worldclock/fixedtime.html?msg=OpenEmbedded+Happy+Hour+May+31&iso=20230531T17

-- 
Regards,
Denys Dmytriyenko 
PGP: 0x420902729A92C964 - https://denix.org/0x420902729A92C964
Fingerprint: 25FC E4A5 8A72 2F69 1186  6D76 4209 0272 9A92 C964

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#60157): https://lists.yoctoproject.org/g/yocto/message/60157
Mute This Topic: https://lists.yoctoproject.org/mt/99244879/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] OpenEmbedded Happy Hour April 26 9pm/2100 UTC

[Denys Dmytriyenko]

All,

You are cordially invited to the next OpenEmbedded Happy Hour on April 26 
for Asia/Pacific timezones @ 2100/9pm UTC (5pm ET / 2pm PT):

https://www.openembedded.org/wiki/Calendar
https://www.openembedded.org/wiki/Happy_Hours
https://www.timeanddate.com/worldclock/fixedtime.html?msg=OpenEmbedded+Happy+Hour+April+26&iso=20230426T21

-- 
Regards,
Denys Dmytriyenko 
PGP: 0x420902729A92C964 - https://denix.org/0x420902729A92C964
Fingerprint: 25FC E4A5 8A72 2F69 1186  6D76 4209 0272 9A92 C964

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#59779): https://lists.yoctoproject.org/g/yocto/message/59779
Mute This Topic: https://lists.yoctoproject.org/mt/98500242/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] OpenEmbedded Happy Hour March 29 5pm/1700 UTC

[Denys Dmytriyenko]

All,

Another month has passed and we will hold our regular OpenEmbedded Happy Hour 
tomorrow, March 29 for Europe/Americas timezones @ 1700/5pm UTC (1pm ET/10am PT)

https://www.openembedded.org/wiki/Calendar
https://www.openembedded.org/wiki/Happy_Hours
https://www.timeanddate.com/worldclock/fixedtime.html?msg=OpenEmbedded+Happy+Hour+March+29&iso=20230329T17

-- 
Regards,
Denys Dmytriyenko 
PGP: 0x420902729A92C964 - https://denix.org/0x420902729A92C964
Fingerprint: 25FC E4A5 8A72 2F69 1186  6D76 4209 0272 9A92 C964

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#59541): https://lists.yoctoproject.org/g/yocto/message/59541
Mute This Topic: https://lists.yoctoproject.org/mt/97908661/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] OpenEmbedded Happy Hour February 22 9pm/2100 UTC

[Denys Dmytriyenko]

All,

You are cordially invited to the next OpenEmbedded Happy Hour on February 22 
for Asia/Pacific timezones @ 2100/9pm UTC (4pm ET / 1pm PT):

https://www.openembedded.org/wiki/Calendar
https://www.openembedded.org/wiki/Happy_Hours
https://www.timeanddate.com/worldclock/fixedtime.html?msg=OpenEmbedded+Happy+Hour+February+22&iso=20230222T21

-- 
Regards,
Denys Dmytriyenko 
PGP: 0x420902729A92C964 - https://denix.org/0x420902729A92C964
Fingerprint: 25FC E4A5 8A72 2F69 1186  6D76 4209 0272 9A92 C964

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#59279): https://lists.yoctoproject.org/g/yocto/message/59279
Mute This Topic: https://lists.yoctoproject.org/mt/97163920/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] OpenEmbedded Happy Hour January 25 5pm/1700 UTC

[Denys Dmytriyenko]

All,

You are cordially invited to the next OpenEmbedded Happy Hour on January 25 
for Europe/Americas timezones @ 1700/5pm UTC (12pm ET / 9am PT):

https://www.openembedded.org/wiki/Calendar
https://www.openembedded.org/wiki/Happy_Hours
https://www.timeanddate.com/worldclock/fixedtime.html?msg=OpenEmbedded+Happy+Hour+January+25&iso=20230125T17

-- 
Regards,
Denys Dmytriyenko 
PGP: 0x420902729A92C964 - https://denix.org/0x420902729A92C964
Fingerprint: 25FC E4A5 8A72 2F69 1186  6D76 4209 0272 9A92 C964

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#59052): https://lists.yoctoproject.org/g/yocto/message/59052
Mute This Topic: https://lists.yoctoproject.org/mt/96508535/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] [OE-core] OpenEmbedded Happy Hour November 30

[Denys Dmytriyenko]

Well, historically we used to have the OpenEmbedded Happy Hour after the 
sessions on the second day of the Yocto Project Summit and ask people to 
re-join a different Zoom room to socialize. This time around there's a 
dedicated YP Summit social time reserved, so to avoid switchig Zooms, we 
decided to move the OpenEmbedded Happy Hour to Friday, December 2, after 
the virtual Developers Meeting. The public calendar has been updated 
accordingly. Thank you.

-- 
Denys


On Tue, Nov 29, 2022 at 07:57:57PM +0100, Alexander Kanavin wrote:
> Isn't that clashing with YPS social slot?
> https://summit.yoctoproject.org/yocto-project-summit-2022-11/talk/UBXLG8/
> 
> Alex
> 
> On Tue, 29 Nov 2022 at 14:15, Denys Dmytriyenko  wrote:
> >
> > All,
> >
> > This month OpenEmbedded Happy Hour coincides with the Yocto Project Summit
> > and will be held on Wednesday, November 30 after the sessions are over,
> > aroud 1800/6pm UTC (1pm ET / 10am PT). The usual Zoom link is in the Wiki:
> >
> > https://www.openembedded.org/wiki/Calendar
> > https://www.openembedded.org/wiki/Happy_Hours

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#58685): https://lists.yoctoproject.org/g/yocto/message/58685
Mute This Topic: https://lists.yoctoproject.org/mt/95341821/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] OpenEmbedded Happy Hour November 30

[Denys Dmytriyenko]

All,

This month OpenEmbedded Happy Hour coincides with the Yocto Project Summit
and will be held on Wednesday, November 30 after the sessions are over,
aroud 1800/6pm UTC (1pm ET / 10am PT). The usual Zoom link is in the Wiki:

https://www.openembedded.org/wiki/Calendar
https://www.openembedded.org/wiki/Happy_Hours

-- 
Regards,
Denys Dmytriyenko 
PGP: 0x420902729A92C964 - https://denix.org/0x420902729A92C964
Fingerprint: 25FC E4A5 8A72 2F69 1186  6D76 4209 0272 9A92 C964

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#58653): https://lists.yoctoproject.org/g/yocto/message/58653
Mute This Topic: https://lists.yoctoproject.org/mt/95333632/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] OpenEmbedded Happy Hour March 30 5pm/1700 UTC

[Denys Dmytriyenko]

Reminder, OpenEmbedded Happy Hour is tomorrow. See you all there.


On Thu, Mar 24, 2022 at 06:41:58PM -0400, Denys Dmytriyenko wrote:
> All,
> 
> You are cordially invited to the next OpenEmbedded Happy Hour on March 30 
> for Europe/Americas timezones @ 1700/5pm UTC (1pm ET / 10am PT):
> 
> https://www.openembedded.org/wiki/Calendar
> https://www.openembedded.org/wiki/Happy_Hours
> https://www.timeanddate.com/worldclock/fixedtime.html?msg=OpenEmbedded+Happy+Hour+March+30&iso=20220330T17

-- 
Regards,
Denys Dmytriyenko 
PGP: 0x420902729A92C964 - https://denix.org/0x420902729A92C964
Fingerprint: 25FC E4A5 8A72 2F69 1186  6D76 4209 0272 9A92 C964

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#56589): https://lists.yoctoproject.org/g/yocto/message/56589
Mute This Topic: https://lists.yoctoproject.org/mt/90011133/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] OpenEmbedded Happy Hour March 30 5pm/1700 UTC

[Denys Dmytriyenko]

All,

You are cordially invited to the next OpenEmbedded Happy Hour on March 30 
for Europe/Americas timezones @ 1700/5pm UTC (1pm ET / 10am PT):

https://www.openembedded.org/wiki/Calendar
https://www.openembedded.org/wiki/Happy_Hours
https://www.timeanddate.com/worldclock/fixedtime.html?msg=OpenEmbedded+Happy+Hour+March+30&iso=20220330T17

-- 
Regards,
Denys Dmytriyenko 
PGP: 0x420902729A92C964 - https://denix.org/0x420902729A92C964
Fingerprint: 25FC E4A5 8A72 2F69 1186  6D76 4209 0272 9A92 C964

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#56556): https://lists.yoctoproject.org/g/yocto/message/56556
Mute This Topic: https://lists.yoctoproject.org/mt/90011133/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] OpenEmbedded Happy Hour February 23 9pm/2100 UTC

[Denys Dmytriyenko]

On Mon, Feb 21, 2022 at 06:26:05PM -0500, Denys Dmytriyenko wrote:
> All,
> 
> You are cordially invited to the next OpenEmbedded Happy Hour on February 23 
> for Asia/Pacific timezones @ 2100/9pm UTC (4pm ET / 1pm PT):
> 
> https://www.openembedded.org/wiki/Calendar
> https://www.openembedded.org/wiki/Happy_Hours
> https://www.timeanddate.com/worldclock/fixedtime.html?msg=OpenEmbedded+Happy+Hour+February+23&iso=20220223T21

Reminder, this is happening in 2 hours! See you then and there.

-- 
Regards,
Denys Dmytriyenko 
PGP: 0x420902729A92C964 - https://denix.org/0x420902729A92C964
Fingerprint: 25FC E4A5 8A72 2F69 1186  6D76 4209 0272 9A92 C964

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#56270): https://lists.yoctoproject.org/g/yocto/message/56270
Mute This Topic: https://lists.yoctoproject.org/mt/89306213/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] [yocto-autobuilder-helper][PATCH] config.json: update check-layer for meta-ti due to restructure

[Denys Dmytriyenko]

meta-ti recently split into sublayers - adjust config.json accordingly.

Signed-off-by: Denys Dmytriyenko 
---
 config.json | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/config.json b/config.json
index fa13545..ba7a6a0 100644
--- a/config.json
+++ b/config.json
@@ -891,7 +891,7 @@
 },
 "step5" : {
 "shortname" : "Test meta-ti YP Compatibility",
-"EXTRACMDS" : ["yocto-check-layer-wrapper ../meta-ti 
--dependency ../meta-arm --no-auto-dependency"]
+"EXTRACMDS" : ["yocto-check-layer-wrapper 
../meta-ti/meta-ti-bsp ../meta-ti/meta-ti-extras --dependency ../meta-arm 
--no-auto-dependency"]
 },
 "step6" : {
 "shortname" : "Test meta-oe YP Compatibility",
-- 
2.25.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#56255): https://lists.yoctoproject.org/g/yocto/message/56255
Mute This Topic: https://lists.yoctoproject.org/mt/89331252/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] OpenEmbedded Happy Hour February 23 9pm/2100 UTC

[Denys Dmytriyenko]

All,

You are cordially invited to the next OpenEmbedded Happy Hour on February 23 
for Asia/Pacific timezones @ 2100/9pm UTC (4pm ET / 1pm PT):

https://www.openembedded.org/wiki/Calendar
https://www.openembedded.org/wiki/Happy_Hours
https://www.timeanddate.com/worldclock/fixedtime.html?msg=OpenEmbedded+Happy+Hour+February+23&iso=20220223T21

-- 
Regards,
Denys Dmytriyenko 
PGP: 0x420902729A92C964 - https://denix.org/0x420902729A92C964
Fingerprint: 25FC E4A5 8A72 2F69 1186  6D76 4209 0272 9A92 C964

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#56227): https://lists.yoctoproject.org/g/yocto/message/56227
Mute This Topic: https://lists.yoctoproject.org/mt/89306213/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] [meta-lts-mixins][dunfell/go PATCH 1/4] Initial commit: add license, readme and layer config.

[Denys Dmytriyenko]

On Thu, Jan 27, 2022 at 06:07:06PM +0100, Alexander Kanavin wrote:
> A question specifically to Denys, how can I actually get this into the
> mixin repo, and have commit rights to the branch? We've tested this quite
> well in private, and there are further enhancements coming up.

Michael,

Would it be possible to create 2 additional branches in the meta-lts-mixins 
repository at https://git.yoctoproject.org/meta-lts-mixins/ called 
"dunfell/go" and also "dunfell/docker" and give Alex push rights to them?

Please let us know, thanks a lot!

-- 
Denys


> On Thu, 27 Jan 2022 at 15:43, Alexander Kanavin via lists.yoctoproject.org
>  wrote:
> 
> > Reviewed-by: Martin Kaistra 
> > Signed-off-by: Alexander Kanavin 
> > ---
> >  COPYING.MIT | 17 +
> >  README  | 23 +++
> >  conf/layer.conf | 19 +++
> >  3 files changed, 59 insertions(+)
> >  create mode 100644 COPYING.MIT
> >  create mode 100644 README
> >  create mode 100644 conf/layer.conf
> >
> > diff --git a/COPYING.MIT b/COPYING.MIT
> > new file mode 100644
> > index 000..fb950dc
> > --- /dev/null
> > +++ b/COPYING.MIT
> > @@ -0,0 +1,17 @@
> > +Permission is hereby granted, free of charge, to any person obtaining a
> > copy
> > +of this software and associated documentation files (the "Software"), to
> > deal
> > +in the Software without restriction, including without limitation the
> > rights
> > +to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
> > +copies of the Software, and to permit persons to whom the Software is
> > +furnished to do so, subject to the following conditions:
> > +
> > +The above copyright notice and this permission notice shall be included
> > in
> > +all copies or substantial portions of the Software.
> > +
> > +THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS
> > OR
> > +IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
> > +FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL
> > THE
> > +AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
> > +LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
> > FROM,
> > +OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
> > +THE SOFTWARE.
> > diff --git a/README b/README
> > new file mode 100644
> > index 000..5b22b72
> > --- /dev/null
> > +++ b/README
> > @@ -0,0 +1,23 @@
> > +"Mixin" layer for adding latest Go toolchain versions into the Yocto
> > Project LTS.
> > +
> > +At the time Dunfell was released in April 2020, Go 1.14 was the latest
> > version
> > +and officially Dunfell supports only that. This thin special-purpose mixin
> > +layer is meant to address this issue by backporting Go recipes from the
> > master
> > +branch of openembedded-core.
> > +
> > +You can see what Go versions are provided by listing recipes-devtools/
> > content.
> > +
> > +Including the layer automatically picks up the latest Go version;
> > different versions
> > +need to be set explicitly by adding the following line to your distro
> > config
> > +or local.conf:
> > +
> > +GOVERSION = "1.16%"
> > +
> > +Please note: enabling these newer Go versions makes docker from dunfell
> > branch
> > +of meta-virtualization unbuildable as it is too old. If you need a
> > working docker
> > +recipe, you can use the supplementary 'dunfell/docker' layer from this
> > meta-lts-mixin
> > +repository.
> > +
> > +
> > +Maintainers:
> > +Alexander Kanavin 
> > diff --git a/conf/layer.conf b/conf/layer.conf
> > new file mode 100644
> > index 000..5f74224
> > --- /dev/null
> > +++ b/conf/layer.conf
> > @@ -0,0 +1,19 @@
> > +# We have a conf and classes directory, append to BBPATH
> > +BBPATH .= ":${LAYERDIR}"
> > +
> > +# We have a recipes directory, add to BBFILES
> > +BBFILES += "${LAYERDIR}/recipes*/*/*.bb ${LAYERDIR}/recipes*/*/*.bbappend"
> > +
> > +BBFILE_COLLECTIONS += "lts-go-mixin"
> > +BBFILE_PATTERN_lts-go-mixin := "^${LAYERDIR}/"
> > +BBFILE_PRIORITY_lts-go-mixin = "6"
> > +
> > +LAYERSERIES_COMPAT_lts-go-mixin = "dunfell"
> > +
> > +LAYERDEPENDS_lts-go-mixin = " \
> > +core \
> > +"
> > +
> > +GOVERSION ?= "1.17%"
> > +PREFERRED_PROVIDER_go-native = "go-binary-native"
> > +
> > --
> > 2.20.1

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#56003): https://lists.yoctoproject.org/g/yocto/message/56003
Mute This Topic: https://lists.yoctoproject.org/mt/88722205/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] OpenEmbedded Happy Hour January 26 5pm/1700 UTC

[Denys Dmytriyenko]

All,

Our next OpenEmbedded Happy Hour is on January 26 for Europe/Americas 
timezones @ 1700/5pm UTC (12pm ET / 9am PT):

https://www.openembedded.org/wiki/Calendar
https://www.timeanddate.com/worldclock/fixedtime.html?msg=OpenEmbedded+Happy+Hour+January+26&iso=20220126T17

-- 
Regards,
Denys Dmytriyenko 
PGP: 0x420902729A92C964 - https://denix.org/0x420902729A92C964
Fingerprint: 25FC E4A5 8A72 2F69 1186  6D76 4209 0272 9A92 C964

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#55969): https://lists.yoctoproject.org/g/yocto/message/55969
Mute This Topic: https://lists.yoctoproject.org/mt/88678724/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] Canceled: OpenEmbedded Happy Hour December 29

[Denys Dmytriyenko]

Hi,

The next OpenEmbedded Happy Hour is being canceled due to the Holidays and 
since we had the last one on December 3. The next Happy Hour will take place 
on January 26 2022:

https://www.openembedded.org/wiki/Calendar

-- 
Regards,
Denys Dmytriyenko 
PGP: 0x420902729A92C964 - https://denix.org/0x420902729A92C964
Fingerprint: 25FC E4A5 8A72 2F69 1186  6D76 4209 0272 9A92 C964

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#55602): https://lists.yoctoproject.org/g/yocto/message/55602
Mute This Topic: https://lists.yoctoproject.org/mt/87775437/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] OpenEmbedded Happy Hour December 3 8pm/2000 UTC after OEDVM

[Denys Dmytriyenko]

All,

As previously announced, OpenEmbedded Developer Virtual Meeting will take 
place on December 3 from 12:00 UTC until 20:00 UTC:

https://www.openembedded.org/wiki/OEDVM_Nov_2021

Once the meeting is over, everybody is invited to hang out and relax at 
the OpenEmbedded Happy Hour, which tentatively will start at 20:00 UTC 
(3pm ET / 12pm PT):

https://www.openembedded.org/wiki/Happy_Hours
https://www.openembedded.org/wiki/Calendar
https://www.timeanddate.com/worldclock/fixedtime.html?msg=OpenEmbedded+Happy+Hour+December+3&iso=20211203T20

-- 
Regards,
Denys Dmytriyenko 
PGP: 0x420902729A92C964 - https://denix.org/0x420902729A92C964
Fingerprint: 25FC E4A5 8A72 2F69 1186  6D76 4209 0272 9A92 C964

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#55434): https://lists.yoctoproject.org/g/yocto/message/55434
Mute This Topic: https://lists.yoctoproject.org/mt/87347697/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] OpenEmbedded Happy Hour October 27 9pm/2100 UTC

[Denys Dmytriyenko]

All,

Our next OpenEmbedded Happy Hour is on October 27 for Asia/Pacific timezones @ 
2100/9pm UTC (5pm ET / 2pm PT):

https://www.openembedded.org/wiki/Calendar
https://www.timeanddate.com/worldclock/fixedtime.html?msg=OpenEmbedded+Happy+Hour+October+27&iso=20211027T21

-- 
Regards,
Denys Dmytriyenko 
PGP: 0x420902729A92C964 - https://denix.org/0x420902729A92C964
Fingerprint: 25FC E4A5 8A72 2F69 1186  6D76 4209 0272 9A92 C964

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#55153): https://lists.yoctoproject.org/g/yocto/message/55153
Mute This Topic: https://lists.yoctoproject.org/mt/86586653/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] OpenEmbedded Happy Hour May 26 8pm/2000 UTC

[Denys Dmytriyenko]

Hi,

Due to the Yocto Project Summit running during our regular OpenEmbedded Happy 
Hour today, we decided to move it down by 3 hours and have Happy Hour at the 
end of the Summit, May 26 @ 2000/8pm UTC (4pm ET / 1pm PT).

Please join us and socialize with fellow developers and have some good time.

https://www.openembedded.org/wiki/Calendar
https://www.timeanddate.com/worldclock/fixedtime.html?msg=OpenEmbedded+Happy+Hour+May+26&iso=20210526T20

-- 
Regards,
Denys Dmytriyenko 
PGP: 0x420902729A92C964 - https://denix.org/0x420902729A92C964
Fingerprint: 25FC E4A5 8A72 2F69 1186  6D76 4209 0272 9A92 C964

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#53664): https://lists.yoctoproject.org/g/yocto/message/53664
Mute This Topic: https://lists.yoctoproject.org/mt/83106664/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] OpenEmbedded Happy Hour April 28 9pm/2100 UTC

[Denys Dmytriyenko]

Reminder, next Happy Hour is in one day - everyone is welcome to meet with 
fellow developers and chat about any interesting topics over Zoom. BYOB - 
bring your own beverage.


On Wed, Apr 21, 2021 at 04:04:25PM -0400, Denys Dmytriyenko wrote:
> Hi,
> 
> Please join us for the upcoming OpenEmbedded Happy Hour on April 28 for 
> Asia/Pacific timezones @ 2100/9pm UTC (5pm EDT):
> 
> https://www.openembedded.org/wiki/Calendar
> https://www.timeanddate.com/worldclock/fixedtime.html?msg=OpenEmbedded+Happy+Hour+April+28&iso=20210428T21

-- 
Regards,
Denys Dmytriyenko 
PGP: 0x420902729A92C964 - https://denix.org/0x420902729A92C964
Fingerprint: 25FC E4A5 8A72 2F69 1186  6D76 4209 0272 9A92 C964

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#53300): https://lists.yoctoproject.org/g/yocto/message/53300
Mute This Topic: https://lists.yoctoproject.org/mt/82270298/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] OpenEmbedded Happy Hour April 28 9pm/2100 UTC

[Denys Dmytriyenko]

Hi,

Please join us for the upcoming OpenEmbedded Happy Hour on April 28 for 
Asia/Pacific timezones @ 2100/9pm UTC (5pm EDT):

https://www.openembedded.org/wiki/Calendar
https://www.timeanddate.com/worldclock/fixedtime.html?msg=OpenEmbedded+Happy+Hour+April+28&iso=20210428T21

-- 
Regards,
Denys Dmytriyenko 
PGP: 0x420902729A92C964 - https://denix.org/0x420902729A92C964
Fingerprint: 25FC E4A5 8A72 2F69 1186  6D76 4209 0272 9A92 C964

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#53207): https://lists.yoctoproject.org/g/yocto/message/53207
Mute This Topic: https://lists.yoctoproject.org/mt/82270298/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] OpenEmbedded Happy Hour March 31 5pm/1700 UTC

[Denys Dmytriyenko]

Hi,

Just a reminder about our upcoming OpenEmbedded Happy Hour on March 31 for
Europe/US timezones @ 1700/5pm UTC (1pm ET / 10am PT):

https://www.openembedded.org/wiki/Calendar
https://www.timeanddate.com/worldclock/fixedtime.html?msg=OpenEmbedded+Happy+Hour+March+31&iso=20210331T17

-- 
Regards,
Denys Dmytriyenko 
PGP: 0x420902729A92C964 - https://denix.org/0x420902729A92C964
Fingerprint: 25FC E4A5 8A72 2F69 1186  6D76 4209 0272 9A92 C964

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#52913): https://lists.yoctoproject.org/g/yocto/message/52913
Mute This Topic: https://lists.yoctoproject.org/mt/81618807/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] OpenEmbedded Happy Hour February 24 9pm/2100 UTC

[Denys Dmytriyenko]

Hi,

Please join us for the upcoming OpenEmbedded Happy Hour on February 24 for 
Asia/Pacific timezones @ 2100/9pm UTC (4pm EST):

https://www.openembedded.org/wiki/Calendar
https://www.timeanddate.com/worldclock/fixedtime.html?msg=OpenEmbedded+Happy+Hour+February+24&iso=20210224T21

-- 
Regards,
Denys Dmytriyenko 
PGP: 0x420902729A92C964 - https://denix.org/0x420902729A92C964
Fingerprint: 25FC E4A5 8A72 2F69 1186  6D76 4209 0272 9A92 C964

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#52459): https://lists.yoctoproject.org/g/yocto/message/52459
Mute This Topic: https://lists.yoctoproject.org/mt/80858126/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] OpenEmbedded Happy Hour January 27 5pm/1700 UTC

[Denys Dmytriyenko]

Hi,

Just a reminder about our upcoming OpenEmbedded Happy Hour on January 27 for
Europe/US timezones @ 1700/5pm UTC (12pm ET):

https://www.openembedded.org/wiki/Calendar
https://www.timeanddate.com/worldclock/fixedtime.html?msg=OpenEmbedded+Happy+Hour+January+27&iso=20210127T17

-- 
Regards,
Denys Dmytriyenko 
PGP: 0x420902729A92C964 - https://denix.org/0x420902729A92C964
Fingerprint: 25FC E4A5 8A72 2F69 1186  6D76 4209 0272 9A92 C964

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#52093): https://lists.yoctoproject.org/g/yocto/message/52093
Mute This Topic: https://lists.yoctoproject.org/mt/80120464/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] Canceled: OpenEmbedded Happy Hour December 30

[Denys Dmytriyenko]

All,

FYI, our OpenEmbedded Happy Hour is being canceled for December 30 due to the 
Holiday season. We will resume the normal schedule in January.

Thank you and Happy Holidays!

-- 
Regards,
Denys Dmytriyenko 
PGP: 0x420902729A92C964 - https://denix.org/0x420902729A92C964
Fingerprint: 25FC E4A5 8A72 2F69 1186  6D76 4209 0272 9A92 C964

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#51760): https://lists.yoctoproject.org/g/yocto/message/51760
Mute This Topic: https://lists.yoctoproject.org/mt/78983951/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] [OE-core] OpenEmbedded Happy Hour November 25 9pm/2100 UTC

[Denys Dmytriyenko]

Just a reminder, Happy Hour is in 1 hour.

9pm UTC, 4pm EST (not EDT) or use time conversion link below for your 
location. See you there!

-- 
Denys


On Thu, Nov 19, 2020 at 01:12:35PM -0500, Denys Dmytriyenko wrote:
> Hi,
> 
> Just a reminder about our upcoming OpenEmbedded Happy Hour on November 25 for
> Oceania/Asia timezones @ 2100/9pm UTC (4pm EDT):
> 
> https://www.openembedded.org/wiki/Calendar
> https://www.timeanddate.com/worldclock/fixedtime.html?msg=OpenEmbedded+Happy+Hour+November+25&iso=20201125T21
> 
> -- 
> Denys

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#51566): https://lists.yoctoproject.org/g/yocto/message/51566
Mute This Topic: https://lists.yoctoproject.org/mt/78507975/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] OpenEmbedded Happy Hour November 25 9pm/2100 UTC

[Denys Dmytriyenko]

Hi,

Just a reminder about our upcoming OpenEmbedded Happy Hour on November 25 for
Oceania/Asia timezones @ 2100/9pm UTC (4pm EDT):

https://www.openembedded.org/wiki/Calendar
https://www.timeanddate.com/worldclock/fixedtime.html?msg=OpenEmbedded+Happy+Hour+November+25&iso=20201125T21

-- 
Denys

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#51452): https://lists.yoctoproject.org/g/yocto/message/51452
Mute This Topic: https://lists.yoctoproject.org/mt/78371357/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] OpenEmbedded Happy Hour September 30 9pm/2100 UTC

[Denys Dmytriyenko]

Just a reminder about our upcoming OpenEmbedded Happy Hour on September 30 for 
Oceania/Asia timezones @ 2100/9pm UTC (5pm EDT):

https://www.openembedded.org/wiki/Calendar
https://www.timeanddate.com/worldclock/fixedtime.html?msg=OpenEmbedded+Happy+Hour+September+30&iso=20200930T21

-- 
Denys

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#50886): https://lists.yoctoproject.org/g/yocto/message/50886
Mute This Topic: https://lists.yoctoproject.org/mt/77208513/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] OpenEmbedded Happy Hour July 29 9pm/2100 UTC

[Denys Dmytriyenko]

Just a reminder about our upcoming OpenEmbedded Happy Hour on July 29 for 
Oceania/Asia timezones @ 2100/9pm UTC (5pm EDT):

https://www.openembedded.org/wiki/Calendar
https://www.timeanddate.com/worldclock/fixedtime.html?msg=OpenEmbedded+Happy+Hour+July+29&iso=20200729T21

-- 
Denys
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#50126): https://lists.yoctoproject.org/g/yocto/message/50126
Mute This Topic: https://lists.yoctoproject.org/mt/75855980/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] Strange error

[Denys Dmytriyenko]

You know that rootfs already creates /etc/version file with $DATETIME?

Either way, you can fix it like this:
mark_os_buildtime[vardepsexclude] = "DATETIME"

-- 
Denys


On Thu, Jun 11, 2020 at 09:56:42AM +0200, Mauro Ziliani wrote:
> In the image recipe i write ${DATETIME} in
> ${IMAGE_ROOTFS}/etc/buildtime by a function.
> 
> This is the part of recipe
> 
> 
> ROOTFS_POSTPROCESS_COMMAND_append = " \
>     mark_os_buildtime; \
> 
> "
> 
> 
> mark_os_buildtime() {
>     echo "${PV} ${DATETIME}" > ${IMAGE_ROOTFS}/etc/buildtime
> 
> }
> 
> 
> 
> Il 10/06/20 20:44, Josef Holzmayr ha scritto:
> >Howdy!
> >
> >Am 10.06.2020 um 19:48 schrieb Mauro Ziliani:
> >>Hi all.
> >>
> >>This error
> >>
> >>NOTE: Executing RunQueue Tasks
> >>ERROR: When reparsing .do_rootfs, the basehash
> >>value changed from 7419bfc242fa2eee9ce87b18ebf40d25 to
> >>5b2654046d2ac406f3484b3286de0acd. The metadata is not
> >>deterministic and this needs to be fixed.
> >>
> >>
> >>Why?
> >
> >Maybe some script / part of the recipe is dependent on the
> >execution time or evaluation order? The error basically tells you
> >that your build is not reproducible across runs.
> >
> >Greetz
> >
> >
> >

> 

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#49625): https://lists.yoctoproject.org/g/yocto/message/49625
Mute This Topic: https://lists.yoctoproject.org/mt/74802412/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] opkg package manifest file is not generated by bitbake

[Denys Dmytriyenko]

bitbake package-index

On Fri, Jun 05, 2020 at 08:48:22AM +0200, Kevin Kettinger wrote:
> Hello,
> 
> i want to use my yocto build sever as opkg package source for
> updating some packages directly, but it seems after generating an
> image the "Packages" file for opkg is not created.
> 
> In the .//tmp/deploy/ipk folder, there are these folders
> -
>   all
>   apalis_imx6
>   cortexa9hf-neon
>   cortexa9t2hf-neon
>   cortexa9t2hf-neon-mx6qdl
> -
> but no "Packages" or "Packages.gz" file.
> 
> My local.conf:
> -
> BB_NUMBER_THREADS ?= "${@oe.utils.cpu_count()}"
> PARALLEL_MAKE ?= "-j ${@oe.utils.cpu_count()}"
> MACHINE ??= "apalis-imx6"
> MACHINE_HOSTNAME ?= "b2qt-${MACHINE}"
> DL_DIR ?= "${TOPDIR}/../downloads"
> SSTATE_DIR ?= "${TOPDIR}/../sstate-cache"
> DISTRO ?= "b2qt"
> PACKAGE_CLASSES ?= "package_ipk"
> EXTRA_IMAGE_FEATURES = "debug-tweaks"
> USER_CLASSES ?= "buildstats image-mklibs"
> PATCHRESOLVE = "noop"
> BB_DISKMON_DIRS = "\
> STOPTASKS,${TMPDIR},1G,100K \
> STOPTASKS,${DL_DIR},1G,100K \
> STOPTASKS,${SSTATE_DIR},1G,100K \
> ABORT,${TMPDIR},100M,1K \
> ABORT,${DL_DIR},100M,1K \
> ABORT,${SSTATE_DIR},100M,1K"
> CONF_VERSION = "1"
> INHERIT += "image-buildinfo"
> INHERIT += "internal-build"
> ACCEPT_FSL_EULA = "1"
> LICENSE_FLAGS_WHITELIST = "commercial"
> QT_SDK_PATH = ""
> PRSERV_HOST = "localhost:0"
> include conf/distro/include/${MACHINE}.pre.inc
> INHERIT+="toaster buildhistory"
> BUILDHISTORY_COMMIT = "1"
> -
> 
> My image.bb file does provider "package-management":
> -
> IMAGE_FEATURES += "\
> package-management \
> ssh-server-dropbear \
> tools-debug \
> tools-profile \
> debug-tweaks \
> hwcodecs \
> "
> -
> (opkg is working on the embedded device)
> 
> Output after building an image:
> -
> BB_VERSION   = "1.42.0"
> BUILD_SYS= "x86_64-linux"
> NATIVELSBSTRING  = "universal"
> TARGET_SYS   = "arm-poky-linux-gnueabi"
> MACHINE  = "apalis-imx6"
> DISTRO   = "b2qt"
> DISTRO_VERSION   = "2.7.3"
> TUNE_FEATURES= "arm vfp cortexa9 neon thumb callconvention-hard"
> TARGET_FPU   = "hard"
> SDKMACHINE   = "x86_64"
> -
> 
> A appreciate any help.
> 
> Mit freundlichen Grüßen / Best regards,
> Kevin Kettinger

> 

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#49585): https://lists.yoctoproject.org/g/yocto/message/49585
Mute This Topic: https://lists.yoctoproject.org/mt/74688030/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] overwrite LAYERSERIES_COMPAT_ for different layer

[Denys Dmytriyenko]

On Mon, May 25, 2020 at 03:28:52PM +0200, Quentin Schulz wrote:
> On Mon, May 25, 2020 at 03:10:39PM +0200, Martin Jansa wrote:
> > You can add a layer which will set LAYERSERIES_COMPAT for another layer,
> > but it needs to be parsed before the layer you want to change, e.g.:
> > https://github.com/webosose/meta-webosose/blob/thud/meta-qt5-compat/conf/layer.conf
> > it's useful to use this layer also to implement whatever modifications are
> > needed to make the layer to be actually compatible with the release you're
> > using, like:
> > https://github.com/webOS-ports/meta-webos-ports/tree/zeus/meta-qt5-compat
> > 
> 
> FWIW, you could make the parsing order not matter (at least in thud,
> from a quick look, master as well). LAYERSERIES_COMPAT is resolved after
> all layer.conf have been parsed[1]. I do not know if it's on purpose or
> not, meaning it could well disappear in the near future.
> 
> So you could override it from anywhere by using __append but it has to
> be done before or during the conf/layer.conf parsing. This also makes it
> future proof wrt layer priorities and how LAYERSERIES_COMPAT is set (+=,
> =, ?= ?).
> 
> I personally have it in conf/bblayers.conf (for some reason we "ship"
> this one, though it's not best practice IIRC).

Also not recommended, you can put this in your conf/bblayers.conf:

OVERRIDES = "iamgroot"
LAYERSERIES_COMPAT_browser-layer_iamgroot = "zeus"

-- 
Denys
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#49511): https://lists.yoctoproject.org/g/yocto/message/49511
Mute This Topic: https://lists.yoctoproject.org/mt/74454321/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] Is http://downloads.yoctoproject.org/ down?

[Denys Dmytriyenko]

On Tue, May 12, 2020 at 02:03:07PM +0100, Paul Barker wrote:
> On Tue, 12 May 2020 at 13:36, Zwicker Severin
>  wrote:
> >
> > I can’t reach http://downloads.yoctoproject.org/ to download 
> > http://downloads.yoctoproject.org/releases/uninative/2.7/x86_64-nativesdk-libc.tar.xz
> >  .
> >
> >
> >
> > Did somebody know anything?
> 
> Yes, it currently appears to be down. The relevant folks will be
> looking at it but it's still early in the US timezones.

Could it be Europe-specific problem?
Seems slow, but still working here in the US:

$ wget 
http://downloads.yoctoproject.org/releases/uninative/2.7/x86_64-nativesdk-libc.tar.xz
--2020-05-12 09:08:15--  
http://downloads.yoctoproject.org/releases/uninative/2.7/x86_64-nativesdk-libc.tar.xz
Resolving downloads.yoctoproject.org... 198.145.29.63
Connecting to downloads.yoctoproject.org|198.145.29.63|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 5450224 (5.2M) [application/octet-stream]
Saving to: ‘x86_64-nativesdk-libc.tar.xz’

x86_64-nativesdk-libc.tar.xz   
100%[==>]
   5.20M   540KB/sin 59s 

2020-05-12 09:09:27 (89.5 KB/s) - ‘x86_64-nativesdk-libc.tar.xz’ saved 
[5450224/5450224]
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#49374): https://lists.yoctoproject.org/g/yocto/message/49374
Mute This Topic: https://lists.yoctoproject.org/mt/74157229/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] short form for unpacking recursively into WORKDIR?

[Denys Dmytriyenko]

https://lists.yoctoproject.org/g/yocto/topic/73258946


On Sat, May 02, 2020 at 11:55:59AM -0400, Robert P. J. Day wrote:
> 
>   was playing with shadow and PAM stuff, and noticed this in
> shadow.inc:
> 
> # Additional Policy files for PAM
> PAM_SRC_URI = "file://pam.d/chfn \
>file://pam.d/chpasswd \
>file://pam.d/chsh \
>file://pam.d/login \
>file://pam.d/newusers \
>file://pam.d/passwd \
>file://pam.d/su"
> 
> which results in that pam.d/ directory (and the identified files)
> being copied into pam.d/ in WORKDIR. but since the above is the entire
> contents of that directory under files/, i wondered if one could just
> refer to the directory alone and it would unpack recursively, and it
> seems to work fine using:
> 
>   PAM_SRC_URI = "file://pam.d/"
> 
> i'd never noticed that before, and am not sure if that's actually
> mentioned in the docs (is it?). in any event, if the above shortcut is
> officially supported, is there a reason to spell it out in full anyway
> as is done in shadow.inc? (i mean, other than to be selective and
> cherry-pick what you want unpacked.)
> 
> rday

> 

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#49309): https://lists.yoctoproject.org/g/yocto/message/49309
Mute This Topic: https://lists.yoctoproject.org/mt/73937683/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: 
https://lists.yoctoproject.org/g/yocto/leave/6691583/737036229/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto][PATCH] openssl: Fix dependency loop with PACKAGECONFIG cryptodev-linux

[Denys Dmytriyenko]

On Thu, Apr 30, 2020 at 08:23:11PM +, Scott Ellis wrote:

Hi, Scott,

Sorry, I'm not trying to discourage you from submitting patches, but there are 
few issues with your patch here - see below and inline.

First of all, patches for OE-core should be sent to:
openembedded-c...@lists.openembedded.org
https://lists.openembedded.org/g/openembedded-core

Looks like you are building poky-zeus - Poky, as a distro, is composed from 
multiple components/layers, such as bitbake, oe-core/meta, meta-poky and 
meta-yocto-bsp. Most of them have own git repos with corresponding mailing 
lists - usually mentioned in corresponding README files, please check those.


> Applies to both zeus and dunfell

The process to get your change backported to older branches/releases is to 
submit it against master, and once accepted, re-send and ask to backport to 
other branches, such as zeus and dunfell with the name of the branch in the 
subject. That is because different branches/versions are usually maintained 
by different people.


> ERROR: Nothing RPROVIDES 'cryptodev-module-native' (but 
> virtual:native:/home/scott/poky-zeus/meta/recipes-connectivity/openssl/openssl_1.1.1f.bb
>  RDEPENDS on or otherwise requires it)
> ERROR: Required build target 'openssl' has no buildable providers.
> Missing or unbuildable dependency chain was: ['openssl', 'rpm-native', 
> 'python3-native', 'openssl-native', 'cryptodev-module-native']

Not sure how you were able to set the wrong PACKAGECONFIG for openssl-native, 
when it gets explicitly emptied in the recipe below.


> diff --git a/meta/recipes-connectivity/openssl/openssl_1.1.1f.bb 
> b/meta/recipes-connectivity/openssl/openssl_1.1.1f.bb
> index aa4ef6f48a..a952fae728 100644
> --- a/meta/recipes-connectivity/openssl/openssl_1.1.1f.bb
> +++ b/meta/recipes-connectivity/openssl/openssl_1.1.1f.bb
> @@ -32,7 +32,7 @@ PACKAGECONFIG ?= ""
>  PACKAGECONFIG_class-native = ""
>  PACKAGECONFIG_class-nativesdk = ""

Here, ^^^ PACKAGECONFIG should all be empty for native and nativesdk versions 
of openssl.


> -PACKAGECONFIG[cryptodev-linux] = 
> "enable-devcryptoeng,disable-devcryptoeng,cryptodev-linux,,cryptodev-module"
> +PACKAGECONFIG[cryptodev-linux] = 
> "enable-devcryptoeng,disable-devcryptoeng,cryptodev-linux"

This is not a fix, but rather a workaround for a bad setup. Moreover, it 
actually reverts my recent fix to RDEPENDS on cryptodev-module, which is 
needed to properly support devcryptoeng in openssl.

Maybe if you share with us how you set your environment, we would be able to 
help you resolve it properly. Thank you!

-- 
Denys


>  B = "${WORKDIR}/build"
>  do_configure[cleandirs] = "${B}"
> -- 
> 2.17.1
> 

> 

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#49290): https://lists.yoctoproject.org/g/yocto/message/49290
Mute This Topic: https://lists.yoctoproject.org/mt/73384166/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: 
https://lists.yoctoproject.org/g/yocto/leave/6691583/737036229/xyzzy  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] FYI: Why people are using #hashtags in yocto email subjects.

[Denys Dmytriyenko]

I doubt people that actually send emails to the list use #hashtags.

But the new list server provides this posting feature for anyone to address 
the list and requests poster to add #hashtags - very annoying, indeed:

https://lists.yoctoproject.org/g/yocto/post

-- 
Denys


On Thu, Apr 16, 2020 at 03:18:34PM -0400, Randy MacLeod wrote:
> FYI:
> 
> I don't know if I missed the memo/tweet about the email archive feature
> but I just noticed that the new archive site will index emails
> by hashtag:
> 
>https://lists.yoctoproject.org/g/yocto
> 
>https://lists.yoctoproject.org/g/yocto/hashtags
> 
> I thought it was an annoying new behaviour coming from Twitter users
> but now I understand why there are hashtags on my lawn^Hsubject lines.
> 
> ;-)
> 
> -- 
> # Randy MacLeod
> # Wind River Linux

> 

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#49171): https://lists.yoctoproject.org/g/yocto/message/49171
Mute This Topic: https://lists.yoctoproject.org/mt/73062105/21656
Mute #hashtags: https://lists.yoctoproject.org/mk?hashtag=hashtags&subid=6691583
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [yocto] menuconf u-boot

[Denys Dmytriyenko]

On Fri, Mar 13, 2020 at 07:07:34PM +0100, Andrey Zhizhikin wrote:
> JH,
> 
> Please refer to my replies to Denys, cross-posting to unrelated lists
> is generally not a good idea.
> 
> On Fri, Mar 13, 2020 at 5:40 PM Denys Dmytriyenko  wrote:
> >
> > What's u-boot-imx?
> 
> This is U-Boot fork for NXP devices (former Freescale),

This was a rhetorical question - no answer was required.


> which is not maintained by OE-Core.

Exactly my point.


> > It's definitely not in openembedded-core, so there's no reason to cross-post
> > there.
> >
> > If google doesn't help, it's recommended to post such specific questions to
> > the corresponding mailing list for the layer this recipe comes from.
> 
> The correct mailing list would be meta-freesc...@yoctoproject.org and
> JH already had some questions posted there.
> 
> >
> > If it's not clear where the recipe comes from, Layer Index can help:
> > https://layers.openembedded.org/
> >
> > Thanks.
> >
> > --
> > Denys
> >
> >
> > On Fri, Mar 13, 2020 at 08:15:17PM +1100, JH wrote:
> > > Hi,
> > >
> > > I tried to run bitbake -c menuconfig u-boot, it popped up a terminal
> > > u-boot-imx configuration:
> 
> It is not clear which yocto branch/machine you're trying to build
> here. If you provide more details - then there is a bigger chance that
> people would step in to assist you.
> 
> > >
> > > make: *** No rule make target 'menuconfig'. Stop.
> > > Command failed.
> > > Press any key to continue...
> > >
> > > How can I  run menuconfig u-boot?
> 
> I've tried it now on the [master] branch of yocto for imx8mmevk
> machine - it is building OK and I have the menuconfig from u-boot-imx.
> Hence, please refer to my point above regarding more pre-information
> on the issue.
> 
> > >
> > > Thank you.
> > >
> > > Kind regards,
> > >
> > > - jh
> >
> > > 
> >
> > --
> > ___
> > Openembedded-core mailing list
> > openembedded-c...@lists.openembedded.org
> > http://lists.openembedded.org/mailman/listinfo/openembedded-core
> 
> 
> 
> -- 
> Regards,
> Andrey.
> 
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#48757): https://lists.yoctoproject.org/g/yocto/message/48757
Mute This Topic: https://lists.yoctoproject.org/mt/71932572/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] menuconf u-boot

[Denys Dmytriyenko]

What's u-boot-imx?

It's definitely not in openembedded-core, so there's no reason to cross-post 
there.

If google doesn't help, it's recommended to post such specific questions to 
the corresponding mailing list for the layer this recipe comes from.

If it's not clear where the recipe comes from, Layer Index can help:
https://layers.openembedded.org/

Thanks.

-- 
Denys


On Fri, Mar 13, 2020 at 08:15:17PM +1100, JH wrote:
> Hi,
> 
> I tried to run bitbake -c menuconfig u-boot, it popped up a terminal
> u-boot-imx configuration:
> 
> make: *** No rule make target 'menuconfig'. Stop.
> Command failed.
> Press any key to continue...
> 
> How can I  run menuconfig u-boot?
> 
> Thank you.
> 
> Kind regards,
> 
> - jh

> 

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#48754): https://lists.yoctoproject.org/g/yocto/message/48754
Mute This Topic: https://lists.yoctoproject.org/mt/71921973/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] git fetcher: does not execute git fetch --tags or similar when HEAD has not changed

[Denys Dmytriyenko]

Why not use SRCREV?
Also, bitbake has its own mailing list.

Denys


On Thu, Mar 12, 2020 at 02:55:59PM +0100, Matthias Schoepfer via 
Lists.Yoctoproject.Org wrote:
> Hi!
> 
> We have noticed the following issue: We keep the versions of out
> software by means of tags on the git repositories, i.e. during the
> build, somethings like git describe --tags gets called. In yocto,
> our recipe of SomeLibrary might look then similar to this:
> 
> SRC_URI = "git://our.private.gitserver.org/git/SomeLibrary.git;tags=v${PV}"
> 
> When we build the image, and *then* apply a tag to HEAD, that was
> already built before, it seems like the tags are not fetched (my
> guess is git fetcher sees that origins HEAD and local HEAD have the
> same hash and is fine with it).
> 
> The error is, that while the correct version is built, it will
> report itself with a wrong version.
> 
> Is this a bug?
> 
> Regards,
> 
>   Matthias
> 
> -- 
> Dr.-Ing. Matthias Schöpfer
> matthias.schoep...@googlemail.com

> 

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#48753): https://lists.yoctoproject.org/g/yocto/message/48753
Mute This Topic: https://lists.yoctoproject.org/mt/71902370/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] Getting kernel patch to work

[Denys Dmytriyenko]

${} and not $()

On Wed, Mar 11, 2020 at 11:43:36PM +, Greg Wilson-Lindberg wrote:
> Hi Anders,
> 
> Good catch, thanks for seeing that.
> 
> 
> I also realized that I was missing a FILESEXTRAPATHS_prepend. I have tried 
> both:
> 
> FILESEXTRAPATHS_prepend := "$(FILE_DIRNAME)/files:"
> and
> FILESEXTRAPATHS_prepend := "$(THISDIR)/files:"
> 
> In both cases I don't see the expansion (i.e. I see '$(FILE_DIRNAME)/files:' 
> or '$(THISDIR)/files:') in the list of searched directories. I would think 
> that I should see the expanded directory path.
> 
> Here is the net beginning of my .bbappend file:
> 
> # additions to Kernel configuration
> 
> FILESEXTRAPATHS_prepend := "$(FILE_DIRNAME)/files:"
> #FILESEXTRAPATHS_prepend := "$(THISDIR)/files:"
> SRC_URI+= "file://0001-drm-vc4-Keep-the-binner-BO-through-suspend.patch"
> 
> 
> Regards,
> Greg
> 
> 
> 
> From: yocto@lists.yoctoproject.org  on behalf 
> of Anders Montonen 
> Sent: Tuesday, March 10, 2020 11:07:33 PM
> To: Yocto list discussion
> Subject: Re: [yocto] Getting kernel patch to work
> 
> Hi,
> 
> > On 11 Mar 2020, at 1:57, Greg Wilson-Lindberg  wrote:
> >
> > SRC_URi += 
> > "file://0001-drm-vc4-Keep-the-binner-BO-through-suspend-GWL.patch"
> 
> It looks like you have a typo here, the last letter of SRC_URI isn't 
> capitalized.
> 
> -a
> 

> 

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#48745): https://lists.yoctoproject.org/g/yocto/message/48745
Mute This Topic: https://lists.yoctoproject.org/mt/71869060/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] [meta-security][PATCH] libseccomp: update to 2.4.3

[Denys Dmytriyenko]

On Sat, Mar 07, 2020 at 08:38:49PM +, akuster wrote:
> dropped patch now included in update

Do you want to remove the patch?


> Signed-off-by: Armin Kuster 
> ---
>  .../libseccomp/{libseccomp_2.4.2.bb => libseccomp_2.4.3.bb}| 3 +--
>  1 file changed, 1 insertion(+), 2 deletions(-)
>  rename recipes-security/libseccomp/{libseccomp_2.4.2.bb => 
> libseccomp_2.4.3.bb} (90%)
> 
> diff --git a/recipes-security/libseccomp/libseccomp_2.4.2.bb 
> b/recipes-security/libseccomp/libseccomp_2.4.3.bb
> similarity index 90%
> rename from recipes-security/libseccomp/libseccomp_2.4.2.bb
> rename to recipes-security/libseccomp/libseccomp_2.4.3.bb
> index 07db82a..9ca41e6 100644
> --- a/recipes-security/libseccomp/libseccomp_2.4.2.bb
> +++ b/recipes-security/libseccomp/libseccomp_2.4.3.bb
> @@ -4,10 +4,9 @@ SECTION = "security"
>  LICENSE = "LGPL-2.1"
>  LIC_FILES_CHKSUM = 
> "file://LICENSE;beginline=0;endline=1;md5=8eac08d22113880357ceb8e7c37f989f"
>  
> -SRCREV = "1b6cfd1fc0b7499a28c24299a93a80bd18619563"
> +SRCREV = "1dde9d94e0848e12da20602ca38032b91d521427"
>  
>  SRC_URI = "git://github.com/seccomp/libseccomp.git;branch=release-2.4 \
> -   
> file://0001-tests-rely-on-__SNR_xxx-instead-of-__NR_xxx-for-sysc.patch \
> file://run-ptest \
>  "
>  
> -- 
> 2.17.1
> 

> 

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#48711): https://lists.yoctoproject.org/g/yocto/message/48711
Mute This Topic: https://lists.yoctoproject.org/mt/71802598/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] [PATCH] gcc-cross-canadian: Enable wildcard expansion support

[Denys Dmytriyenko]

On Mon, Mar 02, 2020 at 04:27:05PM -0600, Mark Hatle wrote:
> 
> 
> On 3/2/20 12:42 PM, Khem Raj wrote:
> > 
> > 
> > On 3/2/20 9:39 AM, Mark Hatle wrote:
> >> In gcc 8, the behavior of GCC changed and expansion of wild cards to calls
> >> of gcc were disabled by default.  This behavior may be required by some
> >> (poorly written) makefiles.
> >>
> >> This will allow someone to do:
> >>
> >> gcc *.c -o myoutput
> >>
> >> Signed-off-by: Mark Hatle 
> >> ---
> >>   recipes-devtools/gcc/gcc-cross-canadian_%.bbappend | 2 +-
> >>   1 file changed, 1 insertion(+), 1 deletion(-)
> >>
> >> diff --git a/recipes-devtools/gcc/gcc-cross-canadian_%.bbappend 
> >> b/recipes-devtools/gcc/gcc-cross-canadian_%.bbappend
> >> index 9c0d828..e0463c6 100644
> >> --- a/recipes-devtools/gcc/gcc-cross-canadian_%.bbappend
> >> +++ b/recipes-devtools/gcc/gcc-cross-canadian_%.bbappend
> >> @@ -1,5 +1,5 @@
> >>   INSANE_SKIP_${PN}_append_sdkmingw32 = " staticdev"
> >> -EXTRA_OECONF_append_sdkmingw32 = " --disable-nls"
> >> +EXTRA_OECONF_append_sdkmingw32 = " --disable-nls --enable-mingw-wildcard"
> > 
> > this change is fine. is this the only place we need it ?
> 
> Yes, it doesn't do anything if the generated toolchain isn't mingw.. and 
> AFAIK,

Where does this bbappend go? Should this patch be designated to mingw layer?


> we're only build cross-canadian there.
> 
> (binutils and others don't appear to have this option, unless I just missed 
> it.)
> 
> --Mark
> 
> >>   LDFLAGS_append_sdkmingw32 = " -Wl,-static"
> >>   EXEEXT_sdkmingw32 = ".exe"
> >>   ELFUTILS_sdkmingw32 = ""
> >>
> >>
> >>
> >>
> >>
> >> 

> 

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#48659): https://lists.yoctoproject.org/g/yocto/message/48659
Mute This Topic: https://lists.yoctoproject.org/mt/71680380/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] Using "latest git" versions of recipes

[Denys Dmytriyenko]

On Tue, Feb 25, 2020 at 02:39:28PM -0600, Joshua Watt wrote:
> On Tue, Feb 25, 2020 at 1:32 PM Joel A Cohen  wrote:
> >
> >
> >
> > On Tue, Feb 25, 2020 at 2:28 PM Martin Jansa  wrote:
> >>
> >> On Tue, Feb 25, 2020 at 02:10:15PM -0500, Joel A Cohen wrote:
> >>
> >>
> >> > PV_pn-recipe1 = "1.0.1+git${SRCPV}"  # I'm not sure if this would 
> >> > actually
> >> > work?
> >>
> >> Yes, this is how SRCPV is supposed to be used, but you can have this in
> >> the normal recipe without the override.
> >
> >
> > Everything else you said makes sense to me, but why would I want to append 
> > "+git${SRCPV}" to the actual recipe? Surely I only want to append the git 
> > suffix stuff if I'm using a "latest" version, and I want the PV to be set 
> > by the filename in the default case?
> 
> You should checkout devupstream.bbclass
> (https://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html#ref-classes-devupstream)
> which allows you to do this inside a single recipe (or bbappend and
> existing recipe). You can also combine this with ${AUTOREV} in a
> common include file. I recently fixed this exact same problem with
> this combination in meta-webkit; see
> https://github.com/Igalia/meta-webkit/pull/136

Ah, nice touch with devupstream class and I see bleeding.inc concept lives on! 
:)

-- 
Denys
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#48607): https://lists.yoctoproject.org/g/yocto/message/48607
Mute This Topic: https://lists.yoctoproject.org/mt/71538656/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] Using "latest git" versions of recipes

[Denys Dmytriyenko]

On Tue, Feb 25, 2020 at 01:21:53PM -0500, Joel A Cohen wrote:
> Hi all,
> 
> What I've done for quite a while when creating recipes for code that is
> under heavy development is create 2 version of the recipe.
> 
> 1) recipe_1.0.0.bb (a known-stable recipe)
> 
> 2) recipe_git.bb (which contains something like:
> SRCREV="${AUTOREV}"
> SRCPV="1.0.1+git${SRCPV}"
> DEFAULT_PREFERENCE = "-1"
> 
> 
> The major problem I have with this, is that it defeats BB_NO_NETWORK, even
> if I'm not using the git version of the recipe (because bitbake wants to go
> check what the latest version is of the recipe during parsing).
> 
> I'm currently experimenting with a different approapch, which seems to have
> several advantages. I wanted to share it and get commentary.
> 
> 1) Add a new class, "use-git.bbclass":
> # This allows using the latest version of the source without requiring a
> separate
> # "recipe_git.bb". To use:
> # 1) Add: INHERIT += "use-git"
> # 2) Add: GIT_PNS = "recipe1 recipe2 etc"
> 
> GIT_PNS ?= ""
> GIT_PNS[type] = "list"
> 
> python () {
> pn = d.getVar('PN')
> git_pns = d.getVar('GIT_PNS', [])
> 
> if pn in git_pns:
> d.setVar('SRCREV', d.getVar('AUTOREV'))
> srcpv = d.getVar('SRCPV')
> d.appendVar('PV', '+git' + srcpv)
> bb.note('Using latest git source code for %s, as recipe %s' % (pn,
> d.getVar('BP')))
> }
> 
> 
> 
> 2) In local.conf:
> INHERIT += "use-git"
> GIT_PNS = "recipe1 recipe2 etc"
> 
> 
> 
> This is nice, because I no longer have to create those recipe_git.bb
> recipes, and it's a central place to go configure a "use latest source
> code" setting.
> 
> Is this interesting to anyone else?
> 
> --Aaron

You know that you can poke SRCREV and other vars from a config file, 
such as local.conf?

SRCREV_pn-recipe1 = "${AUTOREV}"
SRCREV_pn-recipe2 = "${AUTOREV}"

-- 
Denys
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#48600): https://lists.yoctoproject.org/g/yocto/message/48600
Mute This Topic: https://lists.yoctoproject.org/mt/71538656/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] [PATCH] dev-manual: phrase should read "inherit packagegroup"

[Denys Dmytriyenko]

On Sun, Feb 16, 2020 at 07:43:31AM -0500, rpj...@crashcourse.ca wrote:
> On Sun, 16 Feb 2020, Peter Kjellerstedt wrote:
> 
> > Wrong mailing list. Changes to (and discussions about) the
> > documentation should go to d...@lists.yoctoproject.org since the end
> > of January.
> 
>   ah, i was unaware of that list, my apologies.

https://lists.yoctoproject.org/g/yocto/message/48362
https://lists.yoctoproject.org/g/yocto/message/48392
https://lists.yoctoproject.org/g/yocto/message/48439


> rday

> 

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#48442): https://lists.yoctoproject.org/g/yocto/message/48442
Mute This Topic: https://lists.yoctoproject.org/mt/71272710/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] how to remove a package from image

[Denys Dmytriyenko]

On Tue, Feb 11, 2020 at 06:50:09PM -0500, Kent Dorfman wrote:
> was able to modify the vendor's machine/inc file to remove the
> offending package.
> Since the whole tree is in git now, I suppose that's OK, but I do wish
> yocto had better tools for managing inclusions and introspection into
> what is in an image and at what level it's defined.

Images are supposed to be all custom. It means if you cannot easily use one of 
the existing images, you create your own. There are ways to bbappend an 
existing image and mangle its content, but it's usually not worth the trouble 
when you can simply create your own.

-- 
Denys


> On 2/11/20, Alexander Kanavin  wrote:
> > You need to modify the image recipe so that those packagegroups are not
> > pulled in. If you cannot do that because it's in a layer controlled by
> > someone else etc, then make a new image recipe, and build that image
> > instead.
> >
> > Alex
> >
> > On Tue, 11 Feb 2020 at 18:05, Kent Dorfman 
> > wrote:
> >
> >> My vendor finally realized that I needed a full yocto release and not
> >> the eSDK.  Anyway, I can build their image, but when I modify the
> >> kernel to remove CAN drivers I get the errors that
> >>
> >> packagegroup-can-support
> >> packagegroup-ow-support
> >>
> >> are required.
> >>
> >> What is the "yocto way"  to remove those packages and dependencies
> >> from the build?
> >> 
> >>
> >

> 

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#48364): https://lists.yoctoproject.org/g/yocto/message/48364
Mute This Topic: https://lists.yoctoproject.org/mt/71172039/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] [meta-security][PATCH] tpm2-tools: update to 4.1.1

[Denys Dmytriyenko]

format-patch -M?

On Fri, Feb 07, 2020 at 08:47:52AM -0800, akuster wrote:
> Signed-off-by: Armin Kuster 
> ---
>  .../recipes-tpm2/tpm2-tools/tpm2-tools_4.0.1.bb | 14 --
>  .../recipes-tpm2/tpm2-tools/tpm2-tools_4.1.1.bb | 17 +
>  2 files changed, 17 insertions(+), 14 deletions(-)
>  delete mode 100644 meta-tpm/recipes-tpm2/tpm2-tools/tpm2-tools_4.0.1.bb
>  create mode 100644 meta-tpm/recipes-tpm2/tpm2-tools/tpm2-tools_4.1.1.bb
> 
> diff --git a/meta-tpm/recipes-tpm2/tpm2-tools/tpm2-tools_4.0.1.bb 
> b/meta-tpm/recipes-tpm2/tpm2-tools/tpm2-tools_4.0.1.bb
> deleted file mode 100644
> index 8f94972..000
> --- a/meta-tpm/recipes-tpm2/tpm2-tools/tpm2-tools_4.0.1.bb
> +++ /dev/null
> @@ -1,14 +0,0 @@
> -SUMMARY = "Tools for TPM2."
> -DESCRIPTION = "tpm2-tools"
> -LICENSE = "BSD"
> -LIC_FILES_CHKSUM = "file://LICENSE;md5=0eb1216e46938bd723098d93a23c3bcc"
> -SECTION = "tpm"
> -
> -DEPENDS = "tpm2-abrmd tpm2-tss openssl curl autoconf-archive"
> -
> -SRC_URI = 
> "https://github.com/tpm2-software/${BPN}/releases/download/${PV}/${BPN}-${PV}.tar.gz";
> -
> -SRC_URI[md5sum] = "071aa40bc8721700ea4ed19cc2fdeabf"
> -SRC_URI[sha256sum] = 
> "ccec3fca6370341a102c5c2ef1ddb4e5cd242bf1bbc6c51d969f77fc78ca67d1"
> -
> -inherit autotools pkgconfig bash-completion
> diff --git a/meta-tpm/recipes-tpm2/tpm2-tools/tpm2-tools_4.1.1.bb 
> b/meta-tpm/recipes-tpm2/tpm2-tools/tpm2-tools_4.1.1.bb
> new file mode 100644
> index 000..e90dcfe
> --- /dev/null
> +++ b/meta-tpm/recipes-tpm2/tpm2-tools/tpm2-tools_4.1.1.bb
> @@ -0,0 +1,17 @@
> +SUMMARY = "Tools for TPM2."
> +DESCRIPTION = "tpm2-tools"
> +LICENSE = "BSD"
> +LIC_FILES_CHKSUM = "file://LICENSE;md5=0eb1216e46938bd723098d93a23c3bcc"
> +SECTION = "tpm"
> +
> +DEPENDS = "tpm2-abrmd tpm2-tss openssl curl autoconf-archive"
> +
> +SRC_URI = 
> "https://github.com/tpm2-software/${BPN}/releases/download/${PV}/${BPN}-${PV}.tar.gz";
> +
> +SRC_URI[md5sum] = "701ae9e8c8cbdd37d89c8ad774f55395"
> +SRC_URI[sha256sum] = 
> "40b9263d8b949bd2bc03a3cd60fa242e27116727467f9bbdd0b5f2539a25a7b1"
> +SRC_URI[sha1sum] = "d097d321237983435f05c974533ad90e6f20acef"
> +SRC_URI[sha384sum] = 
> "396547f400e4f5626d7741d77ec543f312d94e6697899f4c36260d15fab3f4f971ad2c0487e6eaa2d60256f3cf68f85f"
> +SRC_URI[sha512sum] = 
> "25952cf947f0acd16b1a8dbd3ac8573bce85ff970a7e24c290c4f9cd29418e77a3e48ac82c932fbd250887a9303ab301ff92db594c2fffaba47b873382444d26"
> +
> +inherit autotools pkgconfig bash-completion
> -- 
> 2.17.1
> 

> 

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#48304): https://lists.yoctoproject.org/g/yocto/message/48304
Mute This Topic: https://lists.yoctoproject.org/mt/71057508/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] Yocto Project Status WW04'20

[Denys Dmytriyenko]

On Mon, Feb 03, 2020 at 08:16:47AM -0800, akuster wrote:
> 
> 
> On 2/2/20 10:18 AM, Philip Balister wrote:
> > On 2/2/20 2:28 PM, Adrian Bunk wrote:
> >> On Tue, Jan 28, 2020 at 08:01:23AM -0800, Stephen Jolley wrote:
> >>> ...
> >>> * We have created a "documentation" list and a "licensing" list on the
> >>> yocto project mailing list infrastructure. We believe these topics would
> >>> benefit from dedicated discussions, the people involved usually aren't
> >>> interested in bulk email as would be found on other lists. The new lists 
> >>> can
> >>> be found at:  
> >>> https://lists.yoctoproject.org/g/licensing/join and
> >>> 
> >>> https://lists.yoctoproject.org/g/docs/join 
> >>> ...
> >> Would it be possible to also create a yocto-devel or yocto-core
> >> mailing list for discussing development of Yocto?
> >>
> >> Currently the yocto list is a mixture of core development list and forum 
> >> for newbie user questions, with no easy way to have them separate.
> > We have openembedded-architecture for this.
> >
> > http://lists.openembedded.org/mailman/listinfo/openembedded-architecture
> 
> Also openembedded-core

Also openembedded-devel

> > Philip
> >
> >> Thanks
> >> Adrian
> >>
> >>
> >>
> >>
> >>
> >> 
> 

> 

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#48262): https://lists.yoctoproject.org/g/yocto/message/48262
Mute This Topic: https://lists.yoctoproject.org/mt/70220917/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] what does DEPENDS have to do with do_build

[Denys Dmytriyenko]

On Wed, Jan 29, 2020 at 01:45:18AM +0200, Alexandru Onea wrote:
> Hello community,
> 
> I have a recipe which DEPENDS on ncurses. It is clearly a build dependency
> since do_configure cannot execute successfully without finding the ncurses
> headers. It might also be a run-time dependency but I have not specified it
> so I expect that bitbake will take no action in that direction.
> 
> When I inspect the dependency graph with
> 
> bitbake -g myrecipe -u depexp
> 
> I notice that all of a sudden, the do_build task of my recipe now depends
> on basically half of the world, including stuff that has nothing to do
> directly with either the build or the run-time dependencies of my recipe. I
> understand that those are the recursive dependencies of ncurses (my only
> build dependency), however, my understanding was that DEPENDS only puts a
> dependency between myrecipe:do_configure and ncurses:do_populate_sysroot.
> 
> What does do_build have to do with build dependencies and why is it
> necessary that my recipe now depends on the do_package_write* of all the
> recursive build dependencies?
> 
> Any help is greatly appreciated, as at the moment I am lost.

https://www.yoctoproject.org/docs/1.8/ref-manual/ref-manual.html#normal-recipe-build-tasks

8.1.1. do_build
The default task for all recipes. This task depends on all other normal tasks 
required to build a recipe.


In other words, do_build depends on do_fetch, do_unpack, do_patch, 
do_configure, 
do_compile, do_install, do_package, do_package_write*, etc. and hence it pulls 
all the dependencies required to perform all those tasks.

-- 
Denys


> Best regards,
> Alexandru Onea

> 

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#48188): https://lists.yoctoproject.org/g/yocto/message/48188
Mute This Topic: https://lists.yoctoproject.org/mt/70230570/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] ERROR: could not relocate installing toolchain SDK

[Denys Dmytriyenko]

On Tue, Jan 28, 2020 at 09:25:18AM +0100, Marco Cavallini wrote:
> Hello,
> I found a bug when installing a toolchain sdk and the installation
> path contains a dash.
> Using the default directory or a path without a dash it works.

It's not dash, it's the new path is longer than what was reserved in ELF 
headers:
> interp size = 73 and 76 is needed.

I thought there was some attempt to use chrpath or patchelf or something 
to be able to expand the ELF headers with longer paths...

Not sure what the currect status is - I've been using my own workaround 
for many years that extends the "default" toolchain location to the max 
path length and then at the end changes the install script back to the 
original default. That way all ELF headers have "interp" field pre-allocated 
to the max and the resulting SDK/toolchain can be relocated w/o issues.

-- 
Denys


> Yocto 3.0 'zeus'
> 
> $ 
> ./fslc-x11-glibc-x86_64-meta-toolchain-cortexa9t2hf-neon-koan-toolchain-3.0.sh
> FSLC X11 SDK installer version 3.0
> ==
> Enter target directory for SDK (default: /opt/fslc-x11/3.0): 
> /opt/poky/test-3.0
> You are about to install the SDK to "/opt/poky/test-3.0". Proceed [Y/n]?
> Extracting 
> SDK...done
> Setting it up...ERROR: could not relocate
> /opt/poky/test-3.0/sysroots/x86_64-fslcsdk-linux/usr/bin/llvm-mc,
> interp size = 73 and 76 is needed.
> ERROR: could not relocate
> /opt/poky/test-3.0/sysroots/x86_64-fslcsdk-linux/usr/bin/llvm-mca,
> interp size = 73 and 76 is needed.
> ERROR: could not relocate
> /opt/poky/test-3.0/sysroots/x86_64-fslcsdk-linux/usr/bin/clang-9,
> interp size = 73 and 76 is needed.
> ERROR: could not relocate
> /opt/poky/test-3.0/sysroots/x86_64-fslcsdk-linux/usr/bin/llvm-mt,
> interp size = 73 and 76 is needed.
> ...etc...
> 
> Distinti Saluti / Best Regards
> --
> Marco Cavallini | KOAN sas | Bergamo - Italia
> embedded software engineering
> https://KoanSoftware.com

> 

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#48182): https://lists.yoctoproject.org/g/yocto/message/48182
Mute This Topic: https://lists.yoctoproject.org/mt/70213997/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto][meta-rockchip][PATCH 2/4] gcc-arm-none-eabi-native: Add recipe

[Denys Dmytriyenko]

On Thu, Jan 23, 2020 at 02:14:57PM -0600, Joshua Watt wrote:
> 
> On 1/23/20 2:06 PM, Khem Raj wrote:
> >On Thu, Jan 23, 2020 at 11:59 AM Joshua Watt  wrote:
> >>
> >>On 1/23/20 1:49 PM, Khem Raj wrote:
> >>>On Thu, Jan 23, 2020 at 8:08 AM Joshua Watt  wrote:
> Adds a recipe to pull down the prebuilt GCC for compiling on Cortex-R
> and Cortex-M processors from ARM. This toolchain is required to build
> Arm Trusted Firmware for the Rockchip rk3399 SoC, since it must compile
> some firmware for the M0 coprocessor.
> 
> >>>can this use mutliconfig ?
> >>>This seems then can be avoided
> >>I'm not sure if multiconfig is applicable in this case; This is required
> >>because the same recipe (arm-trusted-firmware) requires 2 different
> >>compilers to be available; the target compiler (aarch64-poky-linux), and
> >>an arm-none-eabi-gcc compiler specifically to compile some M0 firmware
> >>that goes into ATF.
> >>
> >>Multiconfig would work (I think), if the recipe only needed one or the
> >>other, but not in this case where it needs both.
> >right, so question is if this recipe can be effectively two such recipes. If 
> >not
> >then perhaps this solution is ok or perhaps we can just use prebuilts for 
> >the M0
> 
> It *might* be possible to build it in two passes, but I'd rather not
> because its not the way the ATF is intended to be built. The code
> currently expects that it can build with the arm-none-eabi-gcc, so
> anything thing we do differently is more likely to break. Right now,
> the AFT recipe should be pretty easy to maintain; breaking it apart
> will make it quite a bit more complicated.
> 
> I'd rather have a prebuilt (for now) GCC building some firmware from
> source that download a prebuilt firmware image :)
> 
> Like I said, long term I'd like to build up the arm-none-eabi-gcc
> from gcc-cross in OE-core, I just haven't figured out the best way
> to do that yet.

Ha, this is quite familiar as well! We had these gcc-arm-none-eabi-native and 
other recipes in meta-ti for compiling different pieces for secondary cores in 
our SoCs - MCUs, DSPs, etc. That was way before multiconfig was available.

Recently I was looking into converting the old model into multiconfig - there 
was a discussion with fray last month regarding this and he posted a more 
generic proposal to oe-architecture list. I still need to get back to that 
activity - kind of got busy after the holidays...

-- 
Denys


> >>I also looked at building an additional gcc-cross recipe that explicitly
> >>targets arm-none-eabi, but the maintenance was going to be a pain unless
> >>A) the recipe lived in OE-core or B) this layer copied all of the GCC
> >>recipes. Neither of those was appealing at the moment, but I plan on
> >>revisiting it. Even when I did have it in OE-core, I had some trouble
> >>with some manifest warnings, so I'm not quite sure I was doing it correctly.
> >>
> Signed-off-by: Joshua Watt 
> ---
>    ...cc-arm-none-eabi-native_9-2019-q4-major.bb | 37 +++
>    1 file changed, 37 insertions(+)
>    create mode 100644 
>  recipes-devtools/gcc-arm-none-eabi/gcc-arm-none-eabi-native_9-2019-q4-major.bb
> 
> diff --git 
> a/recipes-devtools/gcc-arm-none-eabi/gcc-arm-none-eabi-native_9-2019-q4-major.bb
>  
> b/recipes-devtools/gcc-arm-none-eabi/gcc-arm-none-eabi-native_9-2019-q4-major.bb
> new file mode 100644
> index 000..a0c832d
> --- /dev/null
> +++ 
> b/recipes-devtools/gcc-arm-none-eabi/gcc-arm-none-eabi-native_9-2019-q4-major.bb
> @@ -0,0 +1,37 @@
> +# Copyright (C) 2019 Garmin Ltd. or its subsidaries
> +# Released under the MIT license (see COPYING.MIT for the terms)
> +
> +DESCRIPTION = "Baremetal GCC for ARM-R and ARM-M processors"
> +LICENSE = "GPL-3.0-with-GCC-exception & GPLv3"
> +
> +LIC_FILES_CHKSUM = 
> "file://share/doc/gcc-arm-none-eabi/license.txt;md5=c18349634b740b7b95f2c2159af888f5"
> +
> +PROVIDES = "virtual/arm-none-eabi-gcc"
> +
> +SRC_URI = 
> "https://developer.arm.com/-/media/Files/downloads/gnu-rm/9-2019q4/RC2.1/${BPN}-${PV}-x86_64-linux.tar.bz2";
> +
> +SRC_URI[md5sum] = "fe0029de4f4ec43cf7008944e34ff8cc"
> +SRC_URI[sha256sum] = 
> "bcd840f839d5bf49279638e9f67890b2ef3a7c9c7a9b25271e83ec4ff41d177a"
> +
> +S = "${WORKDIR}/${BPN}-${PV}"
> +
> +inherit native
> +
> +COMPATIBLE_HOST = "x86_64.*-linux"
> +
> +do_install() {
> +install -d ${D}${datadir}/arm-none-eabi/
> +cp -r ${S}/. ${D}${datadir}/arm-none-eabi/
> +
> +install -d ${D}${bindir}
> +# Symlink all executables into bindir
> +for f in ${D}${datadir}/arm-none-eabi/bin/arm-none-eabi-*; do
> +lnr $f ${D}${bindir}/$(basename $f)
> +done
> +}
> +
> +INSANE_SKIP_${PN} = "already-stripped"
> +
> +INHIBIT_SYSROOT_STRIP = "1"
> +INHIBIT_PACKAGE_STRIP = "1"
> +INHIB

Re: [yocto][meta-rockchip][PATCH v2 1/4] arm-trusted-firmware: Add recipe

[Denys Dmytriyenko]

Heh, I've been sitting on arm-trusted-firmware recipe in meta-ti for some 
time[1], wondering if I should submit it to oe-core, as it's being used more 
widely among arm64 platforms these days...

I know each SoC/platform has few customizations on top of generic ATF/TF-A, 
but we can probably have a common base in oe-core and then add our own pieces 
on top in each BSP layer.

I already had some preliminary work done in making the recipe more generic, 
but after seeing your version here, I borrowed couple things. Would you mind 
if I submit that to oe-core and we can beef it up as needed to be usable as a 
common base for differen BSPs, if accepted to oe-core?

[Though, I'm not a big fan of vanity copyright banners, but I can add your SoB 
line, if needed.]

Denys

[1] 
http://git.yoctoproject.org/cgit/cgit.cgi/meta-ti/tree/recipes-bsp/arm-trusted-firmware/arm-trusted-firmware_2.2.bb

On Thu, Jan 23, 2020 at 01:46:42PM -0600, Joshua Watt wrote:
> Adds a recipe to build Arm Trusted Firmware
> 
> Signed-off-by: Joshua Watt 
> ---
>  .../arm-trusted-firmware_2.2.bb   | 38 +++
>  1 file changed, 38 insertions(+)
>  create mode 100644 
> recipes-bsp/arm-trusted-firmware/arm-trusted-firmware_2.2.bb
> 
> diff --git a/recipes-bsp/arm-trusted-firmware/arm-trusted-firmware_2.2.bb 
> b/recipes-bsp/arm-trusted-firmware/arm-trusted-firmware_2.2.bb
> new file mode 100644
> index 000..710336a
> --- /dev/null
> +++ b/recipes-bsp/arm-trusted-firmware/arm-trusted-firmware_2.2.bb
> @@ -0,0 +1,38 @@
> +# Copyright (C) 2019 Garmin Ltd. or its subsidaries
> +# Released under the MIT license (see COPYING.MIT for the terms)
> +
> +SUMMARY = "Arm Trusted Firmware"
> +HOMEPAGE = "https://developer.trustedfirmware.org/";
> +LICENSE = "BSD-3-Clause"
> +LIC_FILES_CHKSUM = 
> "file://docs/license.rst;md5=189505435dbcdcc8caa63c46fe93fa89"
> +
> +PROVIDES = "virtual/atf"
> +
> +BRANCH = "master"
> +SRC_URI = 
> "git://git.trustedfirmware.org/TF-A/trusted-firmware-a.git;protocol=http;branch=${BRANCH}"
> +SRCREV = "a04808c16cfc126d9fe572ae7c4b5a3d39de5796"
> +
> +S = "${WORKDIR}/git"
> +B = "${WORKDIR}/build"
> +
> +inherit deploy
> +
> +ATF_SUFFIX ??= "bin"
> +
> +do_compile() {
> + unset LDFLAGS
> + unset CFLAGS
> + unset CPPFLAGS
> +
> +oe_runmake -C ${S} BUILD_BASE=${B} DEBUG=0 
> CROSS_COMPILE=${TARGET_PREFIX} \
> +PLAT=${ATF_PLATFORM} ${ATF_TARGET}
> +}
> +
> +PACKAGE_ARCH = "${MACHINE_ARCH}"
> +
> +do_deploy() {
> +install -m 644 
> ${B}/${ATF_PLATFORM}/release/${ATF_TARGET}/${ATF_TARGET}.${ATF_SUFFIX} \
> +${DEPLOYDIR}/${ATF_TARGET}.${ATF_SUFFIX}
> +}
> +addtask deploy after do_compile
> +
> -- 
> 2.24.1
> 

> 

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#48124): https://lists.yoctoproject.org/g/yocto/message/48124
Mute This Topic: https://lists.yoctoproject.org/mt/70054501/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] [RFC PATCH] python: remove Python 2 and all supporting classes

[Denys Dmytriyenko]

On Fri, Jan 17, 2020 at 09:55:55PM +0100, Andreas Müller wrote:
> On Fri, Jan 17, 2020 at 9:21 PM Denys Dmytriyenko  wrote:
> >
> > On Fri, Jan 17, 2020 at 09:15:09PM +0100, Andreas M?ller wrote:
> > > On Fri, Jan 17, 2020 at 7:35 PM Khem Raj  wrote:
> > > >
> > > > On 1/17/20 6:16 AM, Ross Burton wrote:
> > > > > Python 2 ceased being maintained on the 1st January 2020.  We've 
> > > > > already
> > > > > removed all users of it from oe-core so the final step is to move the
> > > > > recipe and supporting classes to meta-python2.
> > > > >
> > > > > The following are removed in this commit:
> > > > > - python and python-native 2.7.17
> > > > > - python-setuptools
> > > > > - The classes pythonnative, pythondir, distutils, setuptools
> > > > >
> > > >
> > > > perhaps add them to meta-py2 first before this lands
> > > Just a question: What is the plan with all those recipes which are
> > > going to fail (most headaches I have with old waf): Will meta-oe /
> > > meta-networking..., depend on meta-py2 or kick them out or?
> >
> > What, not calling it the worst patch of the year? And the year's just
> > started... :)
> Denys
> 
> 1. Would you accept an apologize for that one?

Don't worry about that, let's file it under "overreaction due to stress" 
category, shall we? :)


> 2. I did not ask for stopping this - just asked how to continue and I
> did that for certain reasons: For example: Few minutes ago we saw a
> series for npm rework on oe-core. Unfortunately npm as is requires
> python2 and many modules. Or the waf stuff: That means somebody has go
> to all the projects and ask them for waf upgrade or prepare patches
> there (and that means not just upgrading waf). So again: How do we
> handle/get rid recipes requiring python2 to build?

Yes, all good points. I would agree with Khem - let's drop it and try to 
fix as many issues as possible, while we still have time until the release. 
Distros can have own dependency on meta-python2, but meta-openembedded and 
openembedded-core should not depend on deprecated components, IMHO.

-- 
Denys
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#48046): https://lists.yoctoproject.org/g/yocto/message/48046
Mute This Topic: https://lists.yoctoproject.org/mt/69843007/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] [RFC PATCH] python: remove Python 2 and all supporting classes

[Denys Dmytriyenko]

On Fri, Jan 17, 2020 at 09:15:09PM +0100, Andreas M?ller wrote:
> On Fri, Jan 17, 2020 at 7:35 PM Khem Raj  wrote:
> >
> > On 1/17/20 6:16 AM, Ross Burton wrote:
> > > Python 2 ceased being maintained on the 1st January 2020.  We've already
> > > removed all users of it from oe-core so the final step is to move the
> > > recipe and supporting classes to meta-python2.
> > >
> > > The following are removed in this commit:
> > > - python and python-native 2.7.17
> > > - python-setuptools
> > > - The classes pythonnative, pythondir, distutils, setuptools
> > >
> >
> > perhaps add them to meta-py2 first before this lands
> Just a question: What is the plan with all those recipes which are
> going to fail (most headaches I have with old waf): Will meta-oe /
> meta-networking..., depend on meta-py2 or kick them out or?

What, not calling it the worst patch of the year? And the year's just 
started... :)
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#48014): https://lists.yoctoproject.org/g/yocto/message/48014
Mute This Topic: https://lists.yoctoproject.org/mt/69843007/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] How to dynamically set PKGV? #yocto #python

[Denys Dmytriyenko]

https://www.yoctoproject.org/docs/3.0/ref-manual/ref-manual.html#var-AUTOREV
https://www.yoctoproject.org/docs/3.0/ref-manual/ref-manual.html#var-SRCPV

-- 
Denys


On Wed, Jan 15, 2020 at 12:38:19PM -0800, bill.k...@azuresummit.com wrote:
> I have a recipe that builds an application from the master branch of a local 
> git repository.  AUTOREV is working, so the recipe automatically rebuilds 
> whenever the repository is updated.  The source code has its own version 
> number.  I'm wondering if it is possible to grab that version number during 
> the do_compile step, and set the package version based on that?
> 
> As a first step, I tried to change the value of PKGV from a bitbake task.
> 
> PKGV = "BadBad"
> python do_foo () {
> d.setVar( "PKGV" , "GoodGood" )
> print ( "PKGV set to " + d.getVar( "PKGV" ))
> }
> addtask foo after do_compile before do_package
> 
> However, this did not work - the resulting RPM packages are named 
> "my_package-BadBad-r0.noarch.rpm".  Can anyone suggest a fix, or a different 
> method?
> 
> Thanks!

> 

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#47979): https://lists.yoctoproject.org/g/yocto/message/47979
Mute This Topic: https://lists.yoctoproject.org/mt/69724867/21656
Mute #yocto: https://lists.yoctoproject.org/mk?hashtag=yocto&subid=6691583
Mute #python: https://lists.yoctoproject.org/mk?hashtag=python&subid=6691583
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] [tsc] QA Cycle report for build (yocto-3.1_M1.rc8)

[Denys Dmytriyenko via Lists.Yoctoproject.Org]

On Wed, Dec 18, 2019 at 12:46:30PM -0800, Khem Raj wrote:
> On 12/18/19 7:38 AM, Armpit wrote:
> >
> >
> >On 12/18/19 2:46 AM, Richard Purdie wrote:
> >>On Wed, 2019-12-18 at 03:32 +, Jain, Sangeeta wrote:
> >>>Hello all,
> >>>
> >>>This is the full report for 3.1_M1.rc8:
> >>>https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/tree/?h=intel-yocto-testresults
> >>>
> >>>
> >>>=== Summary 
> >>>No high milestone defects.
> >>>No new defects are found in this cycle.
> >>>glib and valgrind ptest failed (BUG id:13713).
> >
> >The Valgrind is a known issue:
> >
> >https://bugzilla.yoctoproject.org/show_bug.cgi?id=13666
> >
> >>>
> >>>=== Bugs 
> >>>https://bugzilla.yoctoproject.org/show_bug.cgi?id=13713
> >>Thanks Sangeeta.
> >>
> >>Adding TSC to CC.
> >>
> >>We have the bugs above but they're minor ptest issues (small
> >>regressions).
> >>
> >>We have performance problems in certain world build cases but we need
> >>to work through those issues in master.
> >>
> >>We also have reproducibile build issues but those are in theory fixed
> >>in master.
> >>
> >>I think we should ship this as I can't see any huge improvements from
> >>any further respins, it just collides with vactions. We should move
> >>forward to M2 after the holidays.
> >
> >I would make these blockers for M2/M3 and approve shipping M1

As long as those are being tracked and looked at later, I'm also fine with 
shipping M1.

> I would also agree to ship M1 without this.
> 
> >- armin
> >>
> >>Cheers,
> >>
> >>Richard
> >>
> >>
> >
> >
> >-=-=-=-=-=-=-=-=-=-=-=-
> >Links: You receive all messages sent to this group.
> >
> >View/Reply Online (#247): https://lists.yoctoproject.org/g/tsc/message/247
> >Mute This Topic: https://lists.yoctoproject.org/mt/68790744/1997914
> >Group Owner: tsc+ow...@lists.yoctoproject.org
> >Unsubscribe: https://lists.yoctoproject.org/g/tsc/unsub  [raj.k...@gmail.com]
> >-=-=-=-=-=-=-=-=-=-=-=-
> >
> 

> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> 
> View/Reply Online (#249): https://lists.yoctoproject.org/g/tsc/message/249
> Mute This Topic: https://lists.yoctoproject.org/mt/68790744/1051543
> Group Owner: tsc+ow...@lists.yoctoproject.org
> Unsubscribe: https://lists.yoctoproject.org/g/tsc/unsub  [de...@ti.com]
> -=-=-=-=-=-=-=-=-=-=-=-

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#47763): https://lists.yoctoproject.org/g/yocto/message/47763
Mute This Topic: https://lists.yoctoproject.org/mt/68805623/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [yocto] Missing layer in the layer index

[Denys Dmytriyenko]

On Thu, Dec 05, 2019 at 11:18:22AM +, Paul Barker wrote:
> On Thu, 5 Dec 2019, at 10:07, Paul Eggleton wrote:
> > On Thursday, 5 December 2019 9:48:48 PM NZDT Paul Barker wrote:
> > > On Thu, 5 Dec 2019, at 01:37, Paul Eggleton wrote:
> > > > On Wednesday, 4 December 2019 11:10:49 PM NZDT Nicolas Dechesne wrote:
> > > > > > I'd like to make sure meta-sancloud 
> > > > > > (https://github.com/SanCloudLtd/meta-> > sancloud) is listed in the 
> > > > > > layer index. I can't see it listed for either
> > > > > > of the branches we support (thud & rocko). However, when I try to 
> > > > > > add the
> > > > > > layer I get the error message "Layer with this Layer name already 
> > > > > > exists."
> > > > > >
> > > > > > Perhaps this was already added with an old URL. Is there any way to 
> > > > > > get
> > > > > > this fixed up?
> > > > > 
> > > > > yes, this is the reason. It exists with the following URL:
> > > > > https://bitbucket.sancloud.co.uk/scm/yb/meta-sancloud.git
> > > > > 
> > > > > The maintainer for that layer is not listed.. was it you?
> > > > 
> > > > Oddly there are no maintainer records and no layer branch records 
> > > > either, 
> > > > hence why the layer doesn't show up properly. I'm unsure how it would 
> > > > have got 
> > > > into that state or how long it's been there, but since it's pretty much 
> > > > useless I have gone ahead and deleted it - Paul, could you please file 
> > > > your 
> > > > submission again?
> > > 
> > > Thanks for that, it may have got broken in the layer index when we moved 
> > > the repo from our private Bitbucket instance over to GitHub. I've 
> > > resubmitted now.
> > 
> > Actually looking at the new repo I think I know what might have 
> > happened. The layer index does not currently handle layers that don't 
> > have a master branch perfectly; it could be that the original repo went 
> > away and that caused it to remove all the layerbranches, and since 
> > maintainers are per layerbranch they also got removed. (If a master 
> > layerbranch is there it is protected from deletion even if upstream 
> > master goes away, you just get a warning during parsing.)
> > 
> > I can understand why people don't want to have a master branch if they 
> > aren't using it; that most layers have it was an assumption I made in 
> > the earlier design. It's fixable but will take a bit of work to ensure 
> > the correct behaviour. (This assumption is also reflected in the 
> > submission process - by default a master layerbranch is created, but 
> > for layers without a master branch as the approver you then have to go 
> > in and switch the master branch to whatever the "main" branch is - I 
> > just did that for this layer.)
> 
> Ah ok. I have a pet hate of layers with a master branch that doesn't 
> actually work with master of oe-core and other layers. I'd rather see a 
> repository with no master branch!
> 
> In this case we're building with meta-ti & meta-arago which only support 
> every other release. I know they also have a master branch but it's always 
> been broken when I've tried to use it in the past. I may see if I can give 
> it another try.

FWIW, both of those have been getting some love lately to at least build 
against master, so you might want to try again. But in general, at least 
meta-arago depends on other layers and components that are always lagging 
behind and hence it's rather difficult to keep everything working with 
rapidly changing master...

-- 
Denys
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#47572): https://lists.yoctoproject.org/g/yocto/message/47572
Mute This Topic: https://lists.yoctoproject.org/mt/66429934/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-