Hi Oleg, On 19/05/2023 15:38, Oleg Nikitenko wrote: > > > > Hello, > > Thanks Michal. > > Then the next question. Now it is more related to the integration than to the > development. > A license for the xen in 4.17 revision at branch xlnx_rebase_4.17 xilinx repo > has changed. > I found out when I built this version. > Now bitbake and yocto build fault by COPYING file md5 hashe inequality reason. > I found out md5 hash stored at > sources/libs/meta-virtualization/recipes-extended/xen directory in files > xen-tools_4.15.bb <http://xen-tools_4.15.bb> > xen_4.15.bb <http://xen_4.15.bb> > xen_git.bb <http://xen_git.bb> > xen-tools_git.bb <http://xen-tools_git.bb> > xen-tools_4.16.bb <http://xen-tools_4.16.bb> > xen_4.16.bb <http://xen_4.16.bb> > So this is a question. Should I update the license file for all our branches > or is it possible to keep an old one for old branches ?
I'm not a Yocto expert but it looks like you want to use Xen 4.17 using old meta-virtualization with no support for 4.17. Anyway, this discussion is no longer related to the original issue (nor to Xen itself) which I hope I helped to overcome. In case of other Xen related issues, please send a new e-mail to a mailing list. ~Michal
