[yocto-announce] [ANNOUNCEMENT] Yocto Project 4.0.11 is Released

2023-07-03 Thread Lee Chee Yang 
Hi

We are pleased to announce the Yocto Project 4.0.11 Release is now available 
for download.

http://downloads.yoctoproject.org/releases/yocto/yocto-4.0.11/poky-fc697fe87412b9b179ae3a68d266ace85bb1fcc6.tar.bz2
http://mirrors.kernel.org/yocto/yocto/yocto-4.0.11/poky-fc697fe87412b9b179ae3a68d266ace85bb1fcc6.tar.bz2

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

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

Full Test Report:

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

Thank you for everyone's contributions to this release.

Chee Yang
chee.yang@intel.com
Yocto Project Build and Release



- --
yocto-4.0.11 Release Notes
- --


- --
Repositories/Downloads
- --

Repository Name: poky
Repository Location: https://git.yoctoproject.org/poky
Branch: kirkstone
Tag: yocto-4.0.11
Git Revision: fc697fe87412b9b179ae3a68d266ace85bb1fcc6
Release Artefact: poky-fc697fe87412b9b179ae3a68d266ace85bb1fcc6
sha: d42ab1b76b9d8ab164d86dc0882c908658f6b5be0742b13a71531068f6a5ee98
Download Locations:
http://downloads.yoctoproject.org/releases/yocto/yocto-4.0.11/poky-fc697fe87412b9b179ae3a68d266ace85bb1fcc6.tar.bz2
http://mirrors.kernel.org/yocto/yocto/yocto-4.0.11/poky-fc697fe87412b9b179ae3a68d266ace85bb1fcc6.tar.bz2

Repository Name: openembedded-core
Repository Location: https://git.openembedded.org/openembedded-core
Branch: kirkstone
Tag: yocto-4.0.11
Git Revision: 7949e786cf8e50f716ff1f1c4797136637205e0c
Release Artefact: oecore-7949e786cf8e50f716ff1f1c4797136637205e0c
sha: 3bda3f7d15961bad5490faf3194709528591a97564b5eae3da7345b63be20334
Download Locations:
http://downloads.yoctoproject.org/releases/yocto/yocto-4.0.11/oecore-7949e786cf8e50f716ff1f1c4797136637205e0c.tar.bz2
http://mirrors.kernel.org/yocto/yocto/yocto-4.0.11/oecore-7949e786cf8e50f716ff1f1c4797136637205e0c.tar.bz2

Repository Name: meta-mingw
Repository Location: https://git.yoctoproject.org/meta-mingw
Branch: kirkstone
Tag: yocto-4.0.11
Git Revision: a90614a6498c3345704e9611f2842eb933dc51c1
Release Artefact: meta-mingw-a90614a6498c3345704e9611f2842eb933dc51c1
sha: 49f9900bfbbc1c68136f8115b314e95d0b7f6be75edf36a75d9bcd1cca7c6302
Download Locations:
http://downloads.yoctoproject.org/releases/yocto/yocto-4.0.11/meta-mingw-a90614a6498c3345704e9611f2842eb933dc51c1.tar.bz2
http://mirrors.kernel.org/yocto/yocto/yocto-4.0.11/meta-mingw-a90614a6498c3345704e9611f2842eb933dc51c1.tar.bz2

Repository Name: meta-gplv2
Repository Location: https://git.yoctoproject.org/meta-gplv2
Branch: kirkstone
Tag: yocto-4.0.11
Git Revision: d2f8b5cdb285b72a4ed93450f6703ca27aa42e8a
Release Artefact: meta-gplv2-d2f8b5cdb285b72a4ed93450f6703ca27aa42e8a
sha: c386f59f8a672747dc3d0be1d4234b6039273d0e57933eb87caa20f56b9cca6d
Download Locations:
http://downloads.yoctoproject.org/releases/yocto/yocto-4.0.11/meta-gplv2-d2f8b5cdb285b72a4ed93450f6703ca27aa42e8a.tar.bz2
http://mirrors.kernel.org/yocto/yocto/yocto-4.0.11/meta-gplv2-d2f8b5cdb285b72a4ed93450f6703ca27aa42e8a.tar.bz2

Repository Name: bitbake
Repository Location: https://git.openembedded.org/bitbake
Branch: 2.0
Tag: yocto-4.0.11
Git Revision: 0c6f86b60cfba67c20733516957c0a654eb2b44c
Release Artefact: bitbake-0c6f86b60cfba67c20733516957c0a654eb2b44c
sha: 4caa94ee4d644017b0cc51b702e330191677f7d179018cbcec8b1793949ebc74
Download Locations:
http://downloads.yoctoproject.org/releases/yocto/yocto-4.0.11/bitbake-0c6f86b60cfba67c20733516957c0a654eb2b44c.tar.bz2
http://mirrors.kernel.org/yocto/yocto/yocto-4.0.11/bitbake-0c6f86b60cfba67c20733516957c0a654eb2b44c.tar.bz2

Repository Name: yocto-docs
Repository Location: https://git.yoctoproject.org/yocto-docs
Branch: kirkstone
Tag: yocto-4.0.11
Git Revision: 6d16d2bde0aa32276a035ee49703e6eea7c7b29a


