After opkg upgrade and loading the new kernel image I get the following:
beaglebone:~# uname -a
Linux beaglebone 3.2.13 #1 Sun Apr 1 12:50:41 CEST 2012 armv7l GNU/Linux
beaglebone:~# opkg install something-that-doesnt-exist
Unknown package ‘something-that-doesnt-exist’.
Configuring procps.
update-alternatives: Linking //usr/bin/top to /usr/bin/top.procps
update-alternatives: Linking //usr/bin/uptime to /usr/bin/uptime.procps
update-alternatives: Linking //usr/bin/free to /usr/bin/free.procps
update-alternatives: Linking //usr/bin/pkill to /usr/bin/pkill.procps
update-alternatives: Linking //usr/bin/pmap to /usr/bin/pmap.procps
update-alternatives: Linking //bin/kill to /bin/kill.procps
update-alternatives: Linking //sbin/sysctl to /sbin/sysctl.procps
update-alternatives: Linking //bin/ps to /bin/ps.procps
update-alternatives: Linking //usr/bin/pgrep to /usr/bin/pgrep.procps
update-alternatives: Linking //usr/bin/pwdx to /usr/bin/pwdx.procps
update-alternatives: Error: cannot register alternative watch to /usr/bin/watch since it is already registered to /bin/watch
Collected errors:
- pkg_get_installed_files: Failed to open //var/lib/opkg/info/perl-module-build.pm.list: No such file or directory.
- pkg_get_installed_files: Failed to open //var/lib/opkg/info/perl-module-load.pm.list: No such file or directory.
- opkg_install_cmd: Cannot install package something-that-doesnt-exist.
- pkg_run_script: package “procps” postinst script returned status 1.
- opkg_configure: procps.postinst returned 1.
Everything seems to work fine, but I get the messages above about procps now whenever I do anything with opkg. Is there anything to be worried about here? Any advice to making opkg happy again?
I have located the following files:
/var/lib/opkg/info/perl-module-build.control
/var/lib/opkg/info/perl-module-build.list
Thanks.
Jerrill