FutureMigrationGuide - Revision history

PaulEggleton at 21:32, 22 October 2019

2019-10-22T21:32:32Z

← Older revision		Revision as of 21:32, 22 October 2019
Line 24:		Line 24:
	* cve-check-tool: functionally replaced by cve-update-db recipe and cve-check class		* cve-check-tool: functionally replaced by cve-update-db recipe and cve-check class
	* eglinfo: no longer maintained. eglinfo from mesa-demos is an adequate and maintained alternative.		* eglinfo: no longer maintained. eglinfo from mesa-demos is an adequate and maintained alternative.
	* gcc-8.3: ~~remove~~ 8.3 ~~from zeus~~		* gcc-8.3: version 8.3 removed (replaced by 9.2)
	* gnome-themes-standard: only needed by gtk+ 2.x which has been removed.		* gnome-themes-standard: only needed by gtk+ 2.x which has been removed.
	* gtk+: GTK+ 2 is obsolete (replaced by gtk+3)		* gtk+: GTK+ 2 is obsolete (replaced by gtk+3)
Line 33:		Line 33:
	* libxx86dga: remove obsolete client libary		* libxx86dga: remove obsolete client libary
	* libxx86misc: remove this now redundant library		* libxx86misc: remove this now redundant library
	* linux-yocto: version 5.0 removed		* linux-yocto: version 5.0 removed (5.2 / 4.19 present)
	* lsbinitscripts: part of removed LSB support		* lsbinitscripts: part of removed LSB support
	* lsb: part of removed LSB support		* lsb: part of removed LSB support

PaulEggleton at 12:19, 16 October 2019

2019-10-16T12:19:53Z

← Older revision		Revision as of 12:19, 16 October 2019
Line 94:		Line 94:
	* In the base-files recipe, writing the hostname into /etc/hosts and /etc/hostname is now done within the main do_install function rather than do_install_basefilesissue, so that do_install_basefilesissue can be more easily overridden without having to duplicate the hostname functionality. If you have done the latter (e.g. in a base-files bbappend) then you should remove it from your customised do_install_basefilesissue function.		* In the base-files recipe, writing the hostname into /etc/hosts and /etc/hostname is now done within the main do_install function rather than do_install_basefilesissue, so that do_install_basefilesissue can be more easily overridden without having to duplicate the hostname functionality. If you have done the latter (e.g. in a base-files bbappend) then you should remove it from your customised do_install_basefilesissue function.
	* The wic --expand command-line option now uses commas to separate key:value pairs rather than hyphens, as was documented in the command-line help. Any scripts or commands where you use wic --expand with multiple key:value pairs will need to be updated.		* The wic --expand command-line option now uses commas to separate key:value pairs rather than hyphens, as was documented in the command-line help. Any scripts or commands where you use wic --expand with multiple key:value pairs will need to be updated.
	* UEFI image variable settings have been moved from various places to a central conf/image-uefi.conf. ~~This~~ should not influence any existing configuration as the meta/conf/image-uefi.conf in the core metadata sets defaults that can be overridden in the same manner as before. ~~<span style="color: red; font-weight:bold;">[needs clarification]</span>~~		* UEFI image variable settings have been moved from various places to a central conf/image-uefi.conf. However, this should not influence any existing configuration as the meta/conf/image-uefi.conf in the core metadata sets defaults that can be overridden in the same manner as before.
	* conf/distro/include/world-broken.inc has been removed - where we need to disable certain recipes when using the musl C library, individual recipes now have COMPATIBLE_HOST_libc-musl set with a comment explaining why.		* conf/distro/include/world-broken.inc has been removed - where we need to disable certain recipes when using the musl C library, individual recipes now have COMPATIBLE_HOST_libc-musl set with a comment explaining why.

PaulEggleton at 12:19, 16 October 2019

2019-10-16T12:19:04Z

