Date   

Re: User configuration & host contamination

Jeffrey Simons
 

On Thu, Nov 11, 2021 at 03:34 PM, Jeffrey Simons wrote:
Hi Manuel,

Subject: Re: [yocto] User configuration & host contamination

Hi Jeffrey,

Does the recipe which builds the application DEPEND on the recipe which sets up the user? This is what I would try. If I understand
things correctly, Yocto/Bitbake provides every recipe a pristine environment unnaffected from other recipes going into the same image.
For example, if you want to link your application against some libraries provided by other recipes, you need to add them to DEPENDS.
That populates your build environment with that other recipes output. I'm not sure this applies to user accounts as well, but I guess it's worth a try.

Please note I probably used the termins "recipe" and "package" incorrectly.

Hope this helps,
Manuel
Thank you for your reply and suggestion.
I already have a dependency on the user-configuration script, see the below snippet from my recipe.

# Compile-time dependencies for testapp
DEPENDS = "user-configuration"

# Run-time dependencies for testapp
RDEPENDS_${PN} += "rsyslog \

Unfortunately that did not work, I have seen some suggestions on stack-overflow where they added the user multiple times per recipe by using extrauseradd (I believe).
That seems a bit weird to me to add every time the same user, also the drawback is that if the user changes then I have to adjust all recipes that rely on that specific user.
What I did today to circumvent the issue is to assign the user by reference of UID and GID, but I'm not sure if this is the intended Yocto way. As you stated before
Yocto presents you with a pristine environment with all information present, so I would expect that my user is there. Perhaps I did not include the user-configuration
correctly?
I did include the user-configuration by adding it into our distribution description, see the next coding snippet.

#
# Usernames that will be used within the distro.
# Can be changed when desired, each recipe must use this user for the application.
#
TEST_USER = "testuser"
TEST_USER_UID = "1200"

DISTRO_EXTRA_RDEPENDS += "user-configuration"

Can you or any one else clarify if this is the correct way or not?

Thank you in advance.

Jeffrey Simons

Software Engineer
Royal Boon Edam International B.V.
Hi All,

Can anyone elaborate on my fix if this is the correct way, or point me in the correct direction.

With kind regards,
Jeffrey Simons

Software Engineer
Royal Boon Edam International B.V.


Re: [PATCH yocto-autobuilder-helper] config.json: set ZSTD_THREADS like XZ_THREADS

Richard Purdie
 

On Wed, 2021-11-24 at 09:00 +0100, Alexander Kanavin wrote:
But the AB has not been exhibiting any problems with zstd, and this will
degrade performance. Let's only fix what is broken.
I'm not sure I agree with that. 

We have 60+ "intermittent" bugs and some of us are in weekly meetings trying to
do something about working out why these are failing. It feels like we're not
really getting too far with some subset of them and it is using up a lot of the
SWAT and bug triage time.

We've made a few changes to try and reduce the load spikes on the systems and
this fits with the other changes we've made.

Cheers,

Richard


cross-localedef file not found in do_rootfs #yocto #zeus

Bel Hadj Salem Talel <bhstalel@...>
 

Hello All,

I created a simple image recipe for initramfs type of image with no IMAGE_FEATURES and simply:
IMAGE_INSTALL = "packagegroup-core-boot busybox"
When I bitbake the image I get the following error:

---------------------------
ERROR: menzu-image-initramfs-1.0-r0 do_rootfs: Error executing a python function in exec_python_func() autogenerated:
 
The stack trace of python calls that resulted in this exception/failure was:
File: 'exec_python_func() autogenerated', lineno: 2, function: <module>
     0001:
 *** 0002:do_rootfs(d)
     0003:
