Date   

Re: [docs] [PATCH yocto-autobuilder-helper] scripts/run-docs-build: stop using the "transition" branch

Nicolas Dechesne
 



On Fri, Dec 3, 2021 at 11:03 AM Quentin Schulz <quentin.schulz@...> wrote:
Hi Nicolas,

On Fri, Dec 03, 2021 at 10:49:40AM +0100, Nicolas Dechesne wrote:
> On Fri, Dec 3, 2021 at 10:34 AM Quentin Schulz <
> quentin.schulz@...> wrote:
>
> > On Wed, Dec 01, 2021 at 02:59:49PM +0100, Michael Opdenacker wrote:
> > > No longer necessary now that the transition from DocBook to Sphinx is
> > over
> > >
> > > Signed-off-by: Michael Opdenacker <michael.opdenacker@...>
> >
> > Reviewed-by: Quentin Schulz <foss+yocto@...>
> >
>
> I don't understand. With this change, we no longer build the pages we
> reference here:
> https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.yoctoproject.org_releases.html-23outdated-2Drelease-2Dmanuals&d=DwIBaQ&c=_sEr5x9kUWhuk4_nFwjJtA&r=LYjLexDn7rXIzVmkNPvw5ymA1XTSqHGq8yBP6m6qZZ4njZguQhZhkI_-172IIy1t&m=nyCl21erajBNcx6SkCKI_BEntNgbh6114vcdWp_vB5yDzorVFjmzdqp0WXIIpQyK&s=rw5wG0nk_9KQ8RLvE1-sbSicy4NslWaeMwoyTSUuIyY&e=
>
> Or am I missing here?
>

Indeed. But this should be fixed, because we should handle this the same
way documentation/releases.html is, with a common one across all
releases. With the current implementation, only master has a list of all
outdated releases. e.g.
https://docs.yoctoproject.org/3.3/releases.html#outdated-release-manuals
does not exist, but
https://docs.yoctoproject.org/releases.html#outdated-release-manuals
does (and weirdly enough 3.4 too).

Yes, this part is indeed poorly implemented. But I don't think we can remove the transition branch until we fix it, so I don't think we can take this patch now. 

perhaps we should maintain the overall documentation (for all versions) in the same branch.. all these branches are making everything much complicated.. Or perhaps we should split the documentation 'content' and the documentation config and scripts. I am wondering how other projects are doing it to support such complex doc setup (multiple versions to support and to publish)!
 

I assume we want this in all branches. Therefore I think we should move
documentation/transition from that branch to master and copy the whole
directory for each non-master branch (with the git checkout master trick
from an earlier patch from Michael). I think this makes more sense than
keeping a transition branch? Especially since I assume we want to move
every 6 months one release from "Supported release manuals" to "Outdated
releae manuals" ?

I think we had the 'transition' pages in master initially, and we moved that to its own branch. I believe it's something we discussed with Richard.. but i forgot the details. 
 

Cheers,
Quentin
> >


Re: [docs] [PATCH yocto-autobuilder-helper] scripts/run-docs-build: stop using the "transition" branch

Nicolas Dechesne
 



On Fri, Dec 3, 2021 at 10:34 AM Quentin Schulz <quentin.schulz@...> wrote:
On Wed, Dec 01, 2021 at 02:59:49PM +0100, Michael Opdenacker wrote:
> No longer necessary now that the transition from DocBook to Sphinx is over
>
> Signed-off-by: Michael Opdenacker <michael.opdenacker@...>

Reviewed-by: Quentin Schulz <foss+yocto@...>

I don't understand. With this change, we no longer build the pages we reference here:

Or am I missing here? 
 

Thanks,
Quentin




Re: [meta-security][hardknott][PATCH v2] sssd: re-package to fix QA issues

kai
 

On 11/27/21 2:41 AM, akuster808 wrote:
merged.
Hi Armin,

Would you like to double check the commit, please? I don't see it in branch hardknott.

Regards,
Kai


On 11/16/21 10:28 AM, Jeremy A. Puhlman wrote:
It packages all file in ${libdir} to package sssd, including the .so
symlink files. Then it causes QA issues:

| ERROR: QA Issue: sssd rdepends on dbus-dev [dev-deps]
| ERROR: QA Issue: sssd rdepends on ding-libs-dev [dev-deps]

So re-package sssd then the .so symlink files and .pc files are packaged
to sssd-dev which should be.

File ${libdir}/libsss_sudo.so is not a symlink file but packaged to
sssd-dev too. Then causes another QA issue:

| ERROR: sssd-2.5.2-r0 do_package_qa: QA Issue:
-dev package sssd-dev contains non-symlink .so '/usr/lib/libsss_sudo.so' [dev-elf]

So create a new sub-package libsss-sudo to package file libsss_sudo.so
and make sssd rdepends on it.

JP: Updated for version differences.

Signed-off-by: Kai Kang <kai.kang@...>
Signed-off-by: Armin Kuster <akuster808@...>
(cherry picked from commit e81c15f851ca5396c78c8737967ee38db0ebe0cd)
Signed-off-by: Jeremy A. Puhlman <jpuhlman@...>
---
recipes-security/sssd/sssd_1.16.5.bb | 21 ++++++++++++++-------
1 file changed, 14 insertions(+), 7 deletions(-)

