Re: [OE-core] [PATCH v2] distro_features_check: expand with MACHINE_FEATURES and COMBINED_FEATURES, rename
Can you please update the documentation to reflect this bbclass rename? Patrick Vacek maintainer of meta-updater mentioned in one PR that the documentation doesn't mention features_check.bbclass: https://github.com/advancedtelematic/meta-updater/pull/771#issuecomment-683618949 It's mentioned in the "Moving to the Yocto Project 3.1 Release" section: https://www.yoctoproject.org/docs/3.1.2/mega-manual/mega-manual.html#migration-3.1-features-check but then all related variables and class reference only mention the old distro_features_check name https://www.yoctoproject.org/docs/3.1.2/mega-manual/mega-manual.html#var-REQUIRED_DISTRO_FEATURES https://www.yoctoproject.org/docs/3.1.2/mega-manual/mega-manual.html#var-CONFLICT_DISTRO_FEATURES https://www.yoctoproject.org/docs/3.1.2/mega-manual/mega-manual.html#ref-classes-distro_features_check Not sure how this looks in the new sphinx generated documentation. Thanks On Sat, Nov 23, 2019 at 12:38 AM Denys Dmytriyenko wrote: > On Fri, Nov 22, 2019 at 06:16:39PM -0500, Denys Dmytriyenko wrote: > > On Fri, Nov 22, 2019 at 11:10:14PM +, Richard Purdie wrote: > > > On Fri, 2019-11-22 at 23:58 +0100, Andreas Müller wrote: > > > > Whatever this patch does renaming does nothing but causing me lots of > > > > useles (rebasing) efforts. To me ist is simlpy the worst patch of > > > > this > > > > year and thanks for blocking me with this. I am really really > > > > upset!!! > > > > > > FWIW you can probably unblock yourself by adding a local copy of the > > > compatibility bbclass with the warning removed. That will then let you > > > fix the fallout at a time of your choosing. > > > > I thought warning would be relatively harmless... Why would it be > blocking? > > Do you want this to be a notice instead? > > > > > > > I was in two minds about the change to be honest but nobody commented > > > in review and I get really tired of a reputation for saying "no" to > > > "everything". What probably swung the balance is the ways you can work > > > around the change at least temporarily. > > > > I was also surprised by relative silence in review. Plus, it was in > > master-next for over a week and nobody complained either... > > And to be fair, this is almost right after the release, so is the best > time > for such invasive changes - I did wait and held off submitting it for > several > months to not disrupt the release process! > So such overreaction is rather unwarranted... > > -- > Denys > -- > ___ > Openembedded-core mailing list > Openembedded-core@lists.openembedded.org > http://lists.openembedded.org/mailman/listinfo/openembedded-core > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#142719): https://lists.openembedded.org/g/openembedded-core/message/142719 Mute This Topic: https://lists.openembedded.org/mt/72388036/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [OE-core] [PATCH v2] distro_features_check: expand with MACHINE_FEATURES and COMBINED_FEATURES, rename
On Sat, Nov 23, 2019 at 12:16 AM Denys Dmytriyenko wrote: > > On Fri, Nov 22, 2019 at 11:10:14PM +, Richard Purdie wrote: > > On Fri, 2019-11-22 at 23:58 +0100, Andreas Müller wrote: > > > Whatever this patch does renaming does nothing but causing me lots of > > > useles (rebasing) efforts. To me ist is simlpy the worst patch of > > > this > > > year and thanks for blocking me with this. I am really really > > > upset!!! > > > > FWIW you can probably unblock yourself by adding a local copy of the > > compatibility bbclass with the warning removed. That will then let you > > fix the fallout at a time of your choosing. > > I thought warning would be relatively harmless... Why would it be blocking? > Do you want this to be a notice instead? am somewhat special: * Am sitting on 50+ patches for meta-openembedded and there was a patch sent adjusting features that causes me lots of nasty rebasing and go through the patches again. * (Try to) maintain MANY recipes. Did not run a test yet but I expect lots of warnings. Problem is that you might miss important so they should be fixed. But since I expect distro-features to go in the long term spawning a warning is the right thing to do. I understand the intention but sometimes we should just keep things stable or as is. Time for zzz Andeas -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH v2] distro_features_check: expand with MACHINE_FEATURES and COMBINED_FEATURES, rename
On Fri, Nov 22, 2019 at 06:16:39PM -0500, Denys Dmytriyenko wrote: > On Fri, Nov 22, 2019 at 11:10:14PM +, Richard Purdie wrote: > > On Fri, 2019-11-22 at 23:58 +0100, Andreas Müller wrote: > > > Whatever this patch does renaming does nothing but causing me lots of > > > useles (rebasing) efforts. To me ist is simlpy the worst patch of > > > this > > > year and thanks for blocking me with this. I am really really > > > upset!!! > > > > FWIW you can probably unblock yourself by adding a local copy of the > > compatibility bbclass with the warning removed. That will then let you > > fix the fallout at a time of your choosing. > > I thought warning would be relatively harmless... Why would it be blocking? > Do you want this to be a notice instead? > > > > I was in two minds about the change to be honest but nobody commented > > in review and I get really tired of a reputation for saying "no" to > > "everything". What probably swung the balance is the ways you can work > > around the change at least temporarily. > > I was also surprised by relative silence in review. Plus, it was in > master-next for over a week and nobody complained either... And to be fair, this is almost right after the release, so is the best time for such invasive changes - I did wait and held off submitting it for several months to not disrupt the release process! So such overreaction is rather unwarranted... -- Denys -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH v2] distro_features_check: expand with MACHINE_FEATURES and COMBINED_FEATURES, rename
On Fri, Nov 22, 2019 at 11:10:14PM +, Richard Purdie wrote: > On Fri, 2019-11-22 at 23:58 +0100, Andreas Müller wrote: > > Whatever this patch does renaming does nothing but causing me lots of > > useles (rebasing) efforts. To me ist is simlpy the worst patch of > > this > > year and thanks for blocking me with this. I am really really > > upset!!! > > FWIW you can probably unblock yourself by adding a local copy of the > compatibility bbclass with the warning removed. That will then let you > fix the fallout at a time of your choosing. I thought warning would be relatively harmless... Why would it be blocking? Do you want this to be a notice instead? > I was in two minds about the change to be honest but nobody commented > in review and I get really tired of a reputation for saying "no" to > "everything". What probably swung the balance is the ways you can work > around the change at least temporarily. I was also surprised by relative silence in review. Plus, it was in master-next for over a week and nobody complained either... -- Denys -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH v2] distro_features_check: expand with MACHINE_FEATURES and COMBINED_FEATURES, rename
On Fri, Nov 22, 2019 at 11:58:16PM +0100, Andreas Müller wrote: > Whatever this patch does renaming does nothing but causing me lots of > useles (rebasing) efforts. To me ist is simlpy the worst patch of this > year and thanks for blocking me with this. I am really really > upset!!! Are you sure you meant rebasing and not fixing the warnings in other layers? The patch has nothing to do with rebasing, obviously. Fixing other layers was on my list, at least for several major ones... -- Denys > On Fri, Nov 15, 2019 at 1:40 AM Denys Dmytriyenko wrote: > > > > From: Denys Dmytriyenko > > > > Besides checking DISTRO_FEATURES for required or conflicting features, > > being able to check MACHINE_FEATURES and/or COMBINED_FEATURES may also > > be useful at times. > > > > Temporarily support the old class name with a warning about future > > deprecation. > > > > Signed-off-by: Denys Dmytriyenko > > --- > > v2 - support old name for a while with a deprecation warning > > > > meta/classes/distro_features_check.bbclass | 35 ++-- > > ...atures_check.bbclass => features_check.bbclass} | 65 > > -- > > meta/conf/documentation.conf | 4 +- > > meta/recipes-bsp/usbutils/usbutils_012.bb | 2 +- > > meta/recipes-connectivity/avahi/avahi-ui_0.7.bb| 2 +- > > meta/recipes-connectivity/bluez5/bluez5.inc| 2 +- > > .../connman/connman-gnome_0.7.bb | 2 +- > > meta/recipes-core/glib-2.0/glib.inc| 2 +- > > meta/recipes-core/glibc/glibc.inc | 2 +- > > meta/recipes-core/libxml/libxml2_2.9.9.bb | 2 +- > > .../packagegroups/packagegroup-self-hosted.bb | 2 +- > > meta/recipes-core/systemd/systemd-compat-units.bb | 2 +- > > meta/recipes-core/systemd/systemd-serialgetty.bb | 2 +- > > meta/recipes-core/systemd/systemd_243.bb | 2 +- > > meta/recipes-core/sysvinit/sysvinit_2.88dsf.bb | 2 +- > > meta/recipes-core/udev/eudev_3.2.8.bb | 2 +- > > meta/recipes-core/volatile-binds/volatile-binds.bb | 2 +- > > meta/recipes-devtools/mtools/mtools_4.0.23.bb | 2 +- > > .../systemd-bootchart/systemd-bootchart_233.bb | 2 +- > > meta/recipes-extended/pam/libpam_1.3.1.bb | 2 +- > > meta/recipes-extended/xdg-utils/xdg-utils_1.1.3.bb | 2 +- > > meta/recipes-gnome/epiphany/epiphany_3.34.1.bb | 2 +- > > meta/recipes-gnome/gcr/gcr_3.34.0.bb | 2 +- > > meta/recipes-gnome/gtk+/gtk+3.inc | 2 +- > > meta/recipes-gnome/libdazzle/libdazzle_3.34.1.bb | 2 +- > > meta/recipes-gnome/libnotify/libnotify_0.7.8.bb| 2 +- > > meta/recipes-graphics/clutter/clutter-1.0.inc | 2 +- > > meta/recipes-graphics/clutter/clutter-gst-3.0.inc | 2 +- > > meta/recipes-graphics/clutter/clutter-gtk-1.0.inc | 2 +- > > meta/recipes-graphics/cogl/cogl-1.0.inc| 2 +- > > meta/recipes-graphics/glew/glew_2.1.0.bb | 2 +- > > meta/recipes-graphics/images/core-image-weston.bb | 2 +- > > meta/recipes-graphics/images/core-image-x11.bb | 2 +- > > meta/recipes-graphics/kmscube/kmscube_git.bb | 2 +- > > meta/recipes-graphics/libepoxy/libepoxy_1.5.3.bb | 2 +- > > meta/recipes-graphics/libfakekey/libfakekey_git.bb | 2 +- > > .../libmatchbox/libmatchbox_1.12.bb| 2 +- > > meta/recipes-graphics/libva/libva-utils_2.5.0.bb | 2 +- > > meta/recipes-graphics/libva/libva_2.5.0.bb | 2 +- > > .../matchbox-wm/matchbox-wm_1.2.2.bb | 2 +- > > meta/recipes-graphics/mesa/libglu_9.0.1.bb | 2 +- > > meta/recipes-graphics/mesa/mesa-demos_8.4.0.bb | 2 +- > > meta/recipes-graphics/mesa/mesa.inc| 2 +- > > meta/recipes-graphics/mx/mx.inc| 2 +- > > .../packagegroups/packagegroup-core-clutter.bb | 2 +- > > .../packagegroups/packagegroup-core-x11-base.bb| 2 +- > > .../packagegroups/packagegroup-core-x11-xserver.bb | 2 +- > > .../packagegroups/packagegroup-core-x11.bb | 2 +- > > meta/recipes-graphics/piglit/piglit_git.bb | 2 +- > > meta/recipes-graphics/pong-clock/pong-clock_1.0.bb | 2 +- > > .../startup-notification_0.12.bb | 2 +- > > .../virglrenderer/virglrenderer_0.8.0.bb | 2 +- > > meta/recipes-graphics/vulkan/vulkan-demos_git.bb | 2 +- > > .../vulkan/vulkan-loader_1.1.108.bb| 2 +- > > .../vulkan/vulkan-tools_1.1.108.bb | 2 +- > > meta/recipes-graphics/waffle/waffle_1.6.0.bb | 2 +- > > meta/recipes-graphics/wayland/weston-init.bb | 2 +- > > meta/recipes-graphics/wayland/weston_7.0.0.bb | 2 +- > > .../x11-common/xserver-nodm-init_3.0.bb| 2 +- > > .../xinput-calibrator/xinput-calibrator_git.bb | 2 +- > > meta/recipes-graphics/xorg-app/xorg-app-common.inc | 2 +- > > .../xorg-driver/xorg-driver-common.inc | 2 +- > >
Re: [OE-core] [PATCH v2] distro_features_check: expand with MACHINE_FEATURES and COMBINED_FEATURES, rename
On Fri, 2019-11-22 at 23:58 +0100, Andreas Müller wrote: > Whatever this patch does renaming does nothing but causing me lots of > useles (rebasing) efforts. To me ist is simlpy the worst patch of > this > year and thanks for blocking me with this. I am really really > upset!!! FWIW you can probably unblock yourself by adding a local copy of the compatibility bbclass with the warning removed. That will then let you fix the fallout at a time of your choosing. I was in two minds about the change to be honest but nobody commented in review and I get really tired of a reputation for saying "no" to "everything". What probably swung the balance is the ways you can work around the change at least temporarily. Cheers, Richard -- ___ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
Re: [OE-core] [PATCH v2] distro_features_check: expand with MACHINE_FEATURES and COMBINED_FEATURES, rename
Whatever this patch does renaming does nothing but causing me lots of useles (rebasing) efforts. To me ist is simlpy the worst patch of this year and thanks for blocking me with this. I am really really upset!!! On Fri, Nov 15, 2019 at 1:40 AM Denys Dmytriyenko wrote: > > From: Denys Dmytriyenko > > Besides checking DISTRO_FEATURES for required or conflicting features, > being able to check MACHINE_FEATURES and/or COMBINED_FEATURES may also > be useful at times. > > Temporarily support the old class name with a warning about future > deprecation. > > Signed-off-by: Denys Dmytriyenko > --- > v2 - support old name for a while with a deprecation warning > > meta/classes/distro_features_check.bbclass | 35 ++-- > ...atures_check.bbclass => features_check.bbclass} | 65 > -- > meta/conf/documentation.conf | 4 +- > meta/recipes-bsp/usbutils/usbutils_012.bb | 2 +- > meta/recipes-connectivity/avahi/avahi-ui_0.7.bb| 2 +- > meta/recipes-connectivity/bluez5/bluez5.inc| 2 +- > .../connman/connman-gnome_0.7.bb | 2 +- > meta/recipes-core/glib-2.0/glib.inc| 2 +- > meta/recipes-core/glibc/glibc.inc | 2 +- > meta/recipes-core/libxml/libxml2_2.9.9.bb | 2 +- > .../packagegroups/packagegroup-self-hosted.bb | 2 +- > meta/recipes-core/systemd/systemd-compat-units.bb | 2 +- > meta/recipes-core/systemd/systemd-serialgetty.bb | 2 +- > meta/recipes-core/systemd/systemd_243.bb | 2 +- > meta/recipes-core/sysvinit/sysvinit_2.88dsf.bb | 2 +- > meta/recipes-core/udev/eudev_3.2.8.bb | 2 +- > meta/recipes-core/volatile-binds/volatile-binds.bb | 2 +- > meta/recipes-devtools/mtools/mtools_4.0.23.bb | 2 +- > .../systemd-bootchart/systemd-bootchart_233.bb | 2 +- > meta/recipes-extended/pam/libpam_1.3.1.bb | 2 +- > meta/recipes-extended/xdg-utils/xdg-utils_1.1.3.bb | 2 +- > meta/recipes-gnome/epiphany/epiphany_3.34.1.bb | 2 +- > meta/recipes-gnome/gcr/gcr_3.34.0.bb | 2 +- > meta/recipes-gnome/gtk+/gtk+3.inc | 2 +- > meta/recipes-gnome/libdazzle/libdazzle_3.34.1.bb | 2 +- > meta/recipes-gnome/libnotify/libnotify_0.7.8.bb| 2 +- > meta/recipes-graphics/clutter/clutter-1.0.inc | 2 +- > meta/recipes-graphics/clutter/clutter-gst-3.0.inc | 2 +- > meta/recipes-graphics/clutter/clutter-gtk-1.0.inc | 2 +- > meta/recipes-graphics/cogl/cogl-1.0.inc| 2 +- > meta/recipes-graphics/glew/glew_2.1.0.bb | 2 +- > meta/recipes-graphics/images/core-image-weston.bb | 2 +- > meta/recipes-graphics/images/core-image-x11.bb | 2 +- > meta/recipes-graphics/kmscube/kmscube_git.bb | 2 +- > meta/recipes-graphics/libepoxy/libepoxy_1.5.3.bb | 2 +- > meta/recipes-graphics/libfakekey/libfakekey_git.bb | 2 +- > .../libmatchbox/libmatchbox_1.12.bb| 2 +- > meta/recipes-graphics/libva/libva-utils_2.5.0.bb | 2 +- > meta/recipes-graphics/libva/libva_2.5.0.bb | 2 +- > .../matchbox-wm/matchbox-wm_1.2.2.bb | 2 +- > meta/recipes-graphics/mesa/libglu_9.0.1.bb | 2 +- > meta/recipes-graphics/mesa/mesa-demos_8.4.0.bb | 2 +- > meta/recipes-graphics/mesa/mesa.inc| 2 +- > meta/recipes-graphics/mx/mx.inc| 2 +- > .../packagegroups/packagegroup-core-clutter.bb | 2 +- > .../packagegroups/packagegroup-core-x11-base.bb| 2 +- > .../packagegroups/packagegroup-core-x11-xserver.bb | 2 +- > .../packagegroups/packagegroup-core-x11.bb | 2 +- > meta/recipes-graphics/piglit/piglit_git.bb | 2 +- > meta/recipes-graphics/pong-clock/pong-clock_1.0.bb | 2 +- > .../startup-notification_0.12.bb | 2 +- > .../virglrenderer/virglrenderer_0.8.0.bb | 2 +- > meta/recipes-graphics/vulkan/vulkan-demos_git.bb | 2 +- > .../vulkan/vulkan-loader_1.1.108.bb| 2 +- > .../vulkan/vulkan-tools_1.1.108.bb | 2 +- > meta/recipes-graphics/waffle/waffle_1.6.0.bb | 2 +- > meta/recipes-graphics/wayland/weston-init.bb | 2 +- > meta/recipes-graphics/wayland/weston_7.0.0.bb | 2 +- > .../x11-common/xserver-nodm-init_3.0.bb| 2 +- > .../xinput-calibrator/xinput-calibrator_git.bb | 2 +- > meta/recipes-graphics/xorg-app/xorg-app-common.inc | 2 +- > .../xorg-driver/xorg-driver-common.inc | 2 +- > .../xorg-font/xorg-font-common.inc | 2 +- > .../xorg-font/xorg-minimal-fonts.bb| 2 +- > meta/recipes-graphics/xorg-lib/libxcb_1.13.1.bb| 2 +- > meta/recipes-graphics/xorg-lib/xcb-util.inc| 2 +- > meta/recipes-graphics/xorg-lib/xorg-lib-common.inc | 2 +- > .../recipes-graphics/xorg-xserver/xserver-xorg.inc | 2 +- > meta/recipes-graphics/xrestop/xrestop_0.4.bb | 2 +- >
[OE-core] [PATCH v2] distro_features_check: expand with MACHINE_FEATURES and COMBINED_FEATURES, rename
From: Denys Dmytriyenko Besides checking DISTRO_FEATURES for required or conflicting features, being able to check MACHINE_FEATURES and/or COMBINED_FEATURES may also be useful at times. Temporarily support the old class name with a warning about future deprecation. Signed-off-by: Denys Dmytriyenko --- v2 - support old name for a while with a deprecation warning meta/classes/distro_features_check.bbclass | 35 ++-- ...atures_check.bbclass => features_check.bbclass} | 65 -- meta/conf/documentation.conf | 4 +- meta/recipes-bsp/usbutils/usbutils_012.bb | 2 +- meta/recipes-connectivity/avahi/avahi-ui_0.7.bb| 2 +- meta/recipes-connectivity/bluez5/bluez5.inc| 2 +- .../connman/connman-gnome_0.7.bb | 2 +- meta/recipes-core/glib-2.0/glib.inc| 2 +- meta/recipes-core/glibc/glibc.inc | 2 +- meta/recipes-core/libxml/libxml2_2.9.9.bb | 2 +- .../packagegroups/packagegroup-self-hosted.bb | 2 +- meta/recipes-core/systemd/systemd-compat-units.bb | 2 +- meta/recipes-core/systemd/systemd-serialgetty.bb | 2 +- meta/recipes-core/systemd/systemd_243.bb | 2 +- meta/recipes-core/sysvinit/sysvinit_2.88dsf.bb | 2 +- meta/recipes-core/udev/eudev_3.2.8.bb | 2 +- meta/recipes-core/volatile-binds/volatile-binds.bb | 2 +- meta/recipes-devtools/mtools/mtools_4.0.23.bb | 2 +- .../systemd-bootchart/systemd-bootchart_233.bb | 2 +- meta/recipes-extended/pam/libpam_1.3.1.bb | 2 +- meta/recipes-extended/xdg-utils/xdg-utils_1.1.3.bb | 2 +- meta/recipes-gnome/epiphany/epiphany_3.34.1.bb | 2 +- meta/recipes-gnome/gcr/gcr_3.34.0.bb | 2 +- meta/recipes-gnome/gtk+/gtk+3.inc | 2 +- meta/recipes-gnome/libdazzle/libdazzle_3.34.1.bb | 2 +- meta/recipes-gnome/libnotify/libnotify_0.7.8.bb| 2 +- meta/recipes-graphics/clutter/clutter-1.0.inc | 2 +- meta/recipes-graphics/clutter/clutter-gst-3.0.inc | 2 +- meta/recipes-graphics/clutter/clutter-gtk-1.0.inc | 2 +- meta/recipes-graphics/cogl/cogl-1.0.inc| 2 +- meta/recipes-graphics/glew/glew_2.1.0.bb | 2 +- meta/recipes-graphics/images/core-image-weston.bb | 2 +- meta/recipes-graphics/images/core-image-x11.bb | 2 +- meta/recipes-graphics/kmscube/kmscube_git.bb | 2 +- meta/recipes-graphics/libepoxy/libepoxy_1.5.3.bb | 2 +- meta/recipes-graphics/libfakekey/libfakekey_git.bb | 2 +- .../libmatchbox/libmatchbox_1.12.bb| 2 +- meta/recipes-graphics/libva/libva-utils_2.5.0.bb | 2 +- meta/recipes-graphics/libva/libva_2.5.0.bb | 2 +- .../matchbox-wm/matchbox-wm_1.2.2.bb | 2 +- meta/recipes-graphics/mesa/libglu_9.0.1.bb | 2 +- meta/recipes-graphics/mesa/mesa-demos_8.4.0.bb | 2 +- meta/recipes-graphics/mesa/mesa.inc| 2 +- meta/recipes-graphics/mx/mx.inc| 2 +- .../packagegroups/packagegroup-core-clutter.bb | 2 +- .../packagegroups/packagegroup-core-x11-base.bb| 2 +- .../packagegroups/packagegroup-core-x11-xserver.bb | 2 +- .../packagegroups/packagegroup-core-x11.bb | 2 +- meta/recipes-graphics/piglit/piglit_git.bb | 2 +- meta/recipes-graphics/pong-clock/pong-clock_1.0.bb | 2 +- .../startup-notification_0.12.bb | 2 +- .../virglrenderer/virglrenderer_0.8.0.bb | 2 +- meta/recipes-graphics/vulkan/vulkan-demos_git.bb | 2 +- .../vulkan/vulkan-loader_1.1.108.bb| 2 +- .../vulkan/vulkan-tools_1.1.108.bb | 2 +- meta/recipes-graphics/waffle/waffle_1.6.0.bb | 2 +- meta/recipes-graphics/wayland/weston-init.bb | 2 +- meta/recipes-graphics/wayland/weston_7.0.0.bb | 2 +- .../x11-common/xserver-nodm-init_3.0.bb| 2 +- .../xinput-calibrator/xinput-calibrator_git.bb | 2 +- meta/recipes-graphics/xorg-app/xorg-app-common.inc | 2 +- .../xorg-driver/xorg-driver-common.inc | 2 +- .../xorg-font/xorg-font-common.inc | 2 +- .../xorg-font/xorg-minimal-fonts.bb| 2 +- meta/recipes-graphics/xorg-lib/libxcb_1.13.1.bb| 2 +- meta/recipes-graphics/xorg-lib/xcb-util.inc| 2 +- meta/recipes-graphics/xorg-lib/xorg-lib-common.inc | 2 +- .../recipes-graphics/xorg-xserver/xserver-xorg.inc | 2 +- meta/recipes-graphics/xrestop/xrestop_0.4.bb | 2 +- .../gstreamer/gst-examples_1.16.0.bb | 2 +- .../gstreamer/gstreamer1.0-python_1.16.1.bb| 2 +- .../gstreamer/gstreamer1.0-vaapi_1.16.1.bb | 2 +- meta/recipes-sato/l3afpad/l3afpad_git.bb | 2 +- .../matchbox-config-gtk/matchbox-config-gtk_0.2.bb | 2 +- .../matchbox-desktop/matchbox-desktop_2.2.bb | 2 +- .../matchbox-keyboard/matchbox-keyboard_0.1.1.bb | 2 +-