- ---
Contributors
- ---
Alexander Kanavin
Andrew Jeffery
Archana Polampalli
Bhabu Bindu
Bruce Ashfield
C. Andy Martin
Chen Qi
Daniel Ammann
Deepthi Hemraj
Ed Beroset
Eero Aaltonen
Enrico Jörns
Hannu Lounento
Hitendra Prajapati
Ian Ray
Jan Luebbe
Jan Vermaete
Khem Raj
Lee Chee Yang
Lei Maohui
Lorenzo Arena
Marek Vasut
Marta Rybczynska
Martin Jansa
Martin Siegumfeldt
Michael Halstead
Michael Opdenacker
Ming Liu
Narpat Mali
Omkar Patil
Pablo Saavedra
Pavel Zhukov
Peter Kjellerstedt
Peter Marko
Qiu Tingting
Quentin Schulz
Randolph Sapp
Randy MacLeod
Ranjitsinh Rathod
Richard Purdie
Riyaz Khan
Sakib Sajal
Sanjay Chitroda
Soumya Sambu
Steve Sakoman
Thomas Roos
Tom Hochstein
Vivek Kumbhar
Wang Mingyu
Yogita Urade
Zoltan Boszormenyi


- ---
Known Issues
- ---
N/A


- ---
Security Fixes
- ---
cups: Fix CVE-2023-32324
curl: Fix CVE-2023-28319 CVE-2023-28320 CVE-2023-28321 CVE-2023-28322
git: Ignore CVE-2023-25815
go: Fix CVE-2023-24539 CVE-2023-24540
nasm: Fix CVE-2022-46457
openssh: Fix CVE-2023-28531
openssl: Fix CVE-2023-1255

[yocto] [ANNOUNCEMENT] Yocto Project 4.0.11 is Released

2023-07-03 Thread Lee Chee Yang 
Hi

We are pleased to announce the Yocto Project 4.0.11 Release is now available 
for download.

http://downloads.yoctoproject.org/releases/yocto/yocto-4.0.11/poky-fc697fe87412b9b179ae3a68d266ace85bb1fcc6.tar.bz2
http://mirrors.kernel.org/yocto/yocto/yocto-4.0.11/poky-fc697fe87412b9b179ae3a68d266ace85bb1fcc6.tar.bz2

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

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

Full Test Report:

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

Thank you for everyone's contributions to this release.

Chee Yang
chee.yang@intel.com
Yocto Project Build and Release



- --
yocto-4.0.11 Release Notes
- --


- --
Repositories/Downloads
- --

Repository Name: poky
Repository Location: https://git.yoctoproject.org/poky
Branch: kirkstone
Tag: yocto-4.0.11
Git Revision: fc697fe87412b9b179ae3a68d266ace85bb1fcc6
Release Artefact: poky-fc697fe87412b9b179ae3a68d266ace85bb1fcc6
sha: d42ab1b76b9d8ab164d86dc0882c908658f6b5be0742b13a71531068f6a5ee98
Download Locations:
http://downloads.yoctoproject.org/releases/yocto/yocto-4.0.11/poky-fc697fe87412b9b179ae3a68d266ace85bb1fcc6.tar.bz2
http://mirrors.kernel.org/yocto/yocto/yocto-4.0.11/poky-fc697fe87412b9b179ae3a68d266ace85bb1fcc6.tar.bz2

Repository Name: openembedded-core
Repository Location: https://git.openembedded.org/openembedded-core
Branch: kirkstone
Tag: yocto-4.0.11
Git Revision: 7949e786cf8e50f716ff1f1c4797136637205e0c
Release Artefact: oecore-7949e786cf8e50f716ff1f1c4797136637205e0c
sha: 3bda3f7d15961bad5490faf3194709528591a97564b5eae3da7345b63be20334
Download Locations:
http://downloads.yoctoproject.org/releases/yocto/yocto-4.0.11/oecore-7949e786cf8e50f716ff1f1c4797136637205e0c.tar.bz2
http://mirrors.kernel.org/yocto/yocto/yocto-4.0.11/oecore-7949e786cf8e50f716ff1f1c4797136637205e0c.tar.bz2

Repository Name: meta-mingw
Repository Location: https://git.yoctoproject.org/meta-mingw
Branch: kirkstone
Tag: yocto-4.0.11
Git Revision: a90614a6498c3345704e9611f2842eb933dc51c1
Release Artefact: meta-mingw-a90614a6498c3345704e9611f2842eb933dc51c1
sha: 49f9900bfbbc1c68136f8115b314e95d0b7f6be75edf36a75d9bcd1cca7c6302
Download Locations:
http://downloads.yoctoproject.org/releases/yocto/yocto-4.0.11/meta-mingw-a90614a6498c3345704e9611f2842eb933dc51c1.tar.bz2
http://mirrors.kernel.org/yocto/yocto/yocto-4.0.11/meta-mingw-a90614a6498c3345704e9611f2842eb933dc51c1.tar.bz2

Repository Name: meta-gplv2
Repository Location: https://git.yoctoproject.org/meta-gplv2
Branch: kirkstone
Tag: yocto-4.0.11
Git Revision: d2f8b5cdb285b72a4ed93450f6703ca27aa42e8a
Release Artefact: meta-gplv2-d2f8b5cdb285b72a4ed93450f6703ca27aa42e8a
sha: c386f59f8a672747dc3d0be1d4234b6039273d0e57933eb87caa20f56b9cca6d
Download Locations:
http://downloads.yoctoproject.org/releases/yocto/yocto-4.0.11/meta-gplv2-d2f8b5cdb285b72a4ed93450f6703ca27aa42e8a.tar.bz2
http://mirrors.kernel.org/yocto/yocto/yocto-4.0.11/meta-gplv2-d2f8b5cdb285b72a4ed93450f6703ca27aa42e8a.tar.bz2

Repository Name: bitbake
Repository Location: https://git.openembedded.org/bitbake
Branch: 2.0
Tag: yocto-4.0.11
Git Revision: 0c6f86b60cfba67c20733516957c0a654eb2b44c
Release Artefact: bitbake-0c6f86b60cfba67c20733516957c0a654eb2b44c
sha: 4caa94ee4d644017b0cc51b702e330191677f7d179018cbcec8b1793949ebc74
Download Locations:
http://downloads.yoctoproject.org/releases/yocto/yocto-4.0.11/bitbake-0c6f86b60cfba67c20733516957c0a654eb2b44c.tar.bz2
http://mirrors.kernel.org/yocto/yocto/yocto-4.0.11/bitbake-0c6f86b60cfba67c20733516957c0a654eb2b44c.tar.bz2