File: '/home/talel/Desktop/YoctoWork/sources/poky/meta/classes/image.bbclass', lineno: 245, function: do_rootfs
     0241:    progress_reporter.next_stage()
     0242:
     0243:    # generate rootfs
     0244:    d.setVarFlag('REPRODUCIBLE_TIMESTAMP_ROOTFS', 'export', '1')
 *** 0245:    create_rootfs(d, progress_reporter=progress_reporter, logcatcher=logcatcher)
     0246:
     0247:    progress_reporter.finish()
     0248:}
     0249:do_rootfs[dirs] = "${TOPDIR}"
File: '/home/talel/Desktop/YoctoWork/sources/poky/meta/lib/oe/rootfs.py', lineno: 978, function: create_rootfs
     0974:    img_type = d.getVar('IMAGE_PKGTYPE')
     0975:    if img_type == "rpm":
     0976:        RpmRootfs(d, manifest_dir, progress_reporter, logcatcher).create()
     0977:    elif img_type == "ipk":
 *** 0978:        OpkgRootfs(d, manifest_dir, progress_reporter, logcatcher).create()
     0979:    elif img_type == "deb":
     0980:        DpkgRootfs(d, manifest_dir, progress_reporter, logcatcher).create()
     0981:
     0982:    os.environ.clear()
File: '/home/talel/Desktop/YoctoWork/sources/poky/meta/lib/oe/rootfs.py', lineno: 204, function: create
     0200:        if self.progress_reporter:
     0201:            self.progress_reporter.next_stage()
     0202:
     0203:        # call the package manager dependent create method
 *** 0204:        self._create()
     0205:
     0206:        sysconfdir = self.image_rootfs + self.d.getVar('sysconfdir')
     0207:        bb.utils.mkdirhier(sysconfdir)
     0208:        with open(sysconfdir + "/version", "w+") as ver:
File: '/home/talel/Desktop/YoctoWork/sources/poky/meta/lib/oe/rootfs.py', lineno: 922, function: _create
     0918:
     0919:        if self.progress_reporter:
     0920:            self.progress_reporter.next_stage()
     0921:
 *** 0922:        self.pm.install_complementary()
     0923:
     0924:        if self.progress_reporter:
     0925:            self.progress_reporter.next_stage()
     0926:
File: '/home/talel/Desktop/YoctoWork/sources/poky/meta/lib/oe/package_manager.py', lineno: 614, function: install_complementary
     0610:
     0611:        target_arch = self.d.getVar('TARGET_ARCH')
     0612:        localedir = oe.path.join(self.target_rootfs, self.d.getVar("libdir"), "locale")
     0613:        if os.path.exists(localedir) and os.listdir(localedir):
 *** 0614:            generate_locale_archive(self.d, self.target_rootfs, target_arch, localedir)
     0615:            # And now delete the binary locales
     0616:            self.remove(fnmatch.filter(self.list_installed(), "glibc-binary-localedata-*"), False)
     0617:
     0618:    def deploy_dir_lock(self):
File: '/home/talel/Desktop/YoctoWork/sources/poky/meta/lib/oe/package_manager.py', lineno: 140, function: generate_locale_archive
     0136:        if os.path.isdir(path):
     0137:            cmd = ["cross-localedef", "--verbose"]
     0138:            cmd += arch_options
     0139:            cmd += ["--add-to-archive", path]
 *** 0140:            subprocess.check_output(cmd, env=env, stderr=subprocess.STDOUT)
     0141:
     0142:class Indexer(object, metaclass=ABCMeta):
     0143:    def __init__(self, d, deploy_dir):
     0144:        self.d = d
File: '/usr/lib/python3.8/subprocess.py', lineno: 415, function: check_output
     0411:        else:
     0412:            empty = b''
     0413:        kwargs['input'] = empty
     0414:
 *** 0415:    return run(*popenargs, stdout=PIPE, timeout=timeout, check=True,
     0416:               **kwargs).stdout
     0417:
     0418:
     0419:class CompletedProcess(object):