← Older revision		Revision as of 12:19, 16 October 2019
Line 82:		Line 82:
	*:Either one of these will now trigger a warning by default. If you wish to disable this check, remove src-uri-bad from WARN_QA.		*:Either one of these will now trigger a warning by default. If you wish to disable this check, remove src-uri-bad from WARN_QA.
	* The file-rdeps runtime dependency check no longer expands RDEPENDS recursively as there is no mechanism to ensure they can be fully computed, and thus races sometimes resulted in errors showing up and sometimes not. Thus you may now see errors for missing runtime dependencies that were previously satisfied recursively e.g. package A contains a shell script starting with #!/bin/bash but has no dependency on bash, but depends on package B that does depend on bash. Add the missing dependency / dependencies to resolve the warning.		* The file-rdeps runtime dependency check no longer expands RDEPENDS recursively as there is no mechanism to ensure they can be fully computed, and thus races sometimes resulted in errors showing up and sometimes not. Thus you may now see errors for missing runtime dependencies that were previously satisfied recursively e.g. package A contains a shell script starting with #!/bin/bash but has no dependency on bash, but depends on package B that does depend on bash. Add the missing dependency / dependencies to resolve the warning.

	* Setting DEPENDS_${PN} anywhere (typically in a recipe) will now trigger an error - this is invalid, as DEPENDS is not a package-specific variable (unlike RDEPENDS). Set DEPENDS instead.		* Setting DEPENDS_${PN} anywhere (typically in a recipe) will now trigger an error - this is invalid, as DEPENDS is not a package-specific variable (unlike RDEPENDS). Set DEPENDS instead.
	* systemd is currently known not to work well with the musl C library as upstream only officially supports linking it with glibc. Thus, a warning will now be shown when building systemd in conjunction with musl.		* systemd is currently known not to work well with the musl C library as upstream only officially supports linking it with glibc. Thus, a warning will now be shown when building systemd in conjunction with musl.

PaulEggleton at 12:18, 16 October 2019

2019-10-16T12:18:51Z

← Older revision		Revision as of 12:18, 16 October 2019
Line 74:		Line 74:
	* The arguments passed to functions used with BB_HASHCHECK_FUNCTION have changed. If you are using own custom hash check function, see http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=40a5e193c4ba45c928fccd899415ea56b5417725 for details.		* The arguments passed to functions used with BB_HASHCHECK_FUNCTION have changed. If you are using own custom hash check function, see http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=40a5e193c4ba45c928fccd899415ea56b5417725 for details.
	* Task specifications in BB_TASKDEPDATA and class implementations used in signature generator classes now use "<fn>:<task>" everywhere rather than the "." delimiter that was being used in some places. This makes it consistent with everywhere else in the code. Custom signature generator classes and code that reads BB_TASKDEPDATA will need to be updated to use ':' as a separator rather than '.'.		* Task specifications in BB_TASKDEPDATA and class implementations used in signature generator classes now use "<fn>:<task>" everywhere rather than the "." delimiter that was being used in some places. This makes it consistent with everywhere else in the code. Custom signature generator classes and code that reads BB_TASKDEPDATA will need to be updated to use ':' as a separator rather than '.'.

	~~== Package runtime dependencies no longer recursive ==~~

	RDEPENDS are no longer automatically expanded recursively when packaging, as there is no mechanism to ensure they were fully computed and thus races were observed. When setting RDEPENDS explicitly in a recipe, you will need to ensure the runtime dependencies are fully specified. <span style="color: red; font-weight:bold;">[needs clarification]</span>

	== Sanity checks ==		== Sanity checks ==
Line 85:		Line 81:
	*# github archive tarballs - these are not guaranteed to be stable and thus it is likely that they will be refreshed and thus the SRC_URI checksums will fail to apply. It is recommended that you fetch either an official release tarball or a specific revision from the actual git repository instead.		*# github archive tarballs - these are not guaranteed to be stable and thus it is likely that they will be refreshed and thus the SRC_URI checksums will fail to apply. It is recommended that you fetch either an official release tarball or a specific revision from the actual git repository instead.
	*:Either one of these will now trigger a warning by default. If you wish to disable this check, remove src-uri-bad from WARN_QA.		*:Either one of these will now trigger a warning by default. If you wish to disable this check, remove src-uri-bad from WARN_QA.
			* The file-rdeps runtime dependency check no longer expands RDEPENDS recursively as there is no mechanism to ensure they can be fully computed, and thus races sometimes resulted in errors showing up and sometimes not. Thus you may now see errors for missing runtime dependencies that were previously satisfied recursively e.g. package A contains a shell script starting with #!/bin/bash but has no dependency on bash, but depends on package B that does depend on bash. Add the missing dependency / dependencies to resolve the warning.

	* Setting DEPENDS_${PN} anywhere (typically in a recipe) will now trigger an error - this is invalid, as DEPENDS is not a package-specific variable (unlike RDEPENDS). Set DEPENDS instead.		* Setting DEPENDS_${PN} anywhere (typically in a recipe) will now trigger an error - this is invalid, as DEPENDS is not a package-specific variable (unlike RDEPENDS). Set DEPENDS instead.
	* systemd is currently known not to work well with the musl C library as upstream only officially supports linking it with glibc. Thus, a warning will now be shown when building systemd in conjunction with musl.		* systemd is currently known not to work well with the musl C library as upstream only officially supports linking it with glibc. Thus, a warning will now be shown when building systemd in conjunction with musl.

