linux/poky.git/meta/recipes-devtools/opkg, branch uninative-2.6

opkg: fix ptest packaging when OPKGLIBDIR == libdir

2019-05-03T05:11:57+00:00

there is small issue with ptest packaging in cases where OPKGLIBDIR is set to /usr/lib. Then all ptest files get packaged in libopkg instead of opkg-ptest and correct QA error is triggered: ERROR: QA Issue: /usr/lib/opkg/ptest/tests/opkgcl.py contained in package libopkg requires /usr/bin/python3, but no providers found in RDEPENDS_libopkg? [file-rdeps] # $FILES_libopkg # set /jenkins/mjansa/build-webos-master/oe-core/meta/recipes-devtools/opkg/opkg_0.4.0.bb:62 # "${libdir}/*.so.* ${OPKGLIBDIR}/opkg/" FILES_libopkg="/usr/lib/*.so.* /usr/lib/opkg/" # $FILES_opkg-ptest [2 operations] # set /jenkins/mjansa/build-webos-master/oe-core/meta/classes/ptest.bbclass:9 # "${PTEST_PATH}" # rename from FILES_${PN}-ptest data.py:117 [expandKeys] # "${PTEST_PATH}" # pre-expansion value: # "${PTEST_PATH}" FILES_opkg-ptest="/usr/lib/opkg/ptest" # $PACKAGES [4 operations] # set /jenkins/mjansa/build-webos-master/oe-core/meta/conf/bitbake.conf:292 # "${PN}-src ${PN}-dbg ${PN}-staticdev ${PN}-dev ${PN}-doc ${PN}-locale ${PACKAGE_BEFORE_PN} ${PN}" # set /jenkins/mjansa/build-webos-master/oe-core/meta/conf/documentation.conf:314 # [doc] "The list of packages to be created from the recipe." # prepend /jenkins/mjansa/build-webos-master/oe-core/meta/classes/ptest.bbclass:20 # "${@bb.utils.contains('PTEST_ENABLED', '1', '${PN}-ptest', '', d)}" # prepend /jenkins/mjansa/build-webos-master/oe-core/meta/recipes-devtools/opkg/opkg_0.4.0.bb:60 # "libopkg" # pre-expansion value: # "libopkg ${@bb.utils.contains('PTEST_ENABLED', '1', '${PN}-ptest', '', d)} ${PN}-src ${PN}-dbg ${PN}-staticdev ${PN}-dev ${PN}-doc ${PN}-locale ${PACKAGE_BEFORE_PN} ${PN}" PACKAGES="libopkg opkg-ptest opkg-src opkg-dbg opkg-staticdev opkg-dev opkg-doc opkg-locale opkg" The easiest fix should be to reorder PACKAGES (the _prepends) so that ${PN}-ptest is prepended later -> ends before libopkg). (From OE-Core rev: e329f1a9ad7e68575912345ec7c18c12f5971998) Signed-off-by: Martin Jansa Signed-off-by: Richard Purdie

opkg: add ptest

2019-04-12T08:29:06+00:00

Install opkg test suite and run it as ptest. (From OE-Core rev: 6b9963a58eec9f5f5fe72021d13e3c89461a9649) Signed-off-by: Alejandro del Castillo Signed-off-by: Richard Purdie

opkg: add --ignore-recommends flag

2019-02-08T10:57:19+00:00

To be used for BAD_RECOMMENDATIONS feature. (From OE-Core rev: 788d97b4f8e4452cef1ba6bb3e565e1b52dbb7de) Signed-off-by: Alejandro del Castillo Signed-off-by: Richard Purdie

opkg: upgrade to version 0.4.0

2018-12-27T22:52:58+00:00

- Drop 0001-remove_maintainer_scripts-use-strict-matching.patch (From OE-Core rev: 74d3b4a199bfeae99dfbe6f23f1c3cb4bf76abff) Signed-off-by: Alejandro del Castillo Signed-off-by: Richard Purdie

opkg: add strict package matching on removal patch

2018-09-06T09:36:31+00:00

