The submodules shouldn't be changing when you check out the same tag. i.e. git submodule status Should always return the same commit IDs when you check out the same tag, since those hashes are

How should we do here? If I checkout the tag v3.99 in for the UPX repo and carry out the update submodules, I will end up with a different commit ID for the submodules every time. How can we pinpoint

On 2023-03-29 23:17, Bruce Ashfield wrote: Done Sakib

Bumping kubernetes to version 1.23.17, which comprises of the following commits: $ git log --no-merges --oneline fbcfa330..953be892 953be892721 (tag: v1.23.17) Release commit for Kubernetes

I should add, that if the shortlogs blow out the mailing list max message size, then either a pull request or a summary of the release notes from the project are appropriate work arounds. Bruce On

Please do list them in the log. Simply listing the number isn't useful. We aren't charged by the byte of text ;) Bruce

I already have pending updates to the stacks that are in test now, they'll be in place in the next week or so. Bruce

This upgrade fixes a few CVEs: - CVE-2023-27561 - CVE-2023-25809 - CVE-2023-28642 Signed-off-by: Chen Qi <Qi.Chen@...> --- recipes-containers/runc/runc-docker_git.bb | 4 ++--

This upgrade fixes a few CVEs: - CVE-2023-27561 - CVE-2023-25809 - CVE-2023-28642 Signed-off-by: Chen Qi <Qi.Chen@...> --- recipes-containers/runc/runc-docker_git.bb | 4 ++--

Bumping kubernetes to version v1.23.17, which comprises of 251 commits, so not listing them in the log: $ git log --no-merges --oneline fbcfa330..953be892 | wc -l 251 Signed-off-by: Sakib Sajal

Right, we can't have AUTOREV in non special "development" packages. Bruce -- - Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end - "Use the force Harry" - Gandalf,

Hi Joakim, Joakim Roubert <joakim.roubert@...> escreveu no dia quarta, 29/03/2023 à(s) 15:19: The AUTOREV will break the reproducibility of this package. Jose -- Best regards, José Quaresma

It seems there has been recent changes to the UPX repo that make the current 3.96 setup here fail now. This patch mitigates that and also bumps UPX to version 3.99. Change-Id:

1.6.19 is the latest release for 1.6 branch. This upgrade fixes CVEs such as CVE-2023-25173 and CVE-2023-25153. Signed-off-by: Chen Qi <Qi.Chen@...> ---

1.27.x that I have under test is on master-next. I changed this commit to just be part 2) below, and left your Signed-off-by. Bruce In message: [meta-virtualization][PATCH] kubernetes: upgrade to

This is now staged on master-next. Bruce In message: [meta-virtualization][PATCH 1/2] Revert "yq: drop {LINKSHARED}" on 27/03/2023 Jose Quaresma wrote:

Bruce Ashfield <bruce.ashfield@...> escreveu no dia segunda, 27/03/2023 à(s) 13:21: Ok, no problem. I also have checked the size of the binaries and it is mostly the same. static vs shared: tree --du

I'm going to keep this change as-is. The structure of the linkeshared building in buildah isn't well done, and the build -> rm -> build again is strange (to say the least). Bruce -- - Thou shalt

The linkshared is fixed upstream and backported in oe-core. https://git.yoctoproject.org/poky/commit/?id=d5c79ca6a77af1a04992fff4300333e02d94d84d Signed-off-by: Jose Quaresma

This reverts commit d2a630ce6cf67a145f218012fbf02e4d0d9648df. The linkshared is fixed upstream and backported in