File: '/usr/lib/python3.8/subprocess.py', lineno: 493, function: run
     0489:                             'with capture_output.')
     0490:        kwargs['stdout'] = PIPE
     0491:        kwargs['stderr'] = PIPE
     0492:
 *** 0493:    with Popen(*popenargs, **kwargs) as process:
     0494:        try:
     0495:            stdout, stderr = process.communicate(input, timeout=timeout)
     0496:        except TimeoutExpired as exc:
     0497:            process.kill()
File: '/usr/lib/python3.8/subprocess.py', lineno: 858, function: __init__
     0854:                if self.text_mode:
     0855:                    self.stderr = io.TextIOWrapper(self.stderr,
     0856:                            encoding=encoding, errors=errors)
     0857:
 *** 0858:            self._execute_child(args, executable, preexec_fn, close_fds,
     0859:                                pass_fds, cwd, env,
     0860:                                startupinfo, creationflags, shell,
     0861:                                p2cread, p2cwrite,
     0862:                                c2pread, c2pwrite,
File: '/usr/lib/python3.8/subprocess.py', lineno: 1704, function: _execute_child
     1700:                    else:
     1701:                        err_filename = orig_executable
     1702:                    if errno_num != 0:
     1703:                        err_msg = os.strerror(errno_num)
 *** 1704:                    raise child_exception_type(errno_num, err_msg, err_filename)
     1705:                raise child_exception_type(err_msg)
     1706:
     1707:
     1708:        def _handle_exitstatus(self, sts, _WIFSIGNALED=os.WIFSIGNALED,
Exception: FileNotFoundError: [Errno 2] No such file or directory: 'cross-localedef'
 
ERROR: Logfile of failure stored in: /home/talel/Desktop/YoctoWork/arken/tmp/work/menzu-poky-linux/menzu-image-initramfs/1.0-r0/temp/log.do_rootfs.143822
ERROR: Task (/home/talel/Documents/FinalGit/SelfArkenWork/arken/meta-menzu/recipes-core/images/menzu-image-initramfs.bb:do_rootfs) failed with exit code '1'
---------------------------

I was building the image with success, but now it fails, I don't know why.
The other normal images build successfully.

Thanks,
Talel


Re: [PATCH yocto-autobuilder-helper] config.json: set ZSTD_THREADS like XZ_THREADS

Alexander Kanavin
 

But the AB has not been exhibiting any problems with zstd, and this will degrade performance. Let's only fix what is broken.

Alex


On Tue, 23 Nov 2021 at 20:53, Ross Burton <ross@...> wrote:
My personal build machine has been crashing and dying due to overload
with the default ZSTD_THREADS, and the AB has had problems with xz due
to overload so I was being proactive and ensuring zstd is limited on
the AB the same way xz is.

Ross

On Tue, 23 Nov 2021 at 17:11, Alexander Kanavin <alex.kanavin@...> wrote:
>
> Is there a particular reason?
>
> Alex
>
> On Tue, 23 Nov 2021 at 16:03, Ross Burton <ross@...> wrote:
>>
>> Signed-off-by: Ross Burton <ross.burton@...>
>> ---
>>  config.json | 1 +
>>  1 file changed, 1 insertion(+)
>>
>> diff --git a/config.json b/config.json
>> index 7203783..c0543d9 100644
>> --- a/config.json
>> +++ b/config.json
>> @@ -47,6 +47,7 @@
>>              "PARALLEL_MAKE = '-j 16 -l 52'",
>>              "XZ_MEMLIMIT = '5%'",
>>              "XZ_THREADS = '8'",
>> +            "ZSTD_THREADS = '8'",
>>              "BB_TASK_NICE_LEVEL = '5'",
>>              "BB_TASK_NICE_LEVEL:task-testimage = '0'",
>>              "BB_TASK_IONICE_LEVEL = '2.7'",
>> --
>> 2.25.1
>>
>>
>>
>>


Re: [PATCH yocto-autobuilder-helper] config.json: set ZSTD_THREADS like XZ_THREADS

Ernst Sjöstrand
 

There was a long thread about this on oe-core recently:
https://lists.openembedded.org/g/openembedded-core/message/157999

//Ernst


Re: [PATCH yocto-autobuilder-helper] config.json: set ZSTD_THREADS like XZ_THREADS

Ross Burton <ross@...>
 

My personal build machine has been crashing and dying due to overload
with the default ZSTD_THREADS, and the AB has had problems with xz due
to overload so I was being proactive and ensuring zstd is limited on
the AB the same way xz is.

Ross

On Tue, 23 Nov 2021 at 17:11, Alexander Kanavin <alex.kanavin@gmail.com> wrote:

Is there a particular reason?

Alex

On Tue, 23 Nov 2021 at 16:03, Ross Burton <ross@burtonini.com> wrote:

Signed-off-by: Ross Burton <ross.burton@arm.com>
---
config.json | 1 +
1 file changed, 1 insertion(+)

diff --git a/config.json b/config.json
index 7203783..c0543d9 100644
--- a/config.json
+++ b/config.json
@@ -47,6 +47,7 @@
"PARALLEL_MAKE = '-j 16 -l 52'",
"XZ_MEMLIMIT = '5%'",
"XZ_THREADS = '8'",
+ "ZSTD_THREADS = '8'",
"BB_TASK_NICE_LEVEL = '5'",
"BB_TASK_NICE_LEVEL:task-testimage = '0'",
"BB_TASK_IONICE_LEVEL = '2.7'",
--
2.25.1




Re: [qa-build-notification] [yocto] QA notification for completed autobuilder build (yocto-3.1.12.rc1)

Richard Purdie
 

On Tue, 2021-11-23 at 11:54 +0000, Teoh, Jay Shen wrote:
This is the full report for yocto-3.1.12.rc1:
https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/tree/?h=intel-yocto-testresults

======= Summary ========
No high milestone defects.

new issue found

Bug 14622 - bsps-hw.bsps-hw.Test_Seek_bar_and_volume_control manual test case failure

======= Bugs ========
https://bugzilla.yoctoproject.org/show_bug.cgi?id=14622

Thanks,
Jay
Thanks Jay.

The TSC discussed 3.1.12 and are happy for rc1 to be released.

Cheers,

Richard


Re: [PATCH yocto-autobuilder-helper] config.json: set ZSTD_THREADS like XZ_THREADS

Alexander Kanavin
 

Is there a particular reason?

Alex


On Tue, 23 Nov 2021 at 16:03, Ross Burton <ross@...> wrote:
Signed-off-by: Ross Burton <ross.burton@...>
---
 config.json | 1 +
 1 file changed, 1 insertion(+)

diff --git a/config.json b/config.json
index 7203783..c0543d9 100644
--- a/config.json
+++ b/config.json
@@ -47,6 +47,7 @@
             "PARALLEL_MAKE = '-j 16 -l 52'",
             "XZ_MEMLIMIT = '5%'",
             "XZ_THREADS = '8'",
+            "ZSTD_THREADS = '8'",
             "BB_TASK_NICE_LEVEL = '5'",
             "BB_TASK_NICE_LEVEL:task-testimage = '0'",
             "BB_TASK_IONICE_LEVEL = '2.7'",
--
2.25.1





Yocto Project Status WW46`21

Stephen Jolley
 

Current Dev Position: YP 3.5 M1

Next Deadline: 6th Dec. 2021 YP 3.5 M1 build

 

Next Team Meetings:

 

Key Status/Updates:

  • YP 3.3.4 was released
  • YP 3.1.12 has been through QA and is pending release approval.
  • YP 3.4.1 is due to be built after the current patchsets are reviewed and merge.
  • Next week is the Yocto Project Virtual Summit https://www.yoctoproject.org/yocto-project-summit-2021-11/ and OpenEmbedded Virtual Developer Meeting on Friday https://www.openembedded.org/wiki/OEDVM_Nov_2021
  • CVEs in hardknott and dunfell rose this week due to 14 busybox issues being added. Master remains roughly stable but we need to upgrade golang to fix some, the other issues in master do not yet have fixes in upstream (qemu, libarchive and nasm).
  • We continue to see a reduction in the number of patches in “Pending” state. Many thanks to everyone who has taken the time to review patch status and handle accordingly, particularly where they were accepted upstream. This will significantly benefit the project in the long term.
  • Intermittent issues continue to rise and help is very much welcome on these issues. 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:

 

YP 3.5 Milestone Dates:

  • YP 3.5 M1 build date 2021/12/06
  • YP 3.5 M1 Release date 2021/12/17
  • YP 3.5 M2 build date 2022/01/10
  • YP 3.5 M2 Release date 2022/1/21
  • YP 3.5 M3 build date 2022/2/21
  • YP 3.5 M3 Release date 2022/03/04
  • YP 3.5 M4 build date 2022/04/04
  • YP 3.5 M4 Release date 2022/04/29

 

Upcoming dot releases:

  • YP 3.3.4 is released
  • YP 3.1.12 is out of QA
  • YP 3.4.1 build date 2021/11/22
  • YP 3.4.1 Release date 2021/12/03
  • YP 3.1.13 build date 2021/12/13
  • YP 3.1.13 Release date 2021/12/22
  • YP 3.1.14 build date 2022/01/24
  • YP 3.1.14 Release date 2022/02/04
  • YP 3.4.2 build date 2022/02/07
  • YP 3.4.2 Release date 2022/02/18
  • YP 3.1.15 build date 2022/03/14
  • YP 3.1.15 Release date 2022/03/25
  • YP 3.4.3 build date 2022/03/21
  • YP 3.4.3 Release date 2022/04/01
  • YP 3.1.16 build date 2022/04/25
  • YP 3.1.16 Release date 2022/05/06

 

Tracking Metrics:

 

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!]

 

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

(    Cell:                (208) 244-4460

* Email:              sjolley.yp.pm@...

 


[PATCH yocto-autobuilder-helper] config.json: set ZSTD_THREADS like XZ_THREADS

Ross Burton <ross@...>
 

Signed-off-by: Ross Burton <ross.burton@arm.com>
---
config.json | 1 +
1 file changed, 1 insertion(+)

diff --git a/config.json b/config.json
index 7203783..c0543d9 100644
--- a/config.json
+++ b/config.json
@@ -47,6 +47,7 @@
"PARALLEL_MAKE =3D '-j 16 -l 52'",
"XZ_MEMLIMIT =3D '5%'",
"XZ_THREADS =3D '8'",
+ "ZSTD_THREADS =3D '8'",
"BB_TASK_NICE_LEVEL =3D '5'",
"BB_TASK_NICE_LEVEL:task-testimage =3D '0'",
"BB_TASK_IONICE_LEVEL =3D '2.7'",
--=20
2.25.1


[PATCH yocto-autobuilder-helper] config.json: build generic-arm64 instead of Juno

Ross Burton <ross@...>
 

generic-arm64 is the recommeded generic BSP for modern Arm deployments,
so ensure it is exercised in the autobuilder.

Signed-off-by: Ross Burton <ross.burton@arm.com>
---
config.json | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/config.json b/config.json
index f152b47..7203783 100644
--- a/config.json
+++ b/config.json
@@ -330,8 +330,8 @@
"SANITYTARGETS" : "core-image-sato:do_testsdk"
},
"step2": {
- "shortname": "Build for juno",
- "MACHINE": "juno",
+ "shortname": "Build for generic-arm64",
+ "MACHINE": "generic-arm64",
"BBTARGETS": "core-image-minimal core-image-sato core-im=
age-sato:do_populate_sdk",
"SANITYTARGETS" : "core-image-sato:do_testsdk"
}
--=20
2.25.1


Build ROS2 package that contains custom interfaces (msg, srv) #yocto

bojankoce
 

Hi, guys!

I have a DART-MX8M-Mini machine running Yocto Hardknott.

I properly added meta-ros layer and ROS2 foxy distro to our Yocto build by following instructions from here (Sanity Tests pass successfully).

With the help of devtool, I was able to build my custom ROS2 package (containing simple talker and listener nodes - link). For that to happen, I got some great support from the Yocto community - link.

Here is the content of my-first-yocto-pkg_git.bb recipe that enabled me to download my source code from the git and properly build the ROS2 package:

# Recipe created by recipetool
# This is the basis of a recipe and may need further editing in order to be fully functional.
# (Feel free to remove these comments when editing.)

# Unable to find any files that looked like license statements. Check the accompanying
# documentation and source headers and set LICENSE and LIC_FILES_CHKSUM accordingly.
#
# NOTE: LICENSE is being set to "CLOSED" to allow you to at least start building - if
# this is not accurate with respect to the licensing of the software being built (it
# will not be in most cases) you must specify the correct value before using this
# recipe for anything other than initial testing/development!

DESCRIPTION = "Examples of minimal publisher/subscriber using rclcpp."
LICENSE = "Apache-2.0"
LIC_FILES_CHKSUM = "file://package.xml;beginline=8;endline=8;md5=12c26a18c7f493fdc7e8a93b16b7c04f"

SRC_URI = "git://github.com/bojankoce/my_first_yocto_pkg;protocol=https"

# Modify these as desired
PV = "0.1.0"
SRCREV = "1312445de2e6861d9561c0f89f4827b94c2ff6b1"

S = "${WORKDIR}/git"

# NOTE: unable to map the following CMake package dependencies: rclcpp ament_lint_auto std_msgs ros_ament_cmake
inherit ros_distro_foxy
inherit ros_superflore_generated
inherit ros_ament_cmake

ROS_BUILD_DEPENDS = " \
    rclcpp \
    std-msgs \
"

ROS_BUILDTOOL_DEPENDS = " \
	ament-cmake-native \
"

ROS_EXPORT_DEPENDS = ""

ROS_BUILDTOOL_EXPORT_DEPENDS = ""

ROS_EXEC_DEPENDS = " \
    launch-ros \
    std-msgs \
"

DEPENDS = "${ROS_BUILD_DEPENDS} ${ROS_BUILDTOOL_DEPENDS}"

DEPENDS += "${ROS_EXPORT_DEPENDS} ${ROS_BUILDTOOL_EXPORT_DEPENDS}"

# Specify any options you want to pass to cmake using EXTRA_OECMAKE:
#EXTRA_OECMAKE = ""

I currently have a hard time building my ROS2 package that contains only custom ROS2 interfaces (messages and services).
CMakeLists.txt file of that package contains the following lines that are causing the build errors:

find_package(rosidl_default_generators REQUIRED)
...

rosidl_generate_interfaces(${PROJECT_NAME}
  "msg/MessageX.msg"
  "msg/MessageY.msg"
  "srv/SrvX.srv"
  "srv/SrvY.srv"
 )

Do you have any idea about what should be included as inherit xxxxx or within ROS_BUILD_DEPENDS/ROS_BUILDTOOL_DEPENDS /ROS_EXEC_DEPENDS ... in order to successfully generate the ROS2 package containing custom interfaces?

Thanks in advance for your time and efforts. It is appreciated.

Sincerely,
Bojan.


Re: QA notification for completed autobuilder build (yocto-3.1.12.rc1)

Teoh, Jay Shen
 

Hi all,

This is the full report for yocto-3.1.12.rc1:
https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/tree/?h=intel-yocto-testresults

======= Summary ========
No high milestone defects.

new issue found

Bug 14622 - bsps-hw.bsps-hw.Test_Seek_bar_and_volume_control manual test case failure

======= Bugs ========
https://bugzilla.yoctoproject.org/show_bug.cgi?id=14622

Thanks,
Jay

-----Original Message-----
From: yocto@lists.yoctoproject.org <yocto@lists.yoctoproject.org> On Behalf
Of Richard Purdie
Sent: Wednesday, 17 November, 2021 6:25 AM
To: <yocto@lists.yoctoproject.org> <yocto@lists.yoctoproject.org>
Cc: qa-build-notification <qa-build-notification@lists.yoctoproject.org>
Subject: [yocto] QA notification for completed autobuilder build (yocto-
3.1.12.rc1)

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


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


Build hash information:

bitbake: c0348de8121c3a842bf44906f7e2f79e93f7275b
meta-agl: 0406cbb235fb08ce9e6f9d07e64e0932b20050a9
meta-arm: ce535dfb96de4d2529f091d7d85a7172c626001c
meta-aws: 2f72301f5a73279c4d2f12fc6218876629666e06
meta-gplv2: 60b251c25ba87e946a0ca4cdc8d17b1cb09292ac
meta-intel: 625da85e7b01b71cc310267b0ba7119eb139e9f7
meta-mingw: 524de686205b5d6736661d4532f5f98fee8589b7
meta-openembedded: 7889158dcd187546fc5e99fd81d0779cad3e8d17
oecore: 44b1970c40e9d73f6e63fb10cdc55837a26f5921
poky: 0839888394a6e42e96f9f0d201376eb38bc79b24



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


Upgrade to version 1.40 broken WiFi

JH
 

Hi,

I built connman version 1.37 and wpa_supplicant in zeus, it worked
well. I have just upgraded OE / Yoctor to Honister, I built the
connman version 1.40 and ran it with wpa_applicant, but it is now
completely broken, no WiFi IP address assigned. I heard that a new
version of connman is going to replace wpa_supplicant by iwd, is that
correct? If it is true, I am not going to debug it with wpa_applicant,
I am not familiar with iwd, the Yocto does not have iwd option, are
there documents to build Honister connman with iwd?

Thank you.

Kind regards,

- JH


[meta-cgl][PATCH] resource-agents: Fix QA Issue:

leimaohui
 

ERROR: resource-agents-4.5.0-r0 do_package_qa: QA Issue: resource-agents installs files in /var/volatile, but it is expected to be empty [empty-dirs]

Signed-off-by: Lei Maohui <leimaohui@fujitsu.com>
---
.../cluster-resource-agents/resource-agents_4.5.0.bb | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/meta-cgl-common/recipes-cgl/cluster-resource-agents/resource-agents_4.5.0.bb b/meta-cgl-common/recipes-cgl/cluster-resource-agents/resource-agents_4.5.0.bb
index 261681c..d6fb708 100644
--- a/meta-cgl-common/recipes-cgl/cluster-resource-agents/resource-agents_4.5.0.bb
+++ b/meta-cgl-common/recipes-cgl/cluster-resource-agents/resource-agents_4.5.0.bb
@@ -57,8 +57,7 @@ EXTRA_OECONF += "--disable-fatal-warnings \
--with-rsctmpdir=/var/run/heartbeat/rsctmp"

do_install:append() {
- rm -rf "${D}${localstatedir}/run"
- rmdir --ignore-fail-on-non-empty "${D}${localstatedir}"
+ rm -rf "${D}${localstatedir}"
}

# tickle_tcp is published under GPLv3, we just split it into ${PN}-extra,
--
2.25.1


Re: Problem installing python package from a wheel #bitbake #python

David Babich
 

I made it a little further by adding --no-cache-dir to the pip3 install command.  That got rid fo the warning about not being able to access the .cache/pip.  However I still have the error:

| ERROR: torch-1.10.0-cp36-cp36m-linux_aarch64.whl is not a supported wheel on this platform.


Problem installing python package from a wheel #bitbake #python

David Babich
 

Hi,
I'm attempting to create a recipe for pytorch for the TX2i using a wheel file obtained from here:

https://forums.developer.nvidia.com/t/pytorch-for-jetson-version-1-10-now-available/72048

Here is what I have so far for the recipe:

```

DESCRIPTION = "NVIDIA's Python Torch"

HOMEPAGE = "https://nvidia.com"

LICENSE = "BSD-3-Clause"

LIC_FILES_CHKSUM = "file://../LICENSE;md5=91a5dfdaccf53b27488cb3a639e986d5"

 

inherit setuptools3

 

SRC_URI = "\

        file://torch-1.10.0-cp36-cp36m-linux_aarch64.whl \

        file://LICENSE \

"

 

COMPATIBLE_MACHINE = "jetson-tx2-devkit-tx2i"

PACKAGE_ARCH = "${MACHINE_ARCH}"

 

S = "${WORKDIR}/${PN}-${PV}"

 

do_configure() {

        :

}

 

do_compile() {

        :

}

 

do_install() {

        pip3 install ${WORKDIR}/torch-1.10.0-cp36-cp36m-linux_aarch64.whl

}

 

DEPENDS = "python3-pip-native"

```

When I build I get the following ambiguous error during do_install:

| WARNING: The directory '/home/ddbabich/.cache/pip' or its parent directory is not owned or is not writable by the current user. The cache has been disabled. Check the permissions and owner of that directory. If executing pip with sudo, you should use sudo's -H flag.

| ERROR: torch-1.10.0-cp36-cp36m-linux_aarch64.whl is not a supported wheel on this platform.


It seems like I'm missing something with the host vs. the target settings?  But I really don't have any ideas.  Any help is appreciated.
THanks
-David

 

 


Enhancements/Bugs closed WW47!

Stephen Jolley
 

All,

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

Who

Count

richard.purdie@...

4

randy.macleod@...

2

ross@...

1

steve@...

1

akuster808@...

1

Grand Total

9

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

(    Cell:                (208) 244-4460

* Email:              sjolley.yp.pm@...

 


Current high bug count owners for Yocto Project 3.5

Stephen Jolley
 

All,

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

Who

Count

ross@...

36

michael.opdenacker@...

34

david.reyna@...

22

randy.macleod@...

20

trevor.gamblin@...

16

bruce.ashfield@...

16

timothy.t.orling@...

14

JPEWhacker@...

11

sakib.sajal@...

11

richard.purdie@...

8

mhalstead@...

7

kai.kang@...

7

saul.wold@...

6

bluelightning@...

6

kiran.surendran@...

5

chee.yang.lee@...

4

hongxu.jia@...

4

jon.mason@...

3

Qi.Chen@...

3

pokylinux@...

2

pgowda.cve@...

2

mshah@...

2

alejandro@...

2

yf3yu@...

1

angolini@...

1

mark.hatle@...

1

open.source@...

1

alexandre.belloni@...

1

yi.zhao@...

1

jay.shen.teoh@...

1

limon.anibal@...

1

TicoTimo@...

1

raj.khem@...

1

john.kaldas.enpj@...

1

steve@...

1

mingli.yu@...

1

aehs29@...

1

thomas.perrot@...

1

matthewzmd@...

1

vinay.m.engg@...

1

Martin.Jansa@...

1

mostthingsweb@...

1

kexin.hao@...

1

elberger@...

1

shachar@...

1

nicolas.dechesne@...

1

yoctoproject@...

1

Grand Total

265

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

(    Cell:                (208) 244-4460

* Email:              sjolley.yp.pm@...

 


Yocto Project Newcomer & Unassigned Bugs - Help Needed

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 392 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, “3.4”, “3.5, "3.99" and "Future", the more pressing/urgent issues being in "3.4" and then “3.5”.

 

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.pm@...) 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.pm@...

 

1741 - 1760 of 57104