From: Quentin Schulz <quentin.schulz@...> Since commit 84ccba0f4aff91528f764523fe1205a354c889ed, docs of all later releases can be built with Sphinx. Instead of manually updating thi

From: Quentin Schulz <quentin.schulz@...> master and master-next only differ from other branches by their output directory name. Let's put everything in common and only have a check

From: Quentin Schulz <quentin.schulz@...> The patch was meant as a quick temporary work-around to have the docs built and published. Now that releases where -W flag is set (turning w

From: Quentin Schulz <quentin.schulz@...> The patch was missing from yocto-3.4.1 release and only made it to yocto-3.4.2 unfortunately so let's backport it. Cc: Quentin Schulz <foss+

From: Quentin Schulz <quentin.schulz@...> Each Yocto Project release is validated for a specific Bitbake release. By mistake, most release docs are pointing at the development branch

From: Quentin Schulz <quentin.schulz@...> There's no need to keep a list of tags requiring to be patched since the tag is part of the path where patches are stored. Therefore, let's

From: Quentin Schulz <quentin.schulz@...> Default flags for sphinx-build contain -W which turns warnings into errors. This is really helpful during debugging and could be used for co

From: Quentin Schulz <quentin.schulz@...> There are some intermittent issues with the script not publishing all versions. So let's go extreme and fail the script if any error happens

Hi Michael, One change at a time please ☺️ This should be done right after the git checkout. It's better to ensure what you build is clean that try to ensure the next oneto build has a clean env. Espe

Hi Michael, IMO that makes it unsuitable for the docs as we strive to have "simple" examples and having some custom unpack task seems a bit too much to me. Anyway, just my 2¢ and I don't have any othe

Thanks for asking. I wouldn't have minded were you to send this patch without my SoB but if you want you can use foss+yocto@.... The important being that it's fixed ☺️ Cheers, Quentin

Hi Trevor, To be fair, I didn't take the time to formulate correctly and point to the docs ☺️ podman run --help | grep tmp Does return it though. It's just that some options are specific to subcommand

Hi Trevor, https://docs.podman.io/en/latest/markdown/podman-run.1.html#tmpfs-fs I wasn't talking about uids or gids, but pids_limit in containers.conf for podman on your host. See: https://man.archlin

Hi Trevor, I've had similar issues recently with kas-container and podman. What was required were two things: - passing --tmpfs /tmp to podman run, - increase pids_limit in container.conf (your system

Hi JH, IIRC, you need to add your package to KERNEL_MODULE_AUTOLOAD, c.f. https://docs.yoctoproject.org/ref-manual/variables.html#term-KERNEL_MODULE_AUTOLOAD Cheers, Quentin

From: Quentin Schulz <quentin.schulz@...> Not all Rockchip boards have their console running at 1500000 baud in U-Boot and the kernel. Such is the case for puma-haikou RK3399-based S

Hi José, The issue is that you masked a recipe whose packages are required by other recipes packages. Find where the RDEPENDS is set for this recipe package and remove the package which depends on tha

Hi Léon, Did you check that your kernel actually supports squashfs as rootfs? There is a Kconfig option for it IIRC. Since it's an image feature, it's not going to impact anything outside of the image

Hi Khem, We need this patch for honister 3.4 but what I meant is that even though it's not needed for honister >= 3.4.1, I'm still interested in what the policy should be. Especially what we should ha

If you could explain what's *really* bothering you, I could try to find a proper explanation or agree with you but it's a bit too vague to me right now. Anyway, I'll do some guesses in the next paragr