Repository Name: yocto-docs
Repository Location: https://git.yoctoproject.org/yocto-docs
Branch: kirkstone
Tag: yocto-4.0.11
Git Revision: 6d16d2bde0aa32276a035ee49703e6eea7c7b29a


- ---
Contributors
- ---
Alexander Kanavin
Andrew Jeffery
Archana Polampalli
Bhabu Bindu
Bruce Ashfield
C. Andy Martin
Chen Qi
Daniel Ammann
Deepthi Hemraj
Ed Beroset
Eero Aaltonen
Enrico Jörns
Hannu Lounento
Hitendra Prajapati
Ian Ray
Jan Luebbe
Jan Vermaete
Khem Raj
Lee Chee Yang
Lei Maohui
Lorenzo Arena
Marek Vasut
Marta Rybczynska
Martin Jansa
Martin Siegumfeldt
Michael Halstead
Michael Opdenacker
Ming Liu
Narpat Mali
Omkar Patil
Pablo Saavedra
Pavel Zhukov
Peter Kjellerstedt
Peter Marko
Qiu Tingting
Quentin Schulz
Randolph Sapp
Randy MacLeod
Ranjitsinh Rathod
Richard Purdie
Riyaz Khan
Sakib Sajal
Sanjay Chitroda
Soumya Sambu
Steve Sakoman
Thomas Roos
Tom Hochstein
Vivek Kumbhar
Wang Mingyu
Yogita Urade
Zoltan Boszormenyi


- ---
Known Issues
- ---
N/A


- ---
Security Fixes
- ---
cups: Fix CVE-2023-32324
curl: Fix CVE-2023-28319 CVE-2023-28320 CVE-2023-28321 CVE-2023-28322
git: Ignore CVE-2023-25815
go: Fix CVE-2023-24539 CVE-2023-24540
nasm: Fix CVE-2022-46457
openssh: Fix CVE-2023-28531
openssl: Fix CVE-2023-1255

[yocto] Typo in python3/get_module_deps3.py?

2023-07-03 Thread Wes Tarro 
I found a line in get_module_deps3.py that looked weird and could easily be a 
typo:
https://git.yoctoproject.org/poky/tree/meta/recipes-devtools/python/python3/get_module_deps3.py#n35

Specifically on line 35 (for present git version):
dep_path = dep_path.replace('/usr/bin''${bindir}')

All of the following lines handling 'usr/lib' variants pass two arguments 
instead of one joined argument, e.g.:
dep_path = dep_path.replace('/usr/lib32','${libdir}')

Is the former a typo that needs to be fixed or is it intentional?

Thank you for your time.

Wes Tarro


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

Re: [yocto] Building Tailscale with Yocto #golang

2023-07-03 Thread Tom Isaacson 
What Yocto release are you using? I tried building Tailscale with
Dunfell but the version of Go it includes was too old.

On Mon, Jul 3, 2023 at 7:45 AM  wrote:
>
> Hi!
> I'm trying to build Tailscale with Yocto
> This is me recipe:
>
> inherit go-mod
>
> SRC_URI = "git://github.com/tailscale/tailscale;protocol=https;branch=main"
> SRCREV = "30d9201a11ebc2e3a0f17bf8963956b77dadeb5d"
>
> GO_IMPORT = "tailscale.com"
> GO_WORKDIR = "${GO_IMPORT}"
> GO_INSTALL = "\
> ${GO_IMPORT}/cmd/tailscale \
> ${GO_IMPORT}/cmd/tailscaled \
> "
>
> do_install() {
> install -d ${D}/${bindir}
> install -d ${D}/${sbindir}
> install ${B}/bin/tailscale ${D}/${bindir}/tailscale
> install ${B}/bin/tailscaled ${D}/${sbindir}/tailscaled
> }
>
>
> However, build step ends up with errors like these (full log):
>
> | wgengine/netstack/netstack.go:34:2: 
> gvisor.dev/gvisor@v0.0.0-20230504175454-7b0a1988a28f: Get 
> "https://proxy.golang.org/gvisor.dev/gvisor/@v/v0.0.0-20230504175454-7b0a1988a28f.zip":
>  dial tcp: lookup proxy.golang.org on 8.8.8.8:53: dial udp 8.8.8.8:53: 
> connect: network is unreachable
> | wgengine/netstack/netstack.go:35:2: 
> gvisor.dev/gvisor@v0.0.0-20230504175454-7b0a1988a28f: Get 
> "https://proxy.golang.org/gvisor.dev/gvisor/@v/v0.0.0-20230504175454-7b0a1988a28f.zip":
>  dial tcp: lookup proxy.golang.org on 8.8.8.8:53: dial udp 8.8.8.8:53: 
> connect: network is unreachable
> | net/tstun/tap_linux.go:23:2: 
> gvisor.dev/gvisor@v0.0.0-20230504175454-7b0a1988a28f: Get 
> "https://proxy.golang.org/gvisor.dev/gvisor/@v/v0.0.0-20230504175454-7b0a1988a28f.zip":
>  dial tcp: lookup proxy.golang.org on 8.8.8.8:53: dial udp 8.8.8.8:53: 
> connect: network is unreachable
> | wgengine/netstack/netstack.go:37:2: 
> gvisor.dev/gvisor@v0.0.0-20230504175454-7b0a1988a28f: Get 
> "https://proxy.golang.org/gvisor.dev/gvisor/@v/v0.0.0-20230504175454-7b0a1988a28f.zip":
>  dial tcp: lookup proxy.golang.org on 8.8.8.8:53: dial udp 8.8.8.8:53: 
> connect: network is unreachable
> | ipn/ipnauth/ipnauth.go:16:2: 
> inet.af/peercred@v0.0.0-20210906144145-0893ea02156a: Get 
> "https://proxy.golang.org/inet.af/peercred/@v/v0.0.0-20210906144145-0893ea02156a.zip":
>  dial tcp: lookup proxy.golang.org on 8.8.8.8:53: dial udp 8.8.8.8:53: 
> connect: network is unreachable
>
> On some resources I have found it was recomended to add environmental 
> variables: `GOPROXY="direct"` and `GOSUMDB="off"`, but it didn't helped.
>
> Maybe someone has some ideas what is the cause of these errors?
>
> 
>


