[yocto] Failed to build kirkstone branch

2022-05-03 Thread JH 
I was able to build u-boot-imx-2021.04-r0 in honister branch, but
could not build it in kirkstone branch, here is the error message:

ERROR: u-boot-imx-2021.04-r0 do_fetch: Fetcher failure: Fetch command
export PSEUDO_DISABLED=1; export
DBUS_SESSION_BUS_ADDRESS="unix:path=/run/user/1000/bus"; export
PATH="/build/KirkstoneRam/build/tmp-glibc/work/solar-oe-linux-gnueabi/u-boot-imx/2021.04-r0/recipe-sysroot-native/usr/bin/python3-native:/build/KirkstoneRam/oe-core/scripts:/build/KirkstoneRam/build/tmp-glibc/work/solar-oe-linux-gnueabi/u-boot-imx/2021.04-r0/recipe-sysroot-native/usr/bin/arm-oe-linux-gnueabi:/build/KirkstoneRam/build/tmp-glibc/work/solar-oe-linux-gnueabi/u-boot-imx/2021.04-r0/recipe-sysroot/usr/bin/crossscripts:/build/KirkstoneRam/build/tmp-glibc/work/solar-oe-linux-gnueabi/u-boot-imx/2021.04-r0/recipe-sysroot-native/usr/sbin:/build/KirkstoneRam/build/tmp-glibc/work/solar-oe-linux-gnueabi/u-boot-imx/2021.04-r0/recipe-sysroot-native/usr/bin:/build/KirkstoneRam/build/tmp-glibc/work/solar-oe-linux-gnueabi/u-boot-imx/2021.04-r0/recipe-sysroot-native/sbin:/build/KirkstoneRam/build/tmp-glibc/work/solar-oe-linux-gnueabi/u-boot-imx/2021.04-r0/recipe-sysroot-native/bin:/build/KirkstoneRam/bitbake/bin:/build/KirkstoneRam/build/tmp-glibc/hosttools";
export HOME="/home/jupiter"; LANG=C git -c core.fsyncobjectfiles=0 -c
gc.autoDetach=false clone --bare --mirror
https://source.codeaurora.org/external/imx/uboot-imx.git
/build/KirkstoneRam/build/downloads/git2/source.codeaurora.org.external.imx.uboot-imx.git
--progress failed with exit code 128, no output
ERROR: u-boot-imx-2021.04-r0 do_fetch: Bitbake Fetcher Error:
FetchError('Unable to fetch URL from any source.',
'git://source.codeaurora.org/external/imx/uboot-imx.git;protocol=https;branch=lf_v2021.04')

But I was able to run the same command manually git -c
core.fsyncobjectfiles=0 -c gc.autoDetach=false clone --bare --mirror
https://source.codeaurora.org/external/imx/uboot-imx.git.

What could I be missing?

Thank you very much.

jupiter

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

[yocto] QA notification for completed autobuilder build (yocto-3.4.4.rc1)

2022-05-03 Thread Pokybuild User 

A build flagged for QA (yocto-3.4.4.rc1) was completed on the autobuilder and 
is available at:


https://autobuilder.yocto.io/pub/releases/yocto-3.4.4.rc1


Build hash information: 

bitbake: c2d8f9b2137bd4a98eb0f51519493131773e7517
meta-agl: 8543843eeb47fa9b45786d3e09bf497fcd5f95e0
meta-arm: 2623e69db362b357db45c343e6d504909552c2d5
meta-aws: c92344938ab4d37de8bd8b799186dbbe3019a069
meta-gplv2: f04e4369bf9dd3385165281b9fa2ed1043b0e400
meta-intel: daf5c125a744d45d8fa395b576147edd5a714f5c
meta-mingw: f5d761cbd5c957e4405c5d40b0c236d263c916a8
meta-openembedded: 9a0caf5b09e14a28a54c3f8524d97530aeb8152c
meta-virtualization: bd7511c53b921c9ce4ba2fdb42778ca194ebc3e8
oecore: 1a6f5e27249afb6fb4d47c523b62b5dd2482a69d
poky: 780eeec8851950ee6ac07a2a398ba937206bd2e4



This is an automated message from the Yocto Project Autobuilder
Git: git://git.yoctoproject.org/yocto-autobuilder2
Email: richard.pur...@linuxfoundation.org


 

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

Re: [yocto] [PATCH yocto-autobuilder-helper v12] Add a banner on the old documentation docs.