diff --git a/recipes-security/sssd/sssd_1.16.5.bb b/recipes-security/sssd/sssd_1.16.5.bb
index 02d0837..f13fc49 100644
--- a/recipes-security/sssd/sssd_1.16.5.bb
+++ b/recipes-security/sssd/sssd_1.16.5.bb
@@ -120,10 +120,17 @@ SYSTEMD_SERVICE_${PN} = " \
"
SYSTEMD_AUTO_ENABLE = "disable"
-FILES_${PN} += "${libdir} ${datadir} ${base_libdir}/security/pam_sss.so"
-FILES_${PN}-dev = " ${includedir}/* ${libdir}/*la ${libdir}/*/*la"
-
-# The package contains symlinks that trip up insane
-INSANE_SKIP_${PN} = "dev-so"
-
-RDEPENDS_${PN} = "bind dbus libldb libpam"
+PACKAGES =+ "libsss-sudo libsss-autofs"
+ALLOW_EMPTY_libsss-sudo = "1"
+ALLOW_EMPTY_libsss-autofs = "1"
+
+FILES_${PN}-dev += "${libdir}/sssd/modules/lib*.so"
+FILES_${PN} += "${base_libdir}/security/pam_sss*.so \
+ ${datadir}/dbus-1/system-services/*.service \
+ ${libdir}/krb5/* \
+ ${libdir}/ldb/* \
+ "
+FILES_libsss-autofs = "${libdir}/sssd/modules/libsss_autofs.so"
+FILES_libsss-sudo = "${libdir}/libsss_sudo.so"
+
+RDEPENDS_${PN} = "bind dbus libldb libpam libsss-sudo libsss-autofs"

--
Kai Kang
Wind River Linux


Re: raspberrypi0-2w

Joel Winarske
 


On Thu, Dec 2, 2021 at 7:08 AM safouane maaloul <maaloulsafouane@...> wrote:
Hello, I  writed a conf file  to get the raspberrypi0-2 to work in 32 mode to have the camera packages raspivid. It works just fine. But the problem I don't have wlan0 interface. I tried everything but I didn't succeed in getting to work. Here is my conf file:

#@TYPE: Machine
#@NAME: RaspberryPi0 2 Wifi Development Board
#@DESCRIPTION: Machine configuration for the RaspberryPi0 2 Wifi in 32 bits mode

include conf/machine/raspberrypi3.conf

MACHINEOVERRIDES := "${@'${MACHINEOVERRIDES}'
.replace(':${MACHINE}',':raspberrypi3:${MACHINE}')}"

MACHINE_EXTRA_RRECOMMENDS += "\
    linux-firmware-rpidistro-bcm43436 \
    linux-firmware-rpidistro-bcm43436s \
    bluez-firmware-rpidistro-bcm43430b0-hcd \
    linux-firmware-rpidistro-bcm43430 \
"




Best regards,

--
SAFOUANE MAALOUL




Re: raspberrypi0-2w

Khem Raj
 

On Thu, Dec 2, 2021 at 7:08 AM safouane maaloul
<maaloulsafouane@...> wrote:

Hello, I writed a conf file to get the raspberrypi0-2 to work in 32 mode to have the camera packages raspivid. It works just fine. But the problem I don't have wlan0 interface. I tried everything but I didn't succeed in getting to work. Here is my conf file:

#@TYPE: Machine
#@NAME: RaspberryPi0 2 Wifi Development Board
#@DESCRIPTION: Machine configuration for the RaspberryPi0 2 Wifi in 32 bits mode

include conf/machine/raspberrypi3.conf

MACHINEOVERRIDES := "${@'${MACHINEOVERRIDES}'
.replace(':${MACHINE}',':raspberrypi3:${MACHINE}')}"

MACHINE_EXTRA_RRECOMMENDS += "\
linux-firmware-rpidistro-bcm43436 \
linux-firmware-rpidistro-bcm43436s \
bluez-firmware-rpidistro-bcm43430b0-hcd \
linux-firmware-rpidistro-bcm43430 \
"
also add following to machine conf file.

RPI_KERNEL_DEVICETREE = " \
broadcom/bcm2710-rpi-zero-2.dtb \
"





Best regards,

--
SAFOUANE MAALOUL
maaloulsafouane@...




[nativesdk] compilation problem with nativesdk

mlalu
 

Hi everyone,

I'm trying to write a recipe to build openjdk-9 with the Yocto project dunfell.
I want to install the jre (the runtime environment of Java) on my target and install the jdk (the development toolkit of java) on my build machine and only on my build machine.

I succeeded to build openjdk and to install the jre on my target (I can run Java applications on my target).
The fetch/patch/configure/compile tasks are made on a .inc file included on my openjre-9.bb recipe which included only the install task.

Now, I want to install the jdk as part of the Yocto SDK to make it accessible on my build machine. So I created a opendjdk-9.bb recipe wich include my .inc file and added
BBCLASSEXTEND = "nativesdk" in the recipe with the install task.

I added " RDEPENDS_${PN} += "nativesdk-openjdk-9" on a nativesdk-packagegroup-sdk-host.bbappend

and I added TOOLCHAIN_HOST_TASK_append = " nativesdk-openjdk-9" on my image recipe.
Now my problem is that my recipe openjdk-9.bb doesn't compile, I have "Cannot find autoconf" error while compiling.
I don't understand why because the compilation task is described on the .inc file which is the same for the openjre-9.bb recipe (which works) and the openjdk-9.bb recipe (which doesn't work).
I hope you can help me to understand the "nativesdk" extension.