-- 
Tom Isaacson

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

Re: [yocto] File magic/sdk relocation

2023-07-03 Thread Alexander Kanavin 
I think you might want to use create_wrapper helper, similar to how
createrepo_c recipe does it:

do_install:append:class-nativesdk() {
create_wrapper ${D}/${bindir}/createrepo_c \
RPM_CONFIGDIR=${SDKPATHNATIVE}${libdir_nativesdk}/rpm \
MAGIC=${datadir}/misc/magic.mgc
create_wrapper ${D}/${bindir}/modifyrepo_c \
MAGIC=${datadir}/misc/magic.mgc

}

I also just checked that MAGIC is relocated and exported correctly,
e.g. running file from the buildtools tarball works fine on the
'plain' command line after installing and setting up the tarball.

Alex

On Mon, 3 Jul 2023 at 14:53, Oleksandr Hnatiuk -X (ohnatiuk -
GLOBALLOGIC INC at Cisco)  wrote:
>
> I think it hasn’t been noticed because openembedded-core doesn't build `file` 
> in buildtools-tarball.
>
> To reproduce the error, you need to do the following:
> 1. Download openembedded-core and bitbake, source init script
> 2. Add nativesdk-file to TOOLCHAIN_HOST_TASK, e.g. add the following line to 
> conf/local.conf:
> TOOLCHAIN_HOST_TASK:append = " nativesdk-file"
> 3. Run `bitbake buildtools-tarball`
> 4. Install buildtools: 
> `tmp-glibc/deploy/sdk/x86_64-buildtools-nativesdk-standalone-nodistro.0.sh -y 
> -d $buildtools_install_dir`
> 5. Same as (1) but in a different empty directory (first one built the 
> buildtools, this one will use them)
> 6. Source the script provided by buildtools, e.g.: `source 
> $buildtools_install_dir/environment-setup-x86_64-oesdk-linux`
> 7. Run `bitbake quilt-native`
>
> You should get the following error:
>
> ERROR: quilt-native-0.67-r0 do_populate_sysroot: Fatal errors occurred in 
> subprocesses:
> Command '['file', '-b', 
> '/path/to/openembedded-core/build/tmp-glibc/work/x86_64-linux/quilt-native/0.67-r0/sysroot-destdir/path/to/openembedded-core/build/tmp-glibc/work/x86_64-linux/quilt-native/0.67-r0/recipe-sysroot-native/usr/bin/quilt']'
>  returned non-zero exit status 1.
>
> The same error is repeated for each invocation of `file` in 
> do_populate_sysroot
>
> Regards,
> Oleksandr
>
>
> From: Alexander Kanavin 
> Sent: Tuesday, June 27, 2023 7:46 PM
> To: Oleksandr Hnatiuk -X (ohnatiuk - GLOBALLOGIC INC at Cisco) 
> 
> Cc: yocto@lists.yoctoproject.org 
> Subject: Re: [yocto] File magic/sdk relocation
>
> Before we think of a solution, can you provide steps or a test case where the 
> issue can be seen? It’s in one of the most important tasks, so I’d like to 
> know why it hasn’t been a problem and what is the scenario where it is.
>
> Alex

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

Re: [yocto] Building Tailscale with Yocto #golang

2023-07-03 Thread Bruce Ashfield 
On Mon, Jul 3, 2023 at 10:05 AM Janne Kiiskila
 wrote:
>
> Hei,
>
>
>
> Golang does have the required features to support this, but it is more of a 
> challenge to convince the repo owners to start using this.
>
> You can download all of the dependencies in golang with go mod vendor and 
> then store the vendor-folder to the repo as well.
>
> But, the repo will get a lot larger that way. But, that fulfills the Yocto 
> demands as far as I know.
>

