path: root/meta/recipes-devtools/opkg-utils
diff options
authorNiko Mauno <>2018-11-12 19:30:08 +0200
committerRichard Purdie <>2018-11-13 15:18:28 +0000
commitf0912e23629758fe4303284e7db8f4089bb7b4cb (patch)
treeff6db529bfa6eab9328373e042341cbe76448441 /meta/recipes-devtools/opkg-utils
parentbd4f8d12fe1f9f2643ee9e68fa2bb981134294fb (diff)
opkg-utils: Fix update-alternatives link relocation
Recently Debian-style support for link relocation was added to 'update-alternatives' script, but it fails under circumstances where host rootfs root directory differs from target rootfs root directory and two alternative packages provide a symbolic link with source located in different directories. An example of the case is busybox provided /bin/rev (symlinking to /bin/busybox.nosuid) and util-linux provided /usr/bin/rev (symlinking to /usr/bin/rev.util-linux) in which case following failure occurs during image recipe's do_rootfs() task: ERROR: core-image-minimal-1.0-r0 do_rootfs: Postinstall scriptlets of ['util-linux'] have failed. If the intention is to defer them to first boot, then please place them into pkg_postinst_ontarget_${PN} (). Deferring to first boot via 'exit 1' is no longer supported. Details of the failure are in .../tmp/work/qemux86-poky-linux/core-image-minimal/1.0-r0/temp/log.do_rootfs. ERROR: core-image-minimal-1.0-r0 do_rootfs: Function failed: do_rootfs Looking in log.do_rootfs file, following relevant lines can be observed: update-alternatives: renaming rev link from /bin/rev to /usr/bin/rev mv: cannot stat '/bin/rev': No such file or directory Mitigate issue by applying patch which adds target root filesystem root directory path prefix to failing 'mv' calls relevant variable references Signed-off-by: Niko Mauno <> Signed-off-by: Richard Purdie <>
Diffstat (limited to 'meta/recipes-devtools/opkg-utils')
2 files changed, 41 insertions, 0 deletions
diff --git a/meta/recipes-devtools/opkg-utils/opkg-utils/0001-update-alternatives-Fix-link-relocation-support.patch b/meta/recipes-devtools/opkg-utils/opkg-utils/0001-update-alternatives-Fix-link-relocation-support.patch
new file mode 100644
index 0000000000..9dc488b7aa
--- /dev/null
+++ b/meta/recipes-devtools/opkg-utils/opkg-utils/0001-update-alternatives-Fix-link-relocation-support.patch
@@ -0,0 +1,40 @@
+From 18562ccae6996431d37767653b061d4e9e1b9424 Mon Sep 17 00:00:00 2001
+From: Niko Mauno <>
+Date: Sun, 11 Nov 2018 15:50:22 +0200
+Subject: [opkg-utils PATCH] update-alternatives: Fix link relocation support
+Commit fcb26339000021eb9bb711aa264247aebcfdd4ae which added Debian-style
+support for link relocation tries to relocate symbolic link on host OS,
+resulting in following-like error when two alternative packages have
+symbolic link source located in different directories (/bin/rev ->
+/bin/busybox.nosuid and /usr/bin/rev -> /usr/bin/rev.util-linux):
+ update-alternatives: renaming rev link from /bin/rev to /usr/bin/rev
+ mv: cannot stat '/bin/rev': No such file or directory
+Fix the issue by prefixing 'olink' and 'link' variable references with
+path to targeted root filesystem's root directory.
+Upstream-Status: Submitted [opkg-utils]
+Signed-off-by: Niko Mauno <>
+ update-alternatives | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+diff --git a/update-alternatives b/update-alternatives
+index 89a440b..d4fa7eb 100644
+--- a/update-alternatives
++++ b/update-alternatives
+@@ -58,7 +58,7 @@ register_alt() {
+ local link_str=`echo $link | protect_slashes`
+ sed -e "1s/.*/$link_str/" $ad/$name > $ad/$
+ mv $ad/$ $ad/$name
+- mv $olink $link
+ fi
+ else
+ echo "$link" > "$ad/$name"
diff --git a/meta/recipes-devtools/opkg-utils/ b/meta/recipes-devtools/opkg-utils/
index cb3775d9c9..4c41774c39 100644
--- a/meta/recipes-devtools/opkg-utils/
+++ b/meta/recipes-devtools/opkg-utils/
@@ -13,6 +13,7 @@ SRC_URI = "${BPN}/snapshot/${BPN}-${PV
file://0002-opkg-build-Use-local-time-for-build_date-since-opkg-.patch \
file://threaded-xz.patch \
file://pigz.patch \
+ file://0001-update-alternatives-Fix-link-relocation-support.patch \
SRC_URI_append_class-native = " file://tar_ignore_error.patch"