From: Changqing Li <changqing.li@...> Signed-off-by: Changqing Li <changqing.li@...> --- .../libvirt/libvirt/CVE-2022-0897.patch | 57 +++++++++++++++++++

Just for the record, there is${nonarch_libdir} that expands to “/usr/lib” regardless of whether multilib is used or not. It is typically intended for cases like this. //Peter

Hi Qi You are right. My build configuration is also using multilib and this issue appeared.

Hmm. Indeed. In that case, I'll go with a variant of the original patch, with a tweaked commit log. I'll take care of that now. Bruce -- - Thou shalt not follow the NULL pointer, for chaos and

The only package I found which uses /usr/lib/sysctl.d is systemd. It packages ${exec_prefix}/lib/sysctl.d. And it has its reason. It treats /usr/lib as an arch-independent vendor dir, and $libdir is

I've done multiple executions of that exact set of steps, and I've never seen the error you are encountering. Clearly there's something different in the various build environments. We are also getting

That's a larger issue, and it breaks other parts of the system. We shouldn't have anything with hard coded /usr/lib. How are other packages dealing with this ? In that case, I'll do individual scripts

See the patch that I sent as well. There's no reason to have /usr/lib anywhere in the packaging at all. We should just rely on ${libdir}, if libvirt is installing outside of the definition of

Hi Bruce, Looking at the issue a little further, I found we need to use the hardcoded ‘/usr/lib’. This is because sysctl is hardcoding that. Some codes in sysctl.c from procps: static

The libvirtd package has already packaged ${sysconfdir}/sysctl.d, and also the /usr/lib/sysctl.d/60-libvirtd.conf, it would be reasonable for it to package other sysctl conf files, otherwise we will

I've pushed my WIP patch here: https://git.yoctoproject.org/meta-virtualization/commit/?h=master-next Bruce -- - Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end -

Aha. Right you are. So we should tweak libvirt to use ${libdir} and not the hardcoded /user/lib (which it never really should have been), and package anything that gets installed into sysctl.d/ It

Hi Bruce & Preeti, I was trying to fix the same issue when I found this thread. This issue appears when multilib is enabled. When multilib is disabled, ${libdir} is /usr/lib, thus packaging

No libvirt bbappend file in build and multiconfig is created to build with particular kernel version. In recipe

There's definitely something different in your configuration, so that needs to be understood first. That file is packaged as part of libvirt-python here, and should be the same for others, as I

It had a protocol specification already, I just managed to miss an 'o'. I've fixed that, and pushed the change. Annoying that github didn't break/stop my build immediately with that typo, but at least

Also, fix the indentation for the SRC_URI variable assignment. Signed-off-by: Diego Sueiro <diego.sueiro@...> --- recipes-networking/cni/cni_git.bb | 9 +++++---- 1 file changed, 5

Hi Michal, Thanks a lot for this. For the whole serie: Reviewed-by: Bertrand Marquis <bertrand.marquis@...> Cheers Bertrand

ERROR: mc:x86-2020:libvirt-8.1.0-r0 do_package: QA Issue: libvirt: Files/directories were installed but not shipped in any package: /usr/lib/sysctl.d/60-qemu-postcopy-migration.conf Please set FILES

I'm not seeing any packaging issues here. Can you elaborate on what warning/QA/other issue you are seeing ? Bruce -- - Thou shalt not follow the NULL pointer, for chaos and madness await thee at its