PaulEggleton at 04:42, 16 October 2019

2019-10-16T04:42:25Z

← Older revision		Revision as of 04:42, 16 October 2019
Line 58:		Line 58:
	== CVE checking ==		== CVE checking ==

	cve-check-tool has been functionally replaced by a new cve-update-db recipe and functionality built into the cve-check class. The result uses NVD JSON data feeds rather than the deprecated XML feeds that cve-check-tool was using, supports CVSSv3 and makes other improvements.		cve-check-tool has been functionally replaced by a new cve-update-db recipe and functionality built into the cve-check class. The result uses NVD JSON data feeds rather than the deprecated XML feeds that cve-check-tool was using, supports CVSSv3 scoring and makes other improvements.

	Additionally, the CVE_CHECK_CVE_WHITELIST variable has been replaced by CVE_CHECK_WHITELIST.		Additionally, the CVE_CHECK_CVE_WHITELIST variable has been replaced by CVE_CHECK_WHITELIST.

PaulEggleton: Add world-broken.inc

2019-10-16T03:49:49Z

Add world-broken.inc

← Older revision		Revision as of 03:49, 16 October 2019
Line 98:		Line 98:
	* The wic --expand command-line option now uses commas to separate key:value pairs rather than hyphens, as was documented in the command-line help. Any scripts or commands where you use wic --expand with multiple key:value pairs will need to be updated.		* The wic --expand command-line option now uses commas to separate key:value pairs rather than hyphens, as was documented in the command-line help. Any scripts or commands where you use wic --expand with multiple key:value pairs will need to be updated.
	* UEFI image variable settings have been moved from various places to a central conf/image-uefi.conf. This should not influence any existing configuration as the meta/conf/image-uefi.conf in the core metadata sets defaults that can be overridden in the same manner as before. <span style="color: red; font-weight:bold;">[needs clarification]</span>		* UEFI image variable settings have been moved from various places to a central conf/image-uefi.conf. This should not influence any existing configuration as the meta/conf/image-uefi.conf in the core metadata sets defaults that can be overridden in the same manner as before. <span style="color: red; font-weight:bold;">[needs clarification]</span>
			* conf/distro/include/world-broken.inc has been removed - where we need to disable certain recipes when using the musl C library, individual recipes now have COMPATIBLE_HOST_libc-musl set with a comment explaining why.

PaulEggleton at 02:39, 16 October 2019

2019-10-16T02:39:32Z

← Older revision		Revision as of 02:39, 16 October 2019
Line 77:		Line 77:
	== Package runtime dependencies no longer recursive ==		== Package runtime dependencies no longer recursive ==

	RDEPENDS are no longer automatically expanded recursively when packaging, as there is no mechanism to ensure they were fully computed and thus races were observed. When setting RDEPENDS explicitly in a recipe, you will need to ensure the runtime dependencies are fully specified.<span style="color: red; font-weight:bold;">~~Needs~~ clarification</span>		RDEPENDS are no longer automatically expanded recursively when packaging, as there is no mechanism to ensure they were fully computed and thus races were observed. When setting RDEPENDS explicitly in a recipe, you will need to ensure the runtime dependencies are fully specified. <span style="color: red; font-weight:bold;">[needs clarification]</span>

	== Sanity checks ==		== Sanity checks ==