During removal, opkg is using globs to select which metadata files to remove. The glob is too broad and sometimes can result in a package removing the metadata from a package with a close name. Make the matching more strict. Fixes bugzilla 12905 (From OE-Core rev: 715180e41884393d4f2f234dd557df61a21c4745) Signed-off-by: Alejandro del Castillo Signed-off-by: Richard Purdie

opkg-keyrings: do not use 'exit 1' to postpone to first boot

2018-09-06T09:36:31+00:00

Since `229f4e9 package.bbclass: add support for pkg_postinst_ontarget()' applied in oe-core, use pkg_postinst_ontarget to run postinst at first boot. (From OE-Core rev: a6e62aae8f83696755828631e5ff67a579a6462f) Signed-off-by: Hongxu Jia Signed-off-by: Richard Purdie

opkg: avoid running postinst scripts twice when using systemd

2018-06-18T10:07:58+00:00

OpenEmbedded has a built-in mechanism to run postinst scripts offline at build time or, if necessary, on first boot (delayed execution). If the latter is the case and systemd is in use, two services end up doing the same thing: - opkg-configure.service starts "opkg configure" directly. - run-postinsts.service starts "/usr/sbin/run-postinsts" which runs postinst scripts stored in /etc/ipk-postinsts/ or "opkg configure" if package management is installed. Since the run-postinsts.service is also used in cases where no package management is in use, it is the primary means of handling postinsts. Get rid of the opkg-configure.service to avoid duplicate opkg configure execution. (From OE-Core rev: 23dcf7ea3af84721fac126a2b2f0f100f7266368) Signed-off-by: Stefan Agner Signed-off-by: Richard Purdie

opkg: upgrade to version 0.3.6

2018-03-04T11:35:40+00:00

0.3.5 -> 0.3.6 (From OE-Core rev: 151094f603ad817a5106360d1f51656fbe271121) Signed-off-by: Alejandro del Castillo Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

opkg-arch-config: Add HOMEPAGE info into recipe file.

2017-09-21T08:05:50+00:00

(From OE-Core rev: 9caebefd5a64e18f6f8830426461824a9b7d8105) Signed-off-by: Huang Qiyu Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

opkg-configure: do not reload daemon configuration

2017-08-15T23:03:14+00:00

In case a systemd service disables itself while init is still in its boot sequence the reloading of the service files can be problematic. In that case: It seems that systemd looses the state of .device units, and some services depend on such units (namely serial consoles such as serial-getty@ttymxc0.service). As a result no getty is spawned on the affected serial tty. After a power-cycle the second boot (which does not disable services) succeeds. The following sequence shows this problem: | Jan 09 16:36:28 apalis-t30 systemctl[162]: Removed /etc/systemd/system/sysinit.target.wants/run-postinsts.service. | Jan 09 16:36:28 apalis-t30 systemd[1]: Reloading. | ... | And then the failing one: | Feb 22 15:33:15 apalis-t30 systemd[1]: dev-ttyS0.device: Job dev-ttyS0.device/start timed out. | Feb 22 15:33:15 apalis-t30 systemd[1]: Timed out waiting for device dev-ttyS0.device. | Feb 22 15:33:15 apalis-t30 systemd[1]: Dependency failed for Serial Getty on ttyS0. | Feb 22 15:33:15 apalis-t30 systemd[1]: serial-getty@ttyS0.service: Job serial-getty@ttyS0.service/start failed with result 'dependency'. | Feb 22 15:33:15 apalis-t30 systemd[1]: dev-ttyS0.device: Job dev-ttyS0.device/start failed with result 'timeout'. | Feb 22 15:33:15 apalis-t30 systemd[1]: Reached target Login Prompts. (the time has been updated between this two events, but that does not influence the issue) Using --no-reload in the service file avoids the "Reloading." message above and seems to not cause such issues anymore. Reported-by: Stefan Agner (From OE-Core rev: 059bc9b164d239f0ba319f8e6a54b5edf7761b22) Signed-off-by: Max Krummenacher (cherry picked from commit 16b7b455ee40fd1be5bb9aacf24b106df0d9325e) Signed-off-by: Richard Purdie