--
Maureen






This e-mail including any attachments may contain information which is privileged or confidential or constitute non-public information.It is to be conveyed only to the intended recipient(s). If you received this e-mail in error, please notify the sender immediately by e-mail or telephone and delete the e-mail  from your system without reading, copying or disclosing its contents to any other person. 


raspberrypi0-2w

safouane maaloul
 

Hello, I  writed a conf file  to get the raspberrypi0-2 to work in 32 mode to have the camera packages raspivid. It works just fine. But the problem I don't have wlan0 interface. I tried everything but I didn't succeed in getting to work. Here is my conf file:

#@TYPE: Machine
#@NAME: RaspberryPi0 2 Wifi Development Board
#@DESCRIPTION: Machine configuration for the RaspberryPi0 2 Wifi in 32 bits mode

include conf/machine/raspberrypi3.conf

MACHINEOVERRIDES := "${@'${MACHINEOVERRIDES}'
.replace(':${MACHINE}',':raspberrypi3:${MACHINE}')}"

MACHINE_EXTRA_RRECOMMENDS += "\
    linux-firmware-rpidistro-bcm43436 \
    linux-firmware-rpidistro-bcm43436s \
    bluez-firmware-rpidistro-bcm43430b0-hcd \
    linux-firmware-rpidistro-bcm43430 \
"




Best regards,

--
SAFOUANE MAALOUL


Re: downloads.yoctoproject.org down?

Andreas Müller
 

On Wed, Dec 1, 2021 at 10:00 PM Michael Halstead
<mhalstead@...> wrote:

downloads.yoctoproject.org is back online with additional redundancy.

The cause of the outage will take some time to investigate as the drive with the logs is not accessible currently.
Yes download worked for me. You saved my life for today :)

Thanks

Andreas


Re: downloads.yoctoproject.org down?

Michael Halstead
 

downloads.yoctoproject.org is back online with additional redundancy.

The cause of the outage will take some time to investigate as the drive with the logs is not accessible currently. 

On Wed, Dec 1, 2021 at 12:06 PM Andreas Müller <schnitzeltony@...> wrote:
On Wed, Dec 1, 2021 at 7:59 PM Steve Sakoman <steve@...> wrote:
>
> On Wed, Dec 1, 2021 at 8:45 AM Andreas Müller <schnitzeltony@...> wrote:
> >
> > Hi,
> >
> > Trying to install buildtools (dunfell) I get
> >
> > ./sources/openembedded-core/scripts/install-buildtools
> > INFO: Fetching buildtools installer
> > ERROR: Could not download file from
> > http://downloads.yoctoproject.org/releases/yocto/milestones/yocto-3.2_M1/buildtools/x86_64-buildtools-extended-nativesdk-standalone-3.1%2Bsnapshot-20200617.sh
> >
> > Has anybody a chance to help me not being killed :)
>
> Yes, some of the infrastructure is down right now.  Michael knows and
> is hard at work fixing the issue.
So there is hope

Thanks a lot all involved!

Andreas





--
Michael Halstead
Linux Foundation / Yocto Project
Systems Operations Engineer


Re: downloads.yoctoproject.org down?

Andreas Müller
 

On Wed, Dec 1, 2021 at 7:59 PM Steve Sakoman <steve@...> wrote:

On Wed, Dec 1, 2021 at 8:45 AM Andreas Müller <schnitzeltony@...> wrote:

Hi,

Trying to install buildtools (dunfell) I get

./sources/openembedded-core/scripts/install-buildtools
INFO: Fetching buildtools installer
ERROR: Could not download file from
http://downloads.yoctoproject.org/releases/yocto/milestones/yocto-3.2_M1/buildtools/x86_64-buildtools-extended-nativesdk-standalone-3.1%2Bsnapshot-20200617.sh

Has anybody a chance to help me not being killed :)
Yes, some of the infrastructure is down right now. Michael knows and
is hard at work fixing the issue.
So there is hope

Thanks a lot all involved!

Andreas


Re: downloads.yoctoproject.org down?

Steve Sakoman
 

On Wed, Dec 1, 2021 at 8:45 AM Andreas Müller <schnitzeltony@...> wrote:

Hi,

Trying to install buildtools (dunfell) I get

./sources/openembedded-core/scripts/install-buildtools
INFO: Fetching buildtools installer
ERROR: Could not download file from
http://downloads.yoctoproject.org/releases/yocto/milestones/yocto-3.2_M1/buildtools/x86_64-buildtools-extended-nativesdk-standalone-3.1%2Bsnapshot-20200617.sh

Has anybody a chance to help me not being killed :)
Yes, some of the infrastructure is down right now. Michael knows and
is hard at work fixing the issue.

Steve

Cheers,

Andreas



downloads.yoctoproject.org down?

Andreas Müller
 

Hi,

Trying to install buildtools (dunfell) I get

./sources/openembedded-core/scripts/install-buildtools
INFO: Fetching buildtools installer
ERROR: Could not download file from
http://downloads.yoctoproject.org/releases/yocto/milestones/yocto-3.2_M1/buildtools/x86_64-buildtools-extended-nativesdk-standalone-3.1%2Bsnapshot-20200617.sh

Has anybody a chance to help me not being killed :)

Cheers,

Andreas


[PATCH yocto-autobuilder-helper] scripts/run-docs-build: stop using the "transition" branch

Michael Opdenacker
 