Line 97:		Line 97:
	* In the base-files recipe, writing the hostname into /etc/hosts and /etc/hostname is now done within the main do_install function rather than do_install_basefilesissue, so that do_install_basefilesissue can be more easily overridden without having to duplicate the hostname functionality. If you have done the latter (e.g. in a base-files bbappend) then you should remove it from your customised do_install_basefilesissue function.		* In the base-files recipe, writing the hostname into /etc/hosts and /etc/hostname is now done within the main do_install function rather than do_install_basefilesissue, so that do_install_basefilesissue can be more easily overridden without having to duplicate the hostname functionality. If you have done the latter (e.g. in a base-files bbappend) then you should remove it from your customised do_install_basefilesissue function.
	* The wic --expand command-line option now uses commas to separate key:value pairs rather than hyphens, as was documented in the command-line help. Any scripts or commands where you use wic --expand with multiple key:value pairs will need to be updated.		* The wic --expand command-line option now uses commas to separate key:value pairs rather than hyphens, as was documented in the command-line help. Any scripts or commands where you use wic --expand with multiple key:value pairs will need to be updated.
	* UEFI image variable settings have been moved from various places to a central conf/image-uefi.conf. This should not influence any existing configuration as the meta/conf/image-uefi.conf in the core metadata sets defaults that can be overridden in the same manner as before.<span style="color: red; font-weight:bold;">~~Needs~~ clarification</span>		* UEFI image variable settings have been moved from various places to a central conf/image-uefi.conf. This should not influence any existing configuration as the meta/conf/image-uefi.conf in the core metadata sets defaults that can be overridden in the same manner as before. <span style="color: red; font-weight:bold;">[needs clarification]</span>

PaulEggleton at 02:38, 16 October 2019

2019-10-16T02:38:59Z

← Older revision		Revision as of 02:38, 16 October 2019
Line 77:		Line 77:
	== Package runtime dependencies no longer recursive ==		== Package runtime dependencies no longer recursive ==

	RDEPENDS are no longer automatically expanded recursively when packaging, as there is no mechanism to ensure they were fully computed and thus races were observed. When setting RDEPENDS explicitly in a recipe, you will need to ensure the runtime dependencies are fully specified.~~{{font~~ color\|red\|Needs clarification}}		RDEPENDS are no longer automatically expanded recursively when packaging, as there is no mechanism to ensure they were fully computed and thus races were observed. When setting RDEPENDS explicitly in a recipe, you will need to ensure the runtime dependencies are fully specified.<span style="color: red; font-weight:bold;">Needs clarification</span>

	== Sanity checks ==		== Sanity checks ==
Line 97:		Line 97:
	* In the base-files recipe, writing the hostname into /etc/hosts and /etc/hostname is now done within the main do_install function rather than do_install_basefilesissue, so that do_install_basefilesissue can be more easily overridden without having to duplicate the hostname functionality. If you have done the latter (e.g. in a base-files bbappend) then you should remove it from your customised do_install_basefilesissue function.		* In the base-files recipe, writing the hostname into /etc/hosts and /etc/hostname is now done within the main do_install function rather than do_install_basefilesissue, so that do_install_basefilesissue can be more easily overridden without having to duplicate the hostname functionality. If you have done the latter (e.g. in a base-files bbappend) then you should remove it from your customised do_install_basefilesissue function.
	* The wic --expand command-line option now uses commas to separate key:value pairs rather than hyphens, as was documented in the command-line help. Any scripts or commands where you use wic --expand with multiple key:value pairs will need to be updated.		* The wic --expand command-line option now uses commas to separate key:value pairs rather than hyphens, as was documented in the command-line help. Any scripts or commands where you use wic --expand with multiple key:value pairs will need to be updated.
	* UEFI image variable settings have been moved from various places to a central conf/image-uefi.conf. This should not influence any existing configuration as the meta/conf/image-uefi.conf in the core metadata sets defaults that can be overridden in the same manner as before.~~{{font~~ color\|red\|Needs clarification}}		* UEFI image variable settings have been moved from various places to a central conf/image-uefi.conf. This should not influence any existing configuration as the meta/conf/image-uefi.conf in the core metadata sets defaults that can be overridden in the same manner as before.<span style="color: red; font-weight:bold;">Needs clarification</span>

PaulEggleton at 02:37, 16 October 2019

2019-10-16T02:37:31Z

