5789 2014-02-05 11:41:15 +0000 IPK Postinstalls spit out sed failures. 2014-03-03 22:49:08 +0000 1 1 7 Build System, Metadata & Runtime OE-Core core 1.6 All Multiple RESOLVED INVALID Medium normal 1.6 1 david.nystrom sgw jessica.zhang laurentiu.palcu meta.mr.watcher meta.watcher --- --- No (bug/feature does not impact docs) oldest_to_newest 40189 0 david.nystrom 2014-02-05 11:41:15 +0000 | sed: -e expression #1, char 41: unterminated address regex | sed: -e expression #1, char 42: unterminated address regex | sed: -e expression #1, char 41: unterminated address regex | sed: -e expression #1, char 42: unterminated address regex During do_rootfs, when running postinstalls(IPK) for core-image-minimal, these error reports from sed can be seen. 40190 1 david.nystrom 2014-02-05 11:42:21 +0000 These are seen when installing packagegroup-core-boot, I suspect its related to update-alternatives. 40549 2 sgw 2014-02-21 00:49:04 +0000 David, could you give some more details, and possibly double check if this is fixed, we recently refactored the packaging/rootfs generation, I just tried to build core-image-minimal with IPK, but did not see these errors, so I would like better information about a reproducer. 40784 3 david.nystrom 2014-02-28 08:35:02 +0000 Saul asked on IRC yesturday, and yes, I still see this on master. NOTE: Installing the following packages: opkg-collateral run-postinsts tcf-agent packagegroup-core-eclipse-debug dhcp-client packagegroup-core-boot opkg poky-feed-config-opkg NOTE: /media/sdb5/oel/build/tmp/sysroots/x86_64-linux/usr/bin/opkg-cl -f /media/sdb5/oel/build/tmp/work/p1025twr-oel-linux-gnuspe/core-image-minimal/1.0-r0/opkg.conf -o /media/sdb5/oel/build/tmp /work/p1025twr-oel-linux-gnuspe/core-image-minimal/1.0-r0/rootfs --force_postinstall --prefer-arch-to-version install opkg-collateral run-postinsts tcf-agent packagegroup-core-eclipse-debug dh cp-client packagegroup-core-boot opkg poky-feed-config-opkg sed: -e expression #1, char 41: unterminated address regex sed: -e expression #1, char 42: unterminated address regex sed: -e expression #1, char 41: unterminated address regex sed: -e expression #1, char 42: unterminated address regex Isolated the issue with rootfs-sandbox to busybox, when running update alternatives on mdev. update-alternatives: Linking /tmp/rootfs//bin/sh to /usr/lib/busybox/bin/sh update-alternatives: Linking /tmp/rootfs//sbin/fstrim to /usr/lib/busybox/sbin/fstrim update-alternatives: Linking /tmp/rootfs//sbin/mdev to /usr/lib/busybox/sbin/mdev sed: -e expression #1, char 41: unterminated address regex sed: -e expression #1, char 42: unterminated address regex <snip> update-alternatives: Linking /tmp/rootfs//sbin/fstrim to /usr/lib/busybox/sbin/fstrim update-alternatives: Linking /tmp/rootfs//sbin/mdev to /usr/lib/busybox/sbin/mdev sed: -e expression #1, char 41: unterminated address regex sed: -e expression #1, char 42: unterminated address regex Update alternatives seems to be run twice for all symlinks, Thus yeilding 4 sed errors where two are generated each run. 40788 4 david.nystrom 2014-02-28 10:14:42 +0000 Looking at the busybox postinstall it indeed runs update-alternatives twice for each binary. This calls for another bug. 40789 5 david.nystrom 2014-02-28 10:22:17 +0000 Found the issue: Garbage in the generated busybox postinstall $ cat var/lib/opkg/info/busybox.postinst | grep -C 3 mdev update-alternatives --install /bin/ash ash /usr/lib/busybox/bin/ash 50 update-alternatives --install /bin/sh sh /usr/lib/busybox/bin/sh 50 update-alternatives --install /sbin/fstrim fstrim /usr/lib/busybox/sbin/fstrim 50 update-alternatives --install /sbin/mdev mdev /usr/lib/busybox/sbin/mdev 50 update-alternatives --install /usr/bin/[ lbracket /usr/lib/busybox/usr/bin/[ 50 update-alternatives --install /usr/bin/[[ [[ /usr/lib/busybox/usr/bin/[[ 50 update-alternatives --install /usr/sbin/addgroup addgroup /usr/lib/busybox/usr/sbin/addgroup 50 -- update-alternatives --install /bin/ash ash /usr/lib/busybox/bin/ash 50 update-alternatives --install /bin/sh sh /usr/lib/busybox/bin/sh 50 update-alternatives --install /sbin/fstrim fstrim /usr/lib/busybox/sbin/fstrim 50 update-alternatives --install /sbin/mdev mdev /usr/lib/busybox/sbin/mdev 50 update-alternatives --install /usr/bin/[ lbracket /usr/lib/busybox/usr/bin/[ 50 update-alternatives --install /usr/bin/[[ [[ /usr/lib/busybox/usr/bin/[[ 50 update-alternatives --install /usr/sbin/addgroup addgroup /usr/lib/busybox/usr/sbin/addgroup 50 40792 6 david.nystrom 2014-02-28 10:28:08 +0000 $ cat etc/busybox.links.nosuid | grep -C 4 mdev /sbin/rmmod /bin/ash /bin/sh /sbin/fstrim /sbin/mdev /usr/bin/[ /usr/bin/[[ /usr/sbin/addgroup /usr/sbin/adduser links.nosuid is tainted. 40822 7 david.nystrom 2014-03-03 08:40:50 +0000 Stems from meta-selinux busybox bbappend it seems. The bug on oe-core can be closed. 40849 8 sgw 2014-03-03 22:49:08 +0000 David, thanks for following up on this, this is very helpful to know the the additional information that you were using mdev and meta-selinux. Your intitial description did not include that and I would have been chasing this issue. I am glad you could track it down, I will close this.