date:20210419

Re: [OE-core] [PATCH 08/10] linux-yocto/5.10: update to v5.10.30

2021-04-19 Thread Bruce Ashfield

Richard already reported these via IRC this morning.

No need to open a bug for them, I've already taken care of things.

Bruce

On Mon, Apr 19, 2021 at 11:06 PM Saini, Naveen Kumar
 wrote:
>
> [SWAT]
>
> Kernel config warnings  for 'n1sdp' machine from meta-arm build:
> https://autobuilder.yoctoproject.org/typhoon/#/builders/113/builds/911/steps/12/logs/stdio
>
> WARNING: linux-yocto-5.10.30+gitAUTOINC+b7125842b7_8465e471f5-r0 
> do_kernel_configcheck: [kernel config]: specified values did not make it into 
> the kernel's final configuration:
>
> [NOTE]: 'CONFIG_ACPI_APEI_PCIEAER' last val (y) and .config val (n) do 
> not match
> [INFO]: CONFIG_ACPI_APEI_PCIEAER : n
> [INFO]: raw config text:
>
> config ACPI_APEI_PCIEAER
> bool "APEI PCIe AER logging/recovering support"
> depends on ACPI_APEI && PCIEAER && ACPI
> help
>   PCIe AER errors may be reported via APEI firmware first 
> mode.
>   Turn on this option to enable the corresponding support.
>
> Config 'ACPI_APEI_PCIEAER' has the following Direct dependencies 
> (ACPI_APEI_PCIEAER=n):
> ACPI_APEI(=y) && PCIEAER(=n) && ACPI(=y)
> Parent dependencies are:
>  PCIEAER [n] ACPI [y] ACPI_APEI [y]
> [INFO]: config 'CONFIG_ACPI_APEI_PCIEAER' was set, but it wasn't 
> assignable, check (parent) dependencies
>
>
> [NOTE]: 'CONFIG_BT_HCIBTUSB' last val (m) and .config val (n) do not match
> [INFO]: CONFIG_BT_HCIBTUSB : n
> [INFO]: raw config text:
>
> config BT_HCIBTUSB
> tristate "HCI USB driver"
> select BT_INTEL
> depends on USB && BT && NET
> help
>   Bluetooth HCI USB driver.
>   This driver is required if you want to use Bluetooth 
> devices with
>   USB interface.
>
>   Say Y here to compile support for Bluetooth USB devices 
> into the
>   kernel or say M to compile it as module (btusb).
>
> Config 'BT_HCIBTUSB' has the following Direct dependencies 
> (BT_HCIBTUSB=n):
> USB(=y) && BT(=n) && NET(=y)
> Parent dependencies are:
>  BT [n] USB [y] NET [y]
> [INFO]: config 'CONFIG_BT_HCIBTUSB' was set, but it wasn't assignable, 
> check (parent) dependencies
>
>
> [NOTE]: 'CONFIG_BT_HCIUART' last val (m) and .config val (n) do not match
> [INFO]: CONFIG_BT_HCIUART : n
> [INFO]: raw config text:
>
> config BT_HCIUART
> tristate "HCI UART driver"
> depends on (SERIAL_DEV_BUS || !SERIAL_DEV_BUS) && (NVMEM || 
> !NVMEM) && TTY && BT && NET
> help
>   Bluetooth HCI UART driver.
>   This driver is required if you want to use Bluetooth 
> devices with
>   serial port interface. You will also need this driver if 
> you have
>   UART based Bluetooth PCMCIA and CF devices like Xircom 
> Credit Card
>   adapter and BrainBoxes Bluetooth PC Card.
>
>   Say Y here to compile support for Bluetooth UART devices 
> into the
>   kernel or say M to compile it as module (hci_uart).
>
> Config 'BT_HCIUART' has the following Direct dependencies 
> (BT_HCIUART=n):
> SERIAL_DEV_BUS(=y) || !SERIAL_DEV_BUS(=y) (=y) && NVMEM(=y) 
> || !NVMEM(=y) (=y) && TTY(=y) && BT(=n) && NET(=y)
> Parent dependencies are:
>  BT [n] NVMEM [y] TTY [y] NET [y] SERIAL_DEV_BUS [y]
> [INFO]: config 'CONFIG_BT_HCIUART' was set, but it wasn't assignable, 
> check (parent) dependencies
>
>
> [NOTE]: 'CONFIG_BT_HCIUART_LL' last val (y) and .config val (n) do not 
> match
> [INFO]: CONFIG_BT_HCIUART_LL : n
> [INFO]: raw config text:
>
> config BT_HCIUART_LL
> bool "HCILL protocol support"
> select BT_HCIUART_H4
> depends on BT_HCIUART_SERDEV && BT && NET
> help
>   HCILL (HCI Low Level) is a serial protocol for communication
>   between Bluetooth device and host. This protocol is 
> required for
>   serial Bluetooth devices that are based on Texas 
> Instruments'
>   BRF chips.
>
>   Say Y here to compile support for HCILL protocol.
>
> Config 'BT_HCIUART_LL' has the following Direct dependencies 
> (BT_HCIUART_LL=n):
> BT_HCIUART_SERDEV(=n) && BT(=n) && NET(=y)
> Parent dependencies are:
>  BT_HCIUART_SERDEV [n] BT [n] NET [y]
> [INFO]: config 'CONFIG_BT_HCIUART_LL' was set, but it wasn't assignable, 
> check (parent) dependencies
>
>
> [NOTE]: 'CONFIG_BT_HCIUART_BCM' last val (y) and .config val (n) do not 
> match
> [INFO]: CONFIG_BT_HCIUART_BCM : n
> [INFO]: raw config text:
>
> config BT_HCIUART_BCM

Re: [OE-core] [PATCH 10/10] linux-yocto/5.4: update to v5.4.112

2021-04-19 Thread Naveen Saini

[SWAT]

Kernel config warnings  for 'juno' machine from meta-arm build:
https://autobuilder.yoctoproject.org/typhoon/#/builders/113/builds/911/steps/17/logs/stdio

WARNING: linux-yocto-5.4.112+gitAUTOINC+5017570a13_5f54b437b6-r0 
do_kernel_configcheck: [kernel config]: specified values did not make it into 
the kernel's final configuration:

[NOTE]: 'CONFIG_BT_HCIBTUSB' last val (m) and .config val (n) do not match
[INFO]: CONFIG_BT_HCIBTUSB : n 
[INFO]: raw config text:

config BT_HCIBTUSB
tristate "HCI USB driver"
select BT_INTEL
depends on USB && BT && NET
help
  Bluetooth HCI USB driver.
  This driver is required if you want to use Bluetooth devices 
with
  USB interface.
  
  Say Y here to compile support for Bluetooth USB devices into 
the
  kernel or say M to compile it as module (btusb).

Config 'BT_HCIBTUSB' has the following Direct dependencies 
(BT_HCIBTUSB=n):
USB(=y) && BT(=n) && NET(=y)
Parent dependencies are:
 BT [n] USB [y] NET [y]
[INFO]: config 'CONFIG_BT_HCIBTUSB' was set, but it wasn't assignable, 
check (parent) dependencies


[NOTE]: 'CONFIG_BT_HCIUART' last val (m) and .config val (n) do not match
[INFO]: CONFIG_BT_HCIUART : n 
[INFO]: raw config text:

config BT_HCIUART
tristate "HCI UART driver"
depends on (SERIAL_DEV_BUS || !SERIAL_DEV_BUS) && (NVMEM || 
!NVMEM) && TTY && BT && NET
help
  Bluetooth HCI UART driver.
  This driver is required if you want to use Bluetooth devices 
with
  serial port interface. You will also need this driver if you 
have
  UART based Bluetooth PCMCIA and CF devices like Xircom Credit 
Card
  adapter and BrainBoxes Bluetooth PC Card.
  
  Say Y here to compile support for Bluetooth UART devices into 
the
  kernel or say M to compile it as module (hci_uart).

Config 'BT_HCIUART' has the following Direct dependencies 
(BT_HCIUART=n):
SERIAL_DEV_BUS(=y) || !SERIAL_DEV_BUS(=y) (=y) && NVMEM(=y) || 
!NVMEM(=y) (=y) && TTY(=y) && BT(=n) && NET(=y)
Parent dependencies are:
 BT [n] TTY [y] NET [y] NVMEM [y] SERIAL_DEV_BUS [y]
[INFO]: config 'CONFIG_BT_HCIUART' was set, but it wasn't assignable, check 
(parent) dependencies


[NOTE]: 'CONFIG_BT_HCIUART_LL' last val (y) and .config val (n) do not match
[INFO]: CONFIG_BT_HCIUART_LL : n 
[INFO]: raw config text:

config BT_HCIUART_LL
bool "HCILL protocol support"
select BT_HCIUART_H4
depends on BT_HCIUART_SERDEV && BT && NET
help
  HCILL (HCI Low Level) is a serial protocol for communication
  between Bluetooth device and host. This protocol is required 
for
  serial Bluetooth devices that are based on Texas Instruments'
  BRF chips.
  
  Say Y here to compile support for HCILL protocol.

Config 'BT_HCIUART_LL' has the following Direct dependencies 
(BT_HCIUART_LL=n):
BT_HCIUART_SERDEV(=n) && BT(=n) && NET(=y)
Parent dependencies are:
 BT [n] BT_HCIUART_SERDEV [n] NET [y]
[INFO]: config 'CONFIG_BT_HCIUART_LL' was set, but it wasn't assignable, 
check (parent) dependencies


[NOTE]: 'CONFIG_BT_HCIUART_BCM' last val (y) and .config val (n) do not 
match
[INFO]: CONFIG_BT_HCIUART_BCM : n 
[INFO]: raw config text:

config BT_HCIUART_BCM
bool "Broadcom protocol support"
select BT_HCIUART_H4
select BT_BCM
depends on BT_HCIUART && BT_HCIUART_SERDEV && (!ACPI || 
SERIAL_DEV_CTRL_TTYPORT) && GPIOLIB && BT && NET
help
  The Broadcom protocol support enables Bluetooth HCI over 
serial
  port interface for Broadcom Bluetooth controllers.
  
  Say Y here to compile support for Broadcom protocol.

Config 'BT_HCIUART_BCM' has the following Direct dependencies 
(BT_HCIUART_BCM=n):
BT_HCIUART(=n) && BT_HCIUART_SERDEV(=n) && !ACPI(=y) || 
SERIAL_DEV_CTRL_TTYPORT(=y) (=y) && GPIOLIB(=y) && BT(=n) && NET(=y)
Parent dependencies are:
 SERIAL_DEV_CTRL_TTYPORT [y] BT [n] NET [y] BT_HCIUART_SERDEV [n] 
BT_HCIUART [n] ACPI [y] GPIOLIB [y]
[INFO]: config 'CONFIG_BT_HCIUART_BCM' was set, but it wasn't assignable, 
check (parent) dependencies


[NOTE]: 'CONFIG_LEGACY_PTY_COUNT' last val (16) and .config val (n) do not 
match
[INFO]: CONFIG_LEGACY_PTY_COUNT : n 
[INFO]: raw config text:

config LEGACY_PTY_COUNT
int "Maximum number of legacy

Re: [OE-core] [PATCH 08/10] linux-yocto/5.10: update to v5.10.30

2021-04-19 Thread Naveen Saini

[SWAT]

Kernel config warnings  for 'n1sdp' machine from meta-arm build:
https://autobuilder.yoctoproject.org/typhoon/#/builders/113/builds/911/steps/12/logs/stdio

WARNING: linux-yocto-5.10.30+gitAUTOINC+b7125842b7_8465e471f5-r0 
do_kernel_configcheck: [kernel config]: specified values did not make it into 
the kernel's final configuration:

[NOTE]: 'CONFIG_ACPI_APEI_PCIEAER' last val (y) and .config val (n) do not 
match
[INFO]: CONFIG_ACPI_APEI_PCIEAER : n 
[INFO]: raw config text:

config ACPI_APEI_PCIEAER
bool "APEI PCIe AER logging/recovering support"
depends on ACPI_APEI && PCIEAER && ACPI
help
  PCIe AER errors may be reported via APEI firmware first mode.
  Turn on this option to enable the corresponding support.

Config 'ACPI_APEI_PCIEAER' has the following Direct dependencies 
(ACPI_APEI_PCIEAER=n):
ACPI_APEI(=y) && PCIEAER(=n) && ACPI(=y)
Parent dependencies are:
 PCIEAER [n] ACPI [y] ACPI_APEI [y]
[INFO]: config 'CONFIG_ACPI_APEI_PCIEAER' was set, but it wasn't 
assignable, check (parent) dependencies


[NOTE]: 'CONFIG_BT_HCIBTUSB' last val (m) and .config val (n) do not match
[INFO]: CONFIG_BT_HCIBTUSB : n 
[INFO]: raw config text:

config BT_HCIBTUSB
tristate "HCI USB driver"
select BT_INTEL
depends on USB && BT && NET
help
  Bluetooth HCI USB driver.
  This driver is required if you want to use Bluetooth devices 
with
  USB interface.
  
  Say Y here to compile support for Bluetooth USB devices into 
the
  kernel or say M to compile it as module (btusb).

Config 'BT_HCIBTUSB' has the following Direct dependencies 
(BT_HCIBTUSB=n):
USB(=y) && BT(=n) && NET(=y)
Parent dependencies are:
 BT [n] USB [y] NET [y]
[INFO]: config 'CONFIG_BT_HCIBTUSB' was set, but it wasn't assignable, 
check (parent) dependencies


[NOTE]: 'CONFIG_BT_HCIUART' last val (m) and .config val (n) do not match
[INFO]: CONFIG_BT_HCIUART : n 
[INFO]: raw config text:

config BT_HCIUART
tristate "HCI UART driver"
depends on (SERIAL_DEV_BUS || !SERIAL_DEV_BUS) && (NVMEM || 
!NVMEM) && TTY && BT && NET
help
  Bluetooth HCI UART driver.
  This driver is required if you want to use Bluetooth devices 
with
  serial port interface. You will also need this driver if you 
have
  UART based Bluetooth PCMCIA and CF devices like Xircom Credit 
Card
  adapter and BrainBoxes Bluetooth PC Card.
  
  Say Y here to compile support for Bluetooth UART devices into 
the
  kernel or say M to compile it as module (hci_uart).

Config 'BT_HCIUART' has the following Direct dependencies 
(BT_HCIUART=n):
SERIAL_DEV_BUS(=y) || !SERIAL_DEV_BUS(=y) (=y) && NVMEM(=y) || 
!NVMEM(=y) (=y) && TTY(=y) && BT(=n) && NET(=y)
Parent dependencies are:
 BT [n] NVMEM [y] TTY [y] NET [y] SERIAL_DEV_BUS [y]
[INFO]: config 'CONFIG_BT_HCIUART' was set, but it wasn't assignable, check 
(parent) dependencies


[NOTE]: 'CONFIG_BT_HCIUART_LL' last val (y) and .config val (n) do not match
[INFO]: CONFIG_BT_HCIUART_LL : n 
[INFO]: raw config text:

config BT_HCIUART_LL
bool "HCILL protocol support"
select BT_HCIUART_H4
depends on BT_HCIUART_SERDEV && BT && NET
help
  HCILL (HCI Low Level) is a serial protocol for communication
  between Bluetooth device and host. This protocol is required 
for
  serial Bluetooth devices that are based on Texas Instruments'
  BRF chips.
  
  Say Y here to compile support for HCILL protocol.

Config 'BT_HCIUART_LL' has the following Direct dependencies 
(BT_HCIUART_LL=n):
BT_HCIUART_SERDEV(=n) && BT(=n) && NET(=y)
Parent dependencies are:
 BT_HCIUART_SERDEV [n] BT [n] NET [y]
[INFO]: config 'CONFIG_BT_HCIUART_LL' was set, but it wasn't assignable, 
check (parent) dependencies


[NOTE]: 'CONFIG_BT_HCIUART_BCM' last val (y) and .config val (n) do not 
match
[INFO]: CONFIG_BT_HCIUART_BCM : n 
[INFO]: raw config text:

config BT_HCIUART_BCM
bool "Broadcom protocol support"
select BT_HCIUART_H4
select BT_BCM
depends on BT_HCIUART && BT_HCIUART_SERDEV && (!ACPI || 
SERIAL_DEV_CTRL_TTYPORT) && GPIOLIB && BT && NET
help
  The Broadcom protocol support enables Bluetooth HCI over 
serial
  port interface for

[OE-core][PATCH] db: update CVE_PRODUCT

2021-04-19 Thread Chen Qi

Update CVE_PRODUCT to also include 'berkeley_db'. For example,
CVE-2020-2981 uses 'berkeley_db'.

Signed-off-by: Chen Qi 
---
 meta/recipes-support/db/db_5.3.28.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-support/db/db_5.3.28.bb 
b/meta/recipes-support/db/db_5.3.28.bb
index 9cb57e6a53..b2ae98f05c 100644
--- a/meta/recipes-support/db/db_5.3.28.bb
+++ b/meta/recipes-support/db/db_5.3.28.bb
@@ -15,7 +15,7 @@ HOMEPAGE = 
"https://www.oracle.com/database/technologies/related/berkeleydb.html
 LICENSE = "Sleepycat"
 RCONFLICTS_${PN} = "db3"
 
-CVE_PRODUCT = "oracle_berkeley_db"
+CVE_PRODUCT = "oracle_berkeley_db berkeley_db"
 CVE_VERSION = "11.2.${PV}"
 
 PR = "r1"
-- 
2.30.2


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

Re: [OE-core] [PATCH] db: correct CVE_PRODUCT

2021-04-19 Thread Chen Qi


Hi Zheng,

Looking at it further. I have to say that your observation is correct. 
The CVE_PRODUCT for 'db' recipe is not complete.

Both 'oracle_berkeley_db' and 'berkeley_db' are used.
I've sent out a patch to fix it.

Best Regards,
Chen Qi

On 04/20/2021 10:27 AM, Chen Qi wrote:

I think they are two different projects.
https://www.ibm.com/products/db2-database
https://www.oracle.com/database/technologies/related/berkeleydb.html

You can also use the original json file to check.

e.g.
$ grep -l 'cpe:.*:oracle:oracle_berkeley_db:' ~/.cvedb/nvdcve-1.1-*.json
/home/qichen/.cvedb/nvdcve-1.1-2016.json
/home/qichen/.cvedb/nvdcve-1.1-2017.json
$ grep -l 'cpe:.*:ibm:db2:' 
~/.cvedb/nvdcve-1.1-*.json/home/qichen/.cvedb/nvdcve-1.1-2005.json

/home/qichen/.cvedb/nvdcve-1.1-2010.json
/home/qichen/.cvedb/nvdcve-1.1-2012.json
/home/qichen/.cvedb/nvdcve-1.1-2013.json
/home/qichen/.cvedb/nvdcve-1.1-2014.json
/home/qichen/.cvedb/nvdcve-1.1-2015.json
/home/qichen/.cvedb/nvdcve-1.1-2016.json
/home/qichen/.cvedb/nvdcve-1.1-2017.json
/home/qichen/.cvedb/nvdcve-1.1-2018.json
/home/qichen/.cvedb/nvdcve-1.1-2019.json
/home/qichen/.cvedb/nvdcve-1.1-2020.json
/home/qichen/.cvedb/nvdcve-1.1-Modified.json

Best Regards,
Chen Qi

On 04/20/2021 09:55 AM, zhengrq.f...@fujitsu.com wrote:

Hi, Mikko, Chen

Now, cve_check can't checkout any cve issues of db. I read new 
nvdcve_1.1.db and guess the name of CVE_ PRODUCT should be corrected.
ps: I don't have the old nvdcve_1.1.db, so, I can't make sure that 
the old name of db is "oracle_berkeley_db".


$ grep oracle_berkeley_db SELECT_FROM_PRODUCTS.log
$
$ grep "|db2|" SELECT_FROM_PRODUCTS.log
CVE-2010-0462|ibm|db2|9.1|=||
CVE-2010-0462|ibm|db2|9.1_fp1|=||
CVE-2010-0462|ibm|db2|9.1_fp2|=||
CVE-2010-0462|ibm|db2|9.1_fp2a|=||
CVE-2010-0462|ibm|db2|9.1_fp3|=||
CVE-2010-0462|ibm|db2|9.1_fp3a|=||
CVE-2010-0462|ibm|db2|9.1_fp4|=||
CVE-2010-0462|ibm|db2|9.1_fp4a|=||
CVE-2010-0462|ibm|db2|9.1_fp5|=||
CVE-2010-0462|ibm|db2|9.1_fp6|=||
CVE-2010-0462|ibm|db2|9.1_fp6a|=||
CVE-2010-0462|ibm|db2|9.1_fp7|=||
CVE-2010-0462|ibm|db2|9.1_fp7a|=||
CVE-2010-0462|ibm|db2|9.1_fp8|=||
CVE-2010-0462|ibm|db2|9.5|=||
CVE-2010-0462|ibm|db2|9.5_fp1|=||
CVE-2010-0462|ibm|db2|9.5_fp2|=||
CVE-2010-0462|ibm|db2|9.5_fp2a|=||
CVE-2010-0462|ibm|db2|9.5_fp3|=||
CVE-2010-0462|ibm|db2|9.5_fp3a|=||
CVE-2010-0462|ibm|db2|9.5_fp3b|=||
..

Best regards
Zheng



-Original Message-
From: mikko.rap...@bmw.de 
Sent: Monday, April 19, 2021 2:59 PM
To: Zheng, Ruoqin/郑 若钦 
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH] db: correct CVE_PRODUCT

On Mon, Apr 19, 2021 at 09:45:01PM +0800, zhengruoqin wrote:

In the CVE database, now it use db2 instead of oracle_berkeley_db.
So, in order to be handled correctly by CVE check, modify CVE_ 
PRODUCT.
Which CVEs, please add an example? In the past oracle_berkeley_db 
was used.
I wonder if both would need to be there, or if using the new value 
is sufficient

from now on.

-Mikko


Signed-off-by: Zheng Ruoqin 
---
  meta/recipes-support/db/db_5.3.28.bb | 2 +-
  1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-support/db/db_5.3.28.bb
b/meta/recipes-support/db/db_5.3.28.bb
index 9cb57e6a53..05720053f4 100644
--- a/meta/recipes-support/db/db_5.3.28.bb
+++ b/meta/recipes-support/db/db_5.3.28.bb
@@ -15,7 +15,7 @@ HOMEPAGE =
"https://www.oracle.com/database/technologies/related/berkeleydb.html
  LICENSE = "Sleepycat"
  RCONFLICTS_${PN} = "db3"

-CVE_PRODUCT = "oracle_berkeley_db"
+CVE_PRODUCT = "db2"
  CVE_VERSION = "11.2.${PV}"

  PR = "r1"
--
2.25.1












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

Re: [OE-core] [PATCH] db: correct CVE_PRODUCT

2021-04-19 Thread Chen Qi


I think they are two different projects.
https://www.ibm.com/products/db2-database
https://www.oracle.com/database/technologies/related/berkeleydb.html

You can also use the original json file to check.

e.g.
$ grep -l 'cpe:.*:oracle:oracle_berkeley_db:' ~/.cvedb/nvdcve-1.1-*.json
/home/qichen/.cvedb/nvdcve-1.1-2016.json
/home/qichen/.cvedb/nvdcve-1.1-2017.json
$ grep -l 'cpe:.*:ibm:db2:' 
~/.cvedb/nvdcve-1.1-*.json/home/qichen/.cvedb/nvdcve-1.1-2005.json

/home/qichen/.cvedb/nvdcve-1.1-2010.json
/home/qichen/.cvedb/nvdcve-1.1-2012.json
/home/qichen/.cvedb/nvdcve-1.1-2013.json
/home/qichen/.cvedb/nvdcve-1.1-2014.json
/home/qichen/.cvedb/nvdcve-1.1-2015.json
/home/qichen/.cvedb/nvdcve-1.1-2016.json
/home/qichen/.cvedb/nvdcve-1.1-2017.json
/home/qichen/.cvedb/nvdcve-1.1-2018.json
/home/qichen/.cvedb/nvdcve-1.1-2019.json
/home/qichen/.cvedb/nvdcve-1.1-2020.json
/home/qichen/.cvedb/nvdcve-1.1-Modified.json

Best Regards,
Chen Qi

On 04/20/2021 09:55 AM, zhengrq.f...@fujitsu.com wrote:

Hi, Mikko, Chen

Now, cve_check can't checkout any cve issues of db. I read new nvdcve_1.1.db 
and guess the name of CVE_ PRODUCT should be corrected.
ps: I don't have the old nvdcve_1.1.db, so, I can't make sure that the old name of db is 
"oracle_berkeley_db".

$ grep oracle_berkeley_db SELECT_FROM_PRODUCTS.log
$
$ grep "|db2|" SELECT_FROM_PRODUCTS.log
CVE-2010-0462|ibm|db2|9.1|=||
CVE-2010-0462|ibm|db2|9.1_fp1|=||
CVE-2010-0462|ibm|db2|9.1_fp2|=||
CVE-2010-0462|ibm|db2|9.1_fp2a|=||
CVE-2010-0462|ibm|db2|9.1_fp3|=||
CVE-2010-0462|ibm|db2|9.1_fp3a|=||
CVE-2010-0462|ibm|db2|9.1_fp4|=||
CVE-2010-0462|ibm|db2|9.1_fp4a|=||
CVE-2010-0462|ibm|db2|9.1_fp5|=||
CVE-2010-0462|ibm|db2|9.1_fp6|=||
CVE-2010-0462|ibm|db2|9.1_fp6a|=||
CVE-2010-0462|ibm|db2|9.1_fp7|=||
CVE-2010-0462|ibm|db2|9.1_fp7a|=||
CVE-2010-0462|ibm|db2|9.1_fp8|=||
CVE-2010-0462|ibm|db2|9.5|=||
CVE-2010-0462|ibm|db2|9.5_fp1|=||
CVE-2010-0462|ibm|db2|9.5_fp2|=||
CVE-2010-0462|ibm|db2|9.5_fp2a|=||
CVE-2010-0462|ibm|db2|9.5_fp3|=||
CVE-2010-0462|ibm|db2|9.5_fp3a|=||
CVE-2010-0462|ibm|db2|9.5_fp3b|=||
..

Best regards
Zheng



-Original Message-
From: mikko.rap...@bmw.de 
Sent: Monday, April 19, 2021 2:59 PM
To: Zheng, Ruoqin/郑 若钦 
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH] db: correct CVE_PRODUCT

On Mon, Apr 19, 2021 at 09:45:01PM +0800, zhengruoqin wrote:

In the CVE database, now it use db2 instead of oracle_berkeley_db.
So, in order to be handled correctly by CVE check, modify CVE_ PRODUCT.

Which CVEs, please add an example? In the past oracle_berkeley_db was used.
I wonder if both would need to be there, or if using the new value is sufficient
from now on.

-Mikko


Signed-off-by: Zheng Ruoqin 
---
  meta/recipes-support/db/db_5.3.28.bb | 2 +-
  1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-support/db/db_5.3.28.bb
b/meta/recipes-support/db/db_5.3.28.bb
index 9cb57e6a53..05720053f4 100644
--- a/meta/recipes-support/db/db_5.3.28.bb
+++ b/meta/recipes-support/db/db_5.3.28.bb
@@ -15,7 +15,7 @@ HOMEPAGE =
"https://www.oracle.com/database/technologies/related/berkeleydb.html
  LICENSE = "Sleepycat"
  RCONFLICTS_${PN} = "db3"

-CVE_PRODUCT = "oracle_berkeley_db"
+CVE_PRODUCT = "db2"
  CVE_VERSION = "11.2.${PV}"

  PR = "r1"
--
2.25.1






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

Re: [OE-core] [PATCH] db: correct CVE_PRODUCT

2021-04-19 Thread zhengruoqin

Hi, Mikko, Chen

Now, cve_check can't checkout any cve issues of db. I read new nvdcve_1.1.db 
and guess the name of CVE_ PRODUCT should be corrected.
ps: I don't have the old nvdcve_1.1.db, so, I can't make sure that the old name 
of db is "oracle_berkeley_db".

$ grep oracle_berkeley_db SELECT_FROM_PRODUCTS.log 
$ 
$ grep "|db2|" SELECT_FROM_PRODUCTS.log
CVE-2010-0462|ibm|db2|9.1|=||
CVE-2010-0462|ibm|db2|9.1_fp1|=||
CVE-2010-0462|ibm|db2|9.1_fp2|=||
CVE-2010-0462|ibm|db2|9.1_fp2a|=||
CVE-2010-0462|ibm|db2|9.1_fp3|=||
CVE-2010-0462|ibm|db2|9.1_fp3a|=||
CVE-2010-0462|ibm|db2|9.1_fp4|=||
CVE-2010-0462|ibm|db2|9.1_fp4a|=||
CVE-2010-0462|ibm|db2|9.1_fp5|=||
CVE-2010-0462|ibm|db2|9.1_fp6|=||
CVE-2010-0462|ibm|db2|9.1_fp6a|=||
CVE-2010-0462|ibm|db2|9.1_fp7|=||
CVE-2010-0462|ibm|db2|9.1_fp7a|=||
CVE-2010-0462|ibm|db2|9.1_fp8|=||
CVE-2010-0462|ibm|db2|9.5|=||
CVE-2010-0462|ibm|db2|9.5_fp1|=||
CVE-2010-0462|ibm|db2|9.5_fp2|=||
CVE-2010-0462|ibm|db2|9.5_fp2a|=||
CVE-2010-0462|ibm|db2|9.5_fp3|=||
CVE-2010-0462|ibm|db2|9.5_fp3a|=||
CVE-2010-0462|ibm|db2|9.5_fp3b|=||
..

Best regards
Zheng


> -Original Message-
> From: mikko.rap...@bmw.de 
> Sent: Monday, April 19, 2021 2:59 PM
> To: Zheng, Ruoqin/郑 若钦 
> Cc: openembedded-core@lists.openembedded.org
> Subject: Re: [OE-core] [PATCH] db: correct CVE_PRODUCT
> 
> On Mon, Apr 19, 2021 at 09:45:01PM +0800, zhengruoqin wrote:
> > In the CVE database, now it use db2 instead of oracle_berkeley_db.
> > So, in order to be handled correctly by CVE check, modify CVE_ PRODUCT.
> 
> Which CVEs, please add an example? In the past oracle_berkeley_db was used.
> I wonder if both would need to be there, or if using the new value is 
> sufficient
> from now on.
> 
> -Mikko
> 
> > Signed-off-by: Zheng Ruoqin 
> > ---
> >  meta/recipes-support/db/db_5.3.28.bb | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/meta/recipes-support/db/db_5.3.28.bb
> > b/meta/recipes-support/db/db_5.3.28.bb
> > index 9cb57e6a53..05720053f4 100644
> > --- a/meta/recipes-support/db/db_5.3.28.bb
> > +++ b/meta/recipes-support/db/db_5.3.28.bb
> > @@ -15,7 +15,7 @@ HOMEPAGE =
> > "https://www.oracle.com/database/technologies/related/berkeleydb.html
> >  LICENSE = "Sleepycat"
> >  RCONFLICTS_${PN} = "db3"
> >
> > -CVE_PRODUCT = "oracle_berkeley_db"
> > +CVE_PRODUCT = "db2"
> >  CVE_VERSION = "11.2.${PV}"
> >
> >  PR = "r1"
> > --
> > 2.25.1
> >
> 
> >
> > 
> >

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

[OE-core] Yocto Project Newcomer & Unassigned Bugs - Help Needed

2021-04-19 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 357
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.2", "3.3, "3.99" and "Future", the more pressing/urgent issues
being in "3.2" and then "3.3".

 

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 (#150685): 
https://lists.openembedded.org/g/openembedded-core/message/150685
Mute This Topic: https://lists.openembedded.org/mt/82224238/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [PATCH v2 1/3] btrfs-tools: Update to 5.11.1

2021-04-19 Thread Richard Purdie

On Mon, 2021-04-19 at 03:38 +, Naveen Saini wrote:
> [SWAT}
> It causing util-linux build failure on non-gpl3 build.
> 
> ERROR: Nothing RPROVIDES 'btrfs-tools' (but 
> /home/pokybuild/yocto-worker/non-gpl3/build/meta/recipes-core/util-linux/util-linux_2.36.2.bb
>  RDEPENDS on or otherwise requires it)
> btrfs-tools was skipped: it has incompatible license(s): LGPL-3.0-or-later
> https://autobuilder.yoctoproject.org/typhoon/#/builders/75/builds/3312

Just FYI I've a fix queued for this one to meta-gplv2.

Cheers,

Richard


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

Re: [OE-core] [PATCH 3/4] default-distrovars.inc: add debuginfod to default DISTRO_FEATURES

2021-04-19 Thread Richard Purdie

On Mon, 2021-04-19 at 16:41 +0100, Richard Purdie via lists.openembedded.org 
wrote:
> On Mon, 2021-04-19 at 11:00 +0200, Alexander Kanavin wrote:
> > Obtaining debug information by having it served automatically via http
> > is far more pleasant than messing about with debugfs and gdbserver or
> > transferring and installing -dbg packages by hand.
> > 
> > I believe we should follow the desktop distros and have it enabled
> > out of the box. Please see the following commit for the description
> > of how it works.
> > 
> > Signed-off-by: Alexander Kanavin 
> > ---
> >  meta/conf/distro/include/default-distrovars.inc  | 2 +-
> >  meta/recipes-devtools/binutils/binutils_2.36.bb  | 2 +-
> >  meta/recipes-devtools/elfutils/elfutils_0.183.bb | 2 +-
> >  meta/recipes-devtools/gdb/gdb-common.inc | 2 +-
> >  4 files changed, 4 insertions(+), 4 deletions(-)
> 
> I agree we should do this, it did blow up in testing:
> 
> https://autobuilder.yoctoproject.org/typhoon/#/builders/57/builds/3289/steps/11/logs/stdio
> 
> Hopefully an easy fix?

Also:

https://autobuilder.yoctoproject.org/typhoon/#/builders/81/builds/1993
https://autobuilder.yoctoproject.org/typhoon/#/builders/82/builds/1705

(elfutils ptest warning)

Cheers,

Richard


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

Re: [OE-core] [PATCH] Use shutil.move when os.rename fails

2021-04-19 Thread Devendra Tewari



> On 30 Mar 2021, at 08:55, Devendra Tewari  wrote:
> 
> I understand that parallel tasks can result in such issues, but would expect 
> some kind of dependency graph that would prevent them from happening. I wish 
> I had more time to understand the issue fully.
> 
> Here’s the last version of my patch that still uses os.rename, and on error 
> uses shutil.move, with the reasoning explained in the commit message. There 
> are tons of os.rename in code elsewhere, and I’ve encountered similar issues 
> when doing incremental builds, but I’ll leave fixing them to those with more 
> time at hand. Cheers.

Here’s a patch that catches error with all os.rename in the code, and retries 
with shutil.move when that happens.


> 
> From aeba1f9728f69cdf2ce4ba285be86761d8024f9d Mon Sep 17 00:00:00 2001
> From: Devendra Tewari 
> Date: Tue, 30 Mar 2021 08:27:40 -0300
> Subject: [PATCH] Use shutil.move when os.rename fails
> 
> Incremental build in Docker fails with
> 
> OSError: [Errno 18] Invalid cross-device link
> 
> When source and destination are on different overlay filesystems.
> 
> This change handles error with os.rename and retries with shutil.move.
> The reason os.rename is still used is because shutil.move is too slow
> for speed sensitive sections of code.
> ---
> meta/classes/sstate.bbclass | 22 ++
> 1 file changed, 18 insertions(+), 4 deletions(-)
> 
> diff --git a/meta/classes/sstate.bbclass b/meta/classes/sstate.bbclass
> index f579168162..301dfc27db 100644
> --- a/meta/classes/sstate.bbclass
> +++ b/meta/classes/sstate.bbclass
> @@ -384,6 +384,7 @@ def sstate_installpkg(ss, d):
> def sstate_installpkgdir(ss, d):
> import oe.path
> import subprocess
> +import shutil
> 
> sstateinst = d.getVar("SSTATE_INSTDIR")
> d.setVar('SSTATE_FIXMEDIR', ss['fixmedir'])
> @@ -401,7 +402,10 @@ def sstate_installpkgdir(ss, d):
> 
> for state in ss['dirs']:
> prepdir(state[1])
> -os.rename(sstateinst + state[0], state[1])
> +try:
> +os.rename(sstateinst + state[0], state[1])
> +except OSError:
> +shutil.move(sstateinst + state[0], state[1])
> sstate_install(ss, d)
> 
> for plain in ss['plaindirs']:
> @@ -413,7 +417,10 @@ def sstate_installpkgdir(ss, d):
> dest = plain
> bb.utils.mkdirhier(src)
> prepdir(dest)
> -os.rename(src, dest)
> +try:
> +os.rename(src, dest)
> +except OSError:
> +shutil.move(src, dest)
> 
> return True
> 
> @@ -638,6 +645,7 @@ python sstate_hardcode_path () {
> 
> def sstate_package(ss, d):
> import oe.path
> +import shutil
> 
> tmpdir = d.getVar('TMPDIR')
> 
> @@ -664,7 +672,10 @@ def sstate_package(ss, d):
> continue
> bb.error("sstate found an absolute path symlink %s pointing 
> at %s. Please replace this with a relative link." % (srcpath, link))
> bb.debug(2, "Preparing tree %s for packaging at %s" % (state[1], 
> sstatebuild + state[0]))
> -os.rename(state[1], sstatebuild + state[0])
> +try:
> +os.rename(state[1], sstatebuild + state[0])
> +except OSError:
> +shutil.move(state[1], sstatebuild + state[0])
> 
> workdir = d.getVar('WORKDIR')
> sharedworkdir = os.path.join(d.getVar('TMPDIR'), "work-shared")
> @@ -674,7 +685,10 @@ def sstate_package(ss, d):
> pdir = plain.replace(sharedworkdir, sstatebuild)
> bb.utils.mkdirhier(plain)
> bb.utils.mkdirhier(pdir)
> -os.rename(plain, pdir)
> +try:
> +os.rename(plain, pdir)
> +except OSError:
> +shutil.move(plain, pdir)
> 
> d.setVar('SSTATE_BUILDDIR', sstatebuild)
> d.setVar('SSTATE_INSTDIR', sstatebuild)
> -- 
> 2.29.2
> 
> 
>> On 30 Mar 2021, at 08:10, Richard Purdie 
>>  wrote:
>> 
>> On Mon, 2021-03-29 at 16:00 -0700, Andre McCurdy wrote:
>>> On Mon, Mar 29, 2021 at 3:45 PM Devendra Tewari
>>>  wrote:
 
 Thanks! My bad. The example I looked up in Python docs had a break and I 
 just realized it was a looping example.
 
 Here’s the updated patch (or should I submit it again via git send-email?)
>>> 
>>> It would be better to use shutil.move unconditionally in all cases,
>>> rather than have a separate shutil.move code path which only gets
>>> tested by people doing incremental builds in docker.
>> 
>> This is a speed sensitive section of code and shutil has traditionally 
>> proved 
>> to be slow so I disagree with that, rename is very much preferred here where
>> we can.
>> 
>> Cheers,
>> 
>> Richard
>> 
>> 
> 



0001-use-shutil.move-when-os.rename-fails.patch
Description: Binary data

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#150682): 
https://lists.openembedded.org/g/openembedded-core/message/150682
Mute This Topic: https://lists.openembedded.org/mt/81698791/21656
Group Owner:

Re: [OE-core] [PATCH 2/4] libmicrohttpd: add a recipe from meta-oe

2021-04-19 Thread Khem Raj




On 4/19/21 2:00 AM, Alexander Kanavin wrote:

This is required to enable debuginfod in elfutils.



Don't forget to send a patch to remove  it from meta-openembedded once 
merged in core.



Signed-off-by: Alexander Kanavin 
---
  .../libmicrohttpd/libmicrohttpd_0.9.72.bb | 31 +++
  1 file changed, 31 insertions(+)
  create mode 100644 meta/recipes-support/libmicrohttpd/libmicrohttpd_0.9.72.bb

diff --git a/meta/recipes-support/libmicrohttpd/libmicrohttpd_0.9.72.bb 
b/meta/recipes-support/libmicrohttpd/libmicrohttpd_0.9.72.bb
new file mode 100644
index 00..66c48da3b7
--- /dev/null
+++ b/meta/recipes-support/libmicrohttpd/libmicrohttpd_0.9.72.bb
@@ -0,0 +1,31 @@
+DESCRIPTION = "A small C library that is supposed to make it easy to run an HTTP 
server as part of another application"
+HOMEPAGE = "http://www.gnu.org/software/libmicrohttpd/;
+LICENSE = "LGPL-2.1+"
+LIC_FILES_CHKSUM = "file://COPYING;md5=57d09285feac8a64efa878e692b14f36"
+SECTION = "net"
+
+DEPENDS = "file"
+
+SRC_URI = "${GNU_MIRROR}/libmicrohttpd/${BPN}-${PV}.tar.gz"
+SRC_URI[md5sum] = "2a286193af88ab2ae3149748d4b46187"
+SRC_URI[sha256sum] = 
"0ae825f8e0d7f41201fd44a0df1cf454c1cb0bc50fe9d59c26552260264c2ff8"
+
+inherit autotools lib_package pkgconfig gettext
+
+CFLAGS += "-pthread -D_REENTRANT"
+
+EXTRA_OECONF += "--disable-static --with-gnutls=${STAGING_LIBDIR}/../"
+
+PACKAGECONFIG ?= "curl https"
+PACKAGECONFIG_append_class-target = "\
+${@bb.utils.filter('DISTRO_FEATURES', 'largefile', d)} \
+"
+PACKAGECONFIG[largefile] = "--enable-largefile,--disable-largefile,,"
+PACKAGECONFIG[curl] = "--enable-curl,--disable-curl,curl,"
+PACKAGECONFIG[https] = "--enable-https,--disable-https,libgcrypt gnutls,"
+
+do_compile_append() {
+sed -i s:-L${STAGING_LIBDIR}::g libmicrohttpd.pc
+}
+
+BBCLASSEXTEND = "native nativesdk"






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

Re: [OE-core] [PATCH 3/4] default-distrovars.inc: add debuginfod to default DISTRO_FEATURES

2021-04-19 Thread Richard Purdie

On Mon, 2021-04-19 at 11:00 +0200, Alexander Kanavin wrote:
> Obtaining debug information by having it served automatically via http
> is far more pleasant than messing about with debugfs and gdbserver or
> transferring and installing -dbg packages by hand.
> 
> I believe we should follow the desktop distros and have it enabled
> out of the box. Please see the following commit for the description
> of how it works.
> 
> Signed-off-by: Alexander Kanavin 
> ---
>  meta/conf/distro/include/default-distrovars.inc  | 2 +-
>  meta/recipes-devtools/binutils/binutils_2.36.bb  | 2 +-
>  meta/recipes-devtools/elfutils/elfutils_0.183.bb | 2 +-
>  meta/recipes-devtools/gdb/gdb-common.inc | 2 +-
>  4 files changed, 4 insertions(+), 4 deletions(-)

I agree we should do this, it did blow up in testing:

https://autobuilder.yoctoproject.org/typhoon/#/builders/57/builds/3289/steps/11/logs/stdio

Hopefully an easy fix?

Cheers,

Richard


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

Re: [OE-core] [PATCH v2] go: upgrade 1.16.2 -> 1.16.3

2021-04-19 Thread Khem Raj

On Mon, Apr 19, 2021 at 12:51 AM Martin Jansa  wrote:
>
> On Mon, Apr 19, 2021 at 04:25:26AM +, Naveen Saini wrote:
> > [SWAT]
> > Fetching error:
> > recipe go-runtime-1.16.3-r0: task do_fetch: Failed
> > https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/2053/steps/23/logs/stdio
>
> That seems related to
> https://git.openembedded.org/openembedded-core/commit/?id=2a1eb731ed3bcb049192550e362b771c3a9ea6eb
> not this go upgrade.
>

that change came after upgrade to see if it will help this issue :)

> Also locally I can fetch this over http:// as well as https:// without
> any issues with wget, but it's true that with chrome I see valid
> certificate on https://golang.org/dl but not on
> https://golang.org/dl/go1.16.3.src.tar.gz
> or
> https://golang.org/dl/go1.16.2.src.tar.gz
>
> and curl downloads just the link to dl.google.com/go
> $ curl https://golang.org/dl/go1.16.3.src.tar.gz
> https://dl.google.com/go/go1.16.3.src.tar.gz;>Found.
>
> Maybe we should just use https://dl.google.com/go directly to fetch
> go.

yes perhaps that's a better option.

>
> > From: openembedded-core@lists.openembedded.org 
> >  On Behalf Of Alejandro Hernandez 
> > Samaniego
> > Sent: Thursday, April 15, 2021 5:49 AM
> > To: Khem Raj ; openembedded-core@lists.openembedded.org
> > Cc: wangmy 
> > Subject: Re: [OE-core] [PATCH v2] go: upgrade 1.16.2 -> 1.16.3
> >
> >
> > Hello,
> >
> >
> >
> > This one is causing failures in test_yocto_source_mirror
> >
> > https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/2037/steps/23/logs/stdio
> >
> > although since its still on master-next my guess is that its sources havent 
> > been published
> >
> > yet to downloads.yoctoproject.org
> >
> >
> >
> > Alejandro
> >
> >
> > On 4/10/21 1:30 AM, Khem Raj wrote:
> >
> > From: wangmy 
> >
> >
> >
> > This is bugfix release in 1.16 series [1]
> >
> >
> >
> > [1] 
> > https://github.com/golang/go/issues?q=milestone%3AGo1.16.3+label%3ACherryPickApproved
> >
> >
> >
> > Signed-off-by: Wang Mingyu 
> >
> > Signed-off-by: Khem Raj 
> >
> > ---
> >
> > v2: Fix checksums and improve commit msg
> >
> >
> >
> >  meta/recipes-devtools/go/{go-1.16.2.inc => go-1.16.3.inc} | 4 ++--
> >
> >  ...{go-binary-native_1.16.2.bb => go-binary-native_1.16.3.bb} | 4 ++--
> >
> >  ...o-cross-canadian_1.16.2.bb => go-cross-canadian_1.16.3.bb} | 0
> >
> >  .../go/{go-cross_1.16.2.bb => go-cross_1.16.3.bb} | 0
> >
> >  .../go/{go-crosssdk_1.16.2.bb => go-crosssdk_1.16.3.bb}   | 0
> >
> >  .../go/{go-native_1.16.2.bb => go-native_1.16.3.bb}   | 0
> >
> >  .../go/{go-runtime_1.16.2.bb => go-runtime_1.16.3.bb} | 0
> >
> >  meta/recipes-devtools/go/{go_1.16.2.bb => go_1.16.3.bb}   | 0
> >
> >  8 files changed, 4 insertions(+), 4 deletions(-)
> >
> >  rename meta/recipes-devtools/go/{go-1.16.2.inc => go-1.16.3.inc} (88%)
> >
> >  rename meta/recipes-devtools/go/{go-binary-native_1.16.2.bb => 
> > go-binary-native_1.16.3.bb} (83%)
> >
> >  rename meta/recipes-devtools/go/{go-cross-canadian_1.16.2.bb => 
> > go-cross-canadian_1.16.3.bb} (100%)
> >
> >  rename meta/recipes-devtools/go/{go-cross_1.16.2.bb => go-cross_1.16.3.bb} 
> > (100%)
> >
> >  rename meta/recipes-devtools/go/{go-crosssdk_1.16.2.bb => 
> > go-crosssdk_1.16.3.bb} (100%)
> >
> >  rename meta/recipes-devtools/go/{go-native_1.16.2.bb => 
> > go-native_1.16.3.bb} (100%)
> >
> >  rename meta/recipes-devtools/go/{go-runtime_1.16.2.bb => 
> > go-runtime_1.16.3.bb} (100%)
> >
> >  rename meta/recipes-devtools/go/{go_1.16.2.bb => go_1.16.3.bb} (100%)
> >
> >
> >
> > diff --git a/meta/recipes-devtools/go/go-1.16.2.inc 
> > b/meta/recipes-devtools/go/go-1.16.3.inc
> >
> > similarity index 88%
> >
> > rename from meta/recipes-devtools/go/go-1.16.2.inc
> >
> > rename to meta/recipes-devtools/go/go-1.16.3.inc
> >
> > index e65caf8197..ebd25a5eaa 100644
> >
> > --- a/meta/recipes-devtools/go/go-1.16.2.inc
> >
> > +++ b/meta/recipes-devtools/go/go-1.16.3.inc
> >
> > @@ -1,7 +1,7 @@
> >
> >  require go-common.inc
> >
> >
> >
> >  GO_BASEVERSION = "1.16"
> >
> > -PV = "1.16.2"
> >
> > +PV = "1.16.3"
> >
> >  FILESEXTRAPATHS_prepend := "${FILE_DIRNAME}/go-${GO_BASEVERSION}:"
> >
> >
> >
> >  LIC_FILES_CHKSUM = 
> > "file://LICENSE;md5=5d4950ecb7b26d2c5e4e7b4e0dd74707"
> >
> > @@ -17,4 +17,4 @@ SRC_URI += "\
> >
> >  file://0008-use-GOBUILDMODE-to-set-buildmode.patch \
> >
> >  file://0009-Revert-cmd-go-make-sure-CC-and-CXX-are-absolute.patch \
> >
> >  "
> >
> > -SRC_URI[main.sha256sum] = 
> > "37ca14287a23cb8ba2ac3f5c3dd8adbc1f7a54b9701a57824bf19a0b271f83ea"
> >
> > +SRC_URI[main.sha256sum] = 
> > "b298d29de9236ca47a023e382313bcc2d2eed31dfa706b60a04103ce83a71a25"
> >
> > diff --git a/meta/recipes-devtools/go/go-binary-native_1.16.2.bb 
> > b/meta/recipes-devtools/go/go-binary-native_1.16.3.bb
> >
> > similarity index 83%
> >
> > rename from

Re: [OE-core] [PATCH] ca-certificates: Fix openssl runtime cert dependencies

2021-04-19 Thread Khem Raj




On 4/18/21 11:40 PM, mikko.rap...@bmw.de wrote:

Hi,

On Sun, Apr 18, 2021 at 03:53:10PM -0700, Khem Raj wrote:

With commit dc778c70449ee5401b5a24ad18b22b88338c47c5, dependency was
moved to openssl-bin which in itself was a fine change, but dropping
dependency on openssl too should have been kept along, dropping this
meant that openssl binary wont be able to validate secure connections as
the CApath files wont be installed, which infact are required for
openssl bins to work, following call e.g. fails

$ openssl s_client -connect google.com:443


This sounds a lot like a ptest or selftest? Maybe using
some yocto server instead of google though.


Yeah certainly a good idea,



Cheers,

-Mikko



New, TLSv1.3, Cipher is TLS_AES_256_GCM_SHA384
Server public key is 256 bit
Secure Renegotiation IS NOT supported
Compression: NONE
Expansion: NONE
No ALPN negotiated
Early data was not sent
Verify return code: 20 (unable to get local issuer certificate)


The local issuer certs are not found in default location
/usr/lib/ssh-1.1/certs, this dir and its content is installed by openssl package
therefore re-add the dependency on openssl

Signed-off-by: Khem Raj 
Cc: Andrei Gherzan 
---
  .../ca-certificates/ca-certificates_20210119.bb | 6 +++---
  1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/meta/recipes-support/ca-certificates/ca-certificates_20210119.bb 
b/meta/recipes-support/ca-certificates/ca-certificates_20210119.bb
index 888a235c1a..7dcc86fdc1 100644
--- a/meta/recipes-support/ca-certificates/ca-certificates_20210119.bb
+++ b/meta/recipes-support/ca-certificates/ca-certificates_20210119.bb
@@ -83,8 +83,8 @@ do_install_append_class-native () {
  SYSROOT="${D}${base_prefix}" ${D}${sbindir}/update-ca-certificates
  }
  
-RDEPENDS_${PN}_class-target = "openssl-bin"

-RDEPENDS_${PN}_class-native = "openssl-native"
-RDEPENDS_${PN}_class-nativesdk = "nativesdk-openssl-bin"
+RDEPENDS_${PN}_append_class-target = " openssl-bin openssl"
+RDEPENDS_${PN}_append_class-native = " openssl-native"
+RDEPENDS_${PN}_append_class-nativesdk = " nativesdk-openssl-bin 
nativesdk-openssl"
  
  BBCLASSEXTEND = "native nativesdk"

--
2.31.1








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

Re: [OE-core] [PATCH] perl: fix startperl configuration option for perl-native

2021-04-19 Thread Paulo Cesar Zaneti

I just re-send the patch with additional fix for the build failure.

I think the basic problem was an inconsistency in the way perl recipe and 
cpan.bbclass convert the absolute perl path to env path.
Version 2 of the patch tries to use same cpan.bbclass approach on the perl 
recipe.

Before submitting I just ran "bitbake -k world". I hope it doesn't break the 
build again.

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

[OE-core] [PATCH v2] perl: fix startperl configuration option for perl-native

2021-04-19 Thread Paulo Cesar Zaneti

Unlike vanilla Perl "Configure" script, perl-cross "configure" does not
derive "startperl" from "bin". It instead derives from "perlpath".

This patch aims to fix "startperl" configuration option for perl-native by
correctly setting "perlpath" on perl-cross "configure" script.

It also changes do_install_append_class-native task to comply with
cpan_do_install task.

Signed-off-by: Paulo Cesar Zaneti 
---
 meta/recipes-devtools/perl/perl_5.32.1.bb | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/meta/recipes-devtools/perl/perl_5.32.1.bb 
b/meta/recipes-devtools/perl/perl_5.32.1.bb
index b28040c7fb..73d66f6656 100644
--- a/meta/recipes-devtools/perl/perl_5.32.1.bb
+++ b/meta/recipes-devtools/perl/perl_5.32.1.bb
@@ -95,6 +95,7 @@ do_configure_class-nativesdk() {
 do_configure_class-native() {
 ./configure --prefix=${prefix} \
 -Dbin=${bindir}/perl-native \
+-Dperlpath=${bindir}/perl-native/perl \
 -Duseshrplib \
 -Dsoname=libperl.so.5 \
 -Dvendorprefix=${prefix} \
@@ -171,8 +172,8 @@ do_install_append_class-native () {
 create_wrapper ${D}${bindir}/perl-native/perl 
PERL5LIB='$PERL5LIB:${STAGING_LIBDIR}/perl5/site_perl/${PV}:${STAGING_LIBDIR}/perl5/vendor_perl/${PV}:${STAGING_LIBDIR}/perl5/${PV}'
 
 # Use /usr/bin/env nativeperl for the perl script.
-for f in `grep -Il '#! *${bindir}/perl' ${D}/${bindir}/*`; do
-sed -i -e 's|${bindir}/perl|/usr/bin/env nativeperl|' $f
+for f in `grep -Il '#! *${bindir}/perl-native.*/perl' ${D}/${bindir}/*`; do
+sed -i -e 's|${bindir}/perl-native.*/perl|/usr/bin/env 
nativeperl|' $f
 done
 }
 
-- 
2.25.1


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

[OE-core][PATCH] nettle: upgrade 3.7.1 -> 3.7.2

2021-04-19 Thread Trevor Gamblin

Version 3.7.2 includes a fix for CVE-2021-20305.

Signed-off-by: Trevor Gamblin 
---
 .../recipes-support/nettle/{nettle_3.7.1.bb => nettle_3.7.2.bb} | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
 rename meta/recipes-support/nettle/{nettle_3.7.1.bb => nettle_3.7.2.bb} (96%)

diff --git a/meta/recipes-support/nettle/nettle_3.7.1.bb 
b/meta/recipes-support/nettle/nettle_3.7.2.bb
similarity index 96%
rename from meta/recipes-support/nettle/nettle_3.7.1.bb
rename to meta/recipes-support/nettle/nettle_3.7.2.bb
index 3bbcf17c7a..f8f3360086 100644
--- a/meta/recipes-support/nettle/nettle_3.7.1.bb
+++ b/meta/recipes-support/nettle/nettle_3.7.2.bb
@@ -24,7 +24,7 @@ SRC_URI_append_class-target = "\
 file://dlopen-test.patch \
 "
 
-SRC_URI[sha256sum] = 
"156621427c7b00a75ff9b34b770b95d34f80ef7a55c3407de94b16cbf436c42e"
+SRC_URI[sha256sum] = 
"8d2a604ef1cde4cd5fb77e422531ea25ad064679ff0adf956e78b3352e0ef162"
 
 UPSTREAM_CHECK_REGEX = "nettle-(?P\d+(\.\d+)+)\.tar"
 
-- 
2.30.2


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

Re: [OE-core] [docs] [PATCH] dev-manual/common-tasks.rst: correct the documentation for debuginfod

2021-04-19 Thread Quentin Schulz

Hi Alex,

On Mon, Apr 19, 2021 at 02:56:18PM +0200, Alexander Kanavin wrote:
> Particularly,
> - correctly describe the use of DEBUGINFOD_URLS; drop it from bitbake 
> variables
> - all necessary component tweaks are enabled by default via DISTRO_FEATURES
> - provide on-target examples of what to look for when things work properly
> 

Looks good to me.

Reviewed-by: Quentin Schulz 

Thanks!
Quentin

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

[OE-core] [PATCH] dev-manual/common-tasks.rst: correct the documentation for debuginfod

2021-04-19 Thread Alexander Kanavin

Particularly,
- correctly describe the use of DEBUGINFOD_URLS; drop it from bitbake variables
- all necessary component tweaks are enabled by default via DISTRO_FEATURES
- provide on-target examples of what to look for when things work properly

Signed-off-by: Alexander Kanavin 
---
 documentation/dev-manual/common-tasks.rst | 43 +--
 documentation/ref-manual/variables.rst|  6 
 2 files changed, 24 insertions(+), 25 deletions(-)

diff --git a/documentation/dev-manual/common-tasks.rst 
b/documentation/dev-manual/common-tasks.rst
index 176025f9e8..dd8ce98276 100644
--- a/documentation/dev-manual/common-tasks.rst
+++ b/documentation/dev-manual/common-tasks.rst
@@ -9997,42 +9997,47 @@ methods you can use: running a debuginfod server and 
using gdbserver.
 Using the debuginfod server method
 
 
-"debuginfod" from "elfutils" is a way to distribute "debuginfo" files.
-Running a "debuginfod" server makes debug symbols readily available,
+``debuginfod`` from ``elfutils`` is a way to distribute ``debuginfo`` files.
+Running a ``debuginfod`` server makes debug symbols readily available,
 which means you don't need to download debugging information
 and the binaries of the process being debugged. You can just fetch
 debug symbols from the server.
 
-To run a debuginfod server, you need to do the following:
+To run a ``debuginfod`` server, you need to do the following:
 
--  Ensure that this variable is set in your ``local.conf`` file:
-   ::
+-  Ensure that ``debuginfod`` is present in :term:`DISTRO_FEATURES`
+   (it already is in ``OpenEmbedded-core`` defaults and ``poky`` reference 
distribution).
+   If not, set::
 
-  PACKAGECONFIG_pn-elfutils-native = "debuginfod libdebuginfod"
+  DISTRO_FEATURES_append = " debuginfod"
 
-   This :term:`PACKAGECONFIG` option enables debuginfod and libdebuginfod for
-   "elfutils-native".
+   This distro feature enables the server and client library in ``elfutils``,
+   and enables ``debuginfod`` support in clients (at the moment, ``gdb`` and 
``binutils``).
 
--  Run the following commands to set up the "debuginfod" server:
-   ::
+-  Run the following commands to launch the ``debuginfod`` server on the host::
 
   $ oe-debuginfod
 
+-  To use ``debuginfod`` on the target, you need to know the ip:port where
+   ``debuginfod`` is listening on the host (port defaults to 8002), and export
+   that into the shell environment, for example in ``qemu``::
 
-To use debuginfod on the target, you need the following:
+  root@qemux86-64:~# export DEBUGINFOD_URLS="http://192.168.7.1:8002/;
 
--  Ensure that this variable is set in your ``local.conf`` file:
-   ::
+-  Then debug info fetching should simply work when running the target ``gdb``,
+   ``readelf`` or ``objdump``, for example::
 
-  DEBUGINFOD_URLS = "http://localhost:8002/;
+  root@qemux86-64:~# gdb /bin/cat
+  ...
+  Reading symbols from /bin/cat...
+  Downloading separate debug info for /bin/cat...
+  Reading symbols from 
/home/root/.cache/debuginfod_client/923dc4780cfbc545850c616bffa884b6b5eaf322/debuginfo...
 
-   This :term:`DEBUGINFOD_URLS` option does the client configuration.
-
-   ::
+-  It's also possible to use ``debuginfod-find`` to just query the server::
 
-PACKAGECONFIG_pn-gdb = "debuginfod"
+  root@qemux86-64:~# debuginfod-find debuginfo /bin/ls
+  
/home/root/.cache/debuginfod_client/356edc585f7f82d46f94fcb87a86a3fe2d2e60bd/debuginfo
 
-   This :term:`PACKAGECONFIG` option enables "debuginfod" for "gdb".
 
 Using the gdbserver method
 ~
diff --git a/documentation/ref-manual/variables.rst 
b/documentation/ref-manual/variables.rst
index 74ac12bf98..8a35b0960e 100644
--- a/documentation/ref-manual/variables.rst
+++ b/documentation/ref-manual/variables.rst
@@ -1563,12 +1563,6 @@ system and gives an overview of their function and 
contents.
 
  DEBIANNAME_${PN} = "dbus-1"
 
-   :term:`DEBUGINFOD_URLS`
-  Points to the URL of the "debuginfod" server. Such that for every
-  debugging information lookup, the debuginfod client will query the
-  server and return the requested information. You set this variable
-  in your ``local.conf`` file.
-
:term:`DEBUG_BUILD`
   Specifies to build packages with debugging information. This
   influences the value of the ``SELECTED_OPTIMIZATION`` variable.
-- 
2.30.2


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

[OE-core] [PATCH] maintainers.inc: add libmicrohttpd entry

2021-04-19 Thread Alexander Kanavin

Signed-off-by: Alexander Kanavin 
---
 meta/conf/distro/include/maintainers.inc | 1 +
 1 file changed, 1 insertion(+)

diff --git a/meta/conf/distro/include/maintainers.inc 
b/meta/conf/distro/include/maintainers.inc
index e1b1afcd7e..9d4e2ea741 100644
--- a/meta/conf/distro/include/maintainers.inc
+++ b/meta/conf/distro/include/maintainers.inc
@@ -350,6 +350,7 @@ RECIPE_MAINTAINER_pn-libjitterentropy = "Ross Burton 
"
 RECIPE_MAINTAINER_pn-libksba = "Alexander Kanavin "
 RECIPE_MAINTAINER_pn-libmatchbox = "Ross Burton "
 RECIPE_MAINTAINER_pn-libmd = "Alexander Kanavin "
+RECIPE_MAINTAINER_pn-libmicrohttpd = "Alexander Kanavin 
"
 RECIPE_MAINTAINER_pn-libmnl = "Khem Raj "
 RECIPE_MAINTAINER_pn-libmpc = "Khem Raj "
 RECIPE_MAINTAINER_pn-libmodule-build-perl = "Tim Orling 
"
-- 
2.30.2


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

[OE-core] [PATCH] sanity: Further improve directory sanity tests

2021-04-19 Thread Richard Purdie

Add tests to ensure COREBASE/TMPDIR doon't contain ".." as this causes
hard to understand build failures.

Also rework the code to test TMPDIR and COREBASE for all the patterns
since they may be set differently and one may contain problematic
characters.

[YOCTO #14111]

Signed-off-by: Richard Purdie 
---
 meta/classes/sanity.bbclass | 21 -
 1 file changed, 12 insertions(+), 9 deletions(-)

diff --git a/meta/classes/sanity.bbclass b/meta/classes/sanity.bbclass
index 14ffac0bf28..a377917f2a9 100644
--- a/meta/classes/sanity.bbclass
+++ b/meta/classes/sanity.bbclass
@@ -882,15 +882,18 @@ def check_sanity_everybuild(status, d):
 except:
 pass
 
-oeroot = d.getVar('COREBASE')
-if oeroot.find('+') != -1:
-status.addresult("Error, you have an invalid character (+) in your 
COREBASE directory path. Please move the installation to a directory which 
doesn't include any + characters.")
-if oeroot.find('@') != -1:
-status.addresult("Error, you have an invalid character (@) in your 
COREBASE directory path. Please move the installation to a directory which 
doesn't include any @ characters.")
-if oeroot.find('%') != -1:
-status.addresult("Error, you have an invalid character (%) in your 
COREBASE directory path which causes problems with python string formatting. 
Please move the installation to a directory which doesn't include any % 
characters.") 
-if oeroot.find(' ') != -1:
-status.addresult("Error, you have a space in your COREBASE directory 
path. Please move the installation to a directory which doesn't include a space 
since autotools doesn't support this.")
+for checkdir in ['COREBASE', 'TMPDIR']:
+val = d.getVar(checkdir)
+if val.find('..') != -1:
+status.addresult("Error, you have '..' in your %s directory path. 
Please ensure the variable contains an absolute path as this can break some 
recipe builds in obtuse ways." % checkdir)
+if val.find('+') != -1:
+status.addresult("Error, you have an invalid character (+) in your 
%s directory path. Please move the installation to a directory which doesn't 
include any + characters." % checkdir)
+if val.find('@') != -1:
+status.addresult("Error, you have an invalid character (@) in your 
%s directory path. Please move the installation to a directory which doesn't 
include any @ characters." % checkdir)
+if val.find(' ') != -1:
+status.addresult("Error, you have a space in your %s directory 
path. Please move the installation to a directory which doesn't include a space 
since autotools doesn't support this." % checkdir)
+if val.find('%') != -1:
+status.addresult("Error, you have an invalid character (%) in your 
%s directory path which causes problems with python string formatting. Please 
move the installation to a directory which doesn't include any % characters." % 
checkdir)
 
 # Check the format of MIRRORS, PREMIRRORS and SSTATE_MIRRORS
 import re
-- 
2.30.2


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

[OE-core] [PATCH] bitbake: crash when using git LFS and submodules

2021-04-19 Thread Niels Avonds

Gitsm fetcher crashes when cloning a repository that contains LFS files.
This happens because the unpack method is called during download, but the
submodules have not been downloaded yet at this point.

This issue was introduced in this
commit: 977b7268bf4fd425cb86d4a57500350c9b829162

Someone else already encountered the same issue as well:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=14283

>From aa99ad52f9ef11eb2875c5d7930abba52e229f0c Mon Sep 17 00:00:00 2001
From: Niels Avonds 
Date: Thu, 1 Apr 2021 18:48:03 +0200
Subject: [PATCH] NE-630: Temporary fix for gitsm fetcher

Signed-off-by: Niels Avonds 
---
 bitbake/lib/bb/fetch2/git.py | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/bitbake/lib/bb/fetch2/git.py b/bitbake/lib/bb/fetch2/git.py
index 8740e9c05f..112b833f87 100644
--- a/bitbake/lib/bb/fetch2/git.py
+++ b/bitbake/lib/bb/fetch2/git.py
@@ -388,7 +388,7 @@ class Git(FetchMethod):
 tmpdir = tempfile.mkdtemp(dir=d.getVar('DL_DIR'))
 try:
 # Do the checkout. This implicitly involves a Git LFS
fetch.
-self.unpack(ud, tmpdir, d)
+Git.unpack(self, ud, tmpdir, d)

 # Scoop up a copy of any stuff that Git LFS downloaded.
Merge them into
 # the bare clonedir.
--
2.25.1

Niels Avonds
Codebits

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

[OE-core] [PATCH 2/2] weston: use standalone xwayland instead of outdated xserver-xorg version

2021-04-19 Thread Alexander Kanavin

Signed-off-by: Alexander Kanavin 
---
 meta/recipes-graphics/wayland/weston_9.0.0.bb   | 2 +-
 meta/recipes-graphics/xorg-xserver/xserver-xorg.inc | 1 -
 2 files changed, 1 insertion(+), 2 deletions(-)

diff --git a/meta/recipes-graphics/wayland/weston_9.0.0.bb 
b/meta/recipes-graphics/wayland/weston_9.0.0.bb
index 50fbfa613b..34ac66d4e9 100644
--- a/meta/recipes-graphics/wayland/weston_9.0.0.bb
+++ b/meta/recipes-graphics/wayland/weston_9.0.0.bb
@@ -124,7 +124,7 @@ SUMMARY_libweston-${WESTON_MAJOR_VERSION} = "Helper library 
for implementing 'wa
 FILES_${PN}-examples = "${bindir}/*"
 
 FILES_${PN}-xwayland = 
"${libdir}/libweston-${WESTON_MAJOR_VERSION}/xwayland.so"
-RDEPENDS_${PN}-xwayland += "xserver-xorg-xwayland"
+RDEPENDS_${PN}-xwayland += "xwayland"
 
 RDEPENDS_${PN} += "xkeyboard-config"
 RRECOMMENDS_${PN} = "weston-init liberation-fonts"
diff --git a/meta/recipes-graphics/xorg-xserver/xserver-xorg.inc 
b/meta/recipes-graphics/xorg-xserver/xserver-xorg.inc
index b3e03744c0..da025171db 100644
--- a/meta/recipes-graphics/xorg-xserver/xserver-xorg.inc
+++ b/meta/recipes-graphics/xorg-xserver/xserver-xorg.inc
@@ -122,7 +122,6 @@ EXTRA_OECONF += "--with-fop=no \
 OPENGL_PKGCONFIGS = "dri glx glamor dri3 xshmfence"
 PACKAGECONFIG ??= "dga dri2 udev ${XORG_CRYPTO} \
${@bb.utils.contains('DISTRO_FEATURES', 'opengl', 
'${OPENGL_PKGCONFIGS}', '', d)} \
-   ${@bb.utils.contains('DISTRO_FEATURES', 'opengl wayland', 
'xwayland', '', d)} \
${@bb.utils.contains('DISTRO_FEATURES', 'systemd', 'systemd 
systemd-logind', '', d)} \
 "
 
-- 
2.30.2


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

[OE-core] [PATCH 1/2] xwayland: add a standalone recipe

2021-04-19 Thread Alexander Kanavin

Please see here for the rationale for splitting XWayland out of
main xserver-xorg tree:
https://fedoraproject.org/wiki/Changes/XwaylandStandalone

Release announcement:
https://lists.x.org/archives/xorg-announce/2021-March/003076.html

Signed-off-by: Alexander Kanavin 
---
 meta/conf/distro/include/maintainers.inc  |  1 +
 .../xwayland/xwayland_21.1.1.bb   | 21 +++
 2 files changed, 22 insertions(+)
 create mode 100644 meta/recipes-graphics/xwayland/xwayland_21.1.1.bb

diff --git a/meta/conf/distro/include/maintainers.inc 
b/meta/conf/distro/include/maintainers.inc
index e1b1afcd7e..db0b2b4df0 100644
--- a/meta/conf/distro/include/maintainers.inc
+++ b/meta/conf/distro/include/maintainers.inc
@@ -797,6 +797,7 @@ RECIPE_MAINTAINER_pn-xset = "Armin Kuster 
"
 RECIPE_MAINTAINER_pn-xtrans = "Armin Kuster "
 RECIPE_MAINTAINER_pn-xuser-account = "Armin Kuster "
 RECIPE_MAINTAINER_pn-xvinfo = "Armin Kuster "
+RECIPE_MAINTAINER_pn-xwayland = "Armin Kuster "
 RECIPE_MAINTAINER_pn-xwininfo = "Armin Kuster "
 RECIPE_MAINTAINER_pn-xxhash = "Alexander Kanavin "
 RECIPE_MAINTAINER_pn-xz = "Denys Dmytriyenko "
diff --git a/meta/recipes-graphics/xwayland/xwayland_21.1.1.bb 
b/meta/recipes-graphics/xwayland/xwayland_21.1.1.bb
new file mode 100644
index 00..82765cdaf9
--- /dev/null
+++ b/meta/recipes-graphics/xwayland/xwayland_21.1.1.bb
@@ -0,0 +1,21 @@
+SUMMARY = "XWayland is an X Server that runs under Wayland."
+DESCRIPTION = "XWayland is an X Server running as a Wayland client, \
+and thus is capable of displaying native X11 client applications in a \
+Wayland compositor environment. The goal of XWayland is to facilitate \
+the transition from X Window System to Wayland environments, providing \
+a way to run unported applications in the meantime."
+HOMEPAGE = "https://fedoraproject.org/wiki/Changes/XwaylandStandalone;
+
+LICENSE = "MIT-X"
+LIC_FILES_CHKSUM = "file://COPYING;md5=5df87950af51ac2c5822094553ea1880"
+
+SRC_URI = "https://www.x.org/archive/individual/xserver/xwayland-${PV}.tar.xz;
+SRC_URI[sha256sum] = 
"31f261ce51bbee76a6ca3ec02aa367ffa2b5efa2b98412df57ccefd7a19003ce"
+
+inherit meson features_check
+REQUIRED_DISTRO_FEATURES = "x11"
+
+DEPENDS += "xorgproto xtrans pixman libxkbfile libxfont2 wayland 
wayland-native wayland-protocols libdrm libepoxy"
+
+FILES_${PN} += "${libdir}/xorg/protocol.txt"
+
-- 
2.30.2


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

[OE-core] [PATCH 3/4] default-distrovars.inc: add debuginfod to default DISTRO_FEATURES

2021-04-19 Thread Alexander Kanavin

Obtaining debug information by having it served automatically via http
is far more pleasant than messing about with debugfs and gdbserver or
transferring and installing -dbg packages by hand.

I believe we should follow the desktop distros and have it enabled
out of the box. Please see the following commit for the description
of how it works.

Signed-off-by: Alexander Kanavin 
---
 meta/conf/distro/include/default-distrovars.inc  | 2 +-
 meta/recipes-devtools/binutils/binutils_2.36.bb  | 2 +-
 meta/recipes-devtools/elfutils/elfutils_0.183.bb | 2 +-
 meta/recipes-devtools/gdb/gdb-common.inc | 2 +-
 4 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/meta/conf/distro/include/default-distrovars.inc 
b/meta/conf/distro/include/default-distrovars.inc
index 433d4b6651..9fcc10f83a 100644
--- a/meta/conf/distro/include/default-distrovars.inc
+++ b/meta/conf/distro/include/default-distrovars.inc
@@ -10,7 +10,7 @@ LOCALE_UTF8_ONLY ?= "0"
 LOCALE_UTF8_IS_DEFAULT ?= "1"
 LOCALE_UTF8_IS_DEFAULT_class-nativesdk = "0"
 
-DISTRO_FEATURES_DEFAULT ?= "acl alsa argp bluetooth ext2 ipv4 ipv6 largefile 
pcmcia usbgadget usbhost wifi xattr nfs zeroconf pci 3g nfc x11 vfat"
+DISTRO_FEATURES_DEFAULT ?= "acl alsa argp bluetooth debuginfod ext2 ipv4 ipv6 
largefile pcmcia usbgadget usbhost wifi xattr nfs zeroconf pci 3g nfc x11 vfat"
 DISTRO_FEATURES ?= "${DISTRO_FEATURES_DEFAULT}"
 IMAGE_FEATURES ?= ""
 
diff --git a/meta/recipes-devtools/binutils/binutils_2.36.bb 
b/meta/recipes-devtools/binutils/binutils_2.36.bb
index a50d2ee7ee..ee9617de1d 100644
--- a/meta/recipes-devtools/binutils/binutils_2.36.bb
+++ b/meta/recipes-devtools/binutils/binutils_2.36.bb
@@ -25,7 +25,7 @@ EXTRA_OECONF_class-native = "--enable-targets=all \
  --disable-sim \
  --disable-werror"
 
-PACKAGECONFIG ??= ""
+PACKAGECONFIG ??= "${@bb.utils.filter('DISTRO_FEATURES', 'debuginfod', d)}"
 PACKAGECONFIG[debuginfod] = "--with-debuginfod, --without-debuginfod, elfutils"
 # gcc9.0 end up mis-compiling libbfd.so with O2 which then crashes on target
 # So remove -O2 and use -Os as workaround
diff --git a/meta/recipes-devtools/elfutils/elfutils_0.183.bb 
b/meta/recipes-devtools/elfutils/elfutils_0.183.bb
index c0833686de..8b1dece200 100644
--- a/meta/recipes-devtools/elfutils/elfutils_0.183.bb
+++ b/meta/recipes-devtools/elfutils/elfutils_0.183.bb
@@ -38,7 +38,7 @@ EXTRA_OECONF = "--program-prefix=eu-"
 DEPENDS_BZIP2 = "bzip2-replacement-native"
 DEPENDS_BZIP2_class-target = "bzip2"
 
-PACKAGECONFIG ??= ""
+PACKAGECONFIG ??= "${@bb.utils.contains('DISTRO_FEATURES', 'debuginfod', 
'debuginfod libdebuginfod', '', d)}"
 PACKAGECONFIG[bzip2] = "--with-bzlib,--without-bzlib,${DEPENDS_BZIP2}"
 PACKAGECONFIG[xz] = "--with-lzma,--without-lzma,xz"
 PACKAGECONFIG[libdebuginfod] = 
"--enable-libdebuginfod,--disable-libdebuginfod,curl"
diff --git a/meta/recipes-devtools/gdb/gdb-common.inc 
b/meta/recipes-devtools/gdb/gdb-common.inc
index 6e04552034..a2a6364daf 100644
--- a/meta/recipes-devtools/gdb/gdb-common.inc
+++ b/meta/recipes-devtools/gdb/gdb-common.inc
@@ -29,7 +29,7 @@ EXTRA_OECONF = "--disable-gdbtk --disable-x --disable-werror \
 --disable-gprof \
 "
 
-PACKAGECONFIG ??= "readline"
+PACKAGECONFIG ??= "readline ${@bb.utils.filter('DISTRO_FEATURES', 
'debuginfod', d)}"
 # Use --without-system-readline to compile with readline 5.
 PACKAGECONFIG[readline] = 
"--with-system-readline,--without-system-readline,readline"
 PACKAGECONFIG[python] = 
"--with-python=${WORKDIR}/python,--without-python,python3,python3 
python3-codecs"
-- 
2.30.2


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

[OE-core] [PATCH 2/4] libmicrohttpd: add a recipe from meta-oe

2021-04-19 Thread Alexander Kanavin

This is required to enable debuginfod in elfutils.

Signed-off-by: Alexander Kanavin 
---
 .../libmicrohttpd/libmicrohttpd_0.9.72.bb | 31 +++
 1 file changed, 31 insertions(+)
 create mode 100644 meta/recipes-support/libmicrohttpd/libmicrohttpd_0.9.72.bb

diff --git a/meta/recipes-support/libmicrohttpd/libmicrohttpd_0.9.72.bb 
b/meta/recipes-support/libmicrohttpd/libmicrohttpd_0.9.72.bb
new file mode 100644
index 00..66c48da3b7
--- /dev/null
+++ b/meta/recipes-support/libmicrohttpd/libmicrohttpd_0.9.72.bb
@@ -0,0 +1,31 @@
+DESCRIPTION = "A small C library that is supposed to make it easy to run an 
HTTP server as part of another application"
+HOMEPAGE = "http://www.gnu.org/software/libmicrohttpd/;
+LICENSE = "LGPL-2.1+"
+LIC_FILES_CHKSUM = "file://COPYING;md5=57d09285feac8a64efa878e692b14f36"
+SECTION = "net"
+
+DEPENDS = "file"
+
+SRC_URI = "${GNU_MIRROR}/libmicrohttpd/${BPN}-${PV}.tar.gz"
+SRC_URI[md5sum] = "2a286193af88ab2ae3149748d4b46187"
+SRC_URI[sha256sum] = 
"0ae825f8e0d7f41201fd44a0df1cf454c1cb0bc50fe9d59c26552260264c2ff8"
+
+inherit autotools lib_package pkgconfig gettext
+
+CFLAGS += "-pthread -D_REENTRANT"
+
+EXTRA_OECONF += "--disable-static --with-gnutls=${STAGING_LIBDIR}/../"
+
+PACKAGECONFIG ?= "curl https"
+PACKAGECONFIG_append_class-target = "\
+${@bb.utils.filter('DISTRO_FEATURES', 'largefile', d)} \
+"
+PACKAGECONFIG[largefile] = "--enable-largefile,--disable-largefile,,"
+PACKAGECONFIG[curl] = "--enable-curl,--disable-curl,curl,"
+PACKAGECONFIG[https] = "--enable-https,--disable-https,libgcrypt gnutls,"
+
+do_compile_append() {
+sed -i s:-L${STAGING_LIBDIR}::g libmicrohttpd.pc
+}
+
+BBCLASSEXTEND = "native nativesdk"
-- 
2.30.2


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

[OE-core] [PATCH 4/4] dev-manual/common-tasks.rst: correct the documentation for debuginfod

2021-04-19 Thread Alexander Kanavin

Particularly,
- correctly describe the use of DEBUGINFOD_URLS; drop it from bitbake variables
- all necessary component tweaks are enabled by default via DISTRO_FEATURES
- provide on-target examples of what to look for when things work properly

Signed-off-by: Alexander Kanavin 
---
 documentation/dev-manual/common-tasks.rst | 34 +++
 documentation/ref-manual/variables.rst|  6 
 2 files changed, 22 insertions(+), 18 deletions(-)

diff --git a/documentation/dev-manual/common-tasks.rst 
b/documentation/dev-manual/common-tasks.rst
index 176025f9e8..9f33b6b2c8 100644
--- a/documentation/dev-manual/common-tasks.rst
+++ b/documentation/dev-manual/common-tasks.rst
@@ -10005,34 +10005,44 @@ debug symbols from the server.
 
 To run a debuginfod server, you need to do the following:
 
--  Ensure that this variable is set in your ``local.conf`` file:
+-  Ensure that "debuginfod" is present in :term:`DISTRO_FEATURES
+   (it already is in oe-core defaults and poky reference distribution).
+   If not, set:
::
 
-  PACKAGECONFIG_pn-elfutils-native = "debuginfod libdebuginfod"
+  DISTRO_FEATURES_append = " debuginfod"
 
-   This :term:`PACKAGECONFIG` option enables debuginfod and libdebuginfod for
-   "elfutils-native".
+   This distro feature enables the server and client library in elfutils,
+   and enables debuginfod support in clients (at the moment, gdb and binutils).
 
--  Run the following commands to set up the "debuginfod" server:
+-  Run the following commands to launch the "debuginfod" server on the host:
::
 
   $ oe-debuginfod
 
+-  To use debuginfod on the target, you need to know the ip:port where
+   debuginfod is listening on the host (port defaults to 8002), and export
+   that into the shell environment, for example in qemu:
+   ::
 
-To use debuginfod on the target, you need the following:
+  root@qemux86-64:~# export DEBUGINFOD_URLS="http://192.168.7.1:8002/;
 
--  Ensure that this variable is set in your ``local.conf`` file:
+-  Then debug info fetching should simply work when running the target gdb,
+   readelf or objdump, for example:
::
 
-  DEBUGINFOD_URLS = "http://localhost:8002/;
-
-   This :term:`DEBUGINFOD_URLS` option does the client configuration.
+  root@qemux86-64:~# gdb /bin/cat
+  ...
+  Reading symbols from /bin/cat...
+  Downloading separate debug info for /bin/cat...
+  Reading symbols from 
/home/root/.cache/debuginfod_client/923dc4780cfbc545850c616bffa884b6b5eaf322/debuginfo...
 
+-  It's also possible to use "debuginfod-find" to just query the server:
::
 
-PACKAGECONFIG_pn-gdb = "debuginfod"
+  root@qemux86-64:~# debuginfod-find debuginfo /bin/ls
+  
/home/root/.cache/debuginfod_client/356edc585f7f82d46f94fcb87a86a3fe2d2e60bd/debuginfo
 
-   This :term:`PACKAGECONFIG` option enables "debuginfod" for "gdb".
 
 Using the gdbserver method
 ~
diff --git a/documentation/ref-manual/variables.rst 
b/documentation/ref-manual/variables.rst
index 74ac12bf98..8a35b0960e 100644
--- a/documentation/ref-manual/variables.rst
+++ b/documentation/ref-manual/variables.rst
@@ -1563,12 +1563,6 @@ system and gives an overview of their function and 
contents.
 
  DEBIANNAME_${PN} = "dbus-1"
 
-   :term:`DEBUGINFOD_URLS`
-  Points to the URL of the "debuginfod" server. Such that for every
-  debugging information lookup, the debuginfod client will query the
-  server and return the requested information. You set this variable
-  in your ``local.conf`` file.
-
:term:`DEBUG_BUILD`
   Specifies to build packages with debugging information. This
   influences the value of the ``SELECTED_OPTIMIZATION`` variable.
-- 
2.30.2


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

[OE-core] [PATCH 1/4] scripts/oe-debuginfod: correct several issues

2021-04-19 Thread Alexander Kanavin

Particularly:
- nesting subprocess.run() inside subprocess.check_output() does not work at 
all.
How was this tested?
- -R and -U options can be combined; no need to separate the invocations based
on packaging format
- both exception handlers are unnecessary; we can simply print the hint if
invocation did not succeed
- to run debuginfod from its own sysroot, '-c addto_recipe_sysroot' for 
elfutils-native
must be executed

Signed-off-by: Alexander Kanavin 
---
 scripts/oe-debuginfod | 13 -
 1 file changed, 4 insertions(+), 9 deletions(-)

diff --git a/scripts/oe-debuginfod b/scripts/oe-debuginfod
index 967dd5807c..5560769888 100755
--- a/scripts/oe-debuginfod
+++ b/scripts/oe-debuginfod
@@ -20,12 +20,7 @@ if __name__ == "__main__":
 package_classes_var = "DEPLOY_DIR_" + 
tinfoil.config_data.getVar("PACKAGE_CLASSES").split()[0].replace("package_", 
"").upper()
 feed_dir = tinfoil.config_data.getVar(package_classes_var, expand=True)
 
-try:
-if package_classes_var == "DEPLOY_DIR_RPM":
-subprocess.check_output(subprocess.run(['oe-run-native', 
'elfutils-native', 'debuginfod', '--verbose', '-R', feed_dir]))
-else:
-subprocess.check_output(subprocess.run(['oe-run-native', 
'elfutils-native', 'debuginfod', '--verbose', '-U', feed_dir]))
-except subprocess.CalledProcessError:
-print("\nTo use the debuginfod server Please ensure that this variable 
PACKAGECONFIG_pn-elfutils-native = \"debuginfod libdebuginfod\" is set in the 
local.conf")
-except KeyboardInterrupt:
-sys.exit(1)
+subprocess.call(['bitbake', '-c', 'addto_recipe_sysroot', 
'elfutils-native'])
+
+subprocess.call(['oe-run-native', 'elfutils-native', 'debuginfod', 
'--verbose', '-R', '-U', feed_dir])
+print("\nTo use the debuginfod server please ensure that this variable 
PACKAGECONFIG_pn-elfutils-native = \"debuginfod libdebuginfod\" is set in the 
local.conf")
-- 
2.30.2


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

Re: [OE-core] [PATCH v2] go: upgrade 1.16.2 -> 1.16.3

2021-04-19 Thread Martin Jansa

On Mon, Apr 19, 2021 at 04:25:26AM +, Naveen Saini wrote:
> [SWAT]
> Fetching error:
> recipe go-runtime-1.16.3-r0: task do_fetch: Failed
> https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/2053/steps/23/logs/stdio

That seems related to
https://git.openembedded.org/openembedded-core/commit/?id=2a1eb731ed3bcb049192550e362b771c3a9ea6eb
not this go upgrade.

Also locally I can fetch this over http:// as well as https:// without
any issues with wget, but it's true that with chrome I see valid
certificate on https://golang.org/dl but not on
https://golang.org/dl/go1.16.3.src.tar.gz
or
https://golang.org/dl/go1.16.2.src.tar.gz

and curl downloads just the link to dl.google.com/go 
$ curl https://golang.org/dl/go1.16.3.src.tar.gz 
https://dl.google.com/go/go1.16.3.src.tar.gz;>Found.

Maybe we should just use https://dl.google.com/go directly to fetch
go.
 
> From: openembedded-core@lists.openembedded.org 
>  On Behalf Of Alejandro Hernandez 
> Samaniego
> Sent: Thursday, April 15, 2021 5:49 AM
> To: Khem Raj ; openembedded-core@lists.openembedded.org
> Cc: wangmy 
> Subject: Re: [OE-core] [PATCH v2] go: upgrade 1.16.2 -> 1.16.3
> 
> 
> Hello,
> 
> 
> 
> This one is causing failures in test_yocto_source_mirror
> 
> https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/2037/steps/23/logs/stdio
> 
> although since its still on master-next my guess is that its sources havent 
> been published
> 
> yet to downloads.yoctoproject.org
> 
> 
> 
> Alejandro
> 
> 
> On 4/10/21 1:30 AM, Khem Raj wrote:
> 
> From: wangmy 
> 
> 
> 
> This is bugfix release in 1.16 series [1]
> 
> 
> 
> [1] 
> https://github.com/golang/go/issues?q=milestone%3AGo1.16.3+label%3ACherryPickApproved
> 
> 
> 
> Signed-off-by: Wang Mingyu 
> 
> Signed-off-by: Khem Raj 
> 
> ---
> 
> v2: Fix checksums and improve commit msg
> 
> 
> 
>  meta/recipes-devtools/go/{go-1.16.2.inc => go-1.16.3.inc} | 4 ++--
> 
>  ...{go-binary-native_1.16.2.bb => go-binary-native_1.16.3.bb} | 4 ++--
> 
>  ...o-cross-canadian_1.16.2.bb => go-cross-canadian_1.16.3.bb} | 0
> 
>  .../go/{go-cross_1.16.2.bb => go-cross_1.16.3.bb} | 0
> 
>  .../go/{go-crosssdk_1.16.2.bb => go-crosssdk_1.16.3.bb}   | 0
> 
>  .../go/{go-native_1.16.2.bb => go-native_1.16.3.bb}   | 0
> 
>  .../go/{go-runtime_1.16.2.bb => go-runtime_1.16.3.bb} | 0
> 
>  meta/recipes-devtools/go/{go_1.16.2.bb => go_1.16.3.bb}   | 0
> 
>  8 files changed, 4 insertions(+), 4 deletions(-)
> 
>  rename meta/recipes-devtools/go/{go-1.16.2.inc => go-1.16.3.inc} (88%)
> 
>  rename meta/recipes-devtools/go/{go-binary-native_1.16.2.bb => 
> go-binary-native_1.16.3.bb} (83%)
> 
>  rename meta/recipes-devtools/go/{go-cross-canadian_1.16.2.bb => 
> go-cross-canadian_1.16.3.bb} (100%)
> 
>  rename meta/recipes-devtools/go/{go-cross_1.16.2.bb => go-cross_1.16.3.bb} 
> (100%)
> 
>  rename meta/recipes-devtools/go/{go-crosssdk_1.16.2.bb => 
> go-crosssdk_1.16.3.bb} (100%)
> 
>  rename meta/recipes-devtools/go/{go-native_1.16.2.bb => go-native_1.16.3.bb} 
> (100%)
> 
>  rename meta/recipes-devtools/go/{go-runtime_1.16.2.bb => 
> go-runtime_1.16.3.bb} (100%)
> 
>  rename meta/recipes-devtools/go/{go_1.16.2.bb => go_1.16.3.bb} (100%)
> 
> 
> 
> diff --git a/meta/recipes-devtools/go/go-1.16.2.inc 
> b/meta/recipes-devtools/go/go-1.16.3.inc
> 
> similarity index 88%
> 
> rename from meta/recipes-devtools/go/go-1.16.2.inc
> 
> rename to meta/recipes-devtools/go/go-1.16.3.inc
> 
> index e65caf8197..ebd25a5eaa 100644
> 
> --- a/meta/recipes-devtools/go/go-1.16.2.inc
> 
> +++ b/meta/recipes-devtools/go/go-1.16.3.inc
> 
> @@ -1,7 +1,7 @@
> 
>  require go-common.inc
> 
> 
> 
>  GO_BASEVERSION = "1.16"
> 
> -PV = "1.16.2"
> 
> +PV = "1.16.3"
> 
>  FILESEXTRAPATHS_prepend := "${FILE_DIRNAME}/go-${GO_BASEVERSION}:"
> 
> 
> 
>  LIC_FILES_CHKSUM = 
> "file://LICENSE;md5=5d4950ecb7b26d2c5e4e7b4e0dd74707"
> 
> @@ -17,4 +17,4 @@ SRC_URI += "\
> 
>  file://0008-use-GOBUILDMODE-to-set-buildmode.patch \
> 
>  file://0009-Revert-cmd-go-make-sure-CC-and-CXX-are-absolute.patch \
> 
>  "
> 
> -SRC_URI[main.sha256sum] = 
> "37ca14287a23cb8ba2ac3f5c3dd8adbc1f7a54b9701a57824bf19a0b271f83ea"
> 
> +SRC_URI[main.sha256sum] = 
> "b298d29de9236ca47a023e382313bcc2d2eed31dfa706b60a04103ce83a71a25"
> 
> diff --git a/meta/recipes-devtools/go/go-binary-native_1.16.2.bb 
> b/meta/recipes-devtools/go/go-binary-native_1.16.3.bb
> 
> similarity index 83%
> 
> rename from meta/recipes-devtools/go/go-binary-native_1.16.2.bb
> 
> rename to meta/recipes-devtools/go/go-binary-native_1.16.3.bb
> 
> index 4fb060173c..d01a2bd8f1 100644
> 
> --- a/meta/recipes-devtools/go/go-binary-native_1.16.2.bb
> 
> +++ b/meta/recipes-devtools/go/go-binary-native_1.16.3.bb
> 
> @@ -8,8 +8,8 @@ LIC_FILES_CHKSUM = 
> "file://LICENSE;md5=5d4950ecb7b26d2c5e4e7b4e0dd74707"
> 
>  PROVIDES = "go-native"
> 
> 
> 
>  SRC_URI = 
>

Re: [OE-core] [PATCH] perl: fix startperl configuration option for perl-native

2021-04-19 Thread Naveen Saini

[SWAT] 
AB failure link:
https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/2050

> -Original Message-
> From: openembedded-core@lists.openembedded.org  c...@lists.openembedded.org> On Behalf Of Khem Raj
> Sent: Saturday, April 17, 2021 11:01 PM
> To: Paulo Cesar Zaneti 
> Cc: Patches and discussions about the oe-core layer  c...@lists.openembedded.org>
> Subject: Re: [OE-core] [PATCH] perl: fix startperl configuration option for
> perl-native
> 
> I am seeing failure in native recipes e.g. opkg-utils-native
> 
> 
> | /usr/bin/env: ‘nativeperl-native/perl’: No such file or directory
> | make: *** [Makefile:26: opkg-build.1] Error 127
> | WARNING:
> | /mnt/b/yoe/master/build/tmp/work/x86_64-linux/opkg-utils-native/0.4.3-
> | r0/temp/run.do_compil
> e.2244982:187 exit 1 from 'exit 1'
> 
> On Fri, Apr 16, 2021 at 3:29 PM Paulo Cesar Zaneti 
> wrote:
> >
> > Unlike vanilla Perl "Configure" script, perl-cross "configure" does
> > not derive "startperl" from "bin". It instead derives from "perlpath".
> >
> > This patch aims to fix "startperl" configuration option for
> > perl-native by correctly setting "perlpath" on perl-cross "configure" 
> > script.
> >
> > Signed-off-by: Paulo Cesar Zaneti 
> > ---
> >  meta/recipes-devtools/perl/perl_5.32.1.bb | 1 +
> >  1 file changed, 1 insertion(+)
> >
> > diff --git a/meta/recipes-devtools/perl/perl_5.32.1.bb
> > b/meta/recipes-devtools/perl/perl_5.32.1.bb
> > index b28040c7fb..82c2922066 100644
> > --- a/meta/recipes-devtools/perl/perl_5.32.1.bb
> > +++ b/meta/recipes-devtools/perl/perl_5.32.1.bb
> > @@ -95,6 +95,7 @@ do_configure_class-nativesdk() {
> >  do_configure_class-native() {
> >  ./configure --prefix=${prefix} \
> >  -Dbin=${bindir}/perl-native \
> > +-Dperlpath=${bindir}/perl-native/perl \
> >  -Duseshrplib \
> >  -Dsoname=libperl.so.5 \
> >  -Dvendorprefix=${prefix} \
> > --
> > 2.25.1
> >
> >
> >
> >

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

Re: [OE-core] [PATCH v2] mesa: upgrade 21.0.1 -> 21.0.2

2021-04-19 Thread Alexander Kanavin

Seems like mesa has regressed to using softpipe instead of virgl on target,
but only on Fedora 32. It's odd, because other selftest workers in the same
a-full run (Debian, Ubuntu) are fine.

OpenGL ES 2.x information:

  version: "OpenGL ES 3.1 Mesa 21.0.2"
  shading language version: "OpenGL ES GLSL ES 3.10"
  vendor: "Mesa/X.org"
  renderer: "softpipe"

Can you re-run the selftest on Fedora 32?

Alex


On Mon, 19 Apr 2021 at 05:24, Naveen Saini 
wrote:

> [SWAT]
> Oe-selftest on fedora failed.
>
> RESULTS - virgl.VirglTest.test_kmscube: FAILED (0.30s)
>
> AssertionError: 'renderer: "virgl"' not found in 'Using display
> 0x55dccc0562e0 with EGL version 1.4
> https://autobuilder.yoctoproject.org/typhoon/#/builders/86/builds/2005
>
> Regards,
> Naveen
>
> > -Original Message-
> > From: openembedded-core@lists.openembedded.org  > c...@lists.openembedded.org> On Behalf Of wangmy
> > Sent: Friday, April 16, 2021 7:50 AM
> > To: openembedded-core@lists.openembedded.org
> > Cc: Wang Mingyu 
> > Subject: [OE-core] [PATCH v2] mesa: upgrade 21.0.1 -> 21.0.2
> >
> > Signed-off-by: Wang Mingyu 
> > ---
> >  .../mesa/{mesa-gl_21.0.1.bb => mesa-gl_21.0.2.bb}   | 0
> >  meta/recipes-graphics/mesa/mesa.inc | 2 +-
> >  meta/recipes-graphics/mesa/{mesa_21.0.1.bb => mesa_21.0.2.bb}   | 0
> >  3 files changed, 1 insertion(+), 1 deletion(-)  rename meta/recipes-
> > graphics/mesa/{mesa-gl_21.0.1.bb => mesa-gl_21.0.2.bb} (100%)  rename
> > meta/recipes-graphics/mesa/{mesa_21.0.1.bb => mesa_21.0.2.bb} (100%)
> >
> > diff --git a/meta/recipes-graphics/mesa/mesa-gl_21.0.1.bb
> b/meta/recipes-
> > graphics/mesa/mesa-gl_21.0.2.bb
> > similarity index 100%
> > rename from meta/recipes-graphics/mesa/mesa-gl_21.0.1.bb
> > rename to meta/recipes-graphics/mesa/mesa-gl_21.0.2.bb
> > diff --git a/meta/recipes-graphics/mesa/mesa.inc b/meta/recipes-
> > graphics/mesa/mesa.inc
> > index caf3c62ad8..5705ae0f08 100644
> > --- a/meta/recipes-graphics/mesa/mesa.inc
> > +++ b/meta/recipes-graphics/mesa/mesa.inc
> > @@ -21,7 +21,7 @@ SRC_URI =
> > "https://mesa.freedesktop.org/archive/mesa-${PV}.tar.xz \
> >
>  file://0001-futex.h-Define-__NR_futex-if-it-does-not-exist.patch \
> > "
> >
> > -SRC_URI[sha256sum] =
> > "379fc984459394f2ab2d84049efdc3a659869dc1328ce72ef0598506611712bb"
> > +SRC_URI[sha256sum] =
> > "46c1dc5bb54a372dee43ec3c067229c299187d5bdadf1402756bbf66a6df5b88"
> >
> >  UPSTREAM_CHECK_GITTAGREGEX = "mesa-(?P\d+(\.\d+)+)"
> >
> > diff --git a/meta/recipes-graphics/mesa/mesa_21.0.1.bb b/meta/recipes-
> > graphics/mesa/mesa_21.0.2.bb
> > similarity index 100%
> > rename from meta/recipes-graphics/mesa/mesa_21.0.1.bb
> > rename to meta/recipes-graphics/mesa/mesa_21.0.2.bb
> > --
> > 2.25.1
>
>
> 
>
>

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

Re: [OE-core] [PATCH] db: correct CVE_PRODUCT

2021-04-19 Thread Mikko Rapeli

On Mon, Apr 19, 2021 at 09:45:01PM +0800, zhengruoqin wrote:
> In the CVE database, now it use db2 instead of oracle_berkeley_db.
> So, in order to be handled correctly by CVE check, modify CVE_ PRODUCT.

Which CVEs, please add an example? In the past oracle_berkeley_db was used.
I wonder if both would need to be there, or if using the new value is
sufficient from now on.

-Mikko

> Signed-off-by: Zheng Ruoqin 
> ---
>  meta/recipes-support/db/db_5.3.28.bb | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/meta/recipes-support/db/db_5.3.28.bb 
> b/meta/recipes-support/db/db_5.3.28.bb
> index 9cb57e6a53..05720053f4 100644
> --- a/meta/recipes-support/db/db_5.3.28.bb
> +++ b/meta/recipes-support/db/db_5.3.28.bb
> @@ -15,7 +15,7 @@ HOMEPAGE = 
> "https://www.oracle.com/database/technologies/related/berkeleydb.html
>  LICENSE = "Sleepycat"
>  RCONFLICTS_${PN} = "db3"
>
> -CVE_PRODUCT = "oracle_berkeley_db"
> +CVE_PRODUCT = "db2"
>  CVE_VERSION = "11.2.${PV}"
>
>  PR = "r1"
> -- 
> 2.25.1
> 

> 
> 
> 

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

Re: [OE-core] [PATCH] ca-certificates: Fix openssl runtime cert dependencies

2021-04-19 Thread Mikko Rapeli

Hi,

On Sun, Apr 18, 2021 at 03:53:10PM -0700, Khem Raj wrote:
> With commit dc778c70449ee5401b5a24ad18b22b88338c47c5, dependency was
> moved to openssl-bin which in itself was a fine change, but dropping
> dependency on openssl too should have been kept along, dropping this
> meant that openssl binary wont be able to validate secure connections as
> the CApath files wont be installed, which infact are required for
> openssl bins to work, following call e.g. fails
> 
> $ openssl s_client -connect google.com:443

This sounds a lot like a ptest or selftest? Maybe using
some yocto server instead of google though.

Cheers,

-Mikko

> 
> New, TLSv1.3, Cipher is TLS_AES_256_GCM_SHA384
> Server public key is 256 bit
> Secure Renegotiation IS NOT supported
> Compression: NONE
> Expansion: NONE
> No ALPN negotiated
> Early data was not sent
> Verify return code: 20 (unable to get local issuer certificate)
> 
> 
> The local issuer certs are not found in default location
> /usr/lib/ssh-1.1/certs, this dir and its content is installed by openssl 
> package
> therefore re-add the dependency on openssl
> 
> Signed-off-by: Khem Raj 
> Cc: Andrei Gherzan 
> ---
>  .../ca-certificates/ca-certificates_20210119.bb | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/meta/recipes-support/ca-certificates/ca-certificates_20210119.bb 
> b/meta/recipes-support/ca-certificates/ca-certificates_20210119.bb
> index 888a235c1a..7dcc86fdc1 100644
> --- a/meta/recipes-support/ca-certificates/ca-certificates_20210119.bb
> +++ b/meta/recipes-support/ca-certificates/ca-certificates_20210119.bb
> @@ -83,8 +83,8 @@ do_install_append_class-native () {
>  SYSROOT="${D}${base_prefix}" ${D}${sbindir}/update-ca-certificates
>  }
>
> -RDEPENDS_${PN}_class-target = "openssl-bin"
> -RDEPENDS_${PN}_class-native = "openssl-native"
> -RDEPENDS_${PN}_class-nativesdk = "nativesdk-openssl-bin"
> +RDEPENDS_${PN}_append_class-target = " openssl-bin openssl"
> +RDEPENDS_${PN}_append_class-native = " openssl-native"
> +RDEPENDS_${PN}_append_class-nativesdk = " nativesdk-openssl-bin 
> nativesdk-openssl"
>
>  BBCLASSEXTEND = "native nativesdk"
> -- 
> 2.31.1
> 

> 
> 
> 

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

Re: [OE-core] [PATCH 08/10] linux-yocto/5.10: update to v5.10.30

Re: [OE-core] [PATCH 10/10] linux-yocto/5.4: update to v5.4.112

Re: [OE-core] [PATCH 08/10] linux-yocto/5.10: update to v5.10.30

[OE-core][PATCH] db: update CVE_PRODUCT

Re: [OE-core] [PATCH] db: correct CVE_PRODUCT

Re: [OE-core] [PATCH] db: correct CVE_PRODUCT

Re: [OE-core] [PATCH] db: correct CVE_PRODUCT

[OE-core] Yocto Project Newcomer & Unassigned Bugs - Help Needed

Re: [OE-core] [PATCH v2 1/3] btrfs-tools: Update to 5.11.1

Re: [OE-core] [PATCH 3/4] default-distrovars.inc: add debuginfod to default DISTRO_FEATURES

Re: [OE-core] [PATCH] Use shutil.move when os.rename fails

Re: [OE-core] [PATCH 2/4] libmicrohttpd: add a recipe from meta-oe

Re: [OE-core] [PATCH 3/4] default-distrovars.inc: add debuginfod to default DISTRO_FEATURES

Re: [OE-core] [PATCH v2] go: upgrade 1.16.2 -> 1.16.3

Re: [OE-core] [PATCH] ca-certificates: Fix openssl runtime cert dependencies

Re: [OE-core] [PATCH] perl: fix startperl configuration option for perl-native

[OE-core] [PATCH v2] perl: fix startperl configuration option for perl-native

[OE-core][PATCH] nettle: upgrade 3.7.1 -> 3.7.2

Re: [OE-core] [docs] [PATCH] dev-manual/common-tasks.rst: correct the documentation for debuginfod

[OE-core] [PATCH] dev-manual/common-tasks.rst: correct the documentation for debuginfod

[OE-core] [PATCH] maintainers.inc: add libmicrohttpd entry

[OE-core] [PATCH] sanity: Further improve directory sanity tests

[OE-core] [PATCH] bitbake: crash when using git LFS and submodules

[OE-core] [PATCH 2/2] weston: use standalone xwayland instead of outdated xserver-xorg version

[OE-core] [PATCH 1/2] xwayland: add a standalone recipe

[OE-core] [PATCH 3/4] default-distrovars.inc: add debuginfod to default DISTRO_FEATURES

[OE-core] [PATCH 2/4] libmicrohttpd: add a recipe from meta-oe

[OE-core] [PATCH 4/4] dev-manual/common-tasks.rst: correct the documentation for debuginfod

[OE-core] [PATCH 1/4] scripts/oe-debuginfod: correct several issues

Re: [OE-core] [PATCH v2] go: upgrade 1.16.2 -> 1.16.3

Re: [OE-core] [PATCH] perl: fix startperl configuration option for perl-native

Re: [OE-core] [PATCH v2] mesa: upgrade 21.0.1 -> 21.0.2

Re: [OE-core] [PATCH] db: correct CVE_PRODUCT

Re: [OE-core] [PATCH] ca-certificates: Fix openssl runtime cert dependencies

34 matches

Site Navigation

Mail list logo

Footer information