Re: heads-up: planned changes in nvmm

[Chavdar Ivanov <ci4ic4%gmail.com@localhost>]

I've rebuilt my -current system a few hours ago, followed by a build
of  wip/qemu-nvmm, I see now at 4.1.

So far everything seems to be working as expected.

BTW I have been getting - on all my qemu-nvmm builds from wip - a PLIST error -

share/locale/bg/LC_MESSAGES/qemu.mo
share/locale/de_DE/LC_MESSAGES/qemu.mo
share/locale/fr_FR/LC_MESSAGES/qemu.mo
share/locale/hu/LC_MESSAGES/qemu.mo
share/locale/it/LC_MESSAGES/qemu.mo
share/locale/tr/LC_MESSAGES/qemu.mo
share/locale/zh_CN/LC_MESSAGES/qemu.mo

present in the destination folder but missing in PLIST.


On Tue, 22 Oct 2019 at 21:34, Maxime Villard <max%m00nbsd.net@localhost> wrote:
>
> [I am not subscribed to this list, so if you want to answer, make sure to
> CC me.]
>
> I will soon commit a set of changes in NVMM, which will require a full
> rebuild and reinstallation of: the kernel NVMM driver, the libnvmm API,
> the libnvmm ATF tests, and the qemu-nvmm package if you're using it.
>
> You can cherry-pick each change, but it will be easier to just do a full
> distribution rebuild and reinstall.
>
> Overall it is no different than what I've been doing over the last six
> months. This time, however, the changes will also be pulled up to 9beta
> afterwards.
>
> I will push my changes in -current and update the qemu-nvmm package in
> several rounds probably over several days, and then will pull up to 9beta.
>
> In the meantime, do not upgrade your qemu-nvmm package if you're on 9beta.



-- 
----