No longer necessary now that the transition from DocBook to Sphinx is over

Signed-off-by: Michael Opdenacker <michael.opdenacker@...>
---
scripts/run-docs-build | 6 ------
1 file changed, 6 deletions(-)

diff --git a/scripts/run-docs-build b/scripts/run-docs-build
index 4451018..724d709 100755
--- a/scripts/run-docs-build
+++ b/scripts/run-docs-build
@@ -58,12 +58,6 @@ make clean
make publish
cp -r ./_build/final/* $outputdir

-cd $ypdocs
-git checkout transition
-make clean
-make publish
-cp -r ./_build/final/* $outputdir/
-
cd $ypdocs
git checkout master-next
make clean
--
2.25.1


[PATCH yocto-autobuilder-helper] scripts/run-docs-build: make all versions list releases known to master

Michael Opdenacker
 

This allows all versions of Bitbake and Yocto Project manuals
to see the manuals for the latest versions.

This also simplifies the release process, not having to update the
releases.rst file for all releases every time a new release is made.

Note that such synchronization is already done for the
switchers.js file (but in a different way). This way, advertised
releases are in sync with switchers.js.

Signed-off-by: Michael Opdenacker <michael.opdenacker@...>
---
scripts/run-docs-build | 5 +++++
1 file changed, 5 insertions(+)

diff --git a/scripts/run-docs-build b/scripts/run-docs-build
index 4451018..5d6d24a 100755
--- a/scripts/run-docs-build
+++ b/scripts/run-docs-build
@@ -39,8 +39,11 @@ cp -r ./_build/final/* $outputdir/bitbake/next
# A decision was made to keep updating all the Sphinx generated docs for the moment,
# even the ones corresponding to no longer supported releases
# https://lists.yoctoproject.org/g/docs/message/2193
+# We copy the releases.rst file from master so that all versions of the docs
+# see the latest releases.
for branch in 1.46 1.48 1.50 1.52; do
git checkout $branch
+ git checkout master doc/releases.rst
make clean
make publish
mkdir $outputdir/bitbake/$branch
@@ -76,6 +79,7 @@ cp -r ./_build/final/* $outputdir/next
for branch in dunfell gatesgarth hardknott honister; do
cd $ypdocs
git checkout $branch
+ git checkout master documentation/releases.rst
make clean
make publish
mkdir $outputdir/$branch
@@ -97,6 +101,7 @@ for tag in $(git tag --list 'yocto-*'); do
if [ "$tag" = "yocto-3.3" ] || [ "$tag" = "yocto-3.4" ]; then
git am "${scriptdir}/${tag}/0001-conf-update-for-release.patch"
fi
+ git checkout master documentation/releases.rst
make clean
make publish
version=$(echo $tag | cut -c7-)
--
2.25.1


Re: [OE-core] Yocto Project Status WW48`21

Alexander Kanavin
 

On Tue, 30 Nov 2021 at 21:40, Stephen Jolley <sjolley.yp.pm@...> wrote:
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.
Patches in the Pending State: 412 (32%) [last week 422 (33%)]

I went ahead and made a list of top 10 'owners of pending patches'. I have to stress that this is absolutely not a 'wall of shame' or anything negative: these patches are in itself significant work, and sending patches upstream - and crucially, rebasing, fixing CI fails and following up on upstream feedback - is a significant effort on top, and when yocto project itself needs to move forward and company management is asking to deliver a product at the same time, the time for upstreaming may simply not be there. So  please keep these numbers in mind and try to avoid making them bigger.

109 Khem Raj
29 Richard Purdie
24 Alexander Kanavin
15 unknown
15 Ross Burton
15 Robert Yang
11 Hongxu Jia
10 Martin Jansa
8 Joe Slater
8 Chen Qi

Another interesting statistic is that of 108 people with pending patches, 80 own only one or two patches.

Alex


[meta-mingw] [PATCH] mingw32-common.inc: remove qemu-usermode from MACHINE_FEATURES

Alexander Kanavin
 

This is prompted by upcoming exe_wrapper setting in meson, which
is using qemu, subject to qemu-usermode, and so won't work for mingw
executables.

Signed-off-by: Alexander Kanavin <alex@...>
---
conf/machine-sdk/include/mingw32-common.inc | 2 ++
1 file changed, 2 insertions(+)

diff --git a/conf/machine-sdk/include/mingw32-common.inc b/conf/machine-sdk/include/mingw32-common.inc
index 6c43fc9..1ee6cc4 100644
--- a/conf/machine-sdk/include/mingw32-common.inc
+++ b/conf/machine-sdk/include/mingw32-common.inc
@@ -52,3 +52,5 @@ GCCPIE:mingw32 = ""
# wine and wineserver are required to test MinGW SDKs
HOSTTOOLS += "${@'wine wineserver' if (bb.utils.contains_any('IMAGE_CLASSES', 'testsdk', True, False, d) or any(x in (d.getVar("BBINCLUDED") or "") for x in ["testsdk.bbclass"])) else ''}"

+# wine may work to run mingw executables, but qemu certainly isn't
+MACHINE_FEATURES_BACKFILL_CONSIDERED:append = " qemu-usermode"
--
2.20.1


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

Teoh, Jay Shen
 

Hi everyone,

Intel and WR YP QA is planning for QA execution for YP build yocto-3.4.1.rc1. We are planning to execute following tests for this cycle:

OEQA-manual tests for following module:
1. OE-Core
2. BSP-hw

Runtime auto test for following platforms:
1. MinnowTurbot 32-bit
2. Coffee Lake
3. NUC 7
4. NUC 6
5. Edgerouter
6. Beaglebone

ETA for completion next Monday, Dec 6.

Thanks,
Jay

-----Original Message-----
From: qa-build-notification@... <qa-build-
notification@...> On Behalf Of Richard Purdie
Sent: Wednesday, 1 December, 2021 3:06 AM
To: <yocto@...> <yocto@...>
Cc: qa-build-notification <qa-build-notification@...>
Subject: [qa-build-notification] QA notification for completed autobuilder build
(yocto-3.4.1.rc1)

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


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


Build hash information:

bitbake: 44a83b373e1fc34c93cd4a6c6cf8b73b230c1520
meta-agl: 83c5764a38902c6d17f106ea545533192ebd46fe
meta-arm: 55ae0eb1a6c210e6e87f5a553a1ebbb7dcc7a725
meta-aws: c92344938ab4d37de8bd8b799186dbbe3019a069
meta-gplv2: f04e4369bf9dd3385165281b9fa2ed1043b0e400
meta-intel: d0f1c1ebfd9b7fe8d22c6a62208f78bccc6f3bf6
meta-mingw: f5d761cbd5c957e4405c5d40b0c236d263c916a8
meta-openembedded: f31b9854b13e46cb74569538a33c36730c00c695
oecore: 70384dd958c57d1da924a66cffa35f80eb60d4b0
poky: b53230c08d9f02ecaf35b4f0b70512abbf10ae11



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







swupdate update failure.<error logs> #swupdate

vishal.rana118@...
 

Hi Team,
 
Recently, I am able to integrate SWUPDATE on my Linux target.
After building successfully, I tried to do a local update using SD_CARD.
 
Getting below error after doing the update. Please guide me on how to resolve this.
 
/////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
Starting swupdate ...
dd: writing to '/dev/fb0': No space left on device
8001+0 records in
8000+0 records out
4096000 bytes (4.1 MB, 3.9 MiB) copied, 0.0848937 s, 48.2 MB/s
/etc/rc5.d/S99MyBoard: line 5: /HelloWorld: No such file or directory
Swupdate v2018.3.0

Licensed under GPLv2. See source distribution for detailed copyright notices.

[TRACE] : SWUPDATE running :  [start_swupdate_subprocess] : Started webserver with pid 581 and fd 4
[TRACE] : SWUPDATE running :  [start_swupdate_subprocess] : Started suricatta with pid 582 and fd 5
Running on imx6s-comgx-MyBoard Revision 1.0
Registered handlers:
        archive
        tar
        raw
        rawfile
        lua
        shellscript
        preinstall
        postinstall
        remote
        uboot
        bootloader
[TRACE] : SWUPDATE running :  [listener_create] : creating socket at /tmp/swupdateprog
[TRACE] : SWUPDATE running :  [network_initializer] : Main loop Daemon
[TRACE] : SWUPDATE running :  [listener_create] : creating socket at /tmp/sockinstctrl
[TRACE] : SWUPDATE running :  [suricatta_configdata_settings] : Identify for configData: board --> imx6s-comgx-MyBoard

Mongoose web server version 6.11 with pid 581 started on port(s) 8080 with web root [/www] and API v2
Cannot parse config file '/etc/fw_env.config': No such file or directory
[ERROR] : SWUPDATE failed [0] ERROR bootloader/uboot.c : bootloader_env_get : 93 : Error: environment not initialized, No such file or directory

[INFO ] : SWUPDATE running :  [read_state] : Key 'ustate' not found in Bootloader's environment.

[TRACE] : SWUPDATE running :  [get_state] : Read state=4 from persistent storage.

[DEBUG] : SWUPDATE running :  [server_handle_initial_state] : State is STATE_OK/STATE_NOT_AVAILABLE, nothing to report to server.

[TRACE] : SWUPDATE running :  [start_suricatta] : Server initialized, entering suricatta main loop.

[DEBUG] : SWUPDATE running :  [server_get_device_info] : Getting information for device 'imx6s-comgx-MyBoard'

[DEBUG] : SWUPDATE running :  [channel_set_options] : cURL's low download speed timeout is disabled, this is most probably not what you want. Adapted it to 300s instead.

[DEBUG] : SWUPDATE running :  [channel_get] : Trying to GET http://varupdate:8080/default/controller/v1/imx6s-comgx-MyBoard
Trying to connect to SWUpdate...
Connected to SWUpdate via /tmp/swupdateprog
* Could not resolve host: varupdate
* Closing connection 0
[ERROR] : SWUPDATE failed [0] ERROR corelib/channel_curl.c : channel_get : 955 : Channel get operation failed (6): 'Couldn't resolve host name'


[TRACE] : SWUPDATE running :  [server_send_target_data] : KEYVALUE= "board": "imx6s-comgx-MyBoard" board imx6s-comgx-MyBoard
[TRACE] : SWUPDATE running :  [server_send_target_data] : CONFIGDATA= "board": "imx6s-comgx-MyBoard"
[TRACE] : SWUPDATE running :  [server_send_target_data] : URL=http://varupdate:8080/default/controller/v1/imx6s-comgx-MyBoard/configData JSON={ "id": "", "time": "20211129T102651", "status": { "result": { "finished": "success" }, "execution": "closed", "details" : [ "" ] }, "data" : {  "board": "imx6s-comgx-MyBoard" } }
[DEBUG] : SWUPDATE running :  [channel_set_options] : cURL's low download speed timeout is disabled, this is most probably not what you want. Adapted it to 300s instead.

* Could not resolve host: varupdate
* Closing connection 1
[ERROR] : SWUPDATE failed [0] ERROR corelib/channel_curl.c : channel_put_method : 659 : Channel put operation failed (6): 'Couldn't resolve host name'

[DEBUG] : SWUPDATE running :  [suricatta_wait] : Sleeping for 3600 seconds.
 
 
 
///////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////////
 
Thanks in advance .


Yocto Project 3.1.12 (hardknott-23.0.12) is Released

Lee Chee Yang
 

Hello,

 

We are pleased to announce the Yocto Project 3.1.12 (dunfell-23.0.12) Release is now available for download.

 

http://downloads.yoctoproject.org/releases/yocto/yocto-3.1.12/poky-dunfell-23.0.12.tar.bz2

http://mirrors.kernel.org/yocto/yocto/yocto-3.1.12/poky-dunfell-23.0.12.tar.bz2

 

A gpg signed version of these release notes is available at:

 

http://downloads.yoctoproject.org/releases/yocto/yocto-3.1.12/RELEASENOTES

 

Full Test Report:

 

http://downloads.yoctoproject.org/releases/yocto/yocto-3.1.12/testreport.txt

 

Thank you for everyone's contributions to this release.

 

Chee Yang Lee chee.yang.lee@...

Yocto Project Build and Release


 

- --------------------------

yocto-3.1.12 Release Notes

- --------------------------

 

 

- --------------------------

Repositories/Downloads

- --------------------------

 

Repository Name: poky

Repository Location: https://git.yoctoproject.org/git/poky

Branch: dunfell

Tag: yocto-3.1.12

Git Revision: 0839888394a6e42e96f9f0d201376eb38bc79b24

Release Artefact: poky-dunfell-23.0.12

sha: 6d8c70cb17100d6dd5056b8dcae7027833c8f9a53006fd5b651bf9a56494eb01

Download Locations:

http://downloads.yoctoproject.org/releases/yocto/yocto-3.1.12/poky-dunfell-23.0.12.tar.bz2

http://mirrors.kernel.org/yocto/yocto/yocto-3.1.12/poky-dunfell-23.0.12.tar.bz2

 

Repository Name: openembedded-core

Repository Location: https://git.openembedded.org/openembedded-core

Branch: dunfell

Tag: yocto-3.1.12

Git Revision: 44b1970c40e9d73f6e63fb10cdc55837a26f5921

Release Artefact: oecore-dunfell-23.0.12

sha: 2ddef2bbcd156c971b6ce8a05eee64ddc51237d9ad2e17186d8afb840c31e7f9

Download Locations:

http://downloads.yoctoproject.org/releases/yocto/yocto-3.1.12/oecore-dunfell-23.0.12.tar.bz2

http://mirrors.kernel.org/yocto/yocto/yocto-3.1.12/oecore-dunfell-23.0.12.tar.bz2

 

Repository Name: meta-mingw

Repository Location: https://git.yoctoproject.org/git/meta-mingw

Branch: dunfell

Tag: yocto-3.1.12

Git Revision: 524de686205b5d6736661d4532f5f98fee8589b7

Release Artefact: meta-mingw-dunfell-23.0.12

sha: 7a3e2f9922d9677c2357221d00f0e92a54feb7170f5df079527be9654d61b869

Download Locations:

http://downloads.yoctoproject.org/releases/yocto/yocto-3.1.12/meta-mingw-dunfell-23.0.12.tar.bz2

http://mirrors.kernel.org/yocto/yocto/yocto-3.1.12/meta-mingw-dunfell-23.0.12.tar.bz2

 

Repository Name: meta-gplv2

Repository Location: https://git.yoctoproject.org/git/meta-gplv2

Branch: dunfell

Tag: yocto-3.1.12

Git Revision: 60b251c25ba87e946a0ca4cdc8d17b1cb09292ac

Release Artefact: meta-gplv2-dunfell-23.0.12

sha: b6e4f8d9270849154f37db1c5b64febc5339f421caae877efbe6c32873307aa3

Download Locations:

http://downloads.yoctoproject.org/releases/yocto/yocto-3.1.12/meta-gplv2-dunfell-23.0.12.tar.bz2

http://mirrors.kernel.org/yocto/yocto/yocto-3.1.12/meta-gplv2-dunfell-23.0.12.tar.bz2

 

Repository Name: bitbake

Repository Location: https://git.openembedded.org/bitbake

Branch: dunfell

Tag: yocto-3.1.12

Git Revision: c0348de8121c3a842bf44906f7e2f79e93f7275b

Release Artefact: bitbake-dunfell-23.0.12

sha: d87dd125bb9715ccc259d1ecbc8278a1ed48c3f834eee9bcdb569e7c296e9d2d

Download Locations:

http://downloads.yoctoproject.org/releases/yocto/yocto-3.1.12/bitbake-dunfell-23.0.12.tar.bz2

http://mirrors.kernel.org/yocto/yocto/yocto-3.1.12/bitbake-dunfell-23.0.12.tar.bz2

 

Repository Name: yocto-docs

Repository Location: https://git.yoctoproject.org/git/yocto-docs

Branch: dunfell

Tag: yocto-3.1.12

Git Revision: f1cd4d8ae58037609556de51b33a4dbeab7f45ff

 

- ----------------

Contributors

- ----------------

 

Alexander Kanavin

Alexandre Belloni

Andrej Valek

Armin Kuster

Bruce Ashfield

Chandana kalluri

Chris Laplante

Christian Eggers

Claudius Heine

Daniel McGregor

Hongxu Jia

Jon Mason

Jose Quaresma

Joshua Watt

Justin Bronder

Kai Kang

Khem Raj

Marco Felsch

Marek Vasut

Mark Hatle

Markus Volk

Michael Halstead

Mike Crowe

Mingli Yu

Minjae Kim

Oleksandr Kravchuk

Pavel Zhukov

Ralph Siemsen

Ranjitsinh Rathod

Richard Purdie

Robert P. J. Day

Ross Burton

Sakib Sajal

Saloni

Stefano Babic

Steve Sakoman

Teoh Jay Shen

Tom Pollard

Visa Hankala

Wang Mingyu

William A. Kennington III

sana kazi

 

- ---------------

Known Issues

- ---------------

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

 

- ---------------

Security Fixes

- ---------------

curl: Whitelist CVE-2021-22897

ffmpeg: Add fix for CVEs

openssh: Fix CVE-2021-28041

vim: fix CVE-2021-3778

vim: Backport fix for CVE-2021-3770

tar: ignore node-tar CVEs

squashfs-tools: fix CVE-2021-40153

nettle: Security fix for CVE-2021-20305

curl: Fix CVE-2021-22946 and CVE-2021-22947, whitelist CVE-2021-22945

nettle: Security fix for CVE-2021-3580

qemu: fix CVE-2021-3682

qemu: Security fix for CVE-2020-28916

qemu: Security fix for CVE-2020-27617

qemu: Security fix CVE-2020-12829

libsndfile: Security fix for CVE-2021-3246

apr: Security fix for CVE-2021-35940

libgcrypt: Security fix CVE-2021-33560

 

 

- ---------------

Fixes

- ---------------

connman: add CVE_PRODUCT

tar: filter CVEs using vendor name

build-appliance-image: Update to dunfell head revision

mirrors: Add kernel.org sources mirror for downloads.yoctoproject.org

selftest/reproducible: add webkitgtk back to exclusion list for dunfell

reproducible_build: Remove BUILD_REPRODUCIBLE_BINARIES checking

sstate: Avoid deploy_source_date_epoch sstate when unneeded

sstate: Ensure SDE is accounted for in package task timestamps

sstate: another fix for touching files inside pseudo

mirrors: Add uninative mirror on kernel.org

piglit: upgrade to latest revision

pseudo: Add fcntl64 wrapper

pseudo: Add in ability to flush database with shutdown request

linunistring: Add missing gperf-native dependency

python3-magic: add missing DEPENDS

python3-magic: add the missing rdepends

webkitgtk: Fix reproducibility in minibrowser

oeqa: reproducible: Fix test not producing diffs

documentation: prepare for 3.1.12 release

ref-system-requirements.rst: Add Fedora 34 to list of supported distros

ref-system-requirements.rst: Add Debian 11 to list of supported distros

poky.conf: Bump version for 3.1.12 release

bitbake: fetch/wget: Add timeout for checkstatus calls (30s)

meta/scripts: Manual git url branch additions

meta: Add explict branch to git SRC_URIs, handle github url changes

scripts/convert-srcuri: Backport SRC_URI conversion script from master branch

bitbake: tests/fetch: Update pcre.org address after github changes

bitbake: tests/fetch: Update github urls

bitbake: tests/fetch2: Fix quoting warning

bitbake: fetch/git: Handle github dropping git:// support

tzdata: update to 2021e

ca-certificates: update 20210119 -> 20211016

wireless-regdb: upgrade to 2021.08.28

linux-firmware: upgrade to 20210919

git: Fix determinism issue

stress-ng: improve reproducibility

stress-ng: convert to git, website is down

waffle: old website is down, update to new project URLs

mirrors.bbclass: remove dead infozip mirrors

oeqa/runtime/parselogs: modified drm error in common errors list

oeqa/runtime: search sys.path explicitly for modules

oeqa/runtime: load modules using importlib

testimage: fix unclosed testdata file

reproducible_build: Drop obsolete sstate workaround

oe/utils: log exceptions in ThreadedWorker functions

license.bbclass: implement ast.NodeVisitor.visit_Constant

oe/license: implement ast.NodeVisitor.visit_Constant

bitbake.conf: Add gpg-agent as a host tool

base: Use repr() for printing exceptions

base: Clean up unneeded len() calls

sstate: don't silently handle all exceptions in sstate_checkhashes

devtool: fix modify with patches in override directories

sstate: fix touching files inside pseudo

vim: fix 2021-3796

poky.yaml: fedora33: add missing pkgs

selftest/reproducible: adjust exclusion list for dunfell

classes/reproducible_build: Use atomic rename for SDE file

reproducible_build: Work around caching issues

rpm: Deterministically set vendor macro entry

poky.conf: Add debian 11 as a supported distro

poky.conf: Add fedora 34 as a supported distro

uninative: Upgrade to 3.4

target/ssh.py: add HostKeyAlgorithms option to test commands

python3: Add a fix for a make install race

libnewt: Use python3targetconfig to fix reproducibility issue

libxml2: Use python3targetconfig to fix reproducibility issue

externalsrc: Fix a source date epoch race in reproducible builds

externalsrc: Work with reproducible_build

gobject-introspection: Don't write $HOME into scripts

libtool: Allow libtool-cross to reproduce

libtool: Fix lto option passing for reproducible builds

util-linux: Fix reproducibility

gnupg: Be deterministic about sendmail

mesa: Ensure megadrivers runtime mappings are deterministic

package: Ensure pclist files are deterministic and don't use full paths

uninative: Upgrade to 3.3, support glibc 2.34

uninative: Improve glob to handle glibc 2.34

nativesdk-pseudo: Fix to work with glibc 2.34 systems

pseudo: Update with fcntl and glibc 2.34 fixes

pseudo: Fix to work with glibc 2.34 systems

util-linux: disable raw

gpgme: Use glibc provided closefrom API when available

m4: Do not use SIGSTKSZ

gcc: fix missing dependencies for selftests

libpsl: Add config knobs for runtime/builtin conversion choices

patch.bbclass: when the patch fails show more info on the fatal error

oeqa/selftest/sstatetests: fix typo ware -> were

rng-tools: add systemd-udev-settle wants to service

scriptutils.py: Add check before deleting path

binutils: Fix a missing break in case statement

oeqa/manual: Fix no longer valid URLs

multilib: Avoid sysroot race issues when multilib enabled

weston: Use systemd notify,

e2fsprogs: upgrade to 1.45.7

linux-yocto/5.4: update to v5.4.153

bitbake: fetch2/git: Use os.rename instead of mv

bitbake: fetch2/git: Avoid races over mirror tarball creation

bitbake: hashserv: let asyncio discover the running loop

bitbake: bitbake: correct deprecation warning in process.py

bitbake: bitbake: adjust parser error check for python 3.10 compatibility

bitbake: bitbake: do not import imp in layerindexlib

bitbake: bitbake: fix regexp deprecation warnings

bitbake: bitbake: correct the collections vs collections.abc deprecation

bitbake: compat.py: remove file since it no longer actually implements anything

bitbake: test/fetch: Update urls to match upstream branch name changes

glew: Stop polluting /tmp during builds

oeqa/buildproject: Ensure temp directories are cleaned up

oeqa/selftest/gotoolchain: Fix temp file cleanup

rm_work.bbclass: Fix for files starting with -

libc_package/buildstats: Fix python regex quoting warnings

oeqa/qemurunner: Use oe._exit(), not sys.exit()

pybootchart: Avoid divide by zero

libsamplerate0: Set correct soname for 0.1.9

bzip2: Update soname for libbz2 1.0.8

common-licenses: add "Unlicense" license file

systemd: Add fix for systemd-networkd crash during free

mtd-utils: upgrade to 2.1.3

bitbake: build/msg: Cleanup verbose option handling

bitbake: cookerdata: Show a readable error for invalid multiconfig name

bitbake: bitbake-worker: Improve error handling

bitbake: cookerdata: Show error for no BBLAYERS in bblayers.conf

bitbake: cookerdata: Improve missing core layer error message

bitbake: data_smart: Improve error display for handled exceptions

bitbake: build: Catch and error upon circular task references

bitbake: build: Avoid duplicating logs in verbose mode

bitbake: process: Don't include logs in error message if piping them

bitbake: build: Handle SystemExit in python tasks correctly

bitbake: build: Match markup to real function name

bitbake: bitbake: bitbake-layers: add skip reason to output

bitbake: ui/taskexp: Fix to work with empty build directories

bitbake: ui/taskexp: Improve startup exception handling

bitbake: server: Fix early parsing errors preventing zombie bitbake

libsoup-2.4: remove obsolete intltool dependency

testimage: symlink the task log and qemu console log to tmp/log/oeqa

wic: keep rootfs_size as integer

core-image-sato: Fix runqemu error for qemuarmv5

Update mailing list address

bash: Ensure deterministic build

useradd: Ensure preinst data is expanded correctly in pkgdata

rpm: Handle proper return value to avoid major issues

iputils: Fix regression of arp table update

bitbake: tests/fetch2: Use our own git server for dtc test repo


[meta-rockchip][PATCH] README: Add intstructions to add patch template

Khem Raj
 

Signed-off-by: Khem Raj <raj.khem@...>
---
README | 16 +++++++++++++---
1 file changed, 13 insertions(+), 3 deletions(-)

diff --git a/README b/README
index cec1b53..cc63d0a 100644
--- a/README
+++ b/README
@@ -45,10 +45,20 @@ Maintenance:
https://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines
https://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded

- For example, to send your most recent commit (i.e. just one patch),
+ Please send changes to the yocto mailing list with [meta-rockchip] in the subject line,
+ cc'ing the maintainer.
+
+ This can be configured within the repository with following commands:
+
+ git config sendemail.to yocto@...
+ git config sendemail.cc twoerner@...
+ git config format.subjectprefix "meta-rockchip] [PATCH"
+
+ Then, to send your most recent commit (i.e. just one patch),
please use something like:
- git format-patch -M --subject-prefix="meta-rockchip][PATCH" HEAD^
- git send-email --to yocto@... --cc twoerner@... <your patch file>
+
+ git format-patch -M -1
+ git send-email <your patch file>

Maintainer:
----------
--
2.34.1

2381 - 2400 of 57809