[poky] Collected errors when upgrading target device from poky/dylan to poky/dizzy

Bryan Evenson bevenson at melinkcorp.com
Fri Apr 10 11:42:55 PDT 2015


I am on poky/dizzy 1.7.1 for my development system after having recently upgrade from poky/dylan 1.4.4.  I have a custom image that is basically core-image-minimal with the extra packages we need for our system (proprietary packages and a few dependencies).  I am using sysvinit for init and opkg for package management.  If I burn the poky/dizzy derived image on a target device, everything works just fine.  However, if I try to upgrade a device there are a few errors that I can't figure out how to work around.  I'm wondering if someone else has seen similar issues and have a workaround.

* There is an issue with upgrading base-files in that /run and /var/run become softlinks to each other.  I have the start to a workaround posted here: http://lists.openembedded.org/pipermail/openembedded-core/2015-April/103600.html.  It looked to be working for me, but it is still not cleanly adjusting the directories as needed.  The temporary directories are not being removed completely and after a couple reboots there is the softlink run-> /var/run inside of /run.  Any suggestions on improving this would be appreciated.

* The "reboot" command does not immediately work after the upgrade.  My system is using "reboot" from Busybox.  I need to issue "reboot -f" to reboot the system.

* opkg does not report any errors on the upgrade, but it does not record that the packages were upgraded.  If I issue "opkg list-installed" immediately after the upgrade, the old packages are listed.  But, as far as I can tell all the new packages have been installed.  After forcing a reboot, I can issue "opkg upgrade" again and it will re-install all the packages it had just installed.  This time opkg records that the packages have been installed.

* On the second pass of package installation, udev and util-linux are failing upgrade.  Here are the errors that I am seeing from opkg:

    Configuring util-linux-readprofile.
    update-alternatives: Error: not linking //sbin/readprofile to /sbin/readprofile.util-linux since //sbin/readprofile exists and is not a link
    Collected errors:
     * check_data_file_clashes: Package udev wants to install file /usr/bin/udevadm
            But that file is already provided by package  * udev-utils
     * check_data_file_clashes: Package util-linux wants to install file /usr/bin/lastb
            But that file is already provided by package  * sysvinit
     * pkg_run_script: package "util-linux-readprofile" postinst script returned status 1.
     * opkg_configure: util-linux-readprofile.postinst returned 1.

>From looking at the package file lists, I don't see why the data file clashes are happening.  After the repeated upgrade everything appears to be functioning okay but I'd like to clean up these errors.  Has anyone else seen anything like this happen?  Any suggestions?

Regards,
Bryan


More information about the poky mailing list