Yes, again, if you read the mailing list discussions on this in the
past, we are well aware of what golang does (and doesn't do) and the
options to fully integrate into the core capabilities via a dedicated
fetcher.

But no one has stepped up to implement a fully integrated solution, so
we have proposals only as this point.

I've gone a different way with meta-virtualization and am using large
SRC_URIs with the dependencies fetched to allow full integration with
the fetcher, and still build reproducible go binaries.

Bruce

>
>
> Best Regards,
>
>
>
>
>
> Janne Kiiskilä
>
>
>
>
>
> From: yocto@lists.yoctoproject.org  On Behalf 
> Of Markus Volk via lists.yoctoproject.org
> Sent: maanantai 3. heinäkuuta 2023 16.43
> To: Bruce Ashfield 
> Cc: przemek.re...@gmail.com; yocto@lists.yoctoproject.org
> Subject: Re: [yocto] Building Tailscale with Yocto #golang
>
>
>
> On Mon, Jul 3 2023 at 09:07:11 AM -0400, Bruce Ashfield 
>  wrote:
>
> We really shouldn't suggest the above to a developer without also the 
> explanation as to why network access is disabled by default in tasks such as 
> compile.
>
>
>
> You are of course right with your objections. However, this is the only way I 
> know of to get around this problem. Reproducibility is not a must have 
> requirement for me, but I use some gtk go programs and would love to have a 
> way to build at least gotk3 shared, since it takes quite a long time and has 
> to be rebuilt for each program.
>
> I had experimented with this some time ago, but it looked to me like there 
> was no easy solution to this problem. This is somehow quite a conflict 
> between different concepts.



-- 
- Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
- "Use the force Harry" - Gandalf, Star Trek II

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

Re: [yocto] Building Tailscale with Yocto #golang

2023-07-03 Thread Khem Raj 
On Mon, Jul 3, 2023 at 7:25 AM Janne Kiiskila
 wrote:
>
> Hei,
>
>
>
> Golang does have the required features to support this, but it is more of a 
> challenge to convince the repo owners to start using this.
>
> You can download all of the dependencies in golang with go mod vendor and 
> then store the vendor-folder to the repo as well.
>

yes go mod vendor is a way to get this working in a reasonable way.
This also avoid go's module management coming in way of
bitbake fetcher.

> But, the repo will get a lot larger that way. But, that fulfills the Yocto 
> demands as far as I know.

As a distro, I think this should be even preferred even though size is
bigger and several modules will be duplicated per recipe if
there are other go packages in image. As a developer this might be not
preferred however.

>
>
>
> Best Regards,
>
>
>
>
>
> Janne Kiiskilä
>
>
>
>
>
> From: yocto@lists.yoctoproject.org  On Behalf 
> Of Markus Volk via lists.yoctoproject.org
> Sent: maanantai 3. heinäkuuta 2023 16.43
> To: Bruce Ashfield 
> Cc: przemek.re...@gmail.com; yocto@lists.yoctoproject.org
> Subject: Re: [yocto] Building Tailscale with Yocto #golang
>
>
>
> On Mon, Jul 3 2023 at 09:07:11 AM -0400, Bruce Ashfield 
>  wrote:
>
> We really shouldn't suggest the above to a developer without also the 
> explanation as to why network access is disabled by default in tasks such as 
> compile.
>
>
>
> You are of course right with your objections. However, this is the only way I 
> know of to get around this problem. Reproducibility is not a must have 
> requirement for me, but I use some gtk go programs and would love to have a 
> way to build at least gotk3 shared, since it takes quite a long time and has 
> to be rebuilt for each program.
>
> I had experimented with this some time ago, but it looked to me like there 
> was no easy solution to this problem. This is somehow quite a conflict 
> between different concepts.
>
>
> 
>

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

[yocto] [meta-security][PATCH 1/2] python3-tpm2-pytss: add python tss2 support

2023-07-03 Thread Armin Kuster 
Signed-off-by: Armin Kuster 
---
 .../tpm2-pytss/python3-tpm2-pytss_2.1.0.bb| 15 +++
 1 file changed, 15 insertions(+)
 create mode 100644 meta-tpm/recipes-tpm2/tpm2-pytss/python3-tpm2-pytss_2.1.0.bb

diff --git a/meta-tpm/recipes-tpm2/tpm2-pytss/python3-tpm2-pytss_2.1.0.bb 
b/meta-tpm/recipes-tpm2/tpm2-pytss/python3-tpm2-pytss_2.1.0.bb
new file mode 100644
index 000..c98d4ab
--- /dev/null
+++ b/meta-tpm/recipes-tpm2/tpm2-pytss/python3-tpm2-pytss_2.1.0.bb
@@ -0,0 +1,15 @@
+DESCRIPTION = "TPM2 TSS Python bindings for Enhanced System API (ESYS), 
Feature API (FAPI), Marshaling (MU), TCTI Loader (TCTILdr), TCTIs, policy, and 
RC Decoding (rcdecode) libraries"
+HOMEPAGE = "https://github.com/tpm2-software/tpm2-pytss;
+LICENSE = "BSD-2-Clause"
+LIC_FILES_CHKSUM = "file://LICENSE;md5=500b2e742befc3da00684d8a1d5fd9da"
+
+SRC_URI[sha256sum] = 
"5b5b4b1456fdc1aeef3d2c3970beaa078c8f7f2648c97a69bcf60c5a2f95c897"
+
+PYPI_PACKAGE = "tpm2-pytss"
+
+DEPENDS = "python3-pkgconfig-native python3-pycparser-native 
python3-asn1crypto-native"
+DEPENDS:append = " python3-cryptography-native tpm2-tss" 
+
+inherit autotools pkgconfig pypi setuptools3_legacy
+
+RDEPENDS:${PN} = "libtss2"
-- 
2.34.1


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

[yocto] [meta-security][PATCH 2/2] packagegroup: add python3-tpm2-pytss

2023-07-03 Thread Armin Kuster 
Signed-off-by: Armin Kuster 
---
 meta-tpm/recipes-core/packagegroup/packagegroup-security-tpm2.bb | 1 +
 1 file changed, 1 insertion(+)

diff --git a/meta-tpm/recipes-core/packagegroup/packagegroup-security-tpm2.bb 
b/meta-tpm/recipes-core/packagegroup/packagegroup-security-tpm2.bb
index fb0105e..8663b77 100644
--- a/meta-tpm/recipes-core/packagegroup/packagegroup-security-tpm2.bb
+++ b/meta-tpm/recipes-core/packagegroup/packagegroup-security-tpm2.bb
@@ -20,4 +20,5 @@ RDEPENDS:packagegroup-security-tpm2 = " \
 libtss2 \
 tpm2-abrmd \
 tpm2-pkcs11 \
+python3-tpm2-pytss \
 "
-- 
2.34.1


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

[yocto] Enhancements/Bugs closed WW26!

2023-07-03 Thread Stephen Jolley 
All,

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


Who

Count


richard.pur...@linuxfoundation.org

1


randy.macl...@windriver.com

1


Grand Total

2

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

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

2023-07-03 Thread Stephen Jolley 
All,

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


Who

Count


michael.opdenac...@bootlin.com

32


ross.bur...@arm.com

30


david.re...@windriver.com

25


richard.pur...@linuxfoundation.org

24


bruce.ashfi...@gmail.com

24


randy.macl...@windriver.com

21


jpewhac...@gmail.com

10


pa...@zhukoff.net

7


sundeep.kokko...@windriver.com

5


sakib.sa...@windriver.com

5


pi...@pidge.org

4


yash.shi...@windriver.com

3


tim.orl...@konsulko.com

3


alexis.loth...@bootlin.com

3


jon.ma...@arm.com

2


yoann.con...@smile.fr

1


tvgamb...@gmail.com

1


thr...@amazon.de

1


thomas.per...@bootlin.com

1


st...@sakoman.com

1


pokyli...@reliableembeddedsystems.com

1


p.lob...@welotec.com

1


martin.ja...@gmail.com

1


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

1


mark.asselst...@windriver.com

1


louis.ran...@syslinbit.com

1


jens.ge...@desy.de

1


fathi.bou...@linaro.org

1


alexandre.bell...@bootlin.com

1


alejan...@enedino.org

1


Grand Total

213

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

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

2023-07-03 Thread Stephen Jolley 
All,

 

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

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

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

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

 

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

 

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

 

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

Re: [yocto] Building Tailscale with Yocto #golang

2023-07-03 Thread Janne Kiiskila 
Hei,

Golang does have the required features to support this, but it is more of a 
challenge to convince the repo owners to start using this.
You can download all of the dependencies in golang with go mod vendor and then 
store the vendor-folder to the repo as well.
But, the repo will get a lot larger that way. But, that fulfills the Yocto 
demands as far as I know.

Best Regards,


Janne Kiiskilä


From: yocto@lists.yoctoproject.org  On Behalf Of 
Markus Volk via lists.yoctoproject.org
Sent: maanantai 3. heinäkuuta 2023 16.43
To: Bruce Ashfield 
Cc: przemek.re...@gmail.com; yocto@lists.yoctoproject.org
Subject: Re: [yocto] Building Tailscale with Yocto #golang

On Mon, Jul 3 2023 at 09:07:11 AM -0400, Bruce Ashfield 
mailto:bruce.ashfi...@gmail.com>> wrote:

We really shouldn't suggest the above to a developer without also the 
explanation as to why network access is disabled by default in tasks such as 
compile.

You are of course right with your objections. However, this is the only way I 
know of to get around this problem. Reproducibility is not a must have 
requirement for me, but I use some gtk go programs and would love to have a way 
to build at least gotk3 shared, since it takes quite a long time and has to be 
rebuilt for each program.
I had experimented with this some time ago, but it looked to me like there was 
no easy solution to this problem. This is somehow quite a conflict between 
different concepts.

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

Re: [linux-yocto] Trial merge of v5.15.119 v6.1.36 for linux-yocto

2023-07-03 Thread Bruce Ashfield 
In message: Trial merge of v5.15.119 v6.1.36 for linux-yocto
on 29/06/2023 Kevin Hao wrote:

> Hi Bruce,
> 
> This is a trial merge of the stable kernel v5.15.119 v6.1.36 for the 
> following branches in the linux-yocto.
>   be40fc41bd6e  v5.15/standard/sdkv5.10/axxia
>   e75835741a61  v5.15/standard/preempt-rt/sdkv5.10/axxia
>   5286aba085f3  v5.15/standard/base
>   2ecfdafb698d  v5.15/standard/preempt-rt/base
>   8fa9560c4dd4  v5.15/standard/cn-sdkv5.4/octeon
>   63def203e4e4  v5.15/standard/preempt-rt/cn-sdkv5.4/octeon
>   c6a6f3f7ccb0  v5.15/standard/cn-sdkv5.15/octeon
>   c85fe0177765  v5.15/standard/preempt-rt/cn-sdkv5.15/octeon
>   3a984e518a65  v5.15/standard/ti-sdk-5.10/ti-j72xx
>   6e6d68f31692  v5.15/standard/preempt-rt/ti-sdk-5.10/ti-j72xx
>   ef85dc984077  v5.15/standard/nxp-sdk-5.15/nxp-soc   
>#Have textual conflicts
>   d442c239e922  v5.15/standard/preempt-rt/nxp-sdk-5.15/nxp-soc
>#Have textual conflicts
>   ca6190648f39  v5.15/standard/bcm-2xxx-rpi
>   fe77be715143  v5.15/standard/preempt-rt/bcm-2xxx-rpi
>   a0e68ed68874  v5.15/standard/nxp-sdk-5.15/nxp-s32g
>   731e0747cfc8  v5.15/standard/preempt-rt/nxp-sdk-5.15/nxp-s32g
>   33587f804c1f  v5.15/standard/intel-sdk-5.15/intel-socfpga
>   737a52381316  v5.15/standard/preempt-rt/intel-sdk-5.15/intel-socfpga
>   93636851643a  v5.15/standard/x86
>   13e6b9070532  v5.15/standard/preempt-rt/x86
>   06e2203ca6b4  v5.15/standard/sdkv5.15/xlnx-soc
>   fae6ce5c0f62  v5.15/standard/preempt-rt/sdkv5.15/xlnx-soc
>   6ddeb74e2aed  v6.1/standard/base
>#Have textual conflicts
>   5b1265e16f7c  v6.1/standard/preempt-rt/base
>   b6138f7d213f  v6.1/standard/ti-sdk-6.1/ti-j7xxx
>   411bdd3dfd02  v6.1/standard/preempt-rt/ti-sdk-6.1/ti-j7xxx
>   32bbd6f8e4a5  v6.1/standard/nxp-sdk-6.1/nxp-soc 
>#Have textual conflicts
>   b290cbd38c6f  v6.1/standard/preempt-rt/nxp-sdk-6.1/nxp-soc  
>#Have textual conflicts
>   9ed6c482ead6  v6.1/standard/cn-sdkv5.15/octeon
>   ad8cdb51154a  v6.1/standard/preempt-rt/cn-sdkv5.15/octeon
>   1178a4b79ab9  v6.1/standard/bcm-2xxx-rpi
>   e7efd0895134  v6.1/standard/preempt-rt/bcm-2xxx-rpi
>   3bf26017b1d0  v6.1/standard/nxp-sdk-5.15/nxp-s32g
>   60acc0e89194  v6.1/standard/preempt-rt/nxp-sdk-5.15/nxp-s32g
>   363ec7b1b160  v6.1/standard/intel-sdk-6.1/intel-socfpga
>   88d337e2b686  v6.1/standard/preempt-rt/intel-sdk-6.1/intel-socfpga
>   8ae2964866b5  v6.1/standard/x86
>   4bd09df854bd  v6.1/standard/preempt-rt/x86
>   1233d3e4f7e3  v6.1/standard/sdkv6.1/xlnx-soc
>   e9c4e041e2f0  v6.1/standard/preempt-rt/sdkv6.1/xlnx-soc
> 
> This seems a normal stable release. There is a conflict on v6.1/standard/base 
> due to
> the merge of commit 0c6552f83725 ("tick/common: Align tick period during 
> sched_timer setup")

Thanks Kevin,

Yes, this conflict was expected as I couldn't wait for fix to come through 
-stable for our intermittent x86 boot hangs.

I've reverted my previous revert and now the merge is clean to standard/base

Bruce

> and several trivial conflicts on the nxp branches. All the branches have 
> passed my
> build test. I have pushed all these branches to:
> https://github.com/haokexin/linux
> 
> You can use this as a reference for the linux-yocto stable kernel bump.
> 
> Thanks,
> Kevin

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

Re: [yocto] Building Tailscale with Yocto #golang

2023-07-03 Thread Markus Volk 
On Mon, Jul 3 2023 at 09:07:11 AM -0400, Bruce Ashfield 
 wrote:

We really shouldn't suggest the above to a developer without also the
explanation as to why network access is disabled by default in tasks
such as compile.


You are of course right with your objections. However, this is the only 
way I know of to get around this problem. Reproducibility is not a must 
have requirement for me, but I use some gtk go programs and would love 
to have a way to build at least gotk3 shared, since it takes quite a 
long time and has to be rebuilt for each program.
I had experimented with this some time ago, but it looked to me like 
there was no easy solution to this problem. This is somehow quite a 
conflict between different concepts.



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

Re: [yocto] Building Tailscale with Yocto #golang

2023-07-03 Thread Bruce Ashfield 
On Sun, Jul 2, 2023 at 4:30 PM Markus Volk  wrote:
>
> You need to allow network connection for the do_compile task
>
> do_compile[network] = "1"

We really shouldn't suggest the above to a developer without also the
explanation as to why network access is disabled by default in tasks
such as compile.

Your build may in fact work once you've allowed go to fetch its
dependencies / modules, but you will also not have reproducibility, a
full license report or sstate/download reuse (things you'd get from
fetcher integration).

If none of those things are significant to you, then by all means, you
can just allow go fetching in do_compile()

For more details on the options and the long discussions on the topic
in the past, I'd suggest searching the oe-core mailing list archives.

Bruce

>
>
> On Sun, Jul 2 2023 at 12:45:40 PM -0700, przemek.re...@gmail.com wrote:
>
> Hi!
> I'm trying to build Tailscale with Yocto
> This is me recipe:
>
> inherit go-mod
>
> SRC_URI = "git://github.com/tailscale/tailscale;protocol=https;branch=main"
> SRCREV = "30d9201a11ebc2e3a0f17bf8963956b77dadeb5d"
>
> GO_IMPORT = "tailscale.com"
> GO_WORKDIR = "${GO_IMPORT}"
> GO_INSTALL = "\
> ${GO_IMPORT}/cmd/tailscale \
> ${GO_IMPORT}/cmd/tailscaled \
> "
>
> do_install() {
> install -d ${D}/${bindir}
> install -d ${D}/${sbindir}
> install ${B}/bin/tailscale ${D}/${bindir}/tailscale
> install ${B}/bin/tailscaled ${D}/${sbindir}/tailscaled
> }
>
>
> However, build step ends up with errors like these (full log):
>
> | wgengine/netstack/netstack.go:34:2: 
> gvisor.dev/gvisor@v0.0.0-20230504175454-7b0a1988a28f: Get 
> "https://proxy.golang.org/gvisor.dev/gvisor/@v/v0.0.0-20230504175454-7b0a1988a28f.zip":
>  dial tcp: lookup proxy.golang.org on 8.8.8.8:53: dial udp 8.8.8.8:53: 
> connect: network is unreachable
> | wgengine/netstack/netstack.go:35:2: 
> gvisor.dev/gvisor@v0.0.0-20230504175454-7b0a1988a28f: Get 
> "https://proxy.golang.org/gvisor.dev/gvisor/@v/v0.0.0-20230504175454-7b0a1988a28f.zip":
>  dial tcp: lookup proxy.golang.org on 8.8.8.8:53: dial udp 8.8.8.8:53: 
> connect: network is unreachable
> | net/tstun/tap_linux.go:23:2: 
> gvisor.dev/gvisor@v0.0.0-20230504175454-7b0a1988a28f: Get 
> "https://proxy.golang.org/gvisor.dev/gvisor/@v/v0.0.0-20230504175454-7b0a1988a28f.zip":
>  dial tcp: lookup proxy.golang.org on 8.8.8.8:53: dial udp 8.8.8.8:53: 
> connect: network is unreachable
> | wgengine/netstack/netstack.go:37:2: 
> gvisor.dev/gvisor@v0.0.0-20230504175454-7b0a1988a28f: Get 
> "https://proxy.golang.org/gvisor.dev/gvisor/@v/v0.0.0-20230504175454-7b0a1988a28f.zip":
>  dial tcp: lookup proxy.golang.org on 8.8.8.8:53: dial udp 8.8.8.8:53: 
> connect: network is unreachable
> | ipn/ipnauth/ipnauth.go:16:2: 
> inet.af/peercred@v0.0.0-20210906144145-0893ea02156a: Get 
> "https://proxy.golang.org/inet.af/peercred/@v/v0.0.0-20210906144145-0893ea02156a.zip":
>  dial tcp: lookup proxy.golang.org on 8.8.8.8:53: dial udp 8.8.8.8:53: 
> connect: network is unreachable
>
> On some resources I have found it was recomended to add environmental 
> variables: `GOPROXY="direct"` and `GOSUMDB="off"`, but it didn't helped.
>
> Maybe someone has some ideas what is the cause of these errors?
>
>
> 
>


-- 
- Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
- "Use the force Harry" - Gandalf, Star Trek II

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

Re: [yocto] File magic/sdk relocation

2023-07-03 Thread Oleksandr Hnatiuk via lists.yoctoproject.org 
I think it hasn’t been noticed because openembedded-core doesn't build `file` 
in buildtools-tarball.

To reproduce the error, you need to do the following:
1. Download openembedded-core and bitbake, source init script
2. Add nativesdk-file to TOOLCHAIN_HOST_TASK, e.g. add the following line to 
conf/local.conf:
TOOLCHAIN_HOST_TASK:append = " nativesdk-file"
3. Run `bitbake buildtools-tarball`
4. Install buildtools: 
`tmp-glibc/deploy/sdk/x86_64-buildtools-nativesdk-standalone-nodistro.0.sh -y 
-d $buildtools_install_dir`
5. Same as (1) but in a different empty directory (first one built the 
buildtools, this one will use them)
6. Source the script provided by buildtools, e.g.: `source 
$buildtools_install_dir/environment-setup-x86_64-oesdk-linux`
7. Run `bitbake quilt-native`

You should get the following error:

ERROR: quilt-native-0.67-r0 do_populate_sysroot: Fatal errors occurred in 
subprocesses:
Command '['file', '-b', 
'/path/to/openembedded-core/build/tmp-glibc/work/x86_64-linux/quilt-native/0.67-r0/sysroot-destdir/path/to/openembedded-core/build/tmp-glibc/work/x86_64-linux/quilt-native/0.67-r0/recipe-sysroot-native/usr/bin/quilt']'
 returned non-zero exit status 1.

The same error is repeated for each invocation of `file` in do_populate_sysroot

Regards,
Oleksandr


From: Alexander Kanavin 
Sent: Tuesday, June 27, 2023 7:46 PM
To: Oleksandr Hnatiuk -X (ohnatiuk - GLOBALLOGIC INC at Cisco) 

Cc: yocto@lists.yoctoproject.org 
Subject: Re: [yocto] File magic/sdk relocation 
 
Before we think of a solution, can you provide steps or a test case where the 
issue can be seen? It’s in one of the most important tasks, so I’d like to know 
why it hasn’t been a problem and what is the scenario where it is.

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

Re: [yocto] [QUESTION] [meta-security/meta-tpm/recipes-tpm2] Kirkstone release

2023-07-03 Thread Benjamin BARATTE via lists.yoctoproject.org 
Hi Armin,

> -Original Message-
> From: akuster808 
> Sent: Sunday, July 2, 2023 9:11 PM
> To: Benjamin BARATTE ;
> yocto@lists.yoctoproject.org
> Subject: Re: [yocto] [QUESTION] [meta-security/meta-tpm/recipes-tpm2]
> Kirkstone release
> 
> Benjamin,
> 
> On 6/30/23 11:12 AM, Benjamin BARATTE via lists.yoctoproject.org wrote:
> >
> > Dear Maintainers,
> >
> > I’m using the meta-security with Kirkstone version to use discrete TPM
> > with STM32MP1.
> >
> > I’m facing 3 issues :
> >
> >   * The packagegroup does not include libtss2-tcti-device library è
> > mandatory to use discrete TPM.
> >
> 
> Does this Mickledore commit address the issue?
> https://git.yoctoproject.org/meta-security/commit/meta-tpm/recipes-
> core/packagegroup?id=8a7112d37bfe0157289ed7e6baeb1d7e37707b29

yes, this one is working on Kirkstone

> >
> >  *
> >
> >
> >   * The packagegroup does not include tpm2-openssl è support of TPM
> > provides for openssl v3.x
> >
> Mind sending a patch to add this to master and I will backport to kirkstone.

Based on Mickledore commit, you can add tpm2-openssl in the list of 
dependencies for the packagegroup-security-tpm2

> >
> >  *
> >
> >
> >   * Tpm2-tools is on release 5.2 which has an issue with tpm2_nvread
> > (https://bugzilla.redhat.com/show_bug.cgi?id=2158598) è could it
> > be possible to update it at least to release 5.4
> >
> 
> The changes between 5.2 and 5.4 include many new functions/features. You
> can either carry that recipe local or give Mickledore a try.

I have seen that Mickledore use the version 5.4 already. 
The other dependencies seem OK. 
As this is only the tpm2-tools package and I don't have the choice of the Yocto 
release, I have made a local modification to use 5.4

Best Regards,

Benjamin

> 
> BR,
> Armin
> >
> >  *
> >
> > Thanks,
> >
> > Best Regards,
> >
> > Benjamin
> >
> >
> >
> > 
> >


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