| Summary: | Please place them into pkg_postinst_ontarget_${PN} () | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] OE-Core | Reporter: | Robert Berger <pokylinux> |
| Component: | core | Assignee: | Robert Berger <pokylinux> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Medium | CC: | alex.kanavin, meta.mr.watcher, meta.watcher, randy.macleod |
| Version: | 2.5.1 | ||
| Target Milestone: | 2.6 M2 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | Don't know | |
boot log on first boot: Configuring packages on first boot.... (This may take several minutes. Please do not power off the machine.) Running postinst /etc/ipk-postinsts/000-sysvinit-inittab... update-rc.d: /etc/init.d/run-postinsts exists during rc.d purge (continuing) Removing any system startup links for run-postinsts ... /etc/rcS.d/S99run-postinsts INIT: Entering runlevel: 3 I'm certain that this patch should simply be backported: http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=524e84028eccf8b2077f356efa96aba897e3e183 Robert, can you confirm that it fixes the issue and if so, send the backport to the oe-core list please? It looks like the patch made it into oe-core sumo-next[1] [1] http://cgit.openembedded.org/openembedded-core/commit/?h=sumo-next&id=f9f045ce9cbd441375f15911f3535cb1e304ba5b So I am not sure where to backport it to. I added it to my local copy of poky and will test it locally. It looks like the patch made it into oe-core sumo-next[1] [1] http://cgit.openembedded.org/openembedded-core/commit/?h=sumo-next&id=f9f045ce9cbd441375f15911f3535cb1e304ba5b and my local tests look good |
I see this in my build logs: WARNING: custom-packagegroup-image-1.0-r0 do_rootfs: sysvinit-inittab.postinst returned 1, marking as unpacked only, configuration required on target. WARNING: custom-packagegroup-image-1.0-r0 do_rootfs: Intentionally failing postinstall scriptlets of ['sysvinit-inittab'] to defer them to first boot is deprecated. Please place them into pkg_postinst_ontarget_${PN} (). If deferring to first boot wasn't the intent, then scriptlet failure may mean an issue in the recipe, or a regression elsewhere. Details of the failure are in /tmp/yocto-autobuilder/yocto-autobuilder/yocto-worker/res-custom-sumo-multi-v7-core-image-minimal/build/build/tmp/work/multi_v7_ml-poky-linux-gnueabi/custom-packagegroup-image/1.0-r0/temp/log.do_rootfs. WARNING: custom-packagegroup-image-1.0-r0 do_rootfs: sysvinit-inittab.postinst returned 1, marking as unpacked only, configuration required on target. WARNING: custom-packagegroup-image-1.0-r0 do_rootfs: Intentionally failing postinstall scriptlets of ['sysvinit-inittab'] to defer them to first boot is deprecated. Please place them into pkg_postinst_ontarget_${PN} (). If deferring to first boot wasn't the intent, then scriptlet failure may mean an issue in the recipe, or a regression elsewhere. Details of the failure are in /tmp/yocto-autobuilder/yocto-autobuilder/yocto-worker/res-custom-sumo-multi-v7-core-image-minimal/build/build/tmp/work/multi_v7_ml-poky-linux-gnueabi/custom-packagegroup-image/1.0-r0/temp/log.do_rootfs. WARNING: custom-packagegroup-image-1.0-r0 do_rootfs: [log_check] custom-packagegroup-image: found 2 warning messages in the logfile: [log_check] WARNING: Intentionally failing postinstall scriptlets of ['sysvinit-inittab'] to defer them to first boot is deprecated. Please place them into pkg_postinst_ontarget_${PN} (). [log_check] WARNING: Intentionally failing postinstall scriptlets of ['sysvinit-inittab'] to defer them to first boot is deprecated. Please place them into pkg_postinst_ontarget_${PN} (). since I don't do anything special about sysvinit except for this bbappend # use runlevel 3 instead of 5 and # replace funny /bin/getty script with /sbin/getty do_install_append() { sed -i 's/^id:5:initdefault/id:3:initdefault/' ${D}${sysconfdir}/inittab } I am not sure if it's me who caused this.