← Older revision		Revision as of 02:37, 16 October 2019
Line 77:		Line 77:
	== Package runtime dependencies no longer recursive ==		== Package runtime dependencies no longer recursive ==

	RDEPENDS are no longer automatically expanded recursively when packaging, as there is no mechanism to ensure they were fully computed and thus races were observed. When setting RDEPENDS explicitly in a recipe, you will need to ensure the runtime dependencies are fully specified.		RDEPENDS are no longer automatically expanded recursively when packaging, as there is no mechanism to ensure they were fully computed and thus races were observed. When setting RDEPENDS explicitly in a recipe, you will need to ensure the runtime dependencies are fully specified.{{font color\|red\|Needs clarification}}

	== Sanity checks ==		== Sanity checks ==
Line 97:		Line 97:
	* In the base-files recipe, writing the hostname into /etc/hosts and /etc/hostname is now done within the main do_install function rather than do_install_basefilesissue, so that do_install_basefilesissue can be more easily overridden without having to duplicate the hostname functionality. If you have done the latter (e.g. in a base-files bbappend) then you should remove it from your customised do_install_basefilesissue function.		* In the base-files recipe, writing the hostname into /etc/hosts and /etc/hostname is now done within the main do_install function rather than do_install_basefilesissue, so that do_install_basefilesissue can be more easily overridden without having to duplicate the hostname functionality. If you have done the latter (e.g. in a base-files bbappend) then you should remove it from your customised do_install_basefilesissue function.
	* The wic --expand command-line option now uses commas to separate key:value pairs rather than hyphens, as was documented in the command-line help. Any scripts or commands where you use wic --expand with multiple key:value pairs will need to be updated.		* The wic --expand command-line option now uses commas to separate key:value pairs rather than hyphens, as was documented in the command-line help. Any scripts or commands where you use wic --expand with multiple key:value pairs will need to be updated.
	* UEFI image variable settings have been moved from various places to a central conf/image-uefi.conf. This should not influence any existing configuration as the meta/conf/image-uefi.conf in the core metadata sets defaults that can be overridden in the same manner as before.		* UEFI image variable settings have been moved from various places to a central conf/image-uefi.conf. This should not influence any existing configuration as the meta/conf/image-uefi.conf in the core metadata sets defaults that can be overridden in the same manner as before.{{font color\|red\|Needs clarification}}

PaulEggleton at 02:22, 16 October 2019

2019-10-16T02:22:52Z

← Older revision		Revision as of 02:22, 16 October 2019
Line 16:		Line 16:

	Following on from this change, the poky-lsb derivative distribution configuration that was also used for testing alternative configurations has been replaced with a poky-altcfg distribution that has LSB parts removed.		Following on from this change, the poky-lsb derivative distribution configuration that was also used for testing alternative configurations has been replaced with a poky-altcfg distribution that has LSB parts removed.

	~~== CVE checking ==~~

	cve-check-tool has been functionally replaced by a new cve-update-db recipe and functionality built into the cve-check class. The result uses NVD JSON data feeds rather than the deprecated XML feeds that cve-check-tool was using, supports CVSSv3 and makes other improvements.

	~~Additionally, the CVE_CHECK_CVE_WHITELIST variable has been replaced by CVE_CHECK_WHITELIST.~~


	== Removed recipes ==		== Removed recipes ==
Line 62:		Line 55:
	* distcc now provides separate distcc-client and distcc-server packages as typically one or the other are needed, rather than both.		* distcc now provides separate distcc-client and distcc-server packages as typically one or the other are needed, rather than both.
	* python*-setuptools recipes now separately package the pkg_resources module in a python-pkg-resources / python3-pkg-resources package as the module is useful independent of the rest of the setuptools package. The main python-setuptools / python3-setuptools package depends on this new package so you should only need to update dependencies unless you want to take advantage of the increased granularity.		* python*-setuptools recipes now separately package the pkg_resources module in a python-pkg-resources / python3-pkg-resources package as the module is useful independent of the rest of the setuptools package. The main python-setuptools / python3-setuptools package depends on this new package so you should only need to update dependencies unless you want to take advantage of the increased granularity.

			== CVE checking ==

			cve-check-tool has been functionally replaced by a new cve-update-db recipe and functionality built into the cve-check class. The result uses NVD JSON data feeds rather than the deprecated XML feeds that cve-check-tool was using, supports CVSSv3 and makes other improvements.

			Additionally, the CVE_CHECK_CVE_WHITELIST variable has been replaced by CVE_CHECK_WHITELIST.

	== Bitbake changes ==		== Bitbake changes ==