2022-05-03 Thread Abongwa Amahnui Bonalais 
Hi Quentin
On Tue, May 3, 2022 at 10:51 AM, Quentin Schulz wrote:

> 
> 
>> +
>> +
>> +
>> +def dunfell_tags(dir):
>> + dunfell_banners = []
>> + for root, dirs, filenames in os.walk(dir):
>> + dunfell_banners = [ name for name in os.listdir(dir) if not
>> name.startswith('3.1') ]
>> + for d in dirs:
>> + if d in dunfell_banners:
>> + dirs.remove(d)
>> +
>> + for filename in filenames:
>> + if filename.endswith('.html'):
>> + with open(os.path.join(root, filename), 'r', encoding="ISO-8859-1") as
>> f:
>> + current_content = f.read()
>> + with open(os.path.join(root, filename), 'w') as f:
>> + f.write(current_content.replace('', '' +
>> html_content_dunfell))
>> + f.write(current_content.replace('', last_div + ''))
>> + if filename.endswith('.css'):
>> + with open(os.path.join(root, filename), 'r', encoding="ISO-8859-1") as
>> f:
>> + css_content = f.read()
>> + with open(os.path.join(root, filename), 'w') as f:
>> + f.write(css_content.replace(css_content[css_content.find('body
>> {'):css_content.find('}'[0])], 'body {' + css_replacement_content ))
>> + print(dunfell_banners)
> 
> This is all extremely complex just for using a different variable
> depending on the name of the directory.

I wish to ask if your'e referring to the last line of code or this entire 
function, I have actuallly removed the print(dunfell_banners) line

Thanks a lot for reviewing.

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

Re: [yocto] Maintaining ABI Compatibility for LTS branch

2022-05-03 Thread Richard Purdie 
On Mon, 2022-05-02 at 17:44 -0400, Sinan Kaya wrote:
> On 2/9/2022 4:38 PM, Richard Purdie wrote:
> > This probably does need a discussion on the architecture list and we need 
> > some
> > discussion and decisions about where/what buildhistory could/should do. 
> > Adding
> > this to buildhistory is all well and good but we don't have a meaningful
> > integration/monitoring of existing buildhistory issues in our
> > autobuilder/workflow today even before adding new things.
> 
> I was hoping for free cycles. I didn't get one. This will be an intern
> project.
> 
> The way I'm thinking is to have the ABI compat XML be part of the state
> cache tgz file and come up with a CVE check kind of hook maybe called
> "ABI check" that will start flagging problems.
> 
> Would this be a better architecture?

I'm not sure it would.

Shared state works by computing inputs into a checksum and then using that
checksum to access the cache. Finding a "previous version" or a history to
compare to therefore isn't a good fit for it.

Buildhistory does fit much better but isn't scaling in a controlled way and I
think we need the architecture discussion and an agreed plan rather than trying
to tack things onto it. That does mean someone stepping back and considering the
various needs users have rather than just an isolated use case.

Cheers,

Richard



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

[yocto] meta-selinux release for kirkstone #selinux

2022-05-03 Thread jared_terry 
I'm not sure where to get a status on meta-selinux officially released branch 
with kirkstone support, I'm hoping this is the right place.  I see it has been 
added to main but is it planned to be branched anytime soon as a kirkstone 
branch?

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

[yocto] Yocto Project Status WW18`22

2022-05-03 Thread Richard Purdie 
Current Dev Position: YP 4.1 M1
Next Deadline: 30th May 2022 YP 4.1 M1 Build

Next Team Meetings:
Yocto Project Summit - 17th-19th May
(https://www.yoctoproject.org/yocto-project-summit-2022-05/)
Bug Triage meeting Thursday May 5th 7:30 am PDT
(https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
Monthly Project Meeting Tuesday May 3rd at 8 am PDT
(https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
Weekly Engineering Sync Tuesday May 10th at 8 am PDT
(https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
Twitch - See https://www.twitch.tv/theyoctojester

Key Status/Updates:
YP 4.0 was released, thanks to everyone who contributed to it!
YP 3.3.6 was released
YP 3.1.16 is due for release and has TSC approval
YP 3.4.4 is due to build this week
Master has started taking new patches but we have struggled with issues on a
number of autobuilder workers and the cluster was down on capacity as a result.
If people see intermittent issues in their own builds, particularly if they’re
the same as intermittent issues seen on the autobuilder, please do comment in
the bugs mentioning when they happen as the frequency information does help us
prioritize fixing the most common issues.
Intermittent issues continue to be at high levels and help is very much welcome
in trying to resolve them. You can see the list of failures we’re continuing to
see by searching for the “AB-INT” tag in bugzilla:
https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=AB-INT

Ways to contribute:
There are bugs identified as possible for newcomers to the project:
https://wiki.yoctoproject.org/wiki/Newcomers
There are bugs that are currently unassigned for YP 3.5. See:
https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_3.5_Unassigned_Enhancements.2FBugs
We’d welcome new maintainers for recipes in OE-Core. Please see the list at:
http://git.yoctoproject.org/cgit.cgi/poky/tree/meta/conf/distro/include/maintainers.inc
and discuss with the existing maintainer, or ask on the OE-Core mailing list. We
will likely move a chunk of these to “Unassigned” soon to help facilitate this.
Help us resolve CVE issues: CVE metrics 

YP 4.1 Milestone Dates:
YP 4.1 M1 build date 2022/05/30
YP 4.1 M1 Release date 2022/06/10
YP 4.1 M2 build date 2022/07/11
YP 4.1 M2 Release date 2022/07/22
YP 4.1 M3 build date 2022/08/22
YP 4.1 M3 Release date 2022/09/02
YP 4.1 M4 build date 2022/10/03
YP 4.1 M4 Release date 2022/10/28

Upcoming dot releases:
YP 3.3.6 is released.
YP 3.1.16 out of QA
YP 3.4.4 build date 2022/05/02
YP 3.4.4 Release date 2022/05/13
YP 4.0.1 build date 2022/05/16
YP 4.0.1 Release date 2022/05/27
YP 3.1.17 build date 2022/06/06
YP 3.1.17 Release date 2022/06/17
YP 4.0.2 build date 2022/06/27
YP 4.0.2 Release date 2022/07/08
YP 3.1.18 build date 2022/07/18
YP 3.1.18 Release date 2022/07/29
YP 4.0.3 build date 2022/08/08
YP 4.0.3 Release date 2022/08/19
YP 3.1.19 build date 2022/08/29
YP 3.1.19 Release date 2022/09/09
YP 4.0.4 build date 2022/09/19
YP 4.0.4 Release date 2022/09/30
YP 3.1.20 build date 2022/10/10
YP 3.1.20 Release date 2022/10/21
YP 4.0.5 build date 2022/10/31
YP 4.0.5 Release date 2022/11/11

Tracking Metrics:
WDD 2450 (last week 2495) (https://wiki.yoctoproject.org/charts/combo.html)
OE-Core/Poky Patch Metrics
Total patches found: 1205 (last week 1215)
Patches in the Pending State: 341 (28%) [last week 343 (28%)]

The Yocto Project’s technical governance is through its Technical Steering
Committee, more information is available at:
https://wiki.yoctoproject.org/wiki/TSC

The Status reports are now stored on the wiki at:
https://wiki.yoctoproject.org/wiki/Weekly_Status

[If anyone has suggestions for other information you’d like to see on this
weekly status update, let us know!]


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

Re: [yocto] Yocto cyrillic characters support #yocto

2022-05-03 Thread Ashutosh Naik 
On Tue, May 3, 2022 at 2:02 PM Nicolas Jeker  wrote:
> On Fri, 2022-04-29 at 06:48 -0700, Ashutosh Naik wrote:
> > For eg. If I try to create a file like :
> > # touch  1Черная
> >
> > I do get:
> >
> > # ls
> > 1??
>
> Is your file created with the wrong name or is it actually just the
> 'ls' output that doesn't support unicode characters?
>
> If you're using busybox, I think these configuration options could be
> of interest:
>
> CONFIG_UNICODE_SUPPORT
> CONFIG_LAST_SUPPORTED_WCHAR
>
> You'll find this at the bottom of "Settings -> Support Unicode" when
> using menuconfig.

I have enabled those options in Busybox to no avail.

I still cant see my files :

# touch 1Чернаяг
# ls -l 1Чернаяг
-rw-r--r--1 root root 0 May  3 13:35 1???

The file is created though and visible in bash completion and I am
able to delete the file as well.

Is this working for you on yocto ?

Regards
Ash

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

[yocto] M+ & H bugs with Milestone Movements WW18

2022-05-03 Thread Stephen Jolley 
All,

YP M+ or high bugs which moved to a new milestone in WW18 are listed below: 


Priority

Bug ID

Short Description

Changer

Owner

Was

Became


High

  14065

Automated ptest regression testing

randy.macl...@windriver.com

unassig...@yoctoproject.org

4.0 M4

4.1 M1


Medium+

  12723

mysql requires unicode and char length filtering

randy.macl...@windriver.com

david.re...@windriver.com

4.0 M4

4.1 M1


 

  12755

Separate boot config recipes are at odds with setting APPEND at the image level

randy.macl...@windriver.com

unassig...@yoctoproject.org

0.0.0

4.99


 

  13103

[Bug][QA 2.7 M1 rc1][Toaster] "Recipes" table  and  "machines" table are not 
getting populated after clicking on imported layer as well as after clicking 
Machines Tab on project page

randy.macl...@windriver.com

david.re...@windriver.com

4.0 M4

4.1 M1


 

  13226

Support out of tree modules for alternate kernels

randy.macl...@windriver.com

bruce.ashfi...@gmail.com

4.0 M4

4.1 M1


 

  13508

Meson detects googletest installed on system

randy.macl...@windriver.com

newco...@yoctoproject.org

4.0 M4

4.1 M1


 

  13566

Write tests for multiconfig files in layers and document

randy.macl...@windriver.com

richard.pur...@linuxfoundation.org

4

4.1 M1


 

  13567

Add QA check for recipes that use AUTOREV by default

randy.macl...@windriver.com

unassig...@yoctoproject.org

4

4.99


 

  13669

Move Toaster testsuite-2 away from Testopia

randy.macl...@windriver.com

unassig...@yoctoproject.org

4.0 M4

4.1 M2


 

 

 

 

4.1 M2

4.99


 

  13766

Using TCLIBC=musl results in SDKs producing incompatible binaries

randy.macl...@windriver.com

sakib.sa...@windriver.com

4.0 M4

4.1 M1


 

  13904

do_prepare_recipe_sysroot: postinst-useradd-* does not run in order of 
dependency and sometimes fails

randy.macl...@windriver.com

sakib.sa...@windriver.com

4.0 M4

4.1 M2


 

  14121

Implement sphinx switchers.js for bitbake

randy.macl...@windriver.com

nicolas.deche...@linaro.org

4.0 M4

4.1 M1


 

  14139

systemd user/groups different on opkg vs rpm images

randy.macl...@windriver.com

hongxu@windriver.com

4.0 M4

4.1 M2


 

  14339

bitbake generates zombie Parser processes (hard to reproduce)

randy.macl...@windriver.com

randy.macl...@windriver.com

4.0 M4

4.1 M2


 

  14348

Layer dependencies not updated

randy.macl...@windriver.com

unassig...@yoctoproject.org

4.0 M4

4.1 M2


 

  14357

No PDF and EPUB versions of the manuals available on the website

randy.macl...@windriver.com

michael.opdenac...@bootlin.com

4.0 M4

4.1 M1


 

  14394

Add a banner on the old documentation docs

randy.macl...@windriver.com

abongwabonal...@gmail.com

4.0 M4

4.1 M1


 

  14467

curl timeout while dnf is downloading package

randy.macl...@windriver.com

sakib.sa...@windriver.com

4.0 M4

4.1 M2


 

  14522

qemuppc doesn't shutdown within timeout (serial console issues)

randy.macl...@windriver.com

sakib.sa...@windriver.com

4.0 M4

4.1 M1


 

  14571

Add support for arm in poky-tiny

randy.macl...@windriver.com

jon.ma...@arm.com

4.0 M4

4.1 M1


 

  14640

Relocation error when setting up SDK with rust tools

randy.macl...@windriver.com

pgowda@gmail.com

4.0 M4

4.1 M2


 

  14689

Need to show activity when talking to hash equivalence servers

richard.pur...@linuxfoundation.org

unassig...@yoctoproject.org

4.1

4.1 M2


 

  14716

Add additional resolvers to autobuilder workers

randy.macl...@windriver.com

mhalst...@linuxfoundation.org

4.0 M4

4.1 M1


 

  14723

patches not applied by devtool when using overrides in SRC_URI

[yocto] Enhancements/Bugs closed WW18

2022-05-03 Thread Stephen Jolley 
All,

The below were the owners of enhancements or bugs closed during the last
week!


Who

Count


randy.macl...@windriver.com

6


ross.bur...@arm.com

2


akuster...@gmail.com

2


mhalst...@linuxfoundation.org

1


Grand Total

11

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

*Cell:(208) 244-4460

* Email:  sjolley.yp...@gmail.com
 

 


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

[yocto] Current high bug count owners for Yocto Project 4.1

2022-05-03 Thread Stephen Jolley 
All,

Below is the list as of top 39 bug owners as of the end of WW18 of who have
open medium or higher bugs and enhancements against YP 4.1.   There are 125
possible work days left until the final release candidates for YP 4.1 needs
to be released.


Who

Count


michael.opdenac...@bootlin.com

37


ross.bur...@arm.com

23


david.re...@windriver.com

21


bruce.ashfi...@gmail.com

20


randy.macl...@windriver.com

19


sakib.sa...@windriver.com

12


richard.pur...@linuxfoundation.org

10


jpewhac...@gmail.com

9


saul.w...@windriver.com

7


tim.orl...@konsulko.com

7


mhalst...@linuxfoundation.org

6


bluelightn...@bluelightning.org

5


kai.k...@windriver.com

4


chee.yang@intel.com

3


qi.c...@windriver.com

3


jon.ma...@arm.com

3


hongxu@windriver.com

3


akuster...@gmail.com

3


pgowda@gmail.com

2


abongwabonal...@gmail.com

2


alejan...@enedino.org

2


tvgamb...@gmail.com

2


martin.ja...@gmail.com

1


pokyli...@reliableembeddedsystems.com

1


jay.shen.t...@intel.com

1


st...@sakoman.com

1


nicolas.deche...@linaro.org

1


aeh...@gmail.com

1


thomas.per...@bootlin.com

1


raj.k...@gmail.com

1


open.sou...@oleksandr-kravchuk.com

1


sundeep.kokko...@gmail.com

1


martin.bee...@online.de

1


kexin@windriver.com

1


mostthings...@gmail.com

1


liezhi.y...@windriver.com

1


mark.ha...@kernel.crashing.org

1


shac...@vdoo.com

1


alexandre.bell...@bootlin.com

1


Grand Total

220

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

*Cell:(208) 244-4460

* Email:  sjolley.yp...@gmail.com
 

 


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

[yocto] Yocto Project Newcomer & Unassigned Bugs - Help Needed

2022-05-03 Thread Stephen Jolley 
All,

 

The triage team is starting to try and collect up and classify bugs which a
newcomer to the project would be able to work on in a way which means people
can find them. They're being listed on the triage page under the appropriate
heading:

https://wiki.yoctoproject.org/wiki/Bug_Triage#Newcomer_Bugs  Also please
review:
https://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded and
how to create a bugzilla account at:

https://bugzilla.yoctoproject.org/createaccount.cgi

The idea is these bugs should be straight forward for a person to help work
on who doesn't have deep experience with the project.  If anyone can help,
please take ownership of the bug and send patches!  If anyone needs
help/advice there are people on irc who can likely do so, or some of the
more experienced contributors will likely be happy to help too.

 

Also, the triage team meets weekly and does its best to handle the bugs
reported into the Bugzilla. The number of people attending that meeting has
fallen, as have the number of people available to help fix bugs. One of the
things we hear users report is they don't know how to help. We (the triage
team) are therefore going to start reporting out the currently 427
unassigned or newcomer bugs.

 

We're hoping people may be able to spare some time now and again to help out
with these.  Bugs are split into two types, "true bugs" where things don't
work as they should and "enhancements" which are features we'd want to add
to the system.  There are also roughly four different "priority" classes
right now,  "4.1", "4.2", "4.99" and "Future", the more pressing/urgent
issues being in "4.1" and then "4.2".

 

Please review this link and if a bug is something you would be able to help
with either take ownership of the bug, or send me (sjolley.yp...@gmail.com
 ) an e-mail with the bug number you would
like and I will assign it to you (please make sure you have a Bugzilla
account).  The list is at:
https://wiki.yoctoproject.org/wiki/Bug_Triage_Archive#Unassigned_or_Newcomer
_Bugs

 

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

*Cell:(208) 244-4460

* Email:  sjolley.yp...@gmail.com
 

 


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

Re: [yocto] Adding systemd to yocto

2022-05-03 Thread Scott Murray 
On Tue, 3 May 2022, Edgar Mobile wrote:

> Apparently, this is not enough:
>
> bitbake core-image-weston
> /usr/lib/python3.6/importlib/_bootstrap.py:219: ImportWarning: can't resolve 
> package from __spec__ or __package__, falling back on __name__ and __path__
>   return f(*args, **kwds)
> Loading cache: 100% || Time: 
> 0:00:00
> Loaded 1472 entries from dependency cache.
> NOTE: Resolving any missing task queue dependencies
> ERROR: Nothing RPROVIDES 'pam' (but 
> /media/user/SSD1TB/yoctoqemu/poky/meta/recipes-graphics/images/core-image-weston.bb
>  RDEPENDS on or otherwise requires it)
> NOTE: Runtime target 'pam' is unbuildable, removing...
> Missing or unbuildable dependency chain was: ['pam']
> ERROR: Required build target 'core-image-weston' has no buildable providers.
> Missing or unbuildable dependency chain was: ['core-image-weston', 'pam']
>
> These are my current additions to local.conf:
>
> INIT_MANAGER="systemd"
> CORE_IMAGE_EXTRA_INSTALL += " mesa-demos gdb"
> IMAGE_INSTALL:append += " pam"

^ This line what is causing your error, remove it.  With pam in
DISTRO_FEATURES the required packages will get pulled in via dependencies.

> DISTRO_FEATURES:append = " systemd wayland pam x11"

If you specify INIT_MANAGER = "systemd", then you do not need to add
systemd here.

> VIRTUAL-RUNTIME_init_manager = "systemd"
> DISTRO_FEATURES_BACKFILL_CONSIDERED = "sysvinit"
> VIRTUAL-RUNTIME_initscripts = ""

Similarly, with INIT_MANAGER = "systemd" these 3 lines are not required.
If you look at meta/conf/distro/include/init-manager-systemd.inc you can
see what INIT_MANAGER = "systemd" tweaks.

> IMAGE_ROOTFS_EXTRA_SPACE = "38048576"
[snip]

Scott

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

Re: [yocto] Adding systemd to yocto

2022-05-03 Thread Jack Mitchell 
On 03/05/2022 11:57, Edgar Mobile wrote:
> Apparently, this is not enough:
> 
> bitbake core-image-weston
> /usr/lib/python3.6/importlib/_bootstrap.py:219: ImportWarning: can't
> resolve package from __spec__ or __package__, falling back on __name__
> and __path__
>   return f(*args, **kwds)
> Loading cache: 100% || Time:
> 0:00:00
> Loaded 1472 entries from dependency cache.
> NOTE: Resolving any missing task queue dependencies
> ERROR: Nothing RPROVIDES 'pam' (but
> /media/user/SSD1TB/yoctoqemu/poky/meta/recipes-graphics/images/core-image-weston.bb
> RDEPENDS on or otherwise requires it)
> NOTE: Runtime target 'pam' is unbuildable, removing...
> Missing or unbuildable dependency chain was: ['pam']
> ERROR: Required build target 'core-image-weston' has no buildable providers.
> Missing or unbuildable dependency chain was: ['core-image-weston', 'pam']
> 
> These are my current additions to local.conf:
> 
> INIT_MANAGER="systemd"
> CORE_IMAGE_EXTRA_INSTALL += " mesa-demos gdb"
> IMAGE_INSTALL:append += " pam"

pam is a DISTRO_FEATURE as below, not a package as you've added above.

> DISTRO_FEATURES:append = " systemd wayland pam x11"
> VIRTUAL-RUNTIME_init_manager = "systemd" 
> DISTRO_FEATURES_BACKFILL_CONSIDERED =
> "sysvinit"VIRTUAL-RUNTIME_initscripts = ""
> IMAGE_ROOTFS_EXTRA_SPACE = "38048576"
> 
> 
> 
> *From:* Scott Murray 
> *Sent:* Monday, May 2, 2022 2:32 PM
> *To:* Edgar Mobile 
> *Cc:* Joel Winarske ; Yocto-mailing-list
> 
> *Subject:* Re: [yocto] Adding systemd to yocto
>  
> On Mon, 2 May 2022, Edgar Mobile wrote:
> 
>> Ok, correction: I complains about pam missing.
> 
> My apologies, I'd forgotten that wrinkle as we'd been sidestepping it for
> a while in AGL with some custom Weston startup.  There are a few recipes
> in the Weston stuff that explicitly mark pam as a required feature when
> using systemd, so you'll also need to have:
> 
> DISTRO_FEATURES:append = " pam"
> 
> Scott
> 
> 
> 
> 

-- 
Jack Mitchell, Consultant
https://www.tuxable.co.uk

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

Re: [yocto] Adding systemd to yocto

2022-05-03 Thread Edgar Mobile 
Apparently, this is not enough:

bitbake core-image-weston
/usr/lib/python3.6/importlib/_bootstrap.py:219: ImportWarning: can't resolve 
package from __spec__ or __package__, falling back on __name__ and __path__
  return f(*args, **kwds)
Loading cache: 100% || Time: 0:00:00
Loaded 1472 entries from dependency cache.
NOTE: Resolving any missing task queue dependencies
ERROR: Nothing RPROVIDES 'pam' (but 
/media/user/SSD1TB/yoctoqemu/poky/meta/recipes-graphics/images/core-image-weston.bb
 RDEPENDS on or otherwise requires it)
NOTE: Runtime target 'pam' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['pam']
ERROR: Required build target 'core-image-weston' has no buildable providers.
Missing or unbuildable dependency chain was: ['core-image-weston', 'pam']

These are my current additions to local.conf:

INIT_MANAGER="systemd"
CORE_IMAGE_EXTRA_INSTALL += " mesa-demos gdb"
IMAGE_INSTALL:append += " pam"
DISTRO_FEATURES:append = " systemd wayland pam x11" 
VIRTUAL-RUNTIME_init_manager = "systemd"
DISTRO_FEATURES_BACKFILL_CONSIDERED = "sysvinit"VIRTUAL-RUNTIME_initscripts = ""
IMAGE_ROOTFS_EXTRA_SPACE = "38048576"



From: Scott Murray 
Sent: Monday, May 2, 2022 2:32 PM
To: Edgar Mobile 
Cc: Joel Winarske ; Yocto-mailing-list 

Subject: Re: [yocto] Adding systemd to yocto

On Mon, 2 May 2022, Edgar Mobile wrote:

> Ok, correction: I complains about pam missing.

My apologies, I'd forgotten that wrinkle as we'd been sidestepping it for
a while in AGL with some custom Weston startup.  There are a few recipes
in the Weston stuff that explicitly mark pam as a required feature when
using systemd, so you'll also need to have:

DISTRO_FEATURES:append = " pam"

Scott

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

Re: [yocto] [PATCH yocto-autobuilder-helper v12] Add a banner on the old documentation docs.

2022-05-03 Thread Quentin Schulz 

Hi Amahnui,

On 4/27/22 19:27, Abongwa Amahnui Bonalais wrote:> Signed-off-by: 
Abongwa Bonalais Amahnui > ---



Adding a comment in the commit log to explain why this patch is needed 
and what it does would be great.



  scripts/docs_fix_all_html_css.py | 111 +++
  scripts/run-docs-build   |   2 +
  2 files changed, 113 insertions(+)
  create mode 100644 scripts/docs_fix_all_html_css.py

diff --git a/scripts/docs_fix_all_html_css.py b/scripts/docs_fix_all_html_css.py
new file mode 100644
index 000..db99054
--- /dev/null
+++ b/scripts/docs_fix_all_html_css.py
@@ -0,0 +1,111 @@
+#!/usr/bin/env python3
+#
+# SPDX-License-Identifier: GPL-2.0-only
+#
+#Signed-off-by: Abongwa Bonalais Amahnui 
+#
+#
+# function to append to the content of a html file below the body tag
+#


Please add a comment as to what this script is supposed to to. You're 
discussing the implementation here more than the finality. We need to 
know when opening the file and reading the comment what this 
should/would be used for.



+#
+
+import os
+
+
+
+html_content_dunfell = '''
+This document is outdated, you should select the https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.yoctoproject.org_d=DwMDAgc=_sEr5x9kUWhuk4_nFwjJtAr=LYjLexDn7rXIzVmkNPvw5ymA1XTSqHGq8yBP6m6qZZ4njZguQhZhkI_-172IIy1tm=aRH3jUhIOsO6ovQMKiTHiW-F3Xwnx9HWg6yTF99QSvNBJXbkOkdzSNhwGt6I4zHls=QnWAweVmLt12aTlVPVFZsjAeYelStsO_8RsqIskX0Ske=;>latest
 release version in this series.
+
+'''


I would nitpick here and say we should probably point to 
https://docs.yoctoproject.org/dunfell in the href. But that can be 
fixed/discussed later.



+html_content = '''
+This version of the project is now considered obsolete, please select and use a https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.yoctoproject.orgd=DwMDAgc=_sEr5x9kUWhuk4_nFwjJtAr=LYjLexDn7rXIzVmkNPvw5ymA1XTSqHGq8yBP6m6qZZ4njZguQhZhkI_-172IIy1tm=aRH3jUhIOsO6ovQMKiTHiW-F3Xwnx9HWg6yTF99QSvNBJXbkOkdzSNhwGt6I4zHls=XxAPqWFTh9XMmtK4eywrsIFkuOGfwEs8acOxvNGck2ge=;>more
 recent version.
+
+'''
+
+#  and  are added to the html 
files to wrap all the content below the body tag in a div tag whose class is known so it can be controlled in the css file


You are explaining what you are doing, which we can usually understand 
by reading the code, instead of explaining why you're doing it which is 
something we cannot guess. Why was it not possible to just insert the 
banner in the body tag as a div before any other element/tag?



+last_div = '''
+
+
+'''
+
+css_replacement_content = '''
+
+  font-family: Verdana, Sans, sans-serif;
+
+  /*min-width: 640px;*/


You can remove this commented part as it does not provide any context or 
help.



+  width: 100%;
+  margin:  0;
+  padding: 0;
+  color: #333;
+  overflow-x: hidden;
+  }
+
+ /*added books too*/


Not sure what I am supposed to understand with this comment?


+.body{
+margin:  0 auto;
+min-width: 640px;
+padding: 0 5em 5em 5em;
+}
+/* added the id below to make the banner show and be fixed*/
+#outdated-warning{
+text-align: center;
+background-color: rgb(255, 186, 186);
+color: rgb(106, 14, 14);
+padding: 0.5em 0;
+width: 100%;
+position: fixed;
+top: 0;
+
+
+'''
+# pattern = '^3.1*'
+# exclude = re.search(pattern, dir)


Useless comments, please remove.


+def loop_through_html_directories(dir):
+exclude = []
+for root, dirs, filenames in os.walk(dir):
+ # exclude banner for 3.1.x upward as it is an LTS release and is 
still supported
+exclude = [ name for name in os.listdir(dir) if name.startswith('3.1') 
]
+for d in dirs:
+if d in exclude:
+dirs.remove(d)
+for filename in filenames:
+if filename.endswith('.html'):
+with open(os.path.join(root, filename), 'r', 
encoding="ISO-8859-1") as f:
+current_content = f.read()
+with open(os.path.join(root, filename), 'w') as f:
+f.write(current_content.replace('', '' + 
html_content))
+f.write(current_content.replace('', last_div + 
''))
+if filename.endswith('.css'):
+with open(os.path.join(root, filename), 'r', 
encoding="ISO-8859-1") as f:
+css_content = f.read()
+with open(os.path.join(root, filename), 'w') as f:
+
f.write(css_content.replace(css_content[css_content.find('body 
{'):css_content.find('}'[0])], 'body {' + css_replacement_content ))
+print(exclude)
+loop_through_html_directories('.')
+


The function name is not really helpful, you're explaining the 
implementation more than the outcome of it. I should call this function 
if I want to add a banner for olds docs. I could suggest 
add_banner_old_docs as a function name instead, though other people 
could probably come up with something more meaningful.



+
+
+
+def dunfell_tags(dir):
+dunfell_banners = []
+for root, dirs, filenames in

Re: [yocto] Yocto cyrillic characters support #yocto

2022-05-03 Thread Nicolas Jeker 
On Fri, 2022-04-29 at 06:48 -0700, Ashutosh Naik wrote:
> I am having trouble creating files with cyrillic characters on a
> yocto generated image.
>  
> For eg. If I try to create a file like :
> # touch  1Черная
>  
> I do get:
>  
> # ls
> 1?? 

Is your file created with the wrong name or is it actually just the
'ls' output that doesn't support unicode characters?

If you're using busybox, I think these configuration options could be
of interest:

CONFIG_UNICODE_SUPPORT
CONFIG_LAST_SUPPORTED_WCHAR

You'll find this at the bottom of "Settings -> Support Unicode" when
using menuconfig.

> I have verified that my locale has utf8 support:
>  
> # locale
> LANG=en_GB.utf8
> LC_CTYPE="en_GB.utf8"
> LC_NUMERIC="en_GB.utf8"
> LC_TIME="en_GB.utf8"
> LC_COLLATE="en_GB.utf8"
> LC_MONETARY="en_GB.utf8"
> LC_MESSAGES="en_GB.utf8"
> LC_PAPER="en_GB.utf8"
> LC_NAME="en_GB.utf8"
> LC_ADDRESS="en_GB.utf8"
> LC_TELEPHONE="en_GB.utf8"
> LC_MEASUREMENT="en_GB.utf8"
> LC_IDENTIFICATION="en_GB.utf8"
> LC_ALL=en_GB.utf8
>  
> What could I be missing and how can I create files with cyrillic
> characters?
>  
> Regards
> Ash


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