[yocto] iso-codes project

[Michael Nazzareno Trimarchi]

Hi all

anyone has problem on iso-codes in thud. Seems that project was
changed and not possible to download with the actual configuration

Michael

-- 
| Michael Nazzareno Trimarchi Amarula Solutions BV |
| COO  -  Founder  Cruquiuskade 47 |
| +31(0)851119172 Amsterdam 1018 AM NL |
|  [`as] http://www.amarulasolutions.com   |
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

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

[yocto] Yocto Technical Team Minutes, Engineering Sync, for July 7, 2020

[Trevor Woerner]

Yocto Technical Team Minutes, Engineering Sync, for July 7, 2020
archive: 
https://docs.google.com/document/d/1ly8nyhO14kDNnFcW2QskANXW3ZT7QwKC5wWVDg9dDH4/edit

== disclaimer ==
Best efforts are made to ensure the below is accurate and valid. However,
errors sometimes happen. If any errors or omissions are found, please feel
free to reply to this email with any corrections.

== attendees ==
Trevor Woerner, Jan-Simon Möller, Stephen Jolly, Josef Holtzmeyer, Joshua
Watt, Trevor Gamblin, Steve Sakoman, Armin Kuster, Scott Murray, Peter
Kjellerstedt, Saul Wold, Ross Burton, Richard Purdie, Michael Halstead,
Rahul, Vineela?, Bruce Ashfield, Tim Orling, Randy MacLeod, Mathew Zeng,
Rob Woolley, Philip Balister, Paul Barker, Khem Raj

== notes ==
- thanks to everyone involved in any way with ELC and DevDay!
- still have AB instability
- still looking for more maintainers
- looking for way to attract and thank contributors
- lots of unassigned bugs we’d like to see for 3.2 (see unassigned bugs)

== general ==
RP: happy to have some things fixed in AB, but still issues

RP: thanks to everyone involved in ELC and especially the Yocto DevDay

Timo: i see the perl update was merged, but it seems like lots of things
were dropped (RDEPENDS), so i predict there will still be issues with
split-packaging
RP: i noticed that too, the AB was all green
Timo: we’re probably missing tests

Saul: heard a rumor about Stephen
Stephen: that i’m retiring? yes, next week. but i’m continuing on as a
volunteer with YP
Randy: how long at Intel?
Stephen: 34.5 years

RP: ? licenses are inherited globally, are people using the license package
directly?
JPEW: we display the generic and specific license because they’re there
SS: customers i’ve known have always used just the generic
Randy: WR has its own code for analysing the code to pull licenses, but
customers appreciate having the generic
Peter: we have to go through the code to sort out the 20 different variations
on GPLv2, a mess!
RP: it’s been pointed out to me that the checksums of the generic license
files are not checked, so if there was ever a change in the generic text,
there isn’t anything that would alert the users
Peter: is it meaningful to use checksums for the generic text? that’s not
the same case as the license of some upstream code changing
RP: well, if that changes then the task-hash should change which is supposed
to case rebuilds etc
JPEW: there was a bug filed
https://bugzilla.yoctoproject.org/show_bug.cgi?id=13917
RP: this shouldn’t be happening, but there are probably other “games”
going on

RP: is anyone using the SPDX class from OE-core? i hope the answer is
“no”, i imagine it’s quite broken by now. i have a patch i plan to
post
Randy: i don’t see WR using it (quick look)

Timo: i was looking at patchwork again, is there somewhere we can run a test
instance somewhere for testing
Michael: vm at digital ocean currently, i can create a staging instance on YP
hardware. who else will be using it?
Timo: Amber, potentially. i’ll give you an update
Michael: i’ll spin up something new, the current is ubuntu 16.04 so it needs
an update anyway

TW: how did the booth go last week at ELC virtual?
Philip Balister: the interface for the booth was clucky, didn’t get any new
contacts
Timo: i had one interesting contact at the booth, but it didn’t go as well
as it could have
Josef: not a lot of new folks, got a lot of people contacting me in thanks
for the live coding stuff, lots of contacts from the middle-European and
south-central Asia, we have lots of contacts in west Europe and NA, but
need to develop more in the other areas
RP: this would be a good question for the advocacy list
Randy: do you know what sort of communication would work best?
Josef: lots via linked-in, stack overflow. irc and email are not that popular.
lots and lots in twitter!
Timo: agree with twitter

Timo: what did people think of using slack?
TrevorG: hard to know whether to reply in-line or as a thread
Philip: feel it’s terrible for open source to use slack (free version
loses history, bad optics). gnu radio tried slack, moved away. recommend
mattermost
JPEW: slack can work if you have the ability to create arbitrary channels
(which wasn’t available with the ELC slack)
Scott: the mattermost interface has better handling for threads, a “best of
both worlds” between slack and irc
Timo: gitter (meta-python, etc) works better for me. i agree with Philip that
the thread thing
Philip: i’d be curious to see a mattermost try
RP: matrix might be a good way to bridge both worlds (traditional use irc,
younger crowd using other things)
Philip: matrix worked well for gnu radio
Paul: agree with others that slack wasn’t that great, but think that we
should explore other technologies
Timo: looking at what Fedora has done, it’d be great to see more
integration. e.g. reports from AB reported live
Khem: 

Re: [linux-yocto] [yocto-kernel-cache]: bcm-2xxx-rpi: adjuest kernel config for bcm-2xxx-rpi BSP in kernel-cache

[Bruce Ashfield]

In message: [yocto-kernel-cache]: bcm-2xxx-rpi: adjuest kernel config for 
bcm-2xxx-rpi BSP in kernel-cache
on 08/07/2020 meng...@windriver.com wrote:

> From: Limeng 
> 
> Hi Bruce,
> 
> I upgrades kernel patches for BSP bcm-2xxx-rpi when linux-yocto-dev upgrades 
> its version.
> So, the kernel config also should be updated accordingly.
> 
> Could you please help to merge this patch into yocto-kernel-cache, branch is 
> only master?

merged.

Bruce

> 
> diffstat info ad below:
> 
>  bcm-2xxx-rpi.cfg |   42 +-
>  1 file changed, 41 insertions(+), 1 deletion(-)
> 
> 
> thanks,
> Limeng
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

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

Re: [linux-yocto] [yocto-kernel-cache]: [master branch]: renesas-rcar: enable CONFIG_MEDIA_PLATFORM_SUPPORT kernel configuration

[Bruce Ashfield]

In message: [yocto-kernel-cache]: [master branch]: renesas-rcar: enable 
CONFIG_MEDIA_PLATFORM_SUPPORT kernel configuration
on 08/07/2020 meng...@windriver.com wrote:

> From: Limeng 
> 
> Hi Bruce,
> 
> Kernel version has beed upgraded to v5.8, it is need to enable
> CONFIG_MEDIA_PLATFORM_SUPPORT to support media related
> features on renesas-rcar platform.


merged to master of kernel-cache

Bruce

> 
> Could you please merge this patch into yocto-kernel-cache, only branch is 
> master?
> 
> 0001-renesas-rcar-enable-CONFIG_MEDIA_PLATFORM_SUPPORT-ke.patch
> 
>  renesas-rcar.cfg |1 +
>  1 file changed, 1 insertion(+)
> 
> thanks,
> Limeng
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

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

Re: [linux-yocto] [linux-yocto-dev standard/xlnx-soc] xlnx-soc: SDK patches for kernel v5.8

[Bruce Ashfield]

On Tue, Jul 7, 2020 at 3:22 AM Quanyang Wang
 wrote:
>
> Hi Bruce,
>
> Would you please help to remove the obsolete branch standard/xlnx-soc in
> linux-yocto-dev
> and apply these patches for v5.8 as below to the new branch
> standard/xlnx-soc?
>
> There are 1130 patches in this pull request.
>
> Among them, 1128 patches are picked from
> https://github.com/Xilinx/linux-xlnx.git xlnx_rebase_v5.4
>
> and some of them are modified to adapt to the v5.8 kernel.
>
> And the 2 patches "arm: zynq: delete AFLAGS_suspend.o to fix compile
> warning" and
>
> "i2c: cadence: keep bus_hold_flag unless I2C_M_NOSTART is set" are
> picked from the previous

Thanks for the quick update!

I've created the standard/xlnx-soc branch and merged the rebased patches.

Bruce

>
> yocto kernel.
>
> Thanks,
>
> Quanyang
>
>
> The following changes since commit 180bf8803b1282802c22cacc219df5afa08fcf2b:
>
>Merge tag 'v5.8-rc4' into standard/base (2020-07-06 12:21:08 -0400)
>
> are available in the Git repository at:
>
>https://github.com/wqyoung/linux-yocto-dev.git standard/rebase-5.8
>
> for you to fetch changes up to a52b020ba11b87d6f3779eeef9c5ae776331b241:
>
>arm: zynq: delete AFLAGS_suspend.o to fix compile warning (2020-07-07
> 15:07:45 +0800)
>
> 
> Alexandru Ardelean (2):
>uio: rename uio.c -> uio_core.c & unify into uio.ko
>dmaengine: xilinx: dpdma: fix implicit fall-through statements
>
> Alexey Brodkin (1):
>xilinx: Documentation/devicetree - add description for
> "port-number" property
>
> Amit Kumar Mahapatra (24):
>spi: Add Zynq QSPI controller driver
>mtd: spi-nor: Add dual parallel and stacked support for Zynq QSPI
> controller
>mtd: spi-nor: Add 4byte support for Zynq QSPI controller
>dt-bindings: spi: Update dt bindings document
>spi: Update ZynqMP and Versal QSPI controller driver
>mtd: spi-nor: Add support for ZynqMP and Versal QSPI Controller
>dt-bindings: mtd: Update dt binding documentation
>spi: Add multi-die info in spi_device structure
>mtd: spi-nor: Add multi-die read support
>mtd: spi-nor: Update flags for serial NOR flash devices
>mtd: spi-nor: Updated spi_nor_write_ear() api with dual parallel
> and stacked support.
>dt-bindings: spi-xilinx: Updated devicetree bindings for spi-xilinx
>mtd: spi-nor: Added axi-qspi support in spi-nor framework
>spi: spi-xilinx: Updated axi-qspi controller driver
>spi: spi-zynqmp-gqspi: Resolved slab-out-of-bounds bug
>mtd: spi-nor: Fix compilation warnings
>mtd: spi-nor: Fix the issue in checking 4Byte opcode support in
> spi/qspi/ospi controller
>mtd: spi-nor: Remove unwanted spi-nor framework changes
>mtd: spi-nor: Fix kernel crash in case of spi flash
>arm64: zynqmp: Do not duplicate flash partition label property
>mtd: spi-nor: Added support for sst26vf016b spi flash
>mtd: spi-nor: Fix warnings
>spi: spi-mem: Modify update_stripe api to handle different
> commands with same opcode value
>spi: spi-zynqmp-gqspi: Update driver to write appropriate dummy
> cycles as per the tx_buswidth
>
> Anand Ashok Dumbre (2):
>documentation: dt: add bindings documentation for Scene Change
> Detection
>v4l: xilinx: scd: New Scene Change Detection driver
>
> Andrei Simion (1):
>Xilinx: ARM: Devcfg and SLCR drivers updated to support
> reconfiguration.
>
> Anssi Hannula (1):
>serial: uartps: Fix stuck ISR if RX disabled with non-empty FIFO
>
> Anurag Kumar Vulisha (27):
>firmware: xilinx: sync firmware pm_ioctl_id entries with PLM
> pm_ioctl_id entries
>firmware: xilinx: Add IOCTL for handling usb power requests
>usb: xhci: Add workaround for fixing ep stream ring hang issue
>dwc3: core: Enable GUCTL1 chicken bit 10 for fixing crc error
> after resume bug
>dwc3: core: Enable GUCTL1 chicken bit 9 for correcting Inter
> Packet Delay(IPD)
>usb: xhci-plat: Add remote wakeup support
>usb: dwc3: Fix the logic for allocating and setting scratchpad
> buffers
>usb: dwc3: Add hibernation support when operating as gadget
>usb: dwc3: add support for enabling/disabling hibernation dynamically
>usb: dwc3: fix the logic for setting GBLHIBERNATIONEN in GCTL
>usb: xhci: don't clean shared_hcd when otg is enabled
>usb: dwc3: Fix missing peripheral irq error message
>usb: dwc3: Fix the broken suspend/resume functionality in dwc3
>usb: gadget: uvc_video: unlock before submitting a request to ep
>usb: dwc3: Correct usb dma mask for making SMMU work in device mode
>usb: xhci: wait for atleast 1ms after exiting U3
>usb: dwc3: Check for IOC/LST bit in both event->status and
> TRB->ctrl fields
>usb: dwc3: gadget: Don't kick transfer if LST or SHORT bits 

[linux-yocto] [PATCH] renesas-rcar: enable CONFIG_MEDIA_PLATFORM_SUPPORT kernel configure

[Meng Li]

From: Limeng 

Kernel version has beed upgraded to v5.8, it is need to enable
CONFIG_MEDIA_PLATFORM_SUPPORT to support media related
features on renesas-rcar platform.

Signed-off-by: Meng Li 
---
 bsp/renesas-rcar/renesas-rcar.cfg | 1 +
 1 file changed, 1 insertion(+)

diff --git a/bsp/renesas-rcar/renesas-rcar.cfg 
b/bsp/renesas-rcar/renesas-rcar.cfg
index f0a3c2a4..9d5461a2 100644
--- a/bsp/renesas-rcar/renesas-rcar.cfg
+++ b/bsp/renesas-rcar/renesas-rcar.cfg
@@ -173,6 +173,7 @@ CONFIG_CAN_RCAR_CANFD=y
 
 # Multi-Media configuration
 CONFIG_MEDIA_SUPPORT=y
+CONFIG_MEDIA_PLATFORM_SUPPORT=y
 CONFIG_MEDIA_CAMERA_SUPPORT=y
 CONFIG_MEDIA_CONTROLLER=y
 CONFIG_VIDEO_V4L2=y
-- 
2.26.2

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

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

[linux-yocto] [yocto-kernel-cache]: [master branch]: renesas-rcar: enable CONFIG_MEDIA_PLATFORM_SUPPORT kernel configuration

[Meng Li]

From: Limeng 

Hi Bruce,

Kernel version has beed upgraded to v5.8, it is need to enable
CONFIG_MEDIA_PLATFORM_SUPPORT to support media related
features on renesas-rcar platform.

Could you please merge this patch into yocto-kernel-cache, only branch is 
master?

0001-renesas-rcar-enable-CONFIG_MEDIA_PLATFORM_SUPPORT-ke.patch

 renesas-rcar.cfg |1 +
 1 file changed, 1 insertion(+)

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

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

[linux-yocto] [yocto-kernel-cache]: bcm-2xxx-rpi: adjuest kernel config for bcm-2xxx-rpi BSP in kernel-cache

[Meng Li]

From: Limeng 

Hi Bruce,

I upgrades kernel patches for BSP bcm-2xxx-rpi when linux-yocto-dev upgrades 
its version.
So, the kernel config also should be updated accordingly.

Could you please help to merge this patch into yocto-kernel-cache, branch is 
only master?

diffstat info ad below:

 bcm-2xxx-rpi.cfg |   42 +-
 1 file changed, 41 insertions(+), 1 deletion(-)


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

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

[linux-yocto] [PATCH] bcm-2xxx-rpi: adjuest kernel config for bcm-2xxx-rpi BSP in kernel-cache

[Meng Li]

From: Limeng 

In order to match with latest kernel v5.7, some kernel configs
need to be updated.

Signed-off-by: Meng Li 
---
 bsp/bcm-2xxx-rpi/bcm-2xxx-rpi.cfg | 39 +--
 1 file changed, 37 insertions(+), 2 deletions(-)

diff --git a/bsp/bcm-2xxx-rpi/bcm-2xxx-rpi.cfg 
b/bsp/bcm-2xxx-rpi/bcm-2xxx-rpi.cfg
index 0b6eb65c..a8446505 100644
--- a/bsp/bcm-2xxx-rpi/bcm-2xxx-rpi.cfg
+++ b/bsp/bcm-2xxx-rpi/bcm-2xxx-rpi.cfg
@@ -43,6 +43,12 @@ CONFIG_CPU_IDLE=y
 CONFIG_CPU_IDLE_GOV_MENU=y
 CONFIG_ARM_CPUIDLE=y
 
+#
+# CPU frequency
+#
+CONFIG_CPUFREQ_DT=y
+CONFIG_ARM_RASPBERRYPI_CPUFREQ=y
+
 # MTD devices
 CONFIG_MTD=y
 CONFIG_MTD_BLOCK=m
@@ -72,6 +78,7 @@ CONFIG_I2C_CHARDEV=m
 CONFIG_I2C_BCM2708=m
 CONFIG_I2C_BCM2835=m
 CONFIG_I2C_GPIO=m
+CONFIG_I2C_MUX_PINCTRL=m
 CONFIG_EEPROM_AT24=m
 
 # SPI device
@@ -95,6 +102,7 @@ CONFIG_DRM_LOAD_EDID_FIRMWARE=y
 CONFIG_DRM_UDL=m
 CONFIG_DRM_VC4=m
 CONFIG_DRM_V3D=m
+CONFIG_DRM_VC4_HDMI_CEC=y
 
 #PCIe Bus support
 CONFIG_PCI=y
@@ -115,6 +123,12 @@ CONFIG_USB_DWCOTG=y
 CONFIG_USB_XHCI_HCD=y
 CONFIG_USB_PCI=y
 
+#
+# Input Device
+#
+CONFIG_INPUT_TOUCHSCREEN=y
+CONFIG_TOUCHSCREEN_RASPBERRYPI_FW=m
+
 #Media support
 CONFIG_MEDIA_CAMERA_SUPPORT=y
 CONFIG_MEDIA_ANALOG_TV_SUPPORT=y
@@ -130,11 +144,13 @@ CONFIG_VIDEO_EM28XX_V4L2=m
 CONFIG_VIDEO_EM28XX_ALSA=m
 CONFIG_VIDEO_EM28XX_DVB=m
 CONFIG_VIDEO_BCM2835=m
+CONFIG_VIDEO_CODEC_BCM2835=m
+CONFIG_VIDEO_ISP_BCM2835=m
 CONFIG_V4L_PLATFORM_DRIVERS=y
 
 # Thermal configuration
 CONFIG_THERMAL=y
-CONFIG_BCM2835_THERMAL=y
+CONFIG_BCM2711_THERMAL=y
 
 # MMC/SD/SDIO Card Drivers
 CONFIG_MMC=y
@@ -207,8 +223,14 @@ CONFIG_SND_BCM2708_SOC_FE_PI_AUDIO=m
 CONFIG_SND_BCM2708_SOC_ALLO_BOSS_DAC=m
 CONFIG_SND_BCM2708_SOC_ALLO_DIGIONE=m
 CONFIG_SND_BCM2708_SOC_ALLO_KATANA_DAC=m
+CONFIG_SND_BCM2708_SOC_HIFIBERRY_DACPLUSHD=m
+CONFIG_SND_BCM2708_SOC_JUSTBOOM_BOTH=m
+CONFIG_SND_AUDIOINJECTOR_ISOLATED_SOUNDCARD=m
 CONFIG_SND_PISOUND=m
 CONFIG_SND_BCM2835=m
+CONFIG_SND_SOC_CS4271_I2C=m
+CONFIG_SND_SOC_MA120X0P=m
+CONFIG_SND_SOC_MAX98357A=m
 
 # GPIO Support
 CONFIG_MFD_CORE=y
@@ -252,6 +274,19 @@ CONFIG_REGULATOR_GPIO=y
 # Clock configuration
 CONFIG_CLK_RASPBERRYPI=y
 
+#
+# DMABUF options
+#
+CONFIG_DMABUF_HEAPS=y
+CONFIG_DMABUF_HEAPS_SYSTEM=y
+CONFIG_DMABUF_HEAPS_CMA=y
+
+#
+# Multifunction device
+#
+CONFIG_MFD_SYSCON=y
+CONFIG_MFD_WM5102=y
+
 # Misc configuration
 CONFIG_BINFMT_MISC=m
 CONFIG_BRCM_CHAR_DRIVERS=y
@@ -273,4 +308,4 @@ CONFIG_LOGIRUMBLEPAD2_FF=y
 CONFIG_LOGIG940_FF=y
 CONFIG_SENSORS_RPI_POE_FAN=m
 CONFIG_LEDS_CLASS=y
-CONFIG_NEW_LEDS=y
\ No newline at end of file
+CONFIG_NEW_LEDS=y
-- 
2.17.1

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

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

[yocto-announce] [ANNOUNCEMENT] meta-intel 13.1 layer for yocto project "dunfell" 3.1.1 is now available

[Vineela]

Hello,

We are pleased to announce the meta-intel 13.1 layer for the Yocto Project 
3.1.1 "dunfell" release is now available for download.
Thank you for everyone's contributions to this release.

Vineela Tummalapalli 
Intel Corporation



13.1-dunfell-3.1.1 Release Notes


-
Downloads
-

Release Name: meta-intel-13.1-dunfell-3.1.1
Branch: dunfell
Tag: 13.1-dunfell-3.1.1
Hash: be43fbdd34fe8790981b2a804a2f1cece916930d
sha: 1c1911d4388537bd0c02410a581684721e5c860605b6d37d70a4a48cc2a8a1b3
Download Locations:
http://downloads.yoctoproject.org/releases/yocto/yocto-3.1.1/meta-intel-13.1-dunfell-3.1.1.tar.bz2
http://mirrors.kernel.org/yocto/yocto/yocto-3.1.1/meta-intel-13.1-dunfell-3.1.1.tar.bz2


Updates/Upgrades

linux-intel/5.4: update to v5.4.44
intel-microcode: upgrade 20200609 -> 20200616
intel-microcode: upgrade 20200520 -> 20200609
ixgbe: upgrade 5.6.5 -> 5.7.1
ixgbevf: upgrade 4.6.3 -> 4.7.1
linux-intel/5.4: update to v5.4.39
linux-intel-rt/5.4: update to v5.4.39
intel-microcode: upgrade 20200508 -> 20200520
intel-microcode: upgrade 20191115 -> 20200508

--
 Known Issues
--
N\A


---
Security Fixes
---
For Intel processor-specific security information please visit 
https://software.intel.com/en-us/side-channel-security-support
 
Method information on Intel's Security Center site:
https://security-center.intel.com/advisory.aspx?intelid=INTEL-SA-00088=en-fr
 
Intel Security Center:
https://security-center.intel.com/default.aspx


---
Fixes
---
N\A
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

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

Re: [yocto] [yocto-autobuilder2][PATCH 0/2] Clarification and formatting of README-Guide.md

[Trevor Gamblin]

On 6/22/20 10:18 AM, Trevor Gamblin wrote:

Long-overdue patches based on experiences trying to set up an
autobuilder instance. I've split it into two patches because the second
patch (the one that line wraps the majority of the document) may not be
desired, if the doc is meant to be read in the pre-existing format.
Patch 0001 cleans up the doc so that the sections can be more easily
referenced.

Any issues with this patch set? Do I need to resend?


Trevor Gamblin (2):
   README-Guide: cleanup, clarify setup instructions
   README-Guide: wrap lines at 80 characters

  README-Guide.md | 489 
  1 file changed, 372 insertions(+), 117 deletions(-)



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

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

[yocto] Yocto Project Status WW27'20

[Stephen Jolley]

Current Dev Position: YP 3.2 M2

Next Deadline: YP 3.2 M2 build date 2020/7/27

 

Next Team Meetings:

*   Bug Triage meeting Thursday July 9th at 7:30am PDT (
 https://zoom.us/j/454367603)
*   Monthly Project Meeting Tuesday July 7th at 8am PDT (
 https://zoom.us/j/990892712)
*   Weekly Engineering Sync Tuesday July 14th  at 8am PDT (
 https://zoom.us/j/990892712)
*   Twitch -  See https://www.twitch.tv/theyoctojester

 

Key Status/Updates:

*   Thanks to everyone who attended, helped out, organized or otherwise
contributed to our ELC presence and YP Dev Day last week, we believe it was
successful and people found it interesting and useful.
*   We continue to be concerned about autobuilder stability, we're
continuing to see high numbers of intermittent failures. You can see the
list of failures we're seeing by searching for the "AB-INT" tag in bugzilla:

https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=AB-INT

Help is urgently needed to bring these to a manageable level. We have
managed to resolve or work around some of these issues over the past week
and are starting to see green builds again.

*   We are struggling with maintainers for some key components of the
system/infrastructure such as devtool, wic, buildhistory and
patchwork/patchtest. If anyone can help in these areas please contact
Richard.
*   If anyone has thoughts on attracting and recognising project
contributors and contributions, we would be interested in ideas and
assistance in that area.
*   Another way to help the project is to help us with bugs that are
currently unassigned but ideally needed during 3.2. See:

https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_3.2_Unassigned_Enhan
cements.2FBugs
*   We're planning to migrate the project documentation from docbook to
sphinx. If you're interested/able to help with this please join the
discussion over on the docs mailing list.

 

YP 3.2 Milestone Dates:

*   YP 3.2 M2 build date 2020/7/27
*   YP 3.2 M2 Release date 2020/8/7
*   YP 3.2 M3 build date 2020/8/31
*   YP 3.2 M3 Release date 2020/9/11
*   YP 3.2 M4 build date 2020/10/5
*   YP 3.2 M4 Release date 2020/10/30

 

Planned upcoming dot releases:

*   YP 3.0.4 build date 2020/8/10
*   YP 3.0.4 release date 2020/8/21
*   YP 3.1.2 build date 2020/9/14
*   YP 3.1.2 release date 2020/9/25

 

Tracking Metrics:

*   WDD 2485 (last week 2470) (

https://wiki.yoctoproject.org/charts/combo.html)
*   Poky Patch Metrics  

*   Total patches found: 1268 (last week 1272)
*   Patches in the Pending State: 497 (39%) [last week 498 (39%)]

 

The Yocto Project's technical governance is through its Technical Steering
Committee, more information is available at:

 
https://wiki.yoctoproject.org/wiki/TSC

 

The Status reports are now stored on the wiki at:

https://wiki.yoctoproject.org/wiki/Weekly_Status

 

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

 

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

*Cell:(208) 244-4460

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

 

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

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

Re: [yocto] [ptest-runner][PATCH] Fix inappropriate ioctl when detaching tty

[Anibal Limon]

Hi Tero,

First thanks for the patch, Is there an option to test for isatty(fd) for
run ioctl instead?.

Regards,
Anibal

On Tue, 7 Jul 2020 at 02:21, Tero Kinnunen 
wrote:

> Fixes error
>
> ERROR: Unable to detach from controlling tty, Inappropriate ioctl for
> device
>
> when running multiple ptests
>
> ptest-runner a b
>
> or when invoked over ssh single command, like
>
> $ ssh localhost ptest-runner a
>
> For ssh case, fd 0 is not a tty. (isatty(0) is false).
> When running multiple ptests, deattach for parent needs to be
> done only once. On subsequent calls, if deattach fails,
> according to man 4 tty
>
> it is obviously not attached to a terminal and does not
> need to detach itself.
>
> Detach was not necessary, skip the error message.
>
> Signed-off-by: Tero Kinnunen 
> ---
>  utils.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/utils.c b/utils.c
> index a8ba190..35ef551 100644
> --- a/utils.c
> +++ b/utils.c
> @@ -444,7 +444,7 @@ run_ptests(struct ptest_list *head, const struct
> ptest_options opts,
> break;
> }
> dirname(ptest_dir);
> -   if (ioctl(0, TIOCNOTTY) == -1) {
> +   if (ioctl(0, TIOCNOTTY) == -1 && errno != ENOTTY) {
> fprintf(fp, "ERROR: Unable to detach from
> controlling tty, %s\n", strerror(errno));
> }
>
> --
> 2.25.1
>
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

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

[yocto] [meta-selinux][PATCH 1/4] refpolicy: remove version 2.20190201

[Yi Zhao]

There is no need to maintain two versions of repolicy. Drop this version
and only keep the git version.

Signed-off-by: Yi Zhao 
---
 ...tile-alias-common-var-volatile-paths.patch |  36 -
 ...fix-update-alternatives-for-sysvinit.patch |  53 
 ...m-audit-logging-getty-audit-related-.patch |  68 --
 ...box-set-aliases-for-bin-sbin-and-usr.patch |  31 -
 ...m-locallogin-add-allow-rules-for-typ.patch |  54 
 ...ogd-apply-policy-to-sysklogd-symlink.patch |  57 
 ...m-systemd-unconfined-lib-add-systemd.patch | 121 -
 ...y-policy-to-common-yocto-hostname-al.patch |  27 
 ...m-systemd-mount-logging-authlogin-ad.patch |  96 -
 ...sr-bin-bash-context-to-bin-bash.bash.patch |  30 -
 ...m-init-fix-reboot-with-systemd-as-in.patch |  37 -
 ...abel-resolv.conf-in-var-run-properly.patch |  30 -
 ...m-systemd-mount-enable-required-refp.patch |  92 -
 ...-apply-login-context-to-login.shadow.patch |  27 
 ...m-systemd-fix-for-login-journal-serv.patch | 103 --
 .../0008-fc-bind-fix-real-path-for-bind.patch |  31 -
 ...m-systemd-fix-for-systemd-tmp-files-.patch | 109 ---
 ...-fc-hwclock-add-hwclock-alternatives.patch |  28 
 ...olicy-minimum-systemd-fix-for-syslog.patch |  70 --
 ...g-apply-policy-to-dmesg-alternatives.patch |  24 
 ...ssh-apply-policy-to-ssh-alternatives.patch |  27 
 ...work-apply-policy-to-ip-alternatives.patch |  48 ---
 ...v-apply-policy-to-udevadm-in-libexec.patch |  28 
 ...ply-rpm_exec-policy-to-cpio-binaries.patch |  29 
 ...c-su-apply-policy-to-su-alternatives.patch |  26 
 ...fc-fstools-fix-real-path-for-fstools.patch |  76 ---
 ...gging-Add-the-syslogd_t-to-trusted-o.patch |  33 -
 ...gging-add-rules-for-the-symlink-of-v.patch | 100 --
 ...gging-add-rules-for-syslogd-symlink-.patch |  33 -
 ...gging-add-domain-rules-for-the-subdi.patch |  36 -
 ...les-add-rules-for-the-symlink-of-tmp.patch | 100 --
 ...rminals-add-rules-for-bsdpty_device_.patch | 123 -
 ...rminals-don-t-audit-tty_device_t-in-.patch |  37 -
 ...pc-allow-nfsd-to-exec-shell-commands.patch |  29 
 ...c-fix-policy-for-nfsserver-to-mount-.patch |  77 ---
 ...-sysfs-fix-for-new-SELINUXMNT-in-sys.patch | 126 --
 ...dule-rpc-allow-sysadm-to-run-rpcinfo.patch |  31 -
 ...erdomain-fix-selinux-utils-to-manage.patch |  45 ---
 ...linuxutil-fix-setfiles-statvfs-to-ge.patch |  33 -
 ...min-fix-dmesg-to-use-dev-kmsg-as-def.patch |  25 
 ...p-add-ftpd_t-to-mls_file_write_all_l.patch |  41 --
 ...it-update-for-systemd-related-allow-.patch |  32 -
 ...inimum-make-sysadmin-module-optional.patch |  67 --
 ...ache-add-rules-for-the-symlink-of-va.patch |  33 -
 .../refpolicy/refpolicy-mcs_2.20190201.bb |  11 --
 .../refpolicy/refpolicy-minimum_2.20190201.bb |  91 -
 .../refpolicy/refpolicy-mls_2.20190201.bb |  10 --
 .../refpolicy-standard_2.20190201.bb  |   8 --
 .../refpolicy-targeted_2.20190201.bb  |  35 -
 .../refpolicy/refpolicy_2.20190201.inc|   9 --
 50 files changed, 2523 deletions(-)
 delete mode 100644 
recipes-security/refpolicy/refpolicy-2.20190201/0001-fc-subs-volatile-alias-common-var-volatile-paths.patch
 delete mode 100644 
recipes-security/refpolicy/refpolicy-2.20190201/0001-fix-update-alternatives-for-sysvinit.patch
 delete mode 100644 
recipes-security/refpolicy/refpolicy-2.20190201/0001-refpolicy-minimum-audit-logging-getty-audit-related-.patch
 delete mode 100644 
recipes-security/refpolicy/refpolicy-2.20190201/0002-fc-subs-busybox-set-aliases-for-bin-sbin-and-usr.patch
 delete mode 100644 
recipes-security/refpolicy/refpolicy-2.20190201/0002-refpolicy-minimum-locallogin-add-allow-rules-for-typ.patch
 delete mode 100644 
recipes-security/refpolicy/refpolicy-2.20190201/0003-fc-sysklogd-apply-policy-to-sysklogd-symlink.patch
 delete mode 100644 
recipes-security/refpolicy/refpolicy-2.20190201/0003-refpolicy-minimum-systemd-unconfined-lib-add-systemd.patch
 delete mode 100644 
recipes-security/refpolicy/refpolicy-2.20190201/0004-fc-hostname-apply-policy-to-common-yocto-hostname-al.patch
 delete mode 100644 
recipes-security/refpolicy/refpolicy-2.20190201/0004-refpolicy-minimum-systemd-mount-logging-authlogin-ad.patch
 delete mode 100644 
recipes-security/refpolicy/refpolicy-2.20190201/0005-fc-bash-apply-usr-bin-bash-context-to-bin-bash.bash.patch
 delete mode 100644 
recipes-security/refpolicy/refpolicy-2.20190201/0005-refpolicy-minimum-init-fix-reboot-with-systemd-as-in.patch
 delete mode 100644 
recipes-security/refpolicy/refpolicy-2.20190201/0006-fc-resolv.conf-label-resolv.conf-in-var-run-properly.patch
 delete mode 100644 
recipes-security/refpolicy/refpolicy-2.20190201/0006-refpolicy-minimum-systemd-mount-enable-required-refp.patch
 delete mode 100644 

[yocto] [meta-selinux][PATCH 3/4] audit: set correct security context for /var/log/audit

[Yi Zhao]

By default /var/log is a symbolic link of /var/volatile/log. But
restorecon does not follow symbolic links then we will encounter the
following error when set /var/log/audit directory:

$ /sbin/restorecon -F /var/log/audit
/sbin/restorecon: SELinux: Could not get canonical path for /var/log/audit 
restorecon: Permission denied.

Use readlink to find the real path before set security context.

Signed-off-by: Yi Zhao 
---
 recipes-security/audit/audit/auditd | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
 mode change 100755 => 100644 recipes-security/audit/audit/auditd

diff --git a/recipes-security/audit/audit/auditd 
b/recipes-security/audit/audit/auditd
old mode 100755
new mode 100644
index cda2e43..6aa7f94
--- a/recipes-security/audit/audit/auditd
+++ b/recipes-security/audit/audit/auditd
@@ -86,7 +86,7 @@ do_reload() {
 
 if [ ! -e /var/log/audit ]; then
mkdir -p /var/log/audit
-   [ -x /sbin/restorecon ] && /sbin/restorecon -F /var/log/audit
+   [ -x /sbin/restorecon ] && /sbin/restorecon -F $(readlink -f 
/var/log/audit)
 fi
 
 case "$1" in
-- 
2.17.1

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

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

[yocto] [meta-selinux][PATCH 4/4] sysklogd: set correct security context for /var/log in initscript

[Yi Zhao]

We don't need to set security context for /dev/log after syslogd daemon
startup because it is already set by udev. We just need to set the
correct security context for symbolic link /var/log before syslogd
startup.

Signed-off-by: Yi Zhao 
---
 recipes-extended/sysklogd/files/sysklogd | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/recipes-extended/sysklogd/files/sysklogd 
b/recipes-extended/sysklogd/files/sysklogd
index e49c2da..7943b1d 100644
--- a/recipes-extended/sysklogd/files/sysklogd
+++ b/recipes-extended/sysklogd/files/sysklogd
@@ -108,8 +108,8 @@ case "$1" in
   start)
 log_begin_msg "Starting system log daemon..."
 create_xconsole
+test ! -x /sbin/restorecon || /sbin/restorecon -F /var/log
 start-stop-daemon --start --quiet --pidfile $pidfile_syslogd --name 
syslogd --startas $binpath_syslogd -- $SYSLOGD
-test ! -x /sbin/restorecon || /sbin/restorecon -RF /dev/log /var/log/
 log_end_msg $?
 ;;
   stop)
-- 
2.17.1

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

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

[yocto] [meta-selinux][PATCH 0/4] refpolicy: update to 20200229+git

[Yi Zhao]

Here is the changelog for this is patchset:

* Drop refpolicy 2.20190201
  If we still keep two versions of refpolicy, it is difficult to maintain two 
huge local patchsets. So drop this version and only keep the git version.

* Add patches to make systemd/sysvinit can work with all policy types.

Here are the results with this patcheset:

Machine: qemux86-64
Image: core-image-selinux
Init manager: sysvinit and systemd
Policy types: minimum, targeted, standard, mcs, mls
Boot command: runqemu qemux86-64 kvm nographic bootparams="selinux=1 
enforcing=1" qemuparams="-m 1024"

1. All refpolicy type can be built without problems.

2. With parameter selinux=1 & enforcing=1
The qemu can boot up and login with all policy types.


Regards,
Yi


Yi Zhao (4):
  refpolicy: remove version 2.20190201
  refpolicy: update to 20200229+git
  audit: set correct security context for /var/log/audit
  sysklogd: set correct security context for /var/log in initscript

 recipes-extended/sysklogd/files/sysklogd  |   2 +-
 recipes-security/audit/audit/auditd   |   2 +-
 ...fix-update-alternatives-for-sysvinit.patch |  53 -
 ...m-audit-logging-getty-audit-related-.patch |  68 --
 ...m-locallogin-add-allow-rules-for-typ.patch |  54 -
 ...ogd-apply-policy-to-sysklogd-symlink.patch |  57 --
 ...m-systemd-unconfined-lib-add-systemd.patch | 121 ---
 ...m-systemd-mount-logging-authlogin-ad.patch |  96 -
 ...sr-bin-bash-context-to-bin-bash.bash.patch |  30 ---
 ...m-init-fix-reboot-with-systemd-as-in.patch |  37 
 ...abel-resolv.conf-in-var-run-properly.patch |  30 ---
 ...m-systemd-mount-enable-required-refp.patch |  92 -
 ...m-systemd-fix-for-login-journal-serv.patch | 103 --
 ...m-systemd-fix-for-systemd-tmp-files-.patch | 109 --
 ...-fc-hwclock-add-hwclock-alternatives.patch |  28 ---
 ...olicy-minimum-systemd-fix-for-syslog.patch |  70 ---
 ...g-apply-policy-to-dmesg-alternatives.patch |  24 ---
 ...work-apply-policy-to-ip-alternatives.patch |  48 -
 ...ply-rpm_exec-policy-to-cpio-binaries.patch |  29 ---
 ...gging-Add-the-syslogd_t-to-trusted-o.patch |  33 ---
 ...gging-add-rules-for-the-symlink-of-v.patch | 100 -
 ...gging-add-rules-for-syslogd-symlink-.patch |  33 ---
 ...pc-allow-nfsd-to-exec-shell-commands.patch |  29 ---
 ...c-fix-policy-for-nfsserver-to-mount-.patch |  77 ---
 ...-sysfs-fix-for-new-SELINUXMNT-in-sys.patch | 126 
 ...dule-rpc-allow-sysadm-to-run-rpcinfo.patch |  31 ---
 ...erdomain-fix-selinux-utils-to-manage.patch |  45 
 ...linuxutil-fix-setfiles-statvfs-to-ge.patch |  33 ---
 ...min-fix-dmesg-to-use-dev-kmsg-as-def.patch |  25 ---
 ...p-add-ftpd_t-to-mls_file_write_all_l.patch |  41 
 ...it-update-for-systemd-related-allow-.patch |  32 ---
 ...ache-add-rules-for-the-symlink-of-va.patch |  33 ---
 ...tile-alias-common-var-volatile-paths.patch |  36 
 ...m-audit-logging-getty-audit-related-.patch |  68 --
 ...box-set-aliases-for-bin-sbin-and-usr.patch |  31 ---
 ...m-locallogin-add-allow-rules-for-typ.patch |  54 -
 ...ogd-apply-policy-to-sysklogd-symlink.patch |  57 --
 ...m-systemd-unconfined-lib-add-systemd.patch | 121 ---
 ...y-policy-to-common-yocto-hostname-al.patch |  27 ---
 ...m-systemd-mount-logging-authlogin-ad.patch |  96 -
 ...m-init-fix-reboot-with-systemd-as-in.patch |  37 
 ...abel-resolv.conf-in-var-run-properly.patch |  30 ---
 ...m-systemd-mount-enable-required-refp.patch |  92 -
 ...-apply-login-context-to-login.shadow.patch |  27 ---
 ...m-systemd-fix-for-login-journal-serv.patch | 103 --
 .../0008-fc-bind-fix-real-path-for-bind.patch |  31 ---
 ...m-systemd-fix-for-systemd-tmp-files-.patch | 110 --
 ...-fc-hwclock-add-hwclock-alternatives.patch |  28 ---
 ...olicy-minimum-systemd-fix-for-syslog.patch |  70 ---
 ...g-apply-policy-to-dmesg-alternatives.patch |  24 ---
 ...ssh-apply-policy-to-ssh-alternatives.patch |  27 ---
 ...v-apply-policy-to-udevadm-in-libexec.patch |  28 ---
 ...ply-rpm_exec-policy-to-cpio-binaries.patch |  29 ---
 ...c-su-apply-policy-to-su-alternatives.patch |  26 ---
 ...fc-fstools-fix-real-path-for-fstools.patch |  76 ---
 ...gging-add-domain-rules-for-the-subdi.patch |  36 
 ...les-add-rules-for-the-symlink-of-tmp.patch | 100 -
 ...rminals-add-rules-for-bsdpty_device_.patch | 123 ---
 ...rminals-don-t-audit-tty_device_t-in-.patch |  37 
 ...pc-allow-nfsd-to-exec-shell-commands.patch |  29 ---
 ...c-fix-policy-for-nfsserver-to-mount-.patch |  77 ---
 ...-sysfs-fix-for-new-SELINUXMNT-in-sys.patch | 126 
 ...dule-rpc-allow-sysadm-to-run-rpcinfo.patch |  31 ---
 ...erdomain-fix-selinux-utils-to-manage.patch |  45 
 ...linuxutil-fix-setfiles-statvfs-to-ge.patch |  33 ---
 ...min-fix-dmesg-to-use-dev-kmsg-as-def.patch |  25 ---
 ...p-add-ftpd_t-to-mls_file_write_all_l.patch |  41 
 ...it-update-for-systemd-related-allow-.patch |  32 ---
 

Re: [yocto] #yocto howto use deltask

[Hans-Ulrich Schlieben]

Hi Quentin,

thank you, the empty variant "removes" the task and the read-only-rootfs check 
works:
pkg_postinst_ontarget_${PN}() {
}

There are some issues which let me into the wrong direction. First I commented 
out the former code in the bbappend file. Apparmor builds, but the 
read-only-rootfs check fails:
pkg_postinst_ontarget_${PN} () {
#if [ ! -d /etc/apparmor.d/cache ] ; then
#mkdir /etc/apparmor.d/cache
#fi
}

The same result you get with an empty line in the task:
pkg_postinst_ontarget_${PN}() {

}

For the following cases you get a parser errors:
pkg_postinst_ontarget_${PN}() {
 }
pkg_postinst_ontarget_${PN}() { }
pkg_postinst_ontarget_${PN}() {}

Thank you and best regards

hu


-Ursprüngliche Nachricht-
Von: Quentin Schulz  
Gesendet: Monday, 6 July 2020 13:51
An: Hans-Ulrich Schlieben 
Cc: yocto@lists.yoctoproject.org
Betreff: Re: [yocto] #yocto howto use deltask

Hi,

On Mon, Jul 06, 2020 at 04:00:11AM -0700, Hans-Ulrich Schlieben wrote:
> Hi,
> 
> my image build fails with:
> ERROR: ims-image-fieldgate-1.0-r0 do_rootfs: The following packages 
> could not be configured offline and rootfs is read-only: ['apparmor']
> 
> The image build succeeds if i remove the task pkg_postinst_ontarget_${PN} 
> from apparmor_2.13.3.bb.
> 
> I tried to use deltask in my apparmor_2.13.3.bbappend with different settings:
> deltask postinst_ontarget
> deltask postinst
> deltask pkg_postinst
> deltask pkg_postinst_ontarget_
> deltask pkg_postinst_ontarget_apparmor deltask 
> pkg_postinst_ontarget_apparmor_2
> 
> and
> 
> postinst_ontarget[noexec] = "1"
> postinst[noexec] = "1"
> pkg_postinst[noexec] = "1"
> pkg_postinst_ontarget_[noexec] = "1"
> pkg_postinst_ontarget_apparmor[noexec] = "1"
> pkg_postinst_ontarget_apparmor_2[noexec] = "1"
> 

What about:

pkg_postinst_ontarget_${PN}() {
:
}

in your bbappend? This should effectively override the task from a bbappend 
(except if there are _append for the task).

Can't comment on this being a good solution to your problem but that should 
work to remove the content of pkg_postinst_ontarget.

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

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

[yocto] [ptest-runner][PATCH] Fix inappropriate ioctl when detaching tty

[Tero Kinnunen]

Fixes error

ERROR: Unable to detach from controlling tty, Inappropriate ioctl for device

when running multiple ptests

ptest-runner a b

or when invoked over ssh single command, like

$ ssh localhost ptest-runner a

For ssh case, fd 0 is not a tty. (isatty(0) is false).
When running multiple ptests, deattach for parent needs to be
done only once. On subsequent calls, if deattach fails,
according to man 4 tty

it is obviously not attached to a terminal and does not
need to detach itself.

Detach was not necessary, skip the error message.

Signed-off-by: Tero Kinnunen 
---
 utils.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/utils.c b/utils.c
index a8ba190..35ef551 100644
--- a/utils.c
+++ b/utils.c
@@ -444,7 +444,7 @@ run_ptests(struct ptest_list *head, const struct 
ptest_options opts,
break;
}
dirname(ptest_dir);
-   if (ioctl(0, TIOCNOTTY) == -1) {
+   if (ioctl(0, TIOCNOTTY) == -1 && errno != ENOTTY) {
fprintf(fp, "ERROR: Unable to detach from 
controlling tty, %s\n", strerror(errno));
}
 
-- 
2